Software Requirements

Specification
For

Overhauling Inquiry &

Management Software

Prepared by Payal Singh

C07338

Cse, 6th Sem

CCET
Table of Contents
1. Introduction................................................................................................................................1
1.1 Purpose ............................................................................................................................................... 1
1.2 Document Conventions....................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions..................................................................................... 1
1.4 Project Scope....................................................................................................................................... 1
1.5 References........................................................................................................................................... 1
1.6 Glossary.............................................................................................................................................. 2
2. Overall Description....................................................................................................................3
2.1 Product Perspective............................................................................................................................. 3
2.2 Product Features.................................................................................................................................. 3
2.3 User Classes and Characteristics........................................................................................................ 4
2.4 Operating Environment....................................................................................................................... 4
2.5 Design and Implementation Constraints............................................................................................. 4
3. System Features......................................................................................................................... 5
3.1 Processing Queries.............................................................................................................................. 5
3.2 Security............................................................................................................................................... 5
4. External Interface Requirements............................................................................................. 6
4.1 User Interfaces.................................................................................................................................... 6
4.2 Hardware Interfaces............................................................................................................................ 7
Server: Pentium 4 or higher speed processors (versions) with a minimum of 256MB RAM and Hard
Disk of 60 GB or more.............................................................................................................................. 7
Client: Minimum of Pentium 4 processor (Recommended Higher) with 64 MB RAM recommended
128 MB RAM for faster performance with a Hard Disk of 4.3GB or more............................................7
Input Device: It is used to enter data and instructions in the computer. a ) It
serves as an interface between user and computer b ) It converts
data and instructions in machine language. c ) It accepts data and
instructions from outside world................................................................................................................ 7
Output Unit: It provides the information and result of computation to the outside world. Generally
VDU is used as output device. a) It accepts the
results produced by computer. b) It converts the machine
language into human readable form. c) It supplies converted result to the
outside world............................................................................................................................................. 7
4.3 Software Interfaces............................................................................................................................. 7
4.4 Communications Interfaces................................................................................................................. 7
5. Other Nonfunctional Requirements.........................................................................................8
5.1 Performance Requirements................................................................................................................. 8
5.2 Safety Requirements........................................................................................................................... 8
5.3 Security Requirements........................................................................................................................ 8
The system contains highly sensitive information about the administrator’s account status. So this
information is given to the particular administrator who is eligible and authorized to view or change
his/her personal information, and also make changes in the database of the Overhauling Inquiry and
Management Software. For this, the utility like username and password is provided for securing the
sensitive information............................................................................................................................. 8
5.4 Software Quality Attributes................................................................................................................ 8
6. Other Requirements.................................................................................................................. 9
6.1 Database Requirements....................................................................................................................... 9
Revision History
Name Date Reason For Changes Version
Software Requirements Specification for Overhauling Inquiry & Management Software Page 1

1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description of the Overhauling Inquiry &
Management Software. It will explain the purpose and features of the system, the interfaces of
the system, what the system will do, the constraints under which it must operate and how
the system will react to external stimuli. This document is intended for both the
stakeholders and the developers of the system.

1.2 Document Conventions

Every requirement statement is to have its own priority. Moreover, the standard conventions
followed throughout this SRS is a uniform font, that is Arial, and a font size 11 for paragraphs,
and size 14 for Sub-headings.

1.3 Intended Audience and Reading Suggestions

The intended audience for this SRS is mainly the developers of the software, and the respective
group heads of 3 BRD, Air Force Station, Chandigarh. For the developers, it is suggested that
they build, or sketch a blueprint alongside reading the requirements. As for the management of 3
BRD, it is suggested that a developer is present as they read this SRS so further elucidate the
highlights and major requirements of the proposed software.

1.4 Project Scope

The scope or aim of the Overhauling Inquiry and Management Software is to enable the
respective group heads of Engine Division, Admin, Aircraft Division and Logistics Division to keep
a track of each and every part of the helicopter being overhauled. It is often the case in the BRD
that a particular mechanical, electrical or scientific part dismantled from the helicopter is lying in
the hangers for months, without being repaired and made fit for use. With the creation of this
software, the group heads will be able to track the parts of respective helicopters, along with the
dates of dismantling and dispatch and arrival between various divisions, hence saving a lot of
time and contributing to the efficiency and budget of 3 BRD.

1.5 References

1. .Net with c# - Microsoft Publications

