Requirements Specification and Solution Documentation

g
n
i
n
i
a
r
t
l
e
d
a
x
e
#
Requirements Specification and Solution Documentation: General overview
AGENDA
1. Requirements classification 2. Requirements vs. Designs 3. Design fidelity
#exadeltraining
2
g
n
i
n
i
a
r
t
l
e
d
a
x
e
#
Requirements classification
Requirements
Definition
BABOK:
A requirement is a usable representation of a need. Requirements focus on understanding what kind of value could be delivered if a requirement is fulfilled.
The nature of the representation may be a document (or set of documents), but can vary widely depending on the circumstances.
Wiegers K., Beatty J. - Software Requirements:
Requirements are a specification of what should be implemented. They are descriptions of how the system should behave, or of a system property or attribute. They may be a constraint on the development process of the system.

Requirements Levels High-level
Low-level
Business
Requirements
User Requirements Software Requirements
Transition Requirements

Business Requirements contain
Business
High-level goals of the organization High-level goals of system customers
Whole of an enterprise

Requirements
c^{an app}ly t^{o
are expressed b}y
A business area
A specific initiative
Those who finance the project

Business Requirements.
Examples
● to increase revenue
● reduce operating expenses
● improve customer service
● meet regulatory obligations, etc.
Example:
➔ Increase profits by 20% by increasing sales after 3 months from the launch of the application
➔ Reduce the cost of maintaining calls centre by introducing online orders ➔ Increase market share in USA region by 10% percent within 5 months ➔ Save $5000 per year on electricity now wasted by inefficient units

User Requirements
User
Requirements
describe
the goals and objectives that the future system will allow users to solve

Users can be broadly defined to include not only humans who access the software but hardware devices and other software systems as well
Examples
➔ I need to print a mailing label for a package
➔ I need to create an online order
➔ I want to choose cleaning services online, not by phone
*Some people use the broader term “stakeholder requirements,” to acknowledge the reality that various stakeholders other than direct users will provide requirements.

Software Requirements
Functional
Requirements
Software
Requirements
Non-functional
Requirements

Software Requirements.
Functional Requirements (FR)
Determine the functionality of the system that developers must build so that users can complete their tasks within the business requirements.
Examples
➔ Username should contain a link to the user’s Personal profile
➔ The system must allow users to log into their account on mobile by entering their email and password
➔ The system must allow users to reset their password by clicking on “I forgot my password”
➔ If the Passenger’s profile does not indicate a seating preference, the reservation system shall assign a seat
Software Requirements.
Non- functional Requirements (NFR)
Requirements that define properties that a system must exhibit, or constraints that it must adhere to, not related to the behavior of the system.
The requirements for the system that set the criteria for the quality of its work (security, reliability, performance, scalability, etc.)
Examples
➔ Any form submission request should take no more than 5 seconds ➔ The system serves up to 1000 concurrent users
➔ Users should be able to go to any page of the site in 3 clicks
➔ The number of records in the database must be updated in real time
Software Requirements.
FR and NFR main differences
Functional requirements define WHAT should be done by the system, and non-functional - HOW should it be done.
FR NFR

Defines the system
Answers the question: "WHAT should the system do?"
Helps to check the functionality of the system
Defines a quality attribute
Answers the question: "HOW should the system meet the functional requirements?"
Helps to check system efficiency

Software Requirements.
FR and NFR main differences ^{The system shall display to the user the number of records} A. in the database
Software Requirements. FR and NFR main differences

A. B.
The system shall display to the user the number of records in the database
The system shall check the validity of the PIN-code within three seconds

Software Requirements. FR and NFR main differences

A. B. C.
The system shall display to the user the number of records in the database
The system shall check the validity of the PIN-code within three seconds
The number of records in the database shall be updated in real time

Software Requirements. FR and NFR main differences

A. B. C. D.
The system shall display to the user the number of records in the database
The system shall check the validity of the PIN-code within three seconds
The number of records in the database shall be updated in real time
The system shall check the validity of the PIN-code entered by the user
Functional Requirement Non-functional Requirement
Non-functional Requirement Functional Requirement

