this is my first slide for public.

1. Welcome to
My
Presentation

2. Requirements
Engineering
Presented by:
Md.Mahmud.
Id:14234202036
Batch:34th
mahmudahmedsumon@gmail.com
Presented to:
Husne Farah (Juthi)
Lecturer, PUB
Dept:CSE
2

3. OVERVIEW
 What is RE ?
 Task and Participation.
 Understanding Requirements.
 Inception (Beginning).
 Elicitation: (Extraction).
 Elaboration (explanation).
 Negotiation (Cooperation).
 Specifications.
 Validation.
 Requirements Management.
3

4. What is RE ?
 Requirements engineering (RE) refers to the process of defining, documenting
and maintaining requirements in the engineering design process. It is a common
role in system engineering and software engineering.
 Requirements engineering is the process of conforming engineering designs to a
set of core software requirements. This is critically important for creating accurate
results in software engineering.
3

5. Task and Participation
 Helps software engineer to better understand the problem.
 Participants involved:
 Software Engineers
 Managers
 Customers
 Users
4

6. Understanding Requirements
 Collecting needs from the customer.
 Managing the Process.
 Tasks involved:
 Inception
 Elicitation
 Elaboration
 Negotiation
 Specification
 Validation
 Requirements Management
5

7. Inception (Beginning)
 During inception, the requirements asks a set of questions to establish:
 Basic understanding of the problem.
 Nature of the solution that is desired.
 Requirements Engineers needs to Identify the stakeholders, recognize multiple
viewpoints, work toward collaboration and initiate the communication.
6

8. Elicitation: (Extraction)
 Eliciting requirements is difficult because of
 Problems of scope > identify the boundaries of the system.
 Problems of understanding > domain , computing environment.
 Problems of Volatility > requirements may change over time.
 Elicitation may be accomplished through two activities:
 Collaborative Requirements Gathering.
 Quality Function Deployment.
7

9. Elaboration (explanation)
 Takes the information obtained during inception and elicitation.
 Focuses on developing a refined model of software functions, features &
Constraints.
 This is an analyzing phase.
 It defines the functional, informational and behavioral constraints of the problem
domain.
8

10. Negotiation (Cooperation)
 Software engineer reconciles the conflicts between what the customer wants and
what can be achieved.
 Requirements are ranked by the customer, users and other stakeholders.
 Risks associated with each requirement are identified.

11. Specifications
 Final work product produced by the requirements engineer.
 Form of SRS.
 Serves as a foundation.
 It formalizes the functional and behavioral requirements of the proposed software
in both the graphical and textual format.
10

12. Validation
 Specification is examined to ensure that all the se requirements have been stated
unambiguously.
 Errors have been detected and corrected.
 Members involved:
 Software Engineers
 Customers
 Users
 Other stakeholders.
11

13. Requirements Management
 Project team performs a set of activities to identify, control and track requirements
and changes to the requirements at any times as the project proceeds.
 Each requirement is assigned a unique identifier.
 Place the requirements into tables.
 Tables may be stored in a database that relate features, sources, dependencies
subsystems and interfaces to the requirements.
12

14. 1