Software requirements specification
.A software requirements specification
(SRS) is a comprehensive description of
the intended purpose and environment
for .software under development.
The SRS fully describes what the software
will do and how it will be expected to
perform.
SRS is a description of a software system to
be developed.
It lays out functional and non functional
requirement of the software to be
developed.
It may include a set of use cases- situation,
student forget password, faculty wants to
apply leave so on that describe user
interaction
An SRS minimizes the time and effort required by developers
to achieve desired goals and also minimizes the development
cost.
A good SRS defines how an application will interact with
system hardware, other programs and human users in a wide
variety of real-world situations.
Parameters such as operating speed, response time, availability,
portability, maintainability, security and speed of recovery
from adverse events are evaluated
SRS STRUCTURE
Purpose
Intended audience- users
Scope-
Definitions- principal,director,HOD,Members
References-online video, research data, books
Overall description- user interface,system
interface- protocol,server,http,constraints.
Hardware interface,[Link]
requirement-external interface- like payment
mode, database-mysql,oracle,disk required. Non
functional-
safety,security,avalibility,portability,reliable
The Software Requirements
Specification
After review of the customer’s System
Spec.
After educated analysis
A technical, software “approach”
Results in permission to detail-design and
code
Types of SRS Requirements
Functional requirements
Performance requirements
Speed, accuracy, frequency, throughput
External interface requirements
Design constraints
Requirements are usually about “what”, this is a “how”.
Quality attributes
i.e. reliability, portability, maintainability, supportability
Risk Assessment
Technical Risks
hardware
software
interfaces
build vs. buy
Schedule Risks
budget
calendar
personnel – level of expertise required
Requirement Elicitation
.Requirements elicitation is the process of
gathering and defining the requirements for a
software system.
.The goal of requirements elicitation is to
ensure that the software development process
is based on a clear and comprehensive
understanding of the customer’s needs and
requirements.
Requirement Elicitation can be successful
only through an effective customer-
developer partnership. It is needed to know
what the users require.
Requirements elicitation involves the
identification, collection, analysis, and
refinement of the requirements for a
software system.
Requirement Elicitation is a critical part of
the software development life cycle and is
typically performed at the beginning of the
project.
The output of the requirements elicitation process is a
set of clear, concise, and well-defined requirements
that serve as the basis for the design and development
of the software system.
Requirements elicitation is difficult because just
questioning users and customers about system needs
may not collect all relevant requirements, particularly
for safety and dependability.
Interviews, surveys, user observation, workshops,
brainstorming, use cases, role-playing, and prototyping
are all methods for eliciting requirements.
Importance of Requirements
Elicitation
Compliance with Business Objectives
User Satisfaction
Time and Money Savings
Compliance and Regulation Requirements
Traceability and Documentation
Requirements Elicitation
Activities
Knowledge of the overall area where the
systems are applied.
The details of the precise customer problem
where the system is going to be applied
must be understood.
Interaction of system with external
requirements.
Detailed investigation of user needs.
Define the constraints for system
development.
Advantages of
Requirements Elicitation
Clear requirements: Helps to clarify and refine customer
requirements.
Improves communication: Improves communication and
collaboration between stakeholders.
Results in good quality software: Increases the chances of
developing a software system that meets customer needs.
Avoids misunderstandings: Avoids misunderstandings and
helps to manage expectations.
Supports the identification of potential risks: Supports the
identification of potential risks and problems early in the
development cycle.
Facilitates development of accurate plan: Facilitates the
development of a comprehensive and accurate project plan.
Increases user confidence: Increases user and stakeholder
confidence in the software development process.
Disadvantages of
Requirements Elicitation
Time-consuming: It can be time-consuming and expensive.
Skills required: Requires specialized skills and expertise.
Impacted by changing requirements: This may be impacted by changing
business needs and requirements.
Impacted by other factors: Can be impacted by political and organizational
factors.
Lack of commitment from stakeholders: This can result in a lack of buy-in and
commitment from stakeholders.
Impacted by conflicting priorities: Can be impacted by conflicting priorities and
competing interests.
Sometimes inaccurate requirements: This may result in incomplete or
inaccurate requirements if not properly managed.
Increased development cost: This can lead to increased development costs and
decreased efficiency if requirements are not well-defined.
Conclusion