Requirements engineering process in software engineering:
Requirements engineering:
Requirements The goal of the engineering process is to document and maintain the requirements of a system. The overall process includes four high-level engineering sub-processes. These are about evaluating whether
The system is useful for business (feasibility study); discovery requirements (optional and analysis); converting these requirements into some standard format (specification); and checking that the requirements actually define the system that
The customer wants to clarify the relationship between these activities. It also reflects the documentation required at each stage of the engineering process. Details and documents are included in in some previous articles. reasons
Other needs focus on engineering activities. The activities shown in the figure are related to discovery, documentation and needs testing. In virtually all systems, requirements
Change. The people involved get a better understanding of what they want
To do this changes the organization that buys the software / system. Have been modified
In the system hardware, software and organizational environment. Process
Managing these changing:
needs is called need management
needs is called need management
Included in the last part of this article.
I offer an alternative perspective on the requirements in the engineering process. Presents this process as a three-step activity where activities.
Are organized as a repetitive process around a spiral. The amount of time and effort
Dedication to each activity in a movement depends on the stage of the overall process
And the way the system is being developed. Early in the process, there will be a lot of effort
Spent on understanding high-level business and passive requirements
User needs After this process, in the outer circles of the spiral, try harder
System requirements will be dedicated to engineering and system modeling.
This spiral model adjusts the development leaches approach to meet different needs with different features. Number of repetitions around
 |
| Requirements Engineering: |
The spiral can be different, so the spiral can be pulled out after some or all of the user's needs
Posted. If the prototyping activity appears under verification requirements. The development of this model has also been accelerated, as discussed in another article
It allows the implementation of requirements and systems to develop simultaneously.
Some people see requirements as the process of implementing engineering
Method of structural analysis such as object-based analysis (Lerman, 2002). This
This includes analyzing the system and developing a set of graphical system models
As models of usage cases, which then serve as system details. Model set
Describes the behavior of the system and describes it with additional information, for example, its required performance or reliability.
Although serious methods play an important role in the engineering process of need, there is much more to engineering needs than just covering these methods. Explaining the requirements, in particular, is a human-centered activity and people dislike it
Obstacles imposed by strict system models. I focus here on the general perspectives on requirements engineering and cover structural methods and system models in further articles on information technology.