| | Requirements Capturing by the System Architect
abstract
The basis of a good system architecture is the availability and understanding of the requirements.
This presentation shows how a system architect can capture the requirements and how to use these requirements in the context of the product creation process.
The notion of "business key drivers" is introduced and a method is described to link these key drivers to the product specification.
status:
concept
| download statistics: |
Slides: 1553 downloads |
| Paper: 5098 downloads |
History
1.5 June 28, 2010 Gerrit Muller
- textual adaptations
- more consistent use of the terms requirements, product specification and needs
1.4 May 21, 2010 Gerrit Muller
- replaced some lists by figures
- renamed operational requirements in life cycle requirements
1.3 August 28, 2008 Gerrit Muller
- added system as a black box
1.2 April 20, 2005 Gerrit Muller
- added regulations viewpoint
1.1 February 17, 2005 Gerrit Muller
- updated key driver figures
- improved readability of some figures
1.0 May 31 2002 Gerrit Muller
- added abstract
- increased readability of some figures
- modified stakeholder figure
- updated keydriver figure
- modified Motorway management example
0.2 June 22 2001 Gerrit Muller
- annotated the figure with the reference architecture
- added a list of recommendations with respect to the definition of keydrivers
0.1 February 16 2001 Gerrit Muller
0 October 25 1999 Gerrit Muller
- Created, no changelog yet
| figures
|