Software Requirements.
FR and NFR main differences
Functional requirements define WHAT should be done by the system, and non-functional - HOW should it be done.
FR NFR

The system shall display to the user the number of records in the database
The system shall check the validity of the PIN-code entered by the user
The number of records in the database shall be updated in real time
The system shall check the validity of the PIN-code within three seconds

Transition Requirements

Transition
Requirements
describe
the conditions the solution must meet to facilitate transition from the current state to the future state

Not needed once the change is complete Examples
➔ User training
➔ Data migration
➔ Security setup
➔ Training to close skill gaps
Types of Requirements

Business Rules
Phrases such as
● “Must comply with . . . ,”
● “If , then ,”
● “Must be calculated according to . . . ”
suggest that the user is describing a business rule.
Examples
➔ A new client must pay 30 percent of the estimated consulting fee and travel expenses in advance
➔ Time-off approvals must comply with the company’s HR vacation policy
y
r
e
v
i
l
e
d
l
e
d
a
x
e
#
Requirements vs.
Designs
“Requirements are focused on the need; designs are focused on the solution” Requirements ^Design vs.
“Requirements are focused on the need; designs are focused on the solution”
Need
Requirement
Solution
Design
Whether it is the business analyst or some other role that completes the designs, the business analyst often reviews the final designs to ensure that they align with the requirements.
g
n
i
n
i
a
r
t
l
e
d
a
x
e
#
UI / UX stage
Design fidelity
Low-fidelity High-Fidelity
Design fidelity
Sketch
What
Sketches are freehand drawings on a piece of paper or in a digital tool that gives you a basic representation of your concept.
When
Sketches can be very helpful during the conceptualization and initial visualization phase of your design process.
How
Sketches can be created using pen and paper or in almost any design tool.
Design fidelity
Wireframes
What
Wireframes are low-fidelity design artifacts that represent only essential elements of UI.
When
Wireframes are most relevant in the initial stages of the product design process. Wireframes are useful for: ● Evaluating the structure of individual pages/screens; ● Understanding how related screens/pages work together;
● Preparing a detailed project requirements document. How
Similar to sketches, wireframes can be created using pen & paper. When it comes to digital tools, Balsamiq perhaps is the most useful tool.
Design fidelity
Mockups
What
Mockups are a mid- or high-fidelity visualization of your design. They deliver the visual look of the product design.
When
Visual design phase of design process
Mockups can be used both when designing a new product and redesign an existing product.
● Evaluate visual design decisions;
● Experiment with various styles;
● Evaluate the visual consistency of design; ● Evaluate the accessibility of your design;. ● Present the user interface to stakeholders
How
Mockups can be created in Photoshop, Sketch, Figma, and many other design tools.
Design fidelity
Prototypes
What
A prototype is a working model of an app/webpage.
When
Prototypes can be very helpful during the functional design phase of the design process.
Prototypes can help you to:
● Evaluating the user journey.
● Test usability.
How
Adobe XD, InVision, and others.
Tips for BA at the prototyping stage
● Don't get attached to the prototype too emotionally!
There are still many comments from stakeholders ahead
● Put in a minimum of effort
The more time we spend on prototyping, the less willing we are to make subsequent changes
● Do not try to polish your sketches
Details can distract stakeholders from the main thing
● Create scenarios of usage
This helps guide the customer through the expected flow
Useful Materials
● The essential software requirement, Chapter 1 - Software Requirements, Wiegers K., Beatty J.
● Overview of Software Requirements, Chapter 1 - The Software Requirements Memory Jogger, Ellen Gottesdiener
● Requirements and Designs, section 2.5 - BABOK®, Version 3, IIBA ● Risk reduction through prototyping, Chapter 15 - Software Requirements, Wiegers K., Beatty J.

TIME FOR QUESTIONS

#exadeldeltraining
THANK
YOU!