1. Aim: To write SRS in IEEE format for given case study
2. Objectives: From this experiment, the student will be able to, To understand intended purpose and environment for software under development. Learn how documentation is prepared according to functional & non-functional requirements
GET INSTANT HELP FROM EXPERTS!
- Looking for any kind of help on your academic work (essay, assignment, project)?
- Want us to review, proofread or tidy up your work?
- Want a helping hand so that you can focus on the more important tasks?
Hire us as project guide/assistant. Contact us for more information
3. Outcomes: The learner will be able , To analyze software functional & nonfunctional requirements
To analyze the local and global impact of software engineering on individuals,
organizations, and society.
To engage in life-long learning development and higher studies.
4. Hardware / Software Required: Any text editor, Open source tool
5. Theory:
A software requirements specification (SRS) fully describes what the software will do and how it will be expected to perform.
It is a document that captures complete description about how the system is expected to perform. It is usually signed off at the end of requirements engineering phase.
It lays out functional and non-functional requirements , and may include a set of use cases that describe user interactions that the software must provide .
What should the SRS address?
As per the IEEE standard:
The basic issues that the SRS writer(s) shall address are the following:
a) Functionality: What is the software supposed to do?
b) External interfaces: How does the software interact with people, the system hardware, other hardware, and other software?
c) Performance: What is the speed, availability, response time, recovery time of various software functions, etc.?
d) Attributes: What is the portability, correctness, maintainability, security, etc. considerations ?
e) Design constraints imposed on an implementation: Are there any required standards in effect, implementation language, policies for database integrity, resource limits, operating environment(s) etc.?
Template for RFP
Software Requirements Specification for
Version 1.0 approved
Prepared by
Table of Contents
1. Introduction
2. Overall Description
3. External Interface Requirements
4. System Features
5. Other Nonfunctional Requirements
History
Name Date Reason For Changes Version
● Introduction
➢ Purpose
Identify the product whose software requirements are specified in this
document, including the revision or release number. Describe the scope of the
product that is covered by this SRS, particularly if this SRS describes only part
of the system or a single subsystem.
➢ Document Conventions
Describe any standards or typographical conventions that were followed when
writing this SRS, such as fonts or highlighting that have special significance.
For example, state whether priorities for higher-level requirements are
assumed to be inherited by detailed requirements, or whether every
requirement statement is to have its own priority.
➢ Intended Audience and Reading Suggestions
Describe the different types of reader that the document is intended for, such
as developers, project managers, marketing staff, users, testers, and
documentation writers. Describe what the rest of this SRS contains and how it
is organized. Suggest a sequence for reading the document, beginning with the
overview sections and proceeding through the sections that are most pertinent
to each reader type.
➢ Product Scope
Provide a short description of the software being specified and its purpose,
including relevant benefits, objectives, and goals. Relate the software to
corporate goals or business strategies. If a separate vision and scope document
is available, refer to it rather than duplicating its contents here.
➢ References
List any other documents or Web addresses to which this SRS refers. These
may include user interface style guides, contracts, standards, system
requirements specifications, use case documents, or a vision and scope
document. Provide enough information so that the reader could access a copy
of each reference, including title, author, version number, date, and source or
location.
● Overall Description
➢ Product Perspective
Describe the context and origin of the product being specified in this SRS. For
example, state whether this product is a follow-on member of a product
family, a replacement for certain existing systems, or a new, self-contained
product. If the SRS defines a component of a larger system, relate the
requirements of the larger system to the functionality of this software and
identify interfaces between the two. A simple diagram that shows the major
components of the overall system, subsystem interconnections, and external
interfaces can be helpful.
➢ Product Functions
Summarize the major functions the product must perform or must let the user
perform. Details will be provided in Section 3, so only a high level summary
(such as a bullet list) is needed here. Organize the functions to make them
understandable to any reader of the SRS. A picture of the major groups of
related requirements and how they relate, such as a top level data flow
diagram or object class diagram, is often effective.
➢ User Classes and Characteristics
Identify the various user classes that you anticipate will use this product. User
classes may be differentiated based on frequency of use, subset of product
functions used, technical expertise, security or privilege levels, educational
level, or experience. Describe the pertinent characteristics of each user class.
Certain requirements may pertain only to certain user classes. Distinguish the
most important user classes for this product from those who are less important
to satisfy.
➢ Operating Environment
Describe the environment in which the software will operate, including the
hardware platform, operating system and versions, and any other software
components or applications with which it must peacefully coexist.
➢ Design and Implementation Constraints
Describe any items or issues that will limit the options available to the
developers. These might include: corporate or regulatory policies; hardware
limitations (timing requirements, memory requirements); interfaces to other
applications; specific technologies, tools, and databases to be used; parallel
operations; language requirements; communications protocols; security
considerations; design conventions or programming standards (for example, if
the customer’s organization will be responsible for maintaining the delivered
software).
➢ User Documentation
List the user documentation components (such as user manuals, on-line help,
and tutorials) that will be delivered along with the software. Identify any
known user documentation delivery formats or standards.
➢ Assumptions and Dependencies
List any assumed factors (as opposed to known facts) that could affect the
requirements stated in the SRS. These could include third-party or commercial
components that you plan to use issues around the development or operating
environment, or constraints. The project could be affected if these assumptions
are incorrect, are not shared, or change. Also identify any dependencies the
project has on external factors, such as software components that you intend to
reuse from another project, unless they are already documented elsewhere (for
example, in the vision and scope document or the project plan).
● External Interface Requirements
➢ User Interfaces
Describe the logical characteristics of each interface between the software
product and the users. This may include sample screen images, any GUI
standards or product family style guides that are to be followed, screen layout
constraints, standard buttons and functions (e.g., help) that will appear on
every screen, keyboard shortcuts, error message display standards, and so on.
Define the software components for which a user interface is needed. Details
of the user interface design should be documented in a separate user interface
specification.
➢ Hardware Interfaces
Describe the logical and physical characteristics of each interface between the
software product and the hardware components of the system. This may
include the supported device types, the nature of the data and control
interactions between the software and the hardware, and communication
protocols to be used.
➢ Software Interfaces
Describe the connections between this product and other specific software
components (name and version), including databases, operating systems, tools,
libraries, and integrated commercial components. Identify the data items or
messages coming into the system and going out and describe the purpose of
each. Describe the services needed and the nature of communications. Refer to
documents that describe detailed application programming interface protocols.
Identify data that will be shared across software components. If the data
sharing mechanism must be implemented in a specific way (for example, use
of a global data area in a multitasking operating system), specify this as an
implementation constraint.
➢ Communications Interfaces
Describe the requirements associated with any communications functions
required by this product, including e-mail, web browser, network server
communications protocols, electronic forms, and so on. Define any pertinent
message formatting. Identify any communication standards that will be used,
such as FTP or HTTP. Specify any communication security or encryption
issues, data transfer rates, and synchronization mechanisms.
● System Features
This template illustrates organizing the functional requirements for the product
by system features, the major services provided by the product. You may
prefer to organize this section by use case, mode of operation, user class,
object class, functional hierarchy, or combinations of these, whatever makes
the most logical sense for your product.
➢ System Feature 1
(Just not “System Feature 1.” State the feature name in just a few words.)
4.1.1 Description and Priority
Provide a short description of the feature and indicate whether it is of High,
Medium, or Low priority. You could also include specific priority component
ratings, such as benefit, penalty, cost, and risk (each rated on a relative scale
from a low of 1 to a high of 9)
1.1.2 Stimulus/Response Sequences
List the sequences of user actions and system responses that stimulate the
behavior defined for this feature. These will correspond to the dialog elements
associated with use cases.
1.1.3 Functional Requirements
Itemize the detailed functional requirements associated with this feature.
These are the software capabilities that must be present in order for the user to
carry out the services provided by the feature, or to execute the use case.
Include how the product should respond to anticipated error conditions or
invalid inputs. Requirements should be concise, complete, unambiguous,
verifiable, and necessary. Use “TBD” as a placeholder to indicate when
necessary information is not yet available.
Each requirement should be uniquely identified with a sequence number or a
meaningful tag of some kind.
➢ System Feature 2… (And so on)
● Other Nonfunctional Requirements
➢ Performance Requirements
If there are performance requirements for the product under various
circumstances, state them here and explain their rationale, to help the
developers understand the intent and make suitable design choices. Specify the
timing relationships for real time systems. Make such requirements as specific
as possible. You may need to state performance requirements for individual
functional requirements or features.
➢ Safety Requirements
Specify those requirements that are concerned with possible loss, damage, or
harm that could result from the use of the product. Define any safeguards or
actions that must be taken, as well as actions that must be prevented. Refer to
any external policies or regulations that state safety issues that affect the
product’s design or use. Define any safety certifications that must be satisfied.
➢ Security Requirements
Specify any requirements regarding security or privacy issues surrounding use
of the product or protection of the data used or created by the product. Define
any user identity authentication requirements. Refer to any external policies or
regulations containing security issues that affect the product. Define any
security or privacy certifications that must be satisfied.
➢ Software Quality Attributes
Specify any additional quality characteristics for the product that will be
important to either the customers or the developers. Some to consider are:
adaptability, availability, correctness, flexibility, interoperability,
maintainability, portability, reliability, reusability, robustness, testability, and
usability. Write these to be specific, quantitative, and verifiable when possible.
At the least, clarify the relative preferences for various attributes, such as ease
of use over ease of learning.
➢ Business Rules
List any operating principles about the product, such as which individuals or
roles can perform which functions under specific circumstances. These are not
functional requirements in themselves, but they may imply certain functional
requirements to enforce the rules.
6. Documentation:
Students should prepare Software Requirement Specification (SRS) Document as per
the template given above (for their case study)
7. Conclusion:
SRS establish the basis for agreement between the customers and the suppliers also
reduce the development efforts, provide a basis for estimating costs and schedules,
and provide a baseline for validation and verification. The SRS makes it easier to
transfer the software product to new users or new machines &Serve as a basis for
enhancement.
8. Viva Questions:
1. What are the contents of SRS?
2. State functional & nonfunctional requirements in SRS?
9. Reference books & Links:
1. https://www.ibm.com/…/community/…/srs%20format.pdf
2. https://web.cs.dal.ca/~hawkey/3130/srs_template-ieee.doc
3. www.tricity.wsu.edu/~mckinnon/cpts322/cpts322-srs-v1.doc
4. www.jaysonjc.com/…/how-to-write-a-software-requirements-specification.
StudyMumbai.com is an educational resource for students, parents, and teachers, with special focus on Mumbai. Our staff includes educators with several years of experience. Our mission is to simplify learning and to provide free education. Read more about us.
Leave a Reply
You must be logged in to post a comment.