본 포스트는 개인 스터디 용으로 작성된 Ian Sommerville의 Software Engineering, 8/E의 요약본입니다.
Chapter 7.
1. Deeply depended on the application domain, people, organisation developing the requirements.
2. Generic activies
- Requirements elecitation
- Requirements analysis
- Requirements validation
- Requirements management
3. Requirements Engineering Process Step ( '=>' means 'generate')
1) Feasibility Study (=> Feasibility Report) : decides whether proposed system is worthwhile or not(judge through objective, budget, integrationability...)
2) Requirements elicitation and analysis(=> System Models) : find out application domain, the services to provide, constraints. Performs with stakeholders.
3) Requirements specification(=> user and system requirements)
4) Requirements validation(=> Requirements document)
4. Viewpoints : represent the perspectives of different stakeholders
- interactor(direct?) viewpoints
- indirect viewpoints
- domain viewpoints
5. scenario : real-life examples of how a system can be used. UML is used, frequently.
- Use Case
- Sequence diagram
6. Social and Organisational factors
- influence on the system requirements, all viewpoints.
- currently no systematic way to tackle their analysis.
- via ethnography, they can be found more easily.
7. Requirements Validation
- Requirements error costs are high. Fixing requirements error may 100 times lower than fixing implementation error.
- Key : validity, consistency, completeness, realism, verifiability.
- technique : review, prototyping, test case generation
8. Requirements management
- manages requirements changing during requirement engineering process and system development
- planning on requirements engineering processes
1) Requirement identification
2) A change management process
3) traceability policies
4) CASE tool support
- Change management Step
identify problem -> problem analysis & change specification -> change analysis & costing -> change implementation -> revised requirements
댓글을 달아 주세요