Client Needs and Software Requirements

1. Software Requirement

2. What is a Requirement?
most easily understood as a specific description of your
client’s needs, which can be used to help create a real-
world product.

3. Requirements activities:
 1. Eliciting requirements
 2. Expressing requirements
 3. Prioritizing requirements
 4. Analyzing requirements
 5. Managing requirements

4. . Eliciting requirements
 The activity of eliciting requirements is an interactive and investigative
process, which occurs when meeting with the client and users.
 You will show to thing need – wants of the client
 You must apply his need and what he want to add on his
need through requirements gathering through asking the client many
questions about his needs and the feature he want

5. Expressing Requirements
 requirements are first described through notes from
meetings with clients so in this step want to expressing
requirements typically representations include use cases, user
stories, or storyboards
 software product manager and team to determine and use
representations that would work best for the project at hand

6. Prioritizing Requirements
Questions to help establish priorities include:
 What requirements must be completed for the project and product to be
successful?
 What requirements should be done? In other words, what is important but is not
as time-critical or could be satisfied another way or at a later time on the project?
 What could be done to improve the project or product but is not necessary? These
priorities are usually only included if both time and resources allow for it.

7. Analyzing Requirements
 Analyzing requirements helps ensure that the product is the
best one possible. It is an important process, and a constant
one

8. Managing Requirements
 The activity of managing requirements is also a continuous
process. It involves the organizing and re-organizing of
requirements and possibly reusing subsets of requirements in
different stages. It also involves keeping track of priorities,
analyses, and changes in requirements. This is very important
because everything is connected in a project.

9. Types of Requirements
 Business requirements
 Business rules
 User requirements
 Functional requirements
 Non-functional requirements
 External interfaces
 Physical product settings
 Development constraints