1 / 9

Evolutionary/model (SDLC)

Evolutionary/model (SDLC). By: Anthony George Christian Loregnard. Diagram. Main characteristics: The phases of the software construction are interleaved Feedback from the user is used throughout the entire process The software product is refined through many versions. Characteristics.

glynn
Download Presentation

Evolutionary/model (SDLC)

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. Evolutionary/model (SDLC) By: Anthony George Christian Loregnard

  2. Diagram • Main characteristics: • The phases of the software construction are interleaved • Feedback from the user is used throughout the entire process • The software product is refined through many versions

  3. Characteristics • Main characteristics: • The phases of the software construction are interleaved • Feedback from the user is used throughout the entire process • The software product is refined through many versions Phases Define the basic requirements Create a working prototype Verification of prototype Evaluate and deliberate . Advantages • Deals constantly with changes • Provides quickly an initial version of the system • Involves all development teams

  4. Disadvantages • Quick fixes may be involved • “Invisible” process, not well-supported by documentation • The system’s structure can be corrupted by continuous change Applicable • When requirements are not well understood • When the client and the developer agree on a “rapid prototype” that will be thrown away • Good for small and medium-sized software systems

  5. Phases of Rapid Application Development (RAD) • Requirements planning phase (a workshop utilizing structured discussion of business problems) • User design phase – users to participate in the nontechnical design of the system • Construction phase – productivity tools, such as code generators, screen generators. • Cutover phase -- installation of the system, user acceptance testing and user training

  6. RAD Diagram Requirements planning phase User design phase Prototyping Construction phase Cutover phase

  7. Strenghts • Reduced cycle time and improved productivity with fewer people means lower costs • Customer involved throughout the complete cycle minimizes risk of not achieving customer satisfaction and business needs • Focus moves from documentation to code

  8. Weaknesses • Accelerated development processmust give quick responsesto the user • Requires a system that can be modularized • Developers and customers must be committed to rapid-fire activitiesin an abbreviated time frame. • May compromises functionality and performance in exchange for faster development and better application maintenance

  9. Applicable • When requirements are not fully understood. • User involved throughout the life cycle • Functionality delivered in increments • High performance not required • System can be modularized Sources • Ian Sommerville, Software Engineering, 8th Ed., Addison-Wesley, 2006 • John Petlicki of DePaul University, USA

More Related