03-Requirements - Requirements analysis What do...

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

View Full Document Right Arrow Icon
1 Requirements analysis z What do stakeholders want from the system? – What should it to do? – What should it look like? Sound like? Be like? z Analysis starts with a project description – Usually written (or otherwise expressed) by major stakeholder z a.k.a. “Client” – might be a customer, another department in the company, management, professor, … z Or project team writes it for an anticipated market z Results in a series of RA artifacts : 2 purposes – Shows the client what they will be getting – Used to kick-off and guide later development activities RA starts in UP Phase I: Inception z Purpose is to explore project feasibility z Target length: only about a week z Identify most use cases and actors – And write 10-20% of use cases in detail – Used to make rough estimate of costs z Most important requirements artifacts: vision, use cases Project descriptions z Client’s view : system is basically a “black box” z Probably vague, repetitive, confused, … – But remember: client thinks it “says it all” z Often has too many details, or misguided focus – e.g., implementation details – too limiting at this stage – e.g., too many “ilities” – distract from the purpose z May contain contradictions or impossible parts – Often just “wish lists” without clear goals z So, always expect to re-express as requirements Doing requirements analysis z Basically: detailing the requirements – But still in language that the user understands z i.e., all artifacts continue to treat the system as a black box – focus on what goes in and what comes out – For CS 50: write a vision (beefed up) and use cases z Study much more than the project description – Interview users, managers, sponsors, experts, … – Learn about current practices, existing systems, business rules (general and specific), memo trails, … – But no need to become a domain expert z Could take years! A “knowledgeable layperson” is sufficient. Vision 1: problem statement z Should answer two fundamental questions: – What problem(s) will the system solve? – How is the system expected to solve the problem(s)?
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/21/2009 for the course CS 50 taught by Professor Staff during the Winter '08 term at UCSB.

Page1 / 4

03-Requirements - Requirements analysis What do...

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