Requirement Engineering: Process, Methods, and Guidelines Analysis

This report provides a comprehensive overview of requirement engineering, detailing its process, importance, and various methods. It explores the core activities of requirement engineering, including elicitation, analysis and negotiation, specification, verification and validation, and management. The report also examines different methods, approaches, and techniques used to perform and support the requirement engineering process. It highlights the significance of requirement engineering in product development, emphasizing its role in faster product construction, customer satisfaction, defect reduction, and efficient software development. Furthermore, the report illustrates the relationships between different elements of requirement engineering through a case study of AESSEAL company, and it offers practical guidelines for an effective requirement engineering process.

REQUIREMENT
ENGINEERING

Table of Contents
INTRODUCTION...........................................................................................................................3
MAIN BODY...................................................................................................................................3
1. Requirement engineering, its process and importance............................................................3
2. Relation and explanation of requirements elicitation, requirements analysis and
negotiation, requirements specification, requirements verification and validation, and
requirements management activities...........................................................................................6
3. Different methods, approaches, and techniques for performing and supporting the
Requirements Engineering process.............................................................................................7
4. Recommended guidelines and concepts for practical Requirements Engineering process.. . .9
CONCLUSION................................................................................................................................9
REFERENCES..............................................................................................................................10

INTRODUCTION
The requirement engineering can be defined as a process which is related to the defining,
documenting and managing the requirements in a systematic manner (Agarwal and Goel, 2014).
Eventually, in other words this is associated with the collecting and analysing the information
about services offered by system. It includes mainly two types of activities which are as follows:
requirement elicitation and specification. Herein, the project report requirement engineering, its
process and its importance is mentioned for development of the projects. As well as relation of
requirement elicitation, analysis, specification with the management activities is described.
Along with different type of methods and techniques of requirement engineering process is also
included in the project report.
MAIN BODY
1. Requirement engineering, its process and importance.
The requirement engineering is a kind of process that is related to the analysing the
required resources in an organisation (,Mauborgne, Deniaud, Levrat, Bonjour, Micaëlli and
Loise, 2016). Basically, with the help of this, companies can define about the need of resources
in further operations. As well as it plays an important role in the engineering designing process.
This is based on mainly two activities which are elicitation and specification.
Herein, below process of requirement engineering is mentioned below:
The process of requirement engineering is divided into four steps which are as follows:
Requirement elicitation
Requirement specification
Requirement verification and validation
Requirement management
 Requirement elicitation- This is the first step of the requirement engineering. In this
different types of ways are applied to get information about the project's requirement.
Under different kind of knowledge includes customers, manual of business and various
stakeholders of any kind of project. In the requirement elicitation some type of techniques
are included like interviews, brainstorming, Delphi method etc.

 Requirement specification- This activity is associated with the making software
requirement model (Chung, Nixon and Mylopoulos, 2012). These models includes like
ER diagram, data flow diagram etc. Due to this, functional and non functional needs can
be specified. For this step of engineering requirement more knowledge about issues can
be required. Requirement verification and validation- Herein, below the verification and validation is
mentioned below:
Verification- It is related to the group of tasks and activities which ensures that used software is
accurately applied to a particular operation.
Validation- It is related to the various group of tasks which ensures that software is able to fulfil
the requirement of customers.
 Requirement management- The requirement management can be defined as a kind of
process that is related to the evaluating, documenting, accepting on the requirement and
managing the communication with different stakeholders. Main purpose of this stage is to
focusing on the flexible nature of requirements. So overall, this step is related to the
management of the requirement in the soft wars.
So this is the process of requirement engineering which is mentioned above with the help of four
systematic steps.
Importance of requirement engineering for product development project- The requirement
engineering plays an important role in the product development projects which is mentioned
below: Faster product construction- Due to the requirement engineering in the product
development project, companies can produce the products in less time (Garg, Agarwal
and Khan, 2015). This is why because it provides needed resources timely. Higher customer and team member satisfaction- The requirement engineering is also
beneficial in the satisfying the customers in an effective manner. This is why because it
will provide products on time to the customers as per the requirement of the resources.
Apart from it, it leads to the satisfaction of the team member of the product develop
project.

 Fewer requirement defects- Additionally, the requirement engineering is useful for
removing the requirement defects effectively. Due to this, there can be a less possibility
of the defects in the resource requirement. Reduce rework- The requirement engineering is useful in reduce the rework. This is why
because it manage all the resources in a systematic manner so that cost effective
production can be done. It is one of the key benefit of the requirement engineering
because each company wants to complete their production in less time. Beneficial in effective product development software- One of the key advantage of the
requirement engineering is that it is helpful in preparing the effective product
development plan. Due to this, users may implement a kind of software for developing
any new product which may provide detailed information about need of resources in
further. Minimise software errors in early stage of the software development- Another importance
of the requirement engineering process is that it reduce the errors from the software as
much as possible. So basically, in the aspect of product development project this is
beneficial in removing the errors as much as possible.
 Helpful in providing the information for the required resources- In the aspect of product
