{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

Ch15 - Chapter15 Information why...

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

View Full Document Right Arrow Icon
01/17/12   1 Chapter 15 Organizing Requirements  Information    why?  Organizing req.s for complex systems  Organizing req.s for family of systems
Background image of page 1

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

View Full Document Right Arrow Icon
01/17/12 2 Why ..? Communication problems  demand that requirements  should be  captured  and  documented  in a way that they  can be  reviewed, approved, agreed on and referred to  easily. Traditionally this is done by  requirements specifications  which are  large documents  built to capture and  communicate  the external behaviour  of the system. 
Background image of page 2
01/17/12 3 Why ..? Requirements can  rarely  be defined  in a single document   or in a single use-case model  because  the system  may be   very complex be  a member of a family of related products.   be  a subsystem of a larger system  and may satisfy  only a subset of all the requirements identified. contain  marketing and business goals  needed to be  separated from the detailed product requirements.
Background image of page 3

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

View Full Document Right Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}