1 / 13

Software Waterfall Life Cycle

Requirements. Prototype. Design. Construction. Testing. Delivery and Installation. Software Waterfall Life Cycle. Concept Exploration. Operations and Maintenance. V-Model. Spiral Model. Agile Methods. Life Cycle Heuristics. If the requirements are well-defined

astrid
Télécharger la présentation

Software Waterfall 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. Requirements Prototype Design Construction Testing Delivery and Installation Software Waterfall Life Cycle Concept Exploration Operations and Maintenance

  2. V-Model

  3. Spiral Model

  4. Agile Methods

  5. Life Cycle Heuristics • If the requirements are well-defined • use the waterfall model (with prototyping) • If the requirements are very complex and tightly coupled • use a spiral model • If the requirements are uncertain and the project is not large • use an agilemethod, gathering and implementing requirements in increments

  6. Prioritization of Requirements • Essential • Must be satisfied in next release • Desirable • need to be prioritized in light of time • Optional • Can be set aside unless you finish early • In CS 480-481 projects, propose three systems • Minimally acceptable by the faculty adviser • Expected by the team, faculty adviser, and client • Desirable by the client (doable if everything falls into place)

  7. From SWEBOK 2004

  8. Requirements Elicitation • Requirement Sources • High level goals or vision of the software • Domain knowledge • Stakeholders • Operational requirements • Organizational environment • Elicitation Techniques • Interviews, Scenarios (Use Cases), Prototypes, Facilitated Meetings, Observation

  9. Managing Changes in Requirements • Change control process (QA) • Traceability • How does one change affect others? • Version control • How are changes communicated to the team? • How are changes documented? • Status tracking • Pending, approved, rejected, deferred, completed, cancelled

  10. Use Cases Used to capture functional requirements and describe the interactions between various actors and the system • Actors are roles (not individuals) that have a goal for using the system • Actors can be other systems or organizations • Use Cases focus on achieving a user goal • Use cases may have relationships (associations) with each other

  11. Use Case Scenarios • Not UML, no standard format • A written description of the steps involved in an interaction between an actor and the system, always beginning with the primary actor

  12. Written Use Case Scenarios • Use Case Name (use verb-noun) • Participating Actors • Normal Flow of Events (happy path) • Exceptions (error conditions) • Extensions (optional goals) • Entry (pre) Conditions • Exit (post) Conditions • Quality Requirements

More Related