SOFTWARE

REQUIREMENTS

SHYRILL D. OGOC
PRESENTATION TITLE
OBJECTIVES
REQUIREMENT ENGINEERING AND PROCESS SOFTWARE METRICS AND
MEASURES

REQUIREMENT GATHERING

SOFTWARE REQUIREMENT SPECIFICATION (SRS)

SOFTWARE REQUIREMENT VALIDATION

REQUIREMENT ELICITATION PROCESS

REQUIREMENT ELICITATION TECHNIQUES

SOFTWARE REQUIREMENTS CHARACTERISTICS

2
SOFTWARE REQUIREMENTS

USER INTERFACE REQUIREMENTS

PRESENTATION TITLE

REQUIREMENT
ENGINEERING
The process to gather the software requirements from
client, analyze, and document them

3
 REQUIREMENT
ENGINEERING
PROCESS
It is a four step process, which includes –
 Feasibility Study
 Requirement Gathering
 Software Requirement Specification
 Software Requirement Validation
 FEASIBILITY STUDY
• it focused towards goal of the organization. This study analyzes
whether the software product can be practically materialized in terms of
implementation, contribution of project to organization, cost
constraints, and as per values and objectives of the organization.
• It explores technical aspects of the project and product such as
usability, maintainability, productivity, and integration ability.

Requirement Engineering Process

 REQUIREMENT
GATHERING
Analysts and engineers communicate with the client and end-
users to know their ideas on what the software should provide
and which features they want the software to include.

Requirement Engineering Process

 SOFTWARE REQUIREMENT
PRESENTATION TITLE

SPECIFICATION (SRS)
• SRS is a document created by system analyst after
the requirements are collected from various
stakeholders.
• SRS defines how the intended software will interact
with hardware, external interfaces, speed of
operation, response time of system, portability of
software across various platforms, maintainability,
speed of recovery after crashing, Security, Quality,
7
Limitations etc. Requirement Engineering Process
 SRS SHOULD COME UP WITH
PRESENTATION TITLE

THE FOLLOWING FEATURES:

• User Requirements are expressed in natural language.
•  Technical requirements are expressed in structured language, which is used
inside the organization.
•  Design description should be written in Pseudo code.
•  Format of Forms and GUI screen prints.
•  Conditional and mathematical notations for (Data flow Diagrams) DFDs
etc.

8
 SOFTWARE REQUIREMENT
PRESENTATION TITLE

VALIDATION
• After requirement specifications are developed, the requirements
mentioned in this document are validated. User might ask for
illegal, impractical solution or experts may interpret the
requirements inaccurately. This results in huge increase in cost if
not nipped in the bud. Requirements can be checked against
following conditions
• If they can be practically implemented
•  If they are valid and as per functionality and domain of
software
•  If there are any ambiguities
9 •  If they are complete
Requirement Engineering Process
•  If they can be demonstrated
PRESENTATION TITLE

“REQUIREMENT
ELICITATION
PROCESS

10
 REQUIREMENT ELICITATION
PRESENTATION TITLE

PROCESS

11
 REQUIREMENTS GATHERING
PRESENTATION TITLE

The developers discuss with the client and end users and know their expectations
from the software.

ORGANIZING REQUIREMENTS
The developers prioritize and arrange the requirements in order of importance,
urgency and convenience.
NEGOTIATION & DISCUSSION
If requirements are ambiguous or there are some conflicts in requirements of
various stakeholders, it is then negotiated and discussed with the stakeholders.
Requirements may then be prioritized and reasonably compromised

12 Requirement Elicitation
Process
 DOCUMENTATION
PRESENTATION TITLE

All formal and informal, functional and non-functional

requirements are documented and made available for
next phase processing.

13
Requirement Elicitation Process
 REQUIREMENT ELICITATION
PRESENTATION TITLE

