Sunteți pe pagina 1din 13

Software Requirement Specification for GymnoPro 1.

Software Requirements Specification


ON

GymnoPRO 1.1
(Gym Data Base)
BY
Vinayak R. Khedkar.
Susmit Karmalakar.
Ritesh Lad.
Keshaw Jha.

Software Requirement Specification for GymnoPro 1.1

Table of Contents
Table of Contents.....................................................................................................................................................ii
1.0. Purpose............................................................................................................................................................iii
1.1. Introduction.................................................................................................................................................iii
1.2. Scope of project...........................................................................................................................................iii
1.3. Glossary.......................................................................................................................................................iii
1.4. References...................................................................................................................................................iii
1.5. Document overview.....................................................................................................................................iv
2.0. Overall description...........................................................................................................................................iv
2.1. System environment....................................................................................................................................iv
The Gymno PRO Application will be run only on desktop. Fig 1 shows the complete overview of
system. It consists of two basic unit namely logical unit and Database. The function between two units is to
load and retrieve data. Where logical unit has its own functions. Operators are responsible for inserting and
updating information and view retrieved information.2.2. Functional requirements definitions........................v
2.2. Functional requirements definitions.............................................................................................................v
2.3. Use cases.......................................................................................................................................................v
2.3.1. Use Case: Admin/Operator login...........................................................................................................v
2.3.2. Use Case: Make new entry...................................................................................................................vi
2.3.3. Use Case: Update entry.......................................................................................................................vii
2.3.4. Use Case: Delete entry.......................................................................................................................viii
2.3.5. Use Case: Reminder..............................................................................................................................ix
2.4. Non-functional requirements.......................................................................................................................ix
3.0. Requirement specifications...............................................................................................................................x
3.1. External interface specifications...................................................................................................................x
3.2. Functional Requirements..............................................................................................................................x
3.2.1. Admin/operator login.............................................................................................................................x
3.2.2. Make new entry....................................................................................................................................xi
3.2.3. Update a entry.......................................................................................................................................xi
3.2.4 Delete an Entry......................................................................................................................................xi
3.2.5. Reminder..............................................................................................................................................xii
3.3. Detailed non-functional requirements........................................................................................................xii
3.4. System Evolution.......................................................................................................................................xiii

Table of Figures
Figure 1 System Design.................................................................................iv
Figure 2 Admin and operator login..........................................................................................................................v
Figure 3 Make new entry........................................................................................................................................vi
Figure 4 Update entry............................................................................................................................................vii
Figure 5 Delete entry............................................................................................................................................viii
Figure 6 Reminder..................................................................................................................................................ix

Software Requirement Specification for GymnoPro 1.1

1.0. Purpose
1.1. Introduction
This Software Requirements Specification provides a complete description of all the
functions and specifications of the GymnoPRO 1.1
1.2. Scope of project
Gymno PRO 1.1 is designed to run on the desktop and to allow to maintain all data entry
of Gym in efficient way and user friendly graphical user interface make it simple to use and
update an existing database and entry. Main aim behind development of this application is
make gym free from bulky register and make it paper free, easy to maintain data about
costumer and provide any information, statistics and report in one click.
1.3. Glossary
Term
ID
Msg
SQL
Entry

Definition
Identification number
Message
Structured query language
Object of entity customer, operator or
trainee

1.4. References
Book: Object oriented programming in java.
Object oriented software engineering.
Developing Database Application using ADO.NET and XML,Student Guide
Murach's SQL Server 2008 for developers ISBN 978-1-89-077451-6
Bryan syverson and Joel murach
SQL The Complete Reference, Third Edition ISBN: 978-0-07-159256-7
Paul Weinberg, James Groff,Andrew Oppel

iii

Software Requirement Specification for GymnoPro 1.1

1.5. Document overview


The next chapter, the Overall Description section, of this document gives an overview
of the functionality of the product. It describes the informal requirements and is used to
establish a context for the technical requirements specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written
primarily for the developers and describes in technical terms the details of the functionality of
the product.
Both sections of the document describe the same software product in its entirety, but
are intended for different audiences and thus use different language.

2.0. Overall description


The Gymno PRO is a Desktop application which collects data from front end and
saved it in to database in well organized manner. And also retrieve the date on demand from
database show in report. It also allowed updating data manually. It also updates data
automatically on some instance. The system also provides data security. Separate roles are
assigned to each individuals in the gym staff to interact with the system based on their
designation. The system focuses on providing user friendly environment for the employees to
interact with the system.
2.1. System environment

Figure 1 System Design

iv

Software Requirement Specification for GymnoPro 1.1


The Gymno PRO Application will be run only on desktop. Fig 1 shows the complete
overview of system. It consists of two basic unit namely logical unit and Database. The
function between two units is to load and retrieve data. Where logical unit has its own
functions. Operators are responsible for inserting and updating information and view
retrieved information.2.2. Functional requirements definitions
2.2. Functional requirements definitions
Functional Requirements are those that refer to the functionality of the system, i.e.,
what services it will provide to the user. Nonfunctional (supplementary) requirements pertain
to other information needed to produce the correct system and are detailed separately.
2.3. Use cases
The system will consist of welcome page with two login selections namely operator
and admin and some information about software Development Company, team, information
about other product and aim of company
The next page after login via both ways having same functionality only difference is
that operator does not have Wright to make new entry of operator. Other functionality in this
page is make new entry, update entry, and delete entry and reminder.
The function make new entry get information about type of entry and according to type
of entry it ask respective information
Where the update function ask unique id or name to identify entry and provide the form
to fill the information which we want to update. And delete function just ask id or name to
indentify entry and ask once confirmation and then delete it permanently.
The reminder reminds us about the payment date of customer on basis of joining date
or updated last payment date.
All windows have button to come back to main window, button to go back last window
and exit button to close the application.
2.3.1. Use Case: Admin/Operator login

