1 / 12

requirements phase

22 September 2010. requirements phase. Processes (finish up). Fundamental Steps. STEPS Requirements Design Implementation Integration Test Deployment Maintenance. MODELS Waterfall Spiral Iterative DIFFERENCES How often Overhead. Historical Perspective.

skylar
Download Presentation

requirements phase

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. 22 September 2010 requirements phase

  2. Processes (finish up)

  3. Fundamental Steps STEPS • Requirements • Design • Implementation • Integration • Test • Deployment • Maintenance MODELS • Waterfall • Spiral • Iterative DIFFERENCES • How often • Overhead

  4. Historical Perspective • Waterfall: 1970, built on 1950’s stage- wise processes Recognized need for feedback • Iterative (agile): late 70s,modeled on evolutionary model Didn’t work well for large products • Spiral: 1988, risk-based

  5. Unified Process • Variant of Spiral • Identifies that iterations differ • Also known as Rational Unified Process (Rational products)

  6. Requirements

  7. Process

  8. User Requirements - Persona • Microsoft • Persona Power

  9. Persona excerpt (hotel reservation)

  10. Sources of requirements • People • Stakeholders • Who are the stakeholders? • Issues: • Conflicting requirements • Wants vs. needs • Helping the customer articulate the requirements • Use cases • Hardware constraints • Laws of physics and nature • Social responsibility

  11. Social responsibility • Privacy • Security • How it will (can) be used • Does it have the potential for misuse? • Can it be used to harm people?

  12. decision support system for military tactics video game corporate accounting system manufacturing control system enhancement to corporate accounting system flight control system for airliner missile guidance system Sources of Requirements: People vs. Other unconstrained Type of application highly constrained relatively low % of requirements gathered from people relatively high (Brackett, CMU)

More Related