7. Tool support Flashcards
1
Q
Management of requirements tools should support
A
- definition and storage of requirements attributes to identify and collect data about work products and requirements
- Facilitation and documentation of the prioritisation of requirements
- life cycle management, version control, configurations and baselines
- tracking and tracing of requirements as well as defects in the requirements and work products
- change management for requirements
2
Q
Requirements engineering process
A
- measure and report RE process workflow
- information helps to improve the RE process and reduces waste
- measure and report on the product quality
- information helps to find defects and flaws
3
Q
Documentation of knowledge about the requirements
A
- sharing and creation of the common understanding of the requirements
- securing the requirements as a legal obligation
- an overview of an insight into the requirement
4
Q
Different types of tools
A
- management of requirements
- requirements engineering process
- documentation of knowledge about the requirements
- modelling of requirements
- collaboration
6 testing and/or simulation of the requirements
5
Q
Introducing the tools
A
- describe the objectives, context and requirements before selecting and implementing appropriate tools
- tools do not solve organisational or human issues
- can help you to configure the process effectively and efficiently, provide framework based on best practices
NB RE process can be change due to new tool
6
Q
Aspects to consider for tool introduction
A
- life cycle costs
- necessary resources
- avoid risks by running pilot projects
- assessing tools based on definition criteria
- instruct employees on the use of the tool
7
Q
Tool evaluation criteria
A
- project perspective (support project and info required in the project)
- process perspective
- user perspective
- product perspective
- supplier perspective (service reliability of supplier, how is support arranged)
- economic perspective
- architectural perspective (does it fit IT infrastructure)
8
Q
Life cycle tool costs
A
- purchase / licensing costs
- less visible costs: the use of resources in the implementation, operation and maintenance of the tool
9
Q
Test the tool to reduce the risks
A
- apply to a non-critical project/system
- use the tool redundantly alongside an existing project
- apply the tool to a fictional situation/project
- import/copy the requirements of a project that ha already been completed