Scribd
Upload
11 views

Practical 3

1. The document discusses the requirement engineering model which defines, documents, and maintains requirements in engineering design. It helps software engineers better understand the problem and customer needs. 2. The key tasks in requirement engineering are inception to establish problem understanding, elicitation to obtain requirements from stakeholders, elaboration to create an analysis model, negotiation to agree on a realistic system, specification to describe requirements, and validation to review for errors. 3. The document provides an example requirement engineering model for a university management system and describes the procedures for inception, elicitation, negotiation, specification, and validation.

Uploaded by

geet.more15
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
11 views

Practical 3

1. The document discusses the requirement engineering model which defines, documents, and maintains requirements in engineering design. It helps software engineers better understand the problem and customer needs. 2. The key tasks in requirement engineering are inception to establish problem understanding, elicitation to obtain requirements from stakeholders, elaboration to create an analysis model, negotiation to agree on a realistic system, specification to describe requirements, and validation to review for errors. 3. The document provides an example requirement engineering model for a university management system and describes the procedures for inception, elicitation, negotiation, specification, and validation.

Uploaded by

geet.more15
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Practical 3

Title: Gather application specific requirements to assimilate it into requirement Engineering (RE) model.

Theory:

Requirement Engineering model:


It refers to the process of defining, documenting and maintaining requirements in engineering design
process. It is a common role in system engineering and software engineering.

Requirement engineering helps software engineers to better understand the problem they will have to solve.
It encompasses the set of task that will lead to understanding of what the business impact of software will
be,what the customer wants and how end user will interact with software. Designing and building computer
software is challenging, creative and just plain fun. In fact building software is so compelling that many
software developers want to jump right in before they have a clear understanding of what is needed. For this
the requirement Engineering model is present.

Tasks in requirement engineering:


1 Inception: Establish a basic understanding of problem and nature of solution.
2. Elicitation: drawout requirements from stakeholders.
3. Elaboration: Create an analysis model that represents information, functional behavioral aspects of
requirements.
4. Negotiation: Agree on a deliverable system that is realistic for developer and customer.
5. Specification: Describe the requirements formally or informally.
6. Validation: Review the requirement specification for errors, ambiguity, omission and conflicts.
7. Requirement management: Manage changing requirements

Procedure:

The RE model (requirement engineering model) for our project is ' University management'.

1) Inception:
As scheduling and reserving in a large organisation such as University is difficult. Event schedules of
different types such as lectures,Lunches, meetings, cannot record the things on paper. So the database of
each with proper and maintained security should be created.

2) Elicitation: drawout requirements from stakeholders.


In the elicitation process various problems can come across like-
i) problem of scope- first of all the format of software is ill defined.
ii) problem of understanding: Requirement of the customer was not sure that what actually is needed.
iii) problem of volatility: Requirement of the customer changes.
Get answers to above questions to elaborate requirements.

3)Negotiation:
Agree on deliverable system that is realistic for developers and customers, software project and team
stakeholders, the prior availability and cost of each requirement so identifying the stakeholders who will be
involved in the negotiation is a very important process. Determine each of stakeholder's win condition(i.e.
win conditions are not always obvious)and encourage the stakeholder and team towards the set of
requirements that leads to win

4)Specification:
It is a procedure where final work procedure is produced by the requirement engineer. It can be presented by
any one of the following-
A written document
A set of models
A formal collection of user scenarios
A prototype

5) Validation:
In this process, the specification of our software requirement gets tested in a manner that is not
ambiguous(consistent, error-free etc.)
The quality of the software gets tested in this phase. The primary requirement validation mechanism is the
formal technical review. This process contains software engineer, customers, users and other stakeholders to
examine the specifications, looking for errors in content or interpretation area where clarification may be
required, missing information, inconsistencies and conflicting/ unrealistic requirements.

Conclusion:
Thus we have studied different tasks involved in Requirement Engineering.

You might also like