2. Asp.net 3.5 – William Sanders
Software Requirements Specification for Overhauling Inquiry & Management Software Page 2

1.6 Glossary
Software Requirements Specification for Overhauling Inquiry & Management Software Page 3

2. Overall Description
The project is an Asp.net web site, which would be deployed over the Secures LAN of 3 BRD.
The web site will consist of exclusive user accounts based on the position of the user, like an
admin access by the group heads, and a data entry view for the rest of the officials. A proper and
user friendly Graphical User Interface would be provided for the Administrators, while the data
entry operator will also have access to the backend of the software, only on the Server node.

2.1 Product Perspective

The need for this product was being felt among the management officials of 3 BRD for quite
sometime. But, due to the lack of Software Engineers in the industry, the officers were not able to
point out the exact solution for correcting the long time delays between dismantling and
corressponding repairs of specific parts. Hence, this software was perceived as a panacea for all
the inefficiencies presently prevalent in the industry.

2.2 Product Features

The salient features of this software are as follows :-

a.) Provision for Data Warehousing to maintain the history and record of all the helicopter parts
that come for overhauling, along with their date of manufacture and time to live (TTL).

b.) Separate interface for separate types of Overhauling procedures, like repair, functional
testing, and DI/PWR/FBIR repair.

c.) Provision for data entry audit facilities for enhanced security of data entry operations, with
records storing the authenticated user ID, along with the date and time of the modification or
entry.

d.) Login facilities qith independent and separate User ID for group heads, and other officials to
provide varying levels of access throughout the software.
Software Requirements Specification for Overhauling Inquiry & Management Software Page 4

e.) Facility to view group data trends, in the form of Pie charts and Crystal Reports.

f.) A huge set of queries, whose results will be accessible just by a single click for the managers
to view the dismantled parts and overhauling progress.

2.3 User Classes and Characteristics

The following three classes of users exist :-

 Administrator/Commanding Officer :-

1. Has access rights to all pages and all tools of the software.
2. Has access rights to audits on the back-end.
3. Has the right to revoke or annul any user ID authentication.

 Group Heads/Managers:-

1. Have access rights to the inquiry and query page pertaining to their respective divisions.
2. Have access to customized graph and crystal reports generation.

 Data Entry Operators:-

1. Have access to only the data entry forms.

2. Do not have access to forms pertaining to other divisions but their own.
3. Do not have access to query generation and customized reports.

2.4 Operating Environment

The software will operate on Desktop systems connected to the secured LAN of 3 BRD technical
area. The industry has majority of HP desktops with 4 GB ram and 350 GB HDD, 2.0GHz Intel
Core 2 Duo Processors.

2.5 Design and Implementation Constraints

Design Constraints :-

1. Every helicopter consists of thousands of parts, so categorization and record-keeping of each

one is a daunting task. Hence, developers will first aim at implementing the basic framework by
including the most prominent parts first. Gradually, other parts would be incorporated.

2.The software needs to be completely error-free, as its proper functioning is critical to the
progress of military overhauling of helicopters.

Implemetation Constraints:-

1. The deployment of the software over the LAN will require considerable effort as access to
restricted technical area is not provided often. Special permission would be required to implement
the software in the technical area.
Software Requirements Specification for Overhauling Inquiry & Management Software Page 5

2. The . Net framework will have to be installed on all desktops.

3. System Features

3.1 Processing Queries

3.1.1 Description and Priority – This is the most important feature of the software, as the primary
aim of the software is to provide the management with direct access to the progress of the
overhauling process. Thus, it has been given Priority 1.

3.1.2 Stimulus/Response Sequences -

 User (admin. Or group heads) select the query they want to process from a given list of
queries.
 The page for customized query opens up, where user will have to select various parameters
depending on what data he wants.
 The query is processed on the server end and the results are sent back to the user on the
web-page.

3.1.3 Functional Requirements -

REQ.1 : The availability or the options of the various graphs to choose from, such as pie or bar
graphs.

REQ.2 : The provision of Crystal Report Generation for specific queries.

REQ.3 : A normalized and well-related database, that can give the query result efficiently and
accurately.

3.2 Security

3.2.1 Description and Priority – This feature is almost at par with the precious feature, and thus is
2nd in the priority list. Since the software is related to critical military related overhauling of
transport helicopters, namely Mi-8 and Mi-17, any slack or inconsistency, unauthorized
modification or even unauthenticated access to information in the databases could lead to serious
repurcussions.

