Find out the issues of requirement engineering phase and write about the issues that you

have in the requirement engineering phase and methods use to resolve them
(Requirement Issues and Management)
Article By: Naveed Abdullah

Requirement Engineering
The Requirement Engineering states to the process of developing, reporting and conducting the
maintaining activities. The subfield of the Software Engineering is related with the processing of the
software requirement. The term of Requirement Engineering was coined in the year of 1979 in a TRW
technical report which was first made for the requirement of the system by the developers but the concept
of Requirement Engineering was not in the general use until the year 1990s when the publication was
issued by IEEE Software Society.
Diagrammatic Representation of Requirement Engineering Framework

Analysis of Diagram:
The diagram presents the overall framework structure which is used in the overall processes
and the development of the Software. The software is analyzed according to the requirement
of the of the individual user and the requirements of the overall organization.



People Related to the Requirement Engineering Framework
The people related to the Requirement Engineering Framework are basically End-Users,
Suppliers, and Customers
a- Customer:
The customer is a person, or persons who pay for the product and decide the requirements. In
the context of this recommended practice the customer and the supplier may be members of
the same organization.
b- Supplier:
The person, or persons who develop a product for a customer. In the context of this
practice, the customer and the supplier
c- User:
The person, or persons who operate or interact directly with the product. The user(s) and the
customer(s) are often not the same person(s).

Problems of Requirement Engineering
The Requirement Engineering has Three Dimensions of. The overall output of the requirements
engineering phase is documented in the requirements specification document because it
reflects the mutual understanding of the scope of the problem which is persistent in the
requirement engineering framework, generally the problem has been solved between the client
,the developer and the supplier. The requirements specification serves as a starting point for
the next phase, the design phase.
1- Problems in Requirement Elicitation:
The sole purpose of the Requirements elicitation is about understanding the overall
problem. In the general phase the requirements analyst is not termed as an expert in
the domain being modeled. Through interaction with domain specialists, he has to build
himself a sufficiently rich model of that domain. The problem persists when different
elements of the software requirement have been analyzed.



The Problems of requirements elicitation can be grouped and classified into three
categories .These are problems of scope, problems of understanding, and problems of
volatility.
1- The Categories
a) Problems of scope
The requirements may address too little or too much information.
The boundary of the system is ill-defined
Unnecessary design information may be given

b) Problems of understanding
Problems of understanding within groups as well as between groups such as users and
developers.
Users have incomplete understanding of their needs
Users have poor understanding of Computer capabilities and limitations
Analysts have poor knowledge of problem domain
User and analyst speak different
languages
Ease of omitting obvious information
Conflicting views of different users
Requirements are often vague and Un-testable, e.g., user friendly and Robust

c) Problems of volatility
The changing nature of requirements.
Requirements evolve over time

The Problems of Requirements Specification
One of the most difficult challenges we face in the requirements specification process is making
the requirements detailed enough to be well understood without over constraining the system
and predefining a whole host of things that may be better off.
The Problems of Requirements Validation and Verification
Building the right system right depends on continually confirming that the development is on
track and that the results are correct, as well as being able to deal with change during
development.

Verification is supported by the use of traceability techniques to relate parts of our project to
one another. By using traceability, we can verify
All project elements are accounted for, and
All project elements have a purpose

Solutions to Resolve Problems of Requirement Engineering:
These facts and problems give the researchers a place for discussing and proposing the
requirements elicitation techniques. Some techniques are shown in the following:
Interviewing and questionnaires
Requirements workshop
Brainstorming and idea reduction
Storyboards
Use cases
Role playing
Prototyping

Conclusion:
As we have observed the Requirement Engineering we can say that the architecture is capable
of performing at its optimal level but there will be some problems which will lead to the serious
problem for the users if not treated accordingly.