System Engineering offers two distinct requirements in the engineering process, stakeholder requirements and technical requirements. They are both positioned at the beginning of the solution’s architectural design process when a project is started. These two processes consist of ‘the systematic process of developing requirements through an iterative process of analyzing a problem, documenting the resulting observations, and checking the accuracy of the understanding gained’.
Requirement Engineering guides the step from an initial description, often unclear or even contradictory, which is called stakeholder requirements, to a more formal and more contractual specification of these stakeholder requirements, called technical requirements.
Stakeholder requirements engineering is the process of transforming a hazy idea into a precise specification of the needs that support the system specification and interfaces with the environment. A need represents the initial expression of the project owner. It expresses and describes a situation, a wish, a goal or a constraint about the system to be designed. Stakeholder requirements are usually informally defined, in the project owner language, in order to simplify communication with these stakeholders.
On the other hand, a technical requirement is defined as a statement that describes a function, aptitude or characteristic that the system must satisfy.
Technical requirements express stakeholder requirements. They represent the expected properties of the system which will constrain the design of the solution so they must be specified. Project owner and project manager collaboration is needed to analyze needs and to generate technical requirements.
There are two types of technical requirements (ISO15288 2008):
-Functional requirements refer to the features and services that the system must provide.
-Non-functional requirements constrain and specify in terms of performance, security, reliability, ergonomics, maintainability level, portability and others. They may also concern certain aspects related to the management of the development projects such as the cost and the deadlines for completion.
The following steps describe the process of Requirement Engineering:
Identification of stakeholders.
It is important to identify any person, group of people or organization that can influence or be affected by the system or its development, directly or indirectly.
Understanding of the context and expression of Stakeholder requirements.
It is here that the problem is described. After the identification of the stakeholders, it is necessary to involve them to describe, share and focus on:
• The objectives of the future system
• The context in which the system will be used.
• The non-functional, functional stakeholder requirements and constraints which the system must respond to and the information the system must manage.
Analysis, verification and negotiation.
The Requirement Engineering process involves many of the stakeholders. Therefore, the needs they express can be contradictory, even conflicting. These conflicts must be detected and resolved. A step of explanation, verification, justification and negotiation is required to reach consensus.
Transition from stakeholder requirements to technical requirements, verification and documentation of technical requirements.
It must be systematic and rigorous. During this step, the Project owner, in collaboration with the Project manager, decides what can be kept or updated in the current system Engineering, what should be planned to form the expected system and what will be developed. These choices lead to the development of the requirements repository that is written, documented and structured
Validation of technical requirements.
It is here a question of validating the technical requirements based on stakeholder requirements. This process is not sequential. Back tracking and iterations occur, for example, when the requirements check involves corrections.
It is also important to keep track of ‘who said what’ and what changes have been made to justify the requirements repository. This repository is then used as input for the next step of the project.
In short, requirement engineering is the basis of any system engineering project, because it allows the project manager and the project owner to agree on the specifications needed to solve the initial problem.
and now on to the next subject. [ https://mkxprojet.wixsite.com/website/post/definition-of-a-requirement ]
Comentários