development projects, the requirement engineering also help in the giving detailed
information about the resource requirement. Due to this users can identify what types of
resources required as well as can aware about quantity of needed resources. Herein, it is
important to know that effectiveness of requirement engineering depends on the
developed software about the resource requirement. Additionally, another importance of
the requirement engineering is that it reduce the wastage of the resource as much as
possible which results in cost saving.
So these are the importance of the requirement engineering in the context of the product
development projects.

2. Relation and explanation of requirements elicitation, requirements analysis and negotiation,
requirements specification, requirements verification and validation, and requirements
management activities.
Different kind of elements of the requirement engineering are integrated with each other.
To understand in detail about it, AESSEAL company is selected which is located in the UK. The
company is operated in the manufacturing of pumps and rotating equipments. Herein, below the
relation and elaboration of these elements is mentioned:
 Requirement elicitation- This is related to the findings, researching the requirement of
users, customers and different kind of stakeholders (Preston, 2016). The requirement
elicitation is also known by the “requirement gathering”. Such as in the AESSEAL
company, they finds the requirement of their different kind of stakeholders and
customers. So that they can make their plans accordingly.
 Requirement analysis- The requirement analysis is associated with the a process which
includes those activities that are related to the analysing the need and conditions for any
new product. Eventually, the success of any project depends on the requirement analysis.
As well as it is necessary that requirement must be documented, measurable and testable
to find out business needs. Such as in the above respected company the requirement
analysis is linked with their operations. The reason behind this is that on the basis of it
they can manage their resources accordingly.
 Requirement negotiation- The requirement negotiation can be defined as a kind of
process which is related to the identifying the issues and overcoming from the issues.
Eventually, this is done with the help of systematic conflict management. Such as in the
AESSEAL architecture company, they removes the issues and conflicts with the use of
requirement negotiation. Basically, it is necessary to apply because there can be different
kind of issues in the process of manufacturing which can be resolved by this.
 Requirement specification- The requirement specification can be defined as a description
of software which is prepared with the help of functional and non functional
requirements. In other words it specify the the required resources in a systematic manner.
Such as in the above respected company, this can be beneficial for them in deciding the
needed resources in an effective manner so that their activities can be arranged as per
their requirement.

 Requirement verification- It is related to the providing the rules of verifying the data. In
the context of product development projects, the requirement verification is very crucial
because it provides a systematic way to find out about verifying the need of resources.
Such as in the above respected company, they may apply this for verifying about
whether there is any need of resources or not.
 Requirement validation- The requirement validation can be defined as a process of
confirming about the requirement. This is being applied after the requirement
verification. Such as in the AESSEAL architecture company, they can confirm about the
need of resources. Eventually, in the absence of it, this can be difficult to them to
deciding whether the need resource as per the requirement or not.
 Requirement management activity- The requirement management activity is a kind of
process that consists different kind of elements such as documenting, analysing, tracking
and accepting the changes (Xu and Li, 2012). It is being done as per the requirement of
different kind of stakeholders. Such as in the above mentioned architecture company,
they can use this as per their different kind of stakeholders including internal and
external stakeholders.
So this is all about the requirement engineering's elements relationship with different kind of
operations of the organisations. Such as in the AESSEAL architecture company their all
activities are covered as per the product development plan which is linked with the requirement
engineering.
3. Different methods, approaches, and techniques for performing and supporting the
Requirements Engineering process.
The requirement engineering process is based on different types of methods, approaches
and techniques. Some of them are mentioned below:
Methods for requirement engineering: There are different kind of methods of the requirement
engineering which are mentioned below-
 Context level method- The context level models are being used for the purpose of
defining the operational context of any kind of system. Eventually, the main purpose of
these models is to defining about how well applications of I.T. (Information technology)
is applied in the context of any kind of organisation. This method is also known by the
enterprise architecture model.

 Detailed level method- This is a kind of method which is related to the defining the each
step of the process in a detailed manner so that resources can be determined easily
(Sharma and Kushwaha, 2012). As well as in this method, all the steps of the product
development project is analysed and accordingly the resources are chosen. For companies
which are operating in the manufacturing sector, this method plays an important role.
This is why because through this method requirement engineering, consists various kind
of strategies which can be beneficial in manufacturing the products in less time.
Approaches of requirement engineering- The requirement engineering includes some
approaches which are mentioned below:
 Structured oriented approach- It is a kind of approach of the requirement engineering that
