SOFTWARE QUALITY ASSURANCE

PROJECT TIMELINE
PROJECT DELIVERABLES
1. Introduction

1.1 Purpose

1.1.1 Scope and

Delimitations

1.2 Definitions, Acronyms,

and Abbreviations

1.3 References

2. Business Background
2.1 Business Description

2.2 Business Objectives

2.3 Stakeholder Profile

3. Current Business Set-Up

3.1 Statement of Problem/

Objective of the Study
3.2 Current Business Process
4. Solution Description

4.1 Product Perspective

4.1.1 System and User
Interfaces

4.1.2 Operations

CONTENT DESCRIPTION
The following subsections of the Software Requirements
Specifications (SRS) document should provide an overview of the
entire SRS.
Identify the purpose of this SRS and its intended audience. In this
subsection, describe the purpose of the particular SRS and
specify the intended audience for the SRS.
In this subsection:
(1) Identify the software product(s) to be produced by
name
(2) Explain what the software product(s) will, and, if
necessary, will not do
(3) Describe the application of the software being
specified, including relevant benefits, objectives, and
goals
(4) Be consistent with similar statements in higher-level
specifications if they exist
Provide the definitions of all terms, acronyms, and abbreviations
required to properly interpret the SRS. This information may be
provided by reference to one or more appendices in the SRS or
by reference to documents.
In this subsection:
(1) Provide a complete list of all documents referenced
elsewhere in the SRS
(2) Identify each document by title, report number (if
applicable), date, and publishing organization
(3) Specify the sources from which the references can be
obtained.
Describe here the type of business and the unique
characteristics of this domain, e.g. health, telecommunications,
banking, real estate, etc. Also include subdivisions of the
business, like public, private, defense, etc., as each of those
may require or affect the project scope and resource allocation
through understanding of this model (e.g. security clearance
for some type of financial projects). Try to explain the
business environment associated with or related to it, and
other types of business or sectors that is affected by it.
Business Objectives provide the overall direction to help the
company focus on the rationale and its expected
results. Objectives help provide a definition of the end point
that can be used to monitor progress and to identify when
success has been achieved.
Describe each stakeholder in the system by identifying the
profile, responsibilities, involvement, and contact information
of each stakeholder.
This section provides information of the current business
setup of the client and provides the context for the system
being built.
Describe the business problem to be solved or opportunity/
need to be addressed.
Describe the business process that is affected by the problem.
Include a diagram/s to supplement the description
Describe the general factors that affect the product and its
requirements. This section provides a background for the
requirements and makes them easier to understand.
The following subsections describe how the software operates
inside various constraints.
List each system interface and identify the functionality of the
software to accomplish the system requirement and the
interface description to match the system. (per objective)
This is a description of how the system will interact with its
users.
Hardware & Software Interfaces: Specify the logical
characteristics of each interface between the software product
and the hardware components of the system.
Communications Interfaces: Specify the various interfaces to
communications such as local network protocols, etc. These
are protocols you will need to directly interact with.
Specify the normal and special operations required by the user

DEADLINE OF
SUBMISSION

November 19, 2014

November 26,
2014

December 3, 2014

January 14, 2014

4.2 Product Functions

4.3 Data Model

4.4 User Characteristics

4.5 Constraints
4.5.1 Design Constraints

4.6 Standards Compliance

4.7 Assumptions and
Dependencies

5. Specific Requirements

5.1 Performance
Requirements

5.2 Logical Database

Requirements
5.3 Software System
Attributes

5.3.1 Reliability
5.3.2 Availability

5.3.3 Security

5.3.4 Maintainability
5.3.5 Usability
6. Business Rules
7. Supporting Information
8. To be Determined List

such as:
The various modes of operations in the user
organization
Periods of interactive operations and periods of
unattended operations
Data processing support functions
Backup and recovery operations
Provide a summary of the major functions that the software will
perform. This normally contains the list functionality of the
system in the language of the customer.
This section divides the requirements into different sections for
development and delivery. (DFD)
Provide a data model to define data elements and their
relationships in the system. (use case, class diagram, package
diagram, deployment diagram)
Describe those general characteristics of the intended users of
the product. (user account privileges)
Provide a general description of any other items that will limit
the developer's options (system limitation vis--vis standard)
Specify design constraints that can be imposed by other
standards, hardware limitations, etc. (hardware limitation vis-vis standard)
Specify the requirements derived from existing standards or
regulations (International Standards Organization (ISO) 9126
List each of the factors that affect the requirements stated in the
SRS. These factors are not design constraints on the software
but are, rather, any changes to them that can affect the
requirements in the SRS. (Difficulties encountered in both
software and hardware during the development)
This section contains all the software requirements at a level of
detail sufficient to enable designers to design a system to satisfy
those requirements, and testers to test that the system satisfies
those requirements.
This subsection specifies the requirements placed on the
software or on human interaction with the software, as a
whole.
Date and Time Key Test Issues
Test activities
This section specifies the logical requirements for any
information that is to be placed into a database. (database
design)
This section describes quality attributes of the system and the
characteristics the system must possess, but that pervade (or
cross-cut) the design (make a questionnaire with a rating scale
in evaluating a system using the variables listed below)
Specify the factors required to establish the required
reliability of the software system at time of delivery.
Specify the factors required to guarantee a defined availability
level for the entire system such as checkpoint, recovery, and
restart.
Specify the factors that would protect the software from
accidental or malicious access, use, modification, destruction,
or disclosure.
Specify attributes of software that relate to the ease of
maintenance of the software itself.
Specify attributes of software that relate to the ease of
maintenance of the software itself.
This section lists all business rules and will serve as a master
list of all business rules.
The supporting information makes the SRS easier to use. This
includes appendices, tables, diagrams, etc.
This section lists the open requirements issues that remain to
be resolved, including TBDs, pending decisions, information
that is needed, conflicts awaiting resolution, and the like.

January 28, 2014

February 4, 2014
February 11, 2013
February 11, 2013

Note: All project deliverables must be submitted on the dates stated above. Late projects will not be accepted.

LANY L. MACEDA
Asst. Prof. 1