Requirements Engineering Processes | Software Engineering | BSc.CSIT 6th Sem

Download our Android App from Google Play Store and start reading Reference Notes Offline.

requirements engineeringRequirements Engineering Processes,
Software Engineering Notes | Sixth Semester,
BSc.CSIT | Tribhuvan University (TU)

Requirements Engineering Processes
Requirements engineering process is the system of documenting requirements through an interactive co-operative process of analyzing the problems, documenting the resulting observations in a variety of representation format, and checking the accuracy of the understanding gained. Requirement Engineering is the systematic use of proven principles, techniques, tools and languages for the cost effective analysis, documentation and ongoing evolution of user needs and the specification of the external behavior of the system in order to satisfy these needs.

An input to this activity of requirements engineering are requirements which are informal and fuzzy (unclear) and output is clear, well defined, complete and consistent. The requirements engineering activity is the most crucial and most important in the software development life cycle because the errors introduced at this stage are the most expensive errors requiring lot of rework if detected late in software life cycle.

The processes used for Requirement Engineering vary widely depending on the application domain, the people involved and the organization developing the requirements. However, there are a number of generic activities common to all processes and they are as follows;Requirements Engineering Process

  • Feasibility study: An estimate is made of whether the identified user needs may be satisfied using current software and hardware technologies. The study considers whether the proposed system will be cost-effective from a business point of view and if it can be developed within existing budgetary constraints. A feasibility study should be relatively cheap and quick. The result should inform the decision of whether or not to go ahead with a more detailed analysis.
  • Requirements elicitation and analysis: This is the process of deriving the system requirements through observation of existing systems, discussions with potential users and procurers, task analysis, and so on. This may involve the development of one or more system models and prototypes. These help you understand the system to be specified.
  • Requirements specification: Requirements specification is the activity of translating the information gathered during the analysis activity into a document that defines a set of requirements. Two types of requirements may be included in this document. User requirements are abstract statements of the system requirements for the customer and end-user of the system; system requirements are a more detailed description of the functionality to be provided.
  • Requirements validation: This activity checks the requirements for realism, consistency, and completeness. During this process, errors in the requirements document are inevitably discovered. It must then be modified to correct these problems. Of course, the activities in the requirements process are not simply carried out in a strict sequence. Requirements analysis continues during definition and specification and new requirements come to light throughout the process. Therefore, the activities of analysis, definition, and specification are interleaved. In agile methods, such as extreme programming, requirements are developed incrementally according to user priorities and the elicitation of requirements comes from users who are part of the development team.
(Visited 183 times, 3 visits today)

Posted By : Digvijay | Comment RSS | Category : Sixth Semester
Tag :

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

Wordpress DMCA
Community | Toolbar | Android App | Founder/Developer : Hari Prasad Chaudhary | CSIT Portal Manager : Digvijay Chaudhary