Requirement Engineering
By
SHIVANI AGARWAL
AJAY KUMAR GARG ENGINEERING
COLLEGE,GHAZIABAD
Requirement
Steps of Requirement Engineering
Requirement Engineering
Types of requirements
Functional & Non-functional Requirements
Requirement elicitation
• requirements elicitation is the practice of researching and
discovering the requirements of a system from users,
customers, and other stakeholders. The practice is also
sometimes referred to as "requirement gathering".
• Elicitation is important as many stakeholders are unable to
accurately articulate the business problem. Therefore,
analysts performing the elicitation need to ensure that
the requirements produced are clearly understandable,
useful and relevant.
• Number of elicitation techniques:-
Elicitation Techniques
Elicitation Techniques
Elicitation Techniques
FAST
FAST
FAST
FAST
Elicitation Techniques
• Guidelines for the meeting:-
Elicitation Techniques
• FAST session preparation:-
Elicitation Techniques
Elicitation Techniques
Elicitation Techniques
Elicitation Techniques
Use Case Diagram
• In the Unified Modeling Language (UML), a use
case diagram can summarize the details of your
system's users (also known as actors) and their
interactions with the system. UML use case
diagrams are ideal for:
• Representing the goals of system-user interactions
• Defining and organizing functional requirements
in a system
• Specifying the context and requirements of a
system
• Modeling the basic flow of events in a use case
Use Case Diagram
Common components include:
• Actors: The users that interact with a system. An
actor can be a person, an organization, or an
outside system that interacts with your application
or system. They must be external objects that
produce or consume data.
• System: A specific sequence of actions and
interactions between actors and the system. A
system may also be referred to as a scenario.
• Goals: The end result of most use cases. A
successful diagram should describe the activities
and variants used to reach the goal.
Use Case Diagram
• Use cases: Horizontally shaped ovals that represent the
different uses that a user might have.
• Associations: A line between actors and use cases. In
complex diagrams, it is important to know which actors are
associated with which use cases.
• System boundary boxes: A box that sets a system scope to
use cases. All use cases outside the box would be considered
outside the scope of that system. For example, Psycho Killer
is outside the scope of occupations in the chainsaw example
found below.
• Packages: A UML shape that allows you to put different
elements into groups. Just as with component diagrams,
these groupings are represented as file folders.
Use Case Diagram
Railway reservation Use case
Requirement Analysis
Requirement documentation
Requirement documentation
Requirement documentation
Requirement documentation
Requirement documentation
Requirement Validation
Requirement Validation
Requirement Review
After
refine ,fin
alize the
SRS
Review checklist