Figure 2 Admin and operator login.


Brief Description
The starting window is waiting for login either as operator or admin.

Software Requirement Specification for GymnoPro 1.1


Initial step-by-step description
For this use case to be initiated, the admin or operator need to insert there Id & respected
password. And select the type of user.
1. System check inserted id and password in data base
2. If id & password correct then it allow them to use respected functionality as type of user.
Reference SRS 3.2.1
2.3.2. Use Case: Make new entry

Figure 3 Make new entry


Brief Description:
The Admin/Operator can make new entry of operator and customer.

vi

Software Requirement Specification for GymnoPro 1.1


Initial step-by-step description:
1. The user and admin need to select type of new entry.
2. System will provide the form to fill information about new entry.
3. After completion of form press enter to save data and get confirmation of new entry
4. Here admin can make new entry of any type but operator cant make new entry another
operator.
Reference SRS 3.2.2
2.3.3. Use Case: Update entry

Figure 4 Update entry


Brief Description:
Admin/operator can update entry.
vii

Software Requirement Specification for GymnoPro 1.1

Initial step-by-step description:


1. Admin/Operator selects the type of entry and insert id/name to identify entry.
2. Fill the information in provided form which need to update
3. Submit the form and get the confirmation msg.
Reference: SRS 3.2.3
2.3.4. Use Case: Delete entry.

Figure 5 Delete entry


Brief Description:
Admin can delete all type of entry but operator cant delete entry of another entry

viii

Software Requirement Specification for GymnoPro 1.1


Initial step-by-step description:
1. Select type of entry to be delete
2. Insert the ID/Name to identify entry in database.
3. Give confirmation response to system when ask.
Reference: SRS 3.2.4
2.3.5. Use Case: Reminder

Figure 6 Reminder
Brief description:
Reminder gives information about customer pay date
Initial step-by-step description:
1. Admin/operator chose option of reminder
2. System will provide list of customer according to logic implemented to reminder fee date.
Reference: SRS 3.2.5
2.4. Non-functional requirements
There are requirements that are not functional in nature. Specifically, these are the
constraints the system must work within.
The application must be compatible with both the windows7 and windowsXP OS. The
performance must same on different version of OS.

ix

Software Requirement Specification for GymnoPro 1.1

3.0. Requirement specifications


3.1. External interface specifications
3.1.1. Details of SOFTWARE and SOFTWARE LANGUAGE Used: Front end
:
Java interface
Back end

Microsoft SQL server

Operating system

Windows Xp, Windows7 or above

Language

Java

Application

Netbeans 7/ecilips

3.1.2. Hardware Requirements: Minimum: 1.6 GHz CPU, 384 MB RAM, 1024x768 display, 5400 RPM hard
disk
(Recommended: 2.2 GHz or higher CPU, 1024 MB or more RAM, 1280x1024 display,
7200 RPM or higher hard disk)

3.2. Functional Requirements


3.2.1. Admin/operator login.
Use Case Name:
Inputs

Admin/operator login
The admin will have to have/create a
unique login/password for self and
x

Software Requirement Specification for GymnoPro 1.1


operator to
Access their individual functionality.
The login/password will have certain
parameters that must be met to
ensure safety or personal
information. Which also help to
maintain log.
Processing

The users data will be


accessed/created using MySQL
database with encryption

Outputs

The output will allow the user to


create/access System functionality.

3.2.2. Make new entry


Use Case Name:
Inputs

New entry
Type of entry, information related to that
entry.
Check and validate information and save it in
database
Confirmation about created entry and saved
data in database

Processing
Outputs

3.2.3. Update a entry


Use Case Name:
Inputs
processing

Update a entry
Entry type, id/name/data to be update
Check and validate data and save/replace
data.
Confirmation message about updated data.

Output
3.2.4 Delete an Entry
Use Case Name:
Input

Delete an Entry
Id/name which identify the entry and
confirmation of right entry when system ask.
Find out matching id /name entry and ask for
confirmation. Collect confirmation decision
and proceed further.
Confirmation message of deleted entry or
other activity as per confirmation insider ask
before.

Processing
Output

xi

Software Requirement Specification for GymnoPro 1.1


3.2.5. Reminder
Use Case Name:
Input
Process

Reminder
Press reminder button
Find out the entry who need to pay fees, or
due date has been exceed on the basis of last
date of fee paid or date of joining.
List of all entry comes in function logic of
reminder

Output

3.3. Detailed non-functional requirements


Following are some attribute of database that may required in system database.
Attribute Name
LastName*#
FirstName*#
MaidenName*#
Address1*#
Address2#
City*#
State*#
Zip*#
Year*#
Date of joining*#
Type of course*#
Salary*#
Workout*#
EmailAddress#
Other bio ionformation*
Password*#
Username*#

Attribute Type
String
String
String
String
String
String
String
Int
Int
String
String
String
String
String
Boolean
String
Boolean

Attribute Size
30
30
30
50
50
30
2
6
4
50
30
50
50
20
1
10
1

Fields marked with an * are required fields. Fields marked with# can be visible or
not visible and is determined by the Admin

xii

Software Requirement Specification for GymnoPro 1.1


3.4. System Evolution
In the future this system will be update to allow user to create account online from there
Computer Masters Program to join. And also will provide online tips, news and guide lines to
customer.

xiii

S-ar putea să vă placă și