Software specification or requirements engineering is the process of understanding and defining what services are required and identifying the constraints on these services.
Requirements engineering processes ensures your software will meet the user expectations, and ending up with a high quality software.
It’s a critical stage of the software process as errors at this stage will reflect later on the next stages, which definitely will cause you a higher cost.
At the end of this stage, a requirements document that specifies the requirements will be produced and validated with the stockholders.
There are four main activities (or sub-activities) of requirements engineering:
Feasibility study: An estimate is made of whether the identified can be achieved using the current software and hardware technologies, under the current budget, etc. The feasibility study should be cheap and quick; it should inform the decision of whether or not to go ahead with the project.
Requirements elicitation and analysis: This is the process of deriving the system requirements through observation of existing systems, discussions with stakeholders, etc. This may involve the development of one or more system models and prototypes that can help us understanding the system to be specified.
Requirements specification: It’s the activity of writing down the information gathered during the elicitation and analysis activity into a document that defines a set of requirements. Two types of requirements may be included in this document; user and system requirements.
Requirements validation: It’s the process of checking the requirements for realism, consistency and completeness. During this process, our goal is to discover errors in the requirements document. When errors are found, it must be modified to correct these problems.
Requirements management:
Requirement management is the process of analyzing, documenting, tracking, prioritizing and agreeing on the requirement and controlling the communication to relevant stakeholders. This stage takes care of the changing nature of requirements. It should be ensured that the SRS is as modifiable as possible so as to incorporate changes in requirements specified by the end users at later stages too. Being able to modify the software as per requirements in a systematic and controlled manner in an extremely important part of the requirements engineering process.
A requirement Engineering is a process in which various activates such as discovery, analysis and validation of system requirements are done. The spiral model of requirement engineering process is
Requirements engineering processes ensures your software will meet the user expectations, and ending up with a high quality software.
It’s a critical stage of the software process as errors at this stage will reflect later on the next stages, which definitely will cause you a higher cost.
At the end of this stage, a requirements document that specifies the requirements will be produced and validated with the stockholders.
There are four main activities (or sub-activities) of requirements engineering:
Feasibility study: An estimate is made of whether the identified can be achieved using the current software and hardware technologies, under the current budget, etc. The feasibility study should be cheap and quick; it should inform the decision of whether or not to go ahead with the project.
Requirements elicitation and analysis: This is the process of deriving the system requirements through observation of existing systems, discussions with stakeholders, etc. This may involve the development of one or more system models and prototypes that can help us understanding the system to be specified.
Requirements specification: It’s the activity of writing down the information gathered during the elicitation and analysis activity into a document that defines a set of requirements. Two types of requirements may be included in this document; user and system requirements.
Requirements validation: It’s the process of checking the requirements for realism, consistency and completeness. During this process, our goal is to discover errors in the requirements document. When errors are found, it must be modified to correct these problems.
Requirements management:
Requirement management is the process of analyzing, documenting, tracking, prioritizing and agreeing on the requirement and controlling the communication to relevant stakeholders. This stage takes care of the changing nature of requirements. It should be ensured that the SRS is as modifiable as possible so as to incorporate changes in requirements specified by the end users at later stages too. Being able to modify the software as per requirements in a systematic and controlled manner in an extremely important part of the requirements engineering process.
A requirement Engineering is a process in which various activates such as discovery, analysis and validation of system requirements are done. The spiral model of requirement engineering process is
0 comments :
Post a Comment
Note: only a member of this blog may post a comment.