Detailed Project Description of MindMuscle - Xtreme (Gym Management System).

1. 8/3/2014 MindMuscle-Xtreme
Syed Farjad Zia Zaidi
Syed Farjad Zia Zaidi
Lead Software Engineer
VISTA LINK

2. MindMuscle-Xtreme
i
Revision History
Date Description Author Comments
8/3/2014 1.0 Syed Farjad Zia
Zaidi
Completed

3. MindMuscle-Xtreme
ii
Table of Contents
REVISION HISTORY ................................................................................................................................................I
DOCUMENT APPROVAL.........................................................................................................................................I
INDEX ........................................................................................................................................................................ II
1. INTRODUCTION................................................................................................................................................... 1
1.1 OVERVIEW .......................................................................................................................................................... 1
1.2 PURPOSE ............................................................................................................................................................. 1
1.3 SCOPE ................................................................................................................................................................. 1
1.4 REFERENCES ....................................................................................................................................................... 1
2. GENERAL DESCRIPTION.................................................................................................................................. 1
2.1 PRODUCT PERSPECTIVE....................................................................................................................................... 1
2.2 USER CHARACTERISTICS..................................................................................................................................... 1
2.3 ASSUMPTIONS AND DEPENDENCIES .................................................................................................................... 1
3. SPECIFIC REQUIREMENTS .............................................................................................................................. 2
3.1 EXTERNAL INTERFACE REQUIREMENTS .............................................................................................................. 2
3.1.1 User Interfaces ........................................................................................................................................... 2
3.1.2 Hardware Interfaces................................................................................................................................... 2
3.1.3 Software Interfaces..................................................................................................................................... 2
3.1.4 Communications Interfaces........................................................................................................................ 2
3.2 NON-FUNCTIONAL REQUIREMENTS .................................................................................................................... 2
3.5.1 Performance & Reliability ......................................................................................................................... 2
3.5.6 System Modifications.................................................................................................................................. 2
3.3 LOGICAL DATABASE REQUIREMENTS ................................................................................................................. 2
3.4 OTHER REQUIREMENTS....................................................................................................................................... 2
3.9.1 System Requirements.................................................................................................................................. 2
3.9.2 Software Requirements............................................................................................................................... 2
4. DESIGN PHASE..................................................................................................................................................... 3
4.1 ENTITY RELATIONSHIP DIAGRAM ....................................................................................................................... 3
4.1.1 Conceptual Schema .................................................................................................................................... 3
4.1.2 Physical Schema......................................................................................................................................... 4
4.2 DATA FLOW DIAGRAMS (DFD) .......................................................................................................................... 5
4.2.1 Context Level Diagram............................................................................................................................... 5
4.2.2 Level 1 DFD............................................................................................................................................... 5
4.2.3 Level 2 DFD............................................................................................................................................... 6
4.3 SCREENSHOTS .................................................................................................................................................... 6
4.3.1 Login Page ................................................................................................................................................. 6
4.3.2 Member Information................................................................................................................................... 7
4.3.3 Instructor Information................................................................................................................................ 7
4.3.4 Product Information/InventoryManagement.............................................................................................. 8
4.3.5 Gym Staff Information................................................................................................................................ 8
4.3.6 Equipment Information............................................................................................................................... 9
4.3.7 Supplier Information .................................................................................................................................. 9
4.3.8 Competition Information .......................................................................................................................... 10
4.3.9 Eligible Members for Competition ........................................................................................................... 10
4.3.10 Charts..................................................................................................................................................... 11
4.3.11 Reports ................................................................................................................................................... 12

4. MindMuscle-Xtreme
1
1. Introduction
This document is project report for a Gym Management System “MindMuscle - Xtreme”, the improved
version of “MindMuscle - Classic”.
1.1 Overview
The Gym Management requires a system that will handle all the necessary and minute details easily and proper
database security accordingly to the user. They requires software, which will store data about members, employees,
products, payroll, receipts of members etc. & all transactions that occur in Gym and an easy to use graphical
user interface(GUI).
1.2 Purpose
 The main objective of the project is to design and develop a user friendly system.
 Easy to use and efficient computerized system.
 To develop an accurate and flexible system, it will eliminate data redundancy.
 Computerization can be helpful as means of saving time & money.
 To provide better graphical user interface.
 Less chances of information leakage.
 Provides security to data by using login & password.
