Software Requirement Specification for GymnoPro 1.

1

Software Requirements Specification
ON

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

............... Introduction...........................iv 2.....................................2....................3............................................................................iii 1................................................................. Use Case: Make new entry...........................................................1.x 3........................................4.....................................iv 2........................... Admin/operator login................ Glossary........................................................................vi Figure 4 Update entry............. Detailed non-functional requirements................4................... Use cases...................................................ix 3.xi 3...............1.............................. Non-functional requirements.......................................................iv The Gymno PRO Application will be run only on desktop....................................................................Software Requirement Specification for GymnoPro 1..............2.2...................................................................1 Table of Contents Table of Contents.........................................................................................xi 3........................................ Use Case: Update entry. Update a entry.........................xiii Table of Figures Figure 1 System Design............ix ...................4.......... References....................................................................................iii 1........................3........................iv Figure 2 Admin and operator login............................................................................................2.....................2................... Use Case: Delete entry....................... Make new entry.............................................................................................................................3................................2...............................................................................................................................................1..5................................................. Functional requirements definitions........................0........................... Where logical unit has its own functions.................................................................................................................................................................... Purpose..................................................iii 1......................................................................x 3.............................................ix 2............................... Functional requirements definitions........4 Delete an Entry.............v Figure 3 Make new entry............................................................................................................................................................xii 3.............................. Fig 1 shows the complete overview of system.........0..............................4..........................3.................................... External interface specifications.................................iii 1............viii 2............... Reminder.............xi 3......... Use Case: Reminder........................................................... Scope of project............................................................................................................................................... The function between two units is to load and retrieve data....... Requirement specifications.....................................................................................1.............................................................................xii 3..........................3...................................................................................viii Figure 6 Reminder..............................................................................2....................................... Use Case: Admin/Operator login............................5................. System Evolution... Overall description..........................2............................................................. Functional Requirements......v 2..........0...................1....... It consists of two basic unit namely logical unit and Database...............................................iii 1.............................................................................................................................................................................v 2.................. Document overview...................................................ii 1....2..................................................vii Figure 5 Delete entry......................................vi 2...............vii 2... System environment.......................................................2..............................................2..3......................................................................................x 3....................................................................................3.............3...............................................................................................3........................................................................................ Operators are responsible for inserting and updating information and view retrieved information..............2.....................................................................................................5.....................................................v 2...........x 3.....3..........................................................................v 2..............

0.1 1.NET and XML. James Groff. easy to maintain data about costumer and provide any information.Student Guide Murach's SQL Server 2008 for developers ISBN 978-1-89-077451-6 Bryan syverson and Joel murach SQL The Complete Reference. Purpose 1. References  Book: Object oriented programming in java. Scope of project Gymno PRO 1. operator or trainee 1. Object oriented software engineering. Glossary Term ID Msg SQL Entry Definition Identification number Message Structured query language Object of entity customer.3. Third Edition ISBN: 978-0-07-159256-7 Paul Weinberg.1 1. Introduction This Software Requirements Specification provides a complete description of all the functions and specifications of the GymnoPRO 1. Main aim behind development of this application is make gym free from bulky register and make it paper free.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.4.1.Andrew Oppel iii . 1. Developing Database Application using ADO. statistics and report in one click.Software Requirement Specification for GymnoPro 1.2.

Requirements Specification section. It also updates data automatically on some instance. of this document is written primarily for the developers and describes in technical terms the details of the functionality of the product. 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. Both sections of the document describe the same software product in its entirety. 2. The third chapter.0. the Overall Description section.5. The system focuses on providing user friendly environment for the employees to interact with the system. 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. Separate roles are assigned to each individuals in the gym staff to interact with the system based on their designation. The system also provides data security. And also retrieve the date on demand from database show in report. System environment Figure 1 System Design iv .1 1.Software Requirement Specification for GymnoPro 1. 2. but are intended for different audiences and thus use different language. Document overview The next chapter.1. It also allowed updating data manually.

2.1 The Gymno PRO Application will be run only on desktop. Where logical unit has its own functions.Software Requirement Specification for GymnoPro 1. Other functionality in this page is make new entry.1. Functional requirements definitions 2. The function between two units is to load and retrieve data. The reminder reminds us about the payment date of customer on basis of joining date or updated last payment date.2. team. Use cases The system will consist of welcome page with two login selections namely operator and admin and some information about software Development Company. what services it will provide to the user.3. v . button to go back last window and exit button to close the application..3. and delete entry and reminder. Use Case: Admin/Operator login Figure 2 Admin and operator login. update entry. All windows have button to come back to main window. 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.2. 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. Brief Description The starting window is waiting for login either as operator or admin. Nonfunctional (supplementary) requirements pertain to other information needed to produce the correct system and are detailed separately. Functional requirements definitions Functional Requirements are those that refer to the functionality of the system. 2. i. It consists of two basic unit namely logical unit and Database.e. And delete function just ask id or name to indentify entry and ask once confirmation and then delete it permanently. Operators are responsible for inserting and updating information and view retrieved information. 2. Fig 1 shows the complete overview of system.