is related to the focusing on the process and accordingly manage the data required for the
process (Yaseen, Baseer and Sherin, 2015). Eventually, this approach focuses is based on
the top down approach. Such as in the product development software this approach is
very beneficial because in firstly identify the process so that it can be determine about
what type of resources will be required. Herein, below some features of this approach are
mentioned below such as:
-It is also known by Modular
-It can solve only moderate complex programs.
-This approach consists less flexibility.
-It majorly emphasis on the process.
-As well as this approach is less secure because there is no option of hiding the data.
 Object-Oriented approach- The object-oriented approach is a kind of approach of the
requirement engineering that is related to the focusing on the data (Macaulay, 2012). This
approach is different from the above mentioned approach because it is based on the
bottom up approach. In the aspect of product development project, this approach can be
suitable because of below mentioned features:
-This approach provides more flexibility and abstraction in compare to other approaches.
-As well as it provides feature of more re-usability.
-This approach can resolve the complex issues regarding to program.
-It provides more security, this is why because it consists the feature of data hiding feature (Amel
and Amin, 2016).

So these are methods and approaches of the recruitment engineering which are being mentioned
above. All these methods and approaches have their own role in the context of effective
management of the requirement of resources.
4. Recommended guidelines and concepts for practical Requirements Engineering process.
The requirement engineering process plays an important role for managing the
requirement of different kind of resources. By implementation of this, companies can identify
about what type of resources are needed along with quantity of resources. So it can be
recommended to the companies who are applying the requirement engineering software that they
should try to minimise the errors during the initial stage. As well as companies should determine
all the process of manufacturing and can determine about the needed resources. Herein, the
aspect of above mentioned company AESSEAL architecture company they are needed to apply
this software only if it covers all the aspect of their manufacturing process.
On the other hand, if companies want to apply in practical to the requirement engineering
process then they should implement this only if they have enough potential to operate it.
CONCLUSION
As per the above discussion it is concluded that Engineering is a essential for scientific
knowledge as well as mathematics. It is experimented to build up different ways which provides
advantage for mankind and important for society. It is considering as a process which is
categorised into four steps such as Requirement elicitation, Requirement specification,
Requirement verification and validation and Requirement management. Engineering important
for product development because it can help to increase productivity as well as develop product
as per the customer. It is play significant role for various activities that are related top process
and software. To continue of this process need of several types of methods, concepts and
techniques in order to develop product in effective manner. For every type of business
engineering process is important and help to understand production activities.

REFERENCES
Books and journals:
Agarwal, M. and Goel, S., 2014, May. Expert system and it's requirement engineering process.
In International Conference on Recent Advances and Innovations in Engineering
(ICRAIE-2014). (pp. 1-4). IEEE.
Mauborgne, P., Deniaud, S., Levrat, E., Bonjour, E., Micaëlli, J.P. and Loise, D., 2016.
Operational and system hazard analysis in a safe systems requirement engineering
process–application to automotive industry. Safety science. 87. pp.256-268.
Chung, L., Nixon, B. A., Yu, E. and Mylopoulos, J., 2012. Non-functional requirements in
software engineering (Vol. 5). Springer Science & Business Media.
Garg, N., Agarwal, P. and Khan, S., 2015, March. Recent advancements in requirement
elicitation and prioritization techniques. In 2015 International Conference on Advances
in Computer Engineering and Applications (pp. 237-240). IEEE.
Preston, C .J., 2016. Climate engineering and the cessation requirement: the ethics of a life-
cycle. Environmental Values. 25(1). pp.91-107.
Sutcliffe, A., 2012. User-centred requirements engineering. Springer Science & Business Media.
Xu, J. and Li, Z., 2012. A review on ecological engineering based engineering
management. Omega. 40(3). pp.368-378.
Sharma, A. and Kushwaha, D .S., 2012. Applying requirement based complexity for the
estimation of software development and testing effort. ACM SIGSOFT Software
Engineering Notes. 37(1). pp.1-11.
Yaseen, M., Baseer, S. and Sherin, S., 2015, December. Critical challenges for requirement
implementation in context of global software development: A systematic literature
review. In 2015 International Conference on Open Source Systems & Technologies
(ICOSST) (pp. 120-125). IEEE.
Macaulay, L.A., 2012. Requirements engineering. Springer Science & Business Media.
Amel, B. and Amin, B., 2016, September. A multi-level interaction dealing approach with
aspects in requirement engineering phase. In 2016 International Conference on
Engineering & MIS (ICEMIS). (pp. 1-6). IEEE.