FEATURES OF ANSI STANDARDS

ON SOFTWARE REQUIREMENT
SPECIFICATION

ASSIGNMENT OF SOFTWARE ENGINEERING

18
 INTRODUCTION
ABOUT ANSI:
 American National Standards in which software is intended to be
extracted from the standard and used in implementations of the
standard.

 ANSI is a nonprofits , privately funded membership organization that

coordinates the development of U.S. voluntary national standards and
is the U.S. member body to the International Organization for
Standardization (ISO) and, via the United States National Committee
(USNC), the International Electrotechnical Commission (IEC).

ABOUT SRS :
 SRS is software requirement specification
 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.

SOFTWARE PROJECT MANAGEMENT PLAN:

 Software project management is a science of planning and
leading software projects in which software projects are planned,
implemented, monitored and controlled.
 It removes the ambiguity among the project team members and
leads the software to be built in the time limit and budget limit.
 DETAILS

[ IEEE or ANSI SRS Standard ]

There are some features of ANSI or IEEE standards on SRS :

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Definitions, Acronyms and Abbreviations

1.4 References

1.5 Overview

 Purpose

– delineate the purpose of the particular SRS

– specify the intended audience for the SRS

 Scope

– identify the SW products to be produced by name

– explain what the SW product will do, and if necessary,
what it will not do
– describe the application of the SW being specified. ie.
benefits, objectives, goals as precisely as possible
  Overview

– describe what the rest of the SRS contains

– how the SRS is organized

2.General description:

2.1 Product perspective

2.2 Product function summary

2.3 User characteristics

2.4 General constraints

2.5 Assumptions and dependencies

 Product perspective :

State whether the product is independent and

totally self contained.

If the product is component of a larger system then:

– describe the functions of each component of the

larger system and identify interfaces
– overview of the principal external interfaces of this
product
– overview of HW and peripheral equipment to be used

Give a block diagram showing the major components of

the product, interconnections, and external interfaces.
  Product function:

Provide a summary of functions the SW will perform

The functions should be organized in such a way that

they are understandable by the user

 User Characteristics:

Describe the general characteristics of the eventual users

of the product. (such as educational level, experience and
technical expertise )

3.Specific Requirements

- Functional requirements

- External interface requirements

- Performance requirements

- Design constraints

- Attributes eg. security, availability,

maintainability, transferability/conversion

- Other requirements

 Functional requirements:

Processing

– validation of input data

– exact sequence of operations
– responses to abnormal situations
– any methods (eg. equations, algorithms) to be used to
transform inputs to outputs
  External interface requirement:

User interfaces

Hardware interfaces

Software interfaces

Communications interfaces

 Other requirements

– database: frequency of use, accessing capabilities,

static and dynamic organization, retention
requirements for data
– operations: periods of interactive and unattended
operations, backup, recovery operations
– site adaptation requirements

[Software Project Management Plan]

Resource and Schedule Planning
The project involves having a team dedicated to the project with a team
leader included to oversee the development team. The resources would
be divided into two teams with one team responsible for design and
development and the other team doing the requirements and testing
aspects. The second team would have the functional expertise in mapping
out the requirements as well as translating the requirements into usable
specifications for the first team. Further the expertise of this team is to
be utilized for testing as well as they understand the scope and the
functional aspects.
Network Diagram

Effect of crashing the schedule

In case the schedule is crashed, the requirements phase can be merged
with the design phase with parallel activities. This would involve moving
beyond the normal “waterfall” model of SDLC and instead having an agile
methodology.

Effect of Level loading the resources

The two teams of the resources can be used interchangeably with the
requirements that the skills sets of the resources to be the same.

Risk Assessment
The risk management plan for the project would be having the
following items listed as potential risks and their mitigation
plans:

– Resource risk: divided into two components in terms of

knowledge acquisition and attrition risk. The first component
is mitigated by training and knowledge sharing and the second
component is mitigated by documenting the processes and
knowledge management
– Technology: Any change in technology would pose an
immediate risk to the project and it should be ensured that
proper technology is selected for the same.
 CONCLUSION
This topic introduced the features of ANSI
standards on software requirement
specification .The main objective of this is to
ensure that the product to be developed is
fully understood from all angles .All the
focuses and perspectives are important for
building a high quality product .

REFERENCES
1. http://www.gatherspace.com/static/software_requirement_specification.html

2. http://searchsoftwarequality.techtarget.com/definition/software-requirements-

specification

3. http://agnigarh.tezu.ernet.in/~rosy8/SRS.ppt

4. https://www.managementstudyguide.com/software-project-management.html
SUBMITTED BY:
SUPRIYA SUMAN

ID-151001001018

BATCH –BCS3A.

DATE –:24/03/2018.

The end