Requirement Engineering Process
The requirements engineering process includes a feasibility study, requirements
elicitation and analysis, requirements specification and requirements
management
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
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?
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
•
the system‘s operational constraints
May involve end-users, managers, engineers involved in maintenance, domain
experts, trade unions, etc.
•
These are called stakeholders
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 change
