Presentation On Requirements Engineering Processes
Download
Requirements Engineering Processes Presentation Transcript:
1.Requirements Engineering Processes
2.Objectives
To describe the principal requirements engineering activities and their relationships
To introduce techniques for requirements elicitation and analysis
To describe requirements validation and the role of requirements reviews
To discuss the role of requirements management in support of other requirements engineering processes
3.Topics covered
Feasibility studies
Requirements elicitation and analysis
Requirements validation
Requirements management
4.Requirements engineering processes
The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.
However, there are a number of generic activities common to all processes
Requirements elicitation;
Requirements analysis;
Requirements validation;
5.The requirements engineering process
6.Requirements engineering
7.Feasibility studies
A feasibility study decides whether or not the proposed system is worthwhile.
A short focused study that checks
If the system contributes to organisational objectives;
If the system can be engineered using current technology and within budget;
If the system can be integrated with other systems that are used.
8.Feasibility study implementation
Based on information assessment (what is required), information collection and report writing.
Questions for people in the organisation
What if the system wasn’t implemented?
What are current process problems?
How will the proposed system help?
What will be the integration problems?
Is new technology needed? What skills?
What facilities must be supported by the proposed system?
9.Elicitation and analysis
Sometimes called requirements elicitation or requirements discovery.
Involves technical staff working with customers to find out about the application domain, the services that the system should provide and the system’s operational constraints.
May involve end-users, managers, engineers involved in maintenance, domain experts, trade unions, etc. These are called stakeholders.
10.Problems of requirements analysis
Stakeholders don’t know what they really want.
Stakeholders express requirements in their own terms.
Different stakeholders may have conflicting requirements.
Organisational and political factors may influence the system requirements.
The requirements change during the analysis process. New stakeholders may emerge and the business environment
11.The requirements spiral
12.Process activities
Requirements discovery
Interacting with stakeholders to discover their requirements. Domain requirements are also discovered at this stage.
Requirements classification and organisation
Groups related requirements and organises them into coherent clusters.
Prioritisation and negotiation
Prioritising requirements and resolving requirements conflicts.
Requirements documentation
Requirements are documented and input into the next round of the spiral.
13.Requirements discovery
The process of gathering information about the proposed and existing systems and distilling the user and system requirements from this information.
Sources of information include documentation, system stakeholders and the specifications of similar systems.
14.ATM stakeholders
Bank customers
Representatives of other banks
Bank managers
Counter staff
Database administrators
Security managers
Marketing department
Hardware and software maintenance engineers
Banking regulators
15.Viewpoints
Viewpoints are a way of structuring the requirements to represent the perspectives of different stakeholders. Stakeholders may be classified under different viewpoints.
This multi-perspective analysis is important as there is no single correct way to analyse system requirements.
Download
Requirements Engineering Processes Presentation Transcript:
1.Requirements Engineering Processes
2.Objectives
To describe the principal requirements engineering activities and their relationships
To introduce techniques for requirements elicitation and analysis
To describe requirements validation and the role of requirements reviews
To discuss the role of requirements management in support of other requirements engineering processes
3.Topics covered
Feasibility studies
Requirements elicitation and analysis
Requirements validation
Requirements management
4.Requirements engineering processes
The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.
However, there are a number of generic activities common to all processes
Requirements elicitation;
Requirements analysis;
Requirements validation;
5.The requirements engineering process
6.Requirements engineering
7.Feasibility studies
A feasibility study decides whether or not the proposed system is worthwhile.
A short focused study that checks
If the system contributes to organisational objectives;
If the system can be engineered using current technology and within budget;
If the system can be integrated with other systems that are used.
8.Feasibility study implementation
Based on information assessment (what is required), information collection and report writing.
Questions for people in the organisation
What if the system wasn’t implemented?
What are current process problems?
How will the proposed system help?
What will be the integration problems?
Is new technology needed? What skills?
What facilities must be supported by the proposed system?
9.Elicitation and analysis
Sometimes called requirements elicitation or requirements discovery.
Involves technical staff working with customers to find out about the application domain, the services that the system should provide and the system’s operational constraints.
May involve end-users, managers, engineers involved in maintenance, domain experts, trade unions, etc. These are called stakeholders.
10.Problems of requirements analysis
Stakeholders don’t know what they really want.
Stakeholders express requirements in their own terms.
Different stakeholders may have conflicting requirements.
Organisational and political factors may influence the system requirements.
The requirements change during the analysis process. New stakeholders may emerge and the business environment
11.The requirements spiral
12.Process activities
Requirements discovery
Interacting with stakeholders to discover their requirements. Domain requirements are also discovered at this stage.
Requirements classification and organisation
Groups related requirements and organises them into coherent clusters.
Prioritisation and negotiation
Prioritising requirements and resolving requirements conflicts.
Requirements documentation
Requirements are documented and input into the next round of the spiral.
13.Requirements discovery
The process of gathering information about the proposed and existing systems and distilling the user and system requirements from this information.
Sources of information include documentation, system stakeholders and the specifications of similar systems.
14.ATM stakeholders
Bank customers
Representatives of other banks
Bank managers
Counter staff
Database administrators
Security managers
Marketing department
Hardware and software maintenance engineers
Banking regulators
15.Viewpoints
Viewpoints are a way of structuring the requirements to represent the perspectives of different stakeholders. Stakeholders may be classified under different viewpoints.
This multi-perspective analysis is important as there is no single correct way to analyse system requirements.
No comments:
Post a Comment