404 - Non-Functional Requirements: Accessibility,...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Non-Functional Requirements: Accessibility, asthetics, Reliability, maintainability, performance, aesthetics. due by next frieday, add a link to a new requirements page from your requirements milestone in your roadmap, document requirements on this new page, document acceptance tests here software requirements answers what is the system supposed to do and who is going to use it what is the system to do who are the system user groups business case tells us why project plan tells us when and who architecture tells us how requirements issues are the most commonly cited for project failure Sprint Lars Cost of avoiding /fixing defects increases as project progresses cheapest in requirements development project phases requirements => architecture => design => code => test => deploy => maintain waterfall/linear process model: follow each phase in its entirety before moving on extreme/agile programming follow each phase for a small segment of the program for a small amount of time and move on to the next iteration
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 04/07/2008 for the course CSC 307 taught by Professor Janzen during the Spring '08 term at Cal Poly.

Page1 / 2

404 - Non-Functional Requirements: Accessibility,...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online