Software Requirement Specification for GymnoPro 1. the admin or operator need to insert there Id & respected password.1 Initial step-by-step description For this use case to be initiated. System check inserted id and password in data base 2. 1.3. If id & password correct then it allow them to use respected functionality as type of user. And select the type of user. vi .2. Use Case: Make new entry Figure 3 Make new entry Brief Description: The Admin/Operator can make new entry of operator and customer. Reference SRS 3.1 2.2.

System will provide the form to fill information about new entry. vii .3. After completion of form press enter to save data and get confirmation of new entry 4.Software Requirement Specification for GymnoPro 1. Here admin can make new entry of any type but operator can’t make new entry another operator.3. Use Case: Update entry Figure 4 Update entry Brief Description: Admin/operator can update entry. Reference SRS 3.1 Initial step-by-step description: 1. 2. 3.2.2 2. The user and admin need to select type of new entry.

Figure 5 Delete entry Brief Description: Admin can delete all type of entry but operator can’t delete entry of another entry viii . Use Case: Delete entry.2.4. Admin/Operator selects the type of entry and insert id/name to identify entry.1 Initial step-by-step description: 1. Fill the information in provided form which need to update 3. Reference: SRS 3. 2.Software Requirement Specification for GymnoPro 1.3 2. Submit the form and get the confirmation msg.3.

Reference: SRS 3.Software Requirement Specification for GymnoPro 1. 3.2. Non-functional requirements There are requirements that are not functional in nature. Specifically. The application must be compatible with both the windows7 and windowsXP OS. Admin/operator chose option of reminder 2.2. The performance must same on different version of OS.3. ix . Use Case: Reminder Figure 6 Reminder Brief description: Reminder gives information about customer pay date Initial step-by-step description: 1.4 2.4. these are the constraints the system must work within. Give confirmation response to system when ask. Insert the ID/Name to identify entry in database.1 Initial step-by-step description: 1. Reference: SRS 3. Select type of entry to be delete 2.5 2.5. System will provide list of customer according to logic implemented to reminder fee date.

6 GHz CPU. 7200 RPM or higher hard disk) 3.1. Requirement specifications 3. 1280x1024 display.1 3. Functional Requirements 3.2 GHz or higher CPU. 1024x768 display. 5400 RPM hard disk (Recommended: 2. External interface specifications 3.1.Software Requirement Specification for GymnoPro 1. Windows7 or above  Language : Java  Application : Netbeans 7/ecilips 3. Use Case Name: Inputs Admin/operator login The admin will have to have/create a unique login/password for self and x .0. Details of SOFTWARE and SOFTWARE LANGUAGE Used: Front end : Java interface  Back end : Microsoft SQL server  Operating system : Windows Xp.1.2.2.1. Hardware Requirements: Minimum: 1. 384 MB RAM. 1024 MB or more RAM.1.2. Admin/operator login.

2.2.2. 3. Find out matching id /name entry and ask for confirmation. Collect confirmation decision and proceed further.1 operator to Access their individual functionality. Confirmation message of deleted entry or other activity as per confirmation insider ask before. Check and validate information and save it in database Confirmation about created entry and saved data in database Processing Outputs 3. Which also help to maintain log. Update a entry Use Case Name: Inputs processing Update a entry Entry type. Output 3.2. 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. information related to that entry.3. Make new entry Use Case Name: Inputs New entry Type of entry.Software Requirement Specification for GymnoPro 1. The login/password will have certain parameters that must be met to ensure safety or personal information.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. Confirmation message about updated data. Processing Output xi . id/name/data to be update Check and validate data and save/replace data.

1 3.2. Reminder Use Case Name: Input Process Reminder Press reminder button Find out the entry who need to pay fees. 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.5. Detailed non-functional requirements Following are some attribute of database that may required in system database. or due date has been exceed on the basis of last date of fee paid or date of joining.Software Requirement Specification for GymnoPro 1.3. List of all entry comes in function logic of reminder Output 3. Fields marked with‘#’ can be visible or not visible and is determined by the Admin xii .

System Evolution In the future this system will be update to allow user to create account online from there Computer Masters Program to join.Software Requirement Specification for GymnoPro 1.1 3. news and guide lines to customer.4. And also will provide online tips. xiii .

Sign up to vote on this title
UsefulNot useful