Experiment 2

Experiment 2 / Task No.
02
A.1 Aim:
Take any system (e.g. ATM system) and study its system specifications and report the various bugs.
Write the test cases for the same application
A.2 Prerequisite: SRS specification, SE knowledge, OOSE knowledge
A.3 Outcome: SRS specification for the system. It should have the following format.
Table of Contents
1. INTRODUCTION......................................................................................................................................................1
1.1 PURPOSE...............................................................................................................................................................1
1.2 SCOPE...................................................................................................................................................................1
1.3EXISTING SYSTEM
1.4PROPOSED SYSTEM
2. GENERAL DESCRIPTION.......................................................................................................................................2
2.1 PRODUCT FUNCTIONS...........................................................................................................................................2
2.2 USER CHARACTERISTICS......................................................................................................................................2
2.3GENERAL CONSTRAINTS......................................................................................................................................2
3. SPECIFIC REQUIREMENTS....................................................................................................................................2
3.1 EXTERNAL INTERFACE REQUIREMENTS...............................................................................................................3
3.1.1 User Interfaces..............................................................................................................................................3
3.1.2 Hardware Interfaces.....................................................................................................................................3
3.1.3 Software Interfaces.......................................................................................................................................3
3.1.4 Communications Interfaces..........................................................................................................................3
3.2 FUNCTIONAL REQUIREMENTS...............................................................................................................................3
3.2.1 Functional Requirement or Feature #1.........................................................................................................3
3.2.2 Functional Requirement or Feature #2.........................................................................................................3
3.3 NON-FUNCTIONAL REQUIREMENTS......................................................................................................................4
3.5.1 Performance.................................................................................................................................................4
3.5.2 Reliability.....................................................................................................................................................4
3.5.3 Availability...................................................................................................................................................4
3.5.4 Security.........................................................................................................................................................4
3.5.5 Maintainability.............................................................................................................................................4
3.5.6 Portability.....................................................................................................................................................4
A.4 Theory: A software requirements specification (SRS) is a description of a software

system to be developed, laying out functional and non-functional requirements, and may
include a set of use cases that describe interactions the users will have with the software.
Software requirements specification establishes the basis for agreement between customers
and contractors or suppliers (in market-driven projects, these roles may be played by the
marketing and development divisions) on what the software product is to do as well as what it
is not expected to do. Software requirements specification permits a rigorous assessment of
requirements before design can begin and reduces later redesign. It should also provide a
realistic basis for estimating product costs, risks, and schedules.
The software requirements specification document enlists enough and necessary requirements
that are required for the project development. To derive the requirements we need to have
clear and thorough understanding of the products to be developed or being developed. This is
achieved and refined with detailed and continuous communications with the project team and
customer till the completion of the software.
**********************

Experiment 2

Uploaded by

Experiment 2

Uploaded by

Experiment 2 / Task No.

A.2 Prerequisite: SRS specification, SE knowledge, OOSE knowledge

A.4 Theory: A software requirements specification (SRS) is a description of a software

You might also like