3.1.2 Stimulus/Response Sequences -

 User is required to enter his/her Login user ID and password to get access to any page of the
software.
 If user is unable to login after 3 attempts, the software shuts down immediately and reports to
the server officer-in-charge.
 Any new entry of updation of existing records is duly recorded in the audit table of the database
with the user ID and date & time.

3.1.3 Functional Requirements -

Software Requirements Specification for Overhauling Inquiry & Management Software Page 6

REQ.1 : A login table with fields User ID and password belonging to each group head, the
administrator of commanding officer, and 4 or 5 data entry operators from authorized nodes only.

REQ.2 : An audit table in which only automatic records can be added whenever any modification is
made by any of the data entry operators. Modification to the table values is disabled for everyone.

REQ.3 : After a maximum of 3 attempts to log in, the software should shut down automatically.

4. External Interface Requirements

4.1 User Interfaces

 Graphical User Interface(GUI) needs to be provided for the front-end. That is, all the web
pages included in the web site , such as the Login page, Queries page, Graph generator
page, Data entry page needs to have user-friendly and intiutive controls and operations.

 For the server official having access to database audits, it should be ensured that direct entry
into the database is prohibited.

 In case of an connection error, all the entry processes that are midway should immediately be
rollbacked.
Software Requirements Specification for Overhauling Inquiry & Management Software Page 7

4.2 Hardware Interfaces

 Server: Pentium 4 or higher speed processors (versions) with a minimum of 256MB RAM and
Hard Disk of 60 GB or more.

 Client: Minimum of Pentium 4 processor (Recommended Higher) with 64 MB RAM

recommended 128 MB RAM for faster performance with a Hard Disk of 4.3GB or more.

 Input Device: It is used to enter data and instructions in the computer.

a ) It serves as an interface between user and computer
b ) It converts data and instructions in machine language.
c ) It accepts data and instructions from outside world

 Output Unit: It provides the information and result of computation to the outside world.
Generally VDU is used as output device.
a) It accepts the results produced by computer.
b) It converts the machine language into human readable form.
c) It supplies converted result to the outside world.

 Secondary Storage Devices: The memory of C.P.U is too limited and too expensive to provide
the entire data storage .So secondary storage devices are used. Example-Hard Disk, Floppy Disk

4.3 Software Interfaces

 Operating System :WindowsXP or higher

 Database :SQL-Server 2005

 Development Tool :Microsoft .Net 3.5

4.4 Communications Interfaces

 Local Area Network

 .Net framework on the client computers.

 Sql Server 2005 database on the server, and client side application on all the client
computers.
Software Requirements Specification for Overhauling Inquiry & Management Software Page 8

5. Other Nonfunctional Requirements

5.1 Performance Requirements

Consistency of data and non-redundancy are the major requirements. Any kind of inconsistency
can lead to serious effects in the process of overhauling. Thus, proper and immediate updation
and entry of records to the server is the main aim. Apart from this, locks also need to be
incorporated to ensure consistency in data updation and entry.

5.2 Safety Requirements

The information contained in the backend at the server is highly sensitive. Thus, it needs to be
kept strictly confidential. Thus, primary step in this direction is to allow authentication for only
selected users, that includes the 4 group heads, the Air Officer Commanding, and at the most
four to five data entry operators.

Along with the login authentication required, an audit table will also be maintained which will be
visible only to the server manager and the AOC, hence keeping a strict record of the changes
made to the data and by which user.

5.3 Security Requirements

The system contains highly sensitive information about the administrator’s account status. So this
information is given to the particular administrator who is eligible and authorized to view or
change his/her personal information, and also make changes in the database of the Overhauling
Inquiry and Management Software. For this, the utility like username and password is provided
for securing the sensitive information

5.4 Software Quality Attributes

 Testing tools need to be applied for the verification of the software.

 In addition to this, the validation of the software also needs to be performed.
 The software needs to be thoroughly tested on lines of consistency and integrity of data.
 It needs to be ensured that the connection between the client side front-end and the server-side
backend are working properly.
 The deployment of the software over the LAN needs to be handled very carefully.
Software Requirements Specification for Overhauling Inquiry & Management Software Page 9

6. Other Requirements

6.1 Database Requirements

 Large amount of memory is needed for the storage and warehousing of data in the database.

 Normalization of data tables is to be done to avoid data replication.

 Choose appropriate data types for fields; to save space in the database and improve join
operations.