TECHNIQUES
• is the process to find out the requirements for an
intended software system by communicating with
client, end users, system users, and others who have a
stake in the software system development.
• There are various ways to discover requirements.
Some of them are explained below:
14
 Structured (closed) interviews, where
PRESENTATION TITLE
INTERVIEWS every single information to gather is
decided in advance, they follow pattern
Interviews are strong and matter of discussion firmly.
medium to collect  Non-structured (open) interviews,
requirements. Organization where information to gather is not
decided in advance, more flexible and
may conduct several types less biased.
of interviews such as:  Oral interviews
 Written interviews
 One-to-one interviews which are
held between two persons across the
table.
15
 Group interviews which are held
Requirement Elicitation Techniques
between groups of participants. They
PRESENTATION TITLE
SURVEYS
Organization may conduct
surveys among various
stakeholders by querying
about their expectation and
requirements from the
upcoming system.

16
Requirement Elicitation Techniques
 QUESTIONNAIRES
PRESENTATION TITLE

A document with pre-

defined set of objective
questions and respective
options is handed over to all
stakeholders to answer,
which are collected and
compiled.

17
Requirement Elicitation Techniques
 TASK ANALYSIS
PRESENTATION TITLE

Team of engineers and

developers may analyze the
operation for which the new
system is required. If the
client already has some
software to perform certain
operation, it is studied and
requirements of proposed
system are collected.
18
Requirement Elicitation Techniques
PRESENTATION TITLE
DOMAIN
ANALYSIS
Every software falls into
some domain category. The
expert people in the domain
can be a great help to
analyze general and specific
requirements. .

19
Requirement Elicitation Techniques
PRESENTATION TITLE

BRAINSTORMING
An informal debate is held
among various stakeholders
and all their inputs are
recorded for further
requirements analysis

20
Requirement Elicitation Techniques
PRESENTATION TITLE

PROTOTYPING
is building user interface
without adding detail
functionality for user to
interpret the features of
intended software product.

21
Requirement Elicitation Techniques
PRESENTATION TITLE

OBSERVATION
Team of experts visit the
client’s organization or
workplace. They observe
the actual working of the
existing installed systems.
They observe the workflow
at the client’s end and how
execution problems are
dealt. The team itself draws
22
some conclusions which aid
Requirement Elicitation Techniques
to form requirements
 SOFTWARE REQUIREMENTS
PRESENTATION TITLE

CHARACTERISTICS
Gathering software requirements is the foundation of the entire software development
project. Hence they must be clear, correct, and well-defined.
Clear
 Correct
 Consistent
 Coherent
 Comprehensible
 Modifiable
 Verifiable
 Prioritized
 Unambiguous
 Traceable
23
 Credible source
 SOFTWARE REQUIREMENTS
PRESENTATION TITLE

Broadly software requirements should be categorized in

two categories
• Functional Requirements
• Non-Functional Requirements

24
 FUNCTIONAL REQUIREMENTS
PRESENTATION TITLE

• Requirements, which are related to functional aspect of

software fall into this category
• They define functions and functionality within and
from the software system.

25
 NON-FUNCTIONAL REQUIREMENTS
PRESENTATION TITLE

• Requirements, which are not related to functional

aspect of software, fall into this category. They are
implicit or expected characteristics of software, which
users make assumption of.
• Non-functional requirements include –
• Security  Logging  Storage  Configuration 
Performance  Cost  Interoperability  Flexibility 
Disaster recovery  Accessibility
26
 REQUIREMENTS ARE CATEGORIZED
PRESENTATION TITLE

LOGICALLY AS

Must Have : Software cannot be said operational without

them.
Should have : Enhancing the functionality of software.
Could have : Software can still properly function with
these requirements.
Wish list : These requirements do not map to any
objectives of software
27
USER INTERFACE
REQUIREMENTS
USER INTERFACE REQUIREMENTS
User Interface (UI) is an important part of any software or
hardware or hybrid system. A software is widely accepted if it
is –
 easy to operate
 quick in response
 effectively handling operational errors
 providing simple yet consistent user interface
 USER INTERFACE REQUIREMENTS
