Documente Academic
Documente Profesional
Documente Cultură
GymnoPRO 1.1
(Gym Data Base)
BY
Vinayak R. Khedkar.
Susmit Karmalakar.
Ritesh Lad.
Keshaw Jha.
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
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
iv
vi
viii
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
Operating system
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)
Admin/operator login
The admin will have to have/create a
unique login/password for self and
x
Outputs
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
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
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
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
xiii