1.3 Scope
 Store information of members, instructors, employees, machines, weights, supplements and medicines.
 Check validity of information provided by user.
 Use unique Id’s for members, instructors, employees, machines.
 Manage all the data efficiently
1.3 References
SRS document Template: IEEE guide to Project Report.
2. General Description
2.1 Product Perspective
A.) iGo Figure:
iGo Figure is a software just like the one I am making. It is a very popular and successful gym management
system.
http://www3.igofigure.com/
2.2 User Characteristics
The users to be of my product are gym administrators and they have to manage a gym which is not an easy
task. They need a tool to manage their all their records. They also want to keep track of their purchase/sale
to manage their gym effectively and grow prosper.
2.3 Assumptions and Dependencies
My product can only work on windows operating systems and must have SQL server 2012 and .Net
Framework 4.5 installed. I have made it assuming that the user have a windows operating system and a

5. MindMuscle-Xtreme
2
reasonably fast computer. If user is using a different operating system or has a system that does not fulfill
the minimum requirements of this software then this project may or may not change depending on the
client’s demand.
3. Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
The user interface for my product is based on windows forms. It will be made as easy as possible for the
user.
HELP:
A document or a video tutorial will be provided with the software easily teaching how to use the software.
FEEDBACK:
If there is an error. The user will be provided enough information to guide him in the right path and let him
know what mistake has been made.
3.1.2 Hardware Interfaces
My software should be implemented in a hardware-independent fashion and should not rely on any
particular hardware interfaces. However the computer should be reasonably fast.
3.1.3 Software Interfaces
My project can only run on windows operating system. So the user must have a windows OS and SQL
server 2012 plus .Net Framework 4.5 installed.
3.1.4 Communications Interfaces
No communication interface.
3.2 Non-Functional Requirements
3.2.1 Performance & Reliability
The software will be fairly fast and reliable as saving time is the main aim of this project.
3.2.2 System Modifications
The software will be modified in the future to include the system drivers and detailed system information.
3.2.2 System Security
The software should be secured by using a login authentication.
3.3 Logical Database Requirements
SQL Server 2012
3.4 Other Requirements
3.4.1 System Requirements:
The hardware requirements of this project are:
 Intel Dual Core/Core 2 Duo @ 1.80GHz
 2 GB RAM
 160GB HDD

6. MindMuscle-Xtreme
3
3.4.2 Software Requirements:
The software requirements of this project are:
 Windows Operating System
 .Net Framework 3.5/ .Net Framework 4.5/ .Net Framework 4.5.1
 SQL Server 2012
 Telerik UI for WinForms Installed
 Latest drivers installed
4. Design Phase:
4.1 Entity Relationship Diagram (ERD)
4.1.1 Conceptual Schema

7. MindMuscle-Xtreme
4
4.1.2 Physical Schema

8. MindMuscle-Xtreme
5
4.2 Data Flow Diagrams (DFD)
4.2.1 Context Level DFD:
4.2.2 DFD Level 1:

9. MindMuscle-Xtreme
6
4.2.3 DFD Level 2:
4.3 Screenshots of Software
4.3.1 Login Page

10. MindMuscle-Xtreme
7
4.3.2 Member Information
4.3.3 Instructor Information

11. MindMuscle-Xtreme
8
4.3.4 Product Information/Inventory Management
4.3.5 Employee Information

12. MindMuscle-Xtreme
9
4.3.6 Equipment Information
4.3.7 Supplier Information

13. MindMuscle-Xtreme
10
4.3.8 Competition Information
4.3.9 Eligible Members for Competition

14. MindMuscle-Xtreme
11
4.3.10 Charts

15. MindMuscle-Xtreme
12
4.3.11 Reports