ARE BRIEFLY MENTIONED BELOW –
• Content presentation
• Easy Navigation
• Simple interface
• Responsive
• Consistent UI elements
• Feedback mechanism
• Default settings
• Purposeful layout
• Strategical use of color and texture.
• Provide help information
• User centric approach
• Group based view settings
SOFTWARE SYSTEM
ANALYST
 SYSTEM ANALYSTS HAVE THE
FOLLOWING RESPONSIBILITIES: –
• Analyzing and understanding requirements of intended software
• Understanding how the project will contribute to the organizational
objectives
• Identify sources of requirement
• Validation of requirement
• Develop and implement requirement management plan
• Documentation of business, technical, process, and product
requirements
• Coordination with clients to prioritize requirements and remove
ambiguity
• Finalizing acceptance criteria with client and other stakeholders
SOFTWARE METRICS AND
MEASURES
 SOFTWARE METRICS AND
MEASURES
• SOFTWARE MEASURES CAN BE UNDERSTOOD AS A
PROCESS OF QUANTIFYING AND SYMBOLIZING VARIOUS
ATTRIBUTES AND ASPECTS OF SOFTWARE.
• SOFTWARE METRICS PROVIDE MEASURES FOR VARIOUS
ASPECTS OF SOFTWARE PROCESS AND SOFTWARE
PRODUCT.
• SOFTWARE MEASURES ARE FUNDAMENTAL
REQUIREMENTS OF SOFTWARE ENGINEERING. THEY NOT
ONLY HELP TO CONTROL THE SOFTWARE DEVELOPMENT
PROCESS BUT ALSO AID TO KEEP THE QUALITY OF
ULTIMATE PRODUCT EXCELLENT.
 LET US SEE SOME SOFTWARE METRICS:
• SIZE METRICS - LINES OF CODE (LOC) (), MOSTLY CALCULATED IN THOUSANDS OF
DELIVERED SOURCE CODE LINES, DENOTED AS KLOC.
• FUNCTION POINT COUNT IS MEASURE OF THE FUNCTIONALITY PROVIDED BY THE
SOFTWARE. FUNCTION POINT COUNT DEFINES THE SIZE OF FUNCTIONAL ASPECT OF
THE SOFTWARE.
• COMPLEXITY METRICS - MCCABE’S CYCLOMATIC COMPLEXITY QUANTIFIES THE
UPPER BOUND OF THE NUMBER OF INDEPENDENT PATHS IN A PROGRAM, WHICH IS
PERCEIVED AS COMPLEXITY OF THE PROGRAM OR ITS MODULES. IT IS
REPRESENTED IN TERMS OF GRAPH THEORY CONCEPTS BY USING CONTROL FLOW
GRAPH.
• QUALITY METRICS - DEFECTS, THEIR TYPES AND CAUSES, CONSEQUENCE,
INTENSITY OF SEVERITY AND THEIR IMPLICATIONS DEFINE THE QUALITY OF THE
PRODUCT
• THE NUMBER OF DEFECTS FOUND IN DEVELOPMENT PROCESS AND NUMBER OF
DEFECTS REPORTED BY THE CLIENT AFTER THE PRODUCT IS INSTALLED OR
DELIVERED AT CLIENT END, DEFINE QUALITY OF THE PRODUCT.
• PROCESS METRICS - IN VARIOUS PHASES OF SDLC, THE METHODS AND TOOLS
USED, THE COMPANY STANDARDS AND THE PERFORMANCE OF DEVELOPMENT ARE
SOFTWARE PROCESS METRICS.  RESOURCE METRICS - EFFORT, TIME, AND VARIOUS
RESOURCES USED, REPRESENTS METRICS FOR RESOURCE MEASUREMENT
END