1 / 7

System Development Life Cycle

A. J. System Development Life Cycle. Process of creating and altering systems or software by using methodologies or models to develop the systems in a logical ordered fashion. A. J. A. J. Waterfall Model. With feedback. Requirements. Design. Implementation. Testing. Installation.

montana-serrano
Download Presentation

System Development Life Cycle

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A J System Development Life Cycle Process of creating and altering systems or software by using methodologies or models to develop the systems in a logical ordered fashion

  2. A J

  3. A J Waterfall Model With feedback Requirements Design Implementation Testing Installation Maintenance

  4. A J Stages broken down Requirements • Finding out what the client is after Design • Designing the system (garden) Implementation • Gathering of all sections of the system (units) to be integrated in the next stage, and is tested for its functionality (Unit Testing) Testing (Integration) • All integrated together and tested for faults Installation • Deployed to customer environment (on site) Maintenance • Fix issues after the site is live, done to deliver changes to the client requirements or site

  5. A J Advantages • Simple and Easy to understand and use • Easy to manage due to rigidity • Phases are completed one at a time • Better for smaller projects where requirements are clearly defined

  6. A J Disadvantages • It is difficult to go back to amend it after the testing stage if the Requirement stage isn’t well thought out • It is late in the model before working software is created • Not good for complex projects due to the rigidity, most other methods are better suited • Its difficult to measure progress within the stages • With integration done at the end it is difficult to identify technological or business bottleneck stages.

  7. A J Conclusion • In conclusion Waterfall Model was a good starting point for software development, but now systems are often needed to be created rapidly with options for continuous improvement and change, and so other models are more suited to the modern software development models such as Agile, RAD or XP

More Related