Professional Documents
Culture Documents
"Gym Managment System": A Minor Project Report On
"Gym Managment System": A Minor Project Report On
MASTER
OF
COMPUTER APPLICATION
By
DINESH KUMAR
Principal
Dr. Namrata Jain Gandhi
1
A
Minor Project Report
on
“GYM MANAGMENT SYSTEM”
Submitted to
MASTER
OF
COMPUTER APPLICATION
By
DINESH KUMAR
2
DECLARATION
NAME OF STUDENT:
DINESH KUMAR
4
ACKNOWLEDGEMENT
From:
DINESH KUMAR : 0705CA183D03
MCA IVSem
5
INDEX
TABLE OF CONTENTS
1. Introduction.
1.1 Introduction of the Project.
1.2 Objectives Of The Project.
2. System Analysis
2.1. Identification Of The Need
2.2. Preliminary Investigation
2.3. Feasibility Study
2.3.1. Technical Feasibility
2.3.2. Economical Feasibility
2.3.3. Operational Feasibility
2.4. Proposed System Functionality
5. Design
5.1. Data Flow Diagram (DFD)
5.2. Database Design
5.3. Entity Relationship Diagram
6. Source Code
7. Screen Layouts
8. Testing
9. Implementation
10. Maintenance
11. Conclusion
12. Bibliography
6
7
SECTION 1
INTRODUCTION
8
INTRODUCTION TO THE PROJECT
9
OBJECTIVES OF THE PROJECT
10
What the Software Provides in this Regard?
The software is capable enough to allow the concerned person to
store and retrieve any type of record with just a single click of
mouse.The software allows Interactive ,Self decribing Graphic User
Interface environment where even standalone users can work very
comfortably and easily.
11
SECTION 2
SYSTEM ANALYSIS
12
System Analysis refers into the process of examining a situation with
the intent of improving it through better procedures and methods.
System Analysis is the process of planning a new System to either
replace or complement an existing system. But before any planning is
done the old system must be thoroughly understood and the
requirements determined. System Analysis, is therefore, the process of
gathering and interpreting facts, diagnosing problems and using the
information to re-comment improvements in the System. Or in other
words, System Analysis means a detailed explanation or description.
Before computerized a system under consideration, it has to be
analyzed. We need to study how it functions currently, what are the
problems, and what are the requirements that the proposed system
should meet.
System Analysis is conducted with the following objectives in mind:
6. Create a system definition that forms the foundation for all the
subsequent engineering work.
13
2.2 Preliminary Investigation
The client set is just a worker(s),who is regularly indulged in
manual maintainence transactions,keeping regular
records,maintaining the records of fine details of members.
Following manual registers are maintained:
Inventory Register:
The register is used to record the details of the
products(supplements,beverages and apparels supplied and
required) such as its ID,Description,Quantity,Price,service date,time
period for which it is under maintainence etc.
14
3. Details of findings :
An outline of the methods and procedures under-taken
by the existing system, followed by coverage of the
objectives and procedures of the candidate system.
Included are also discussions of output reports, file
structures, and costs and benefits of the candidate
system.
15
iv. The cost if nothing changes (i.e. The proposed system
is not developed).
16
2.4 Proposed System Functionality
The proposed system provides the facility to pull the data from
the server using a key (such as id) and get the desired report.
17
SECTION 3
18
Software Engineering
The basic objective of software engineering is to: develop methods
and procedures for software development that can scale up for large
systems and that can be used to consistently produce high quality
software at low cost and with a small cycle time. That is, the key
objectives are consistency, low cost, high quality, small cycle time,
and scalability.
1) Requirement Analysis
Requirement analysis is done in order to understand the problem the
software system is to solve. The problem could be automating an
existing manual process, developing a new automated system, or a
combination of the two. The amphasis in requirements analysis is on
identifying what is needed from the system, not how the system will
achieve its goals. There are atleast two parties involved in the
software development-a client and a developer. The developer has
to develop the system to satisfy the client’s needs. The developer
does not understand the client’s problem domain, and the client
does not understand the issues involved in the software systems.
This causes a communication gap, which has to be adequately
bridged during requirements analysis.
2) Software Design
The purpose of the design phase is to plan a solution of the problem
specified by the requirements documents. This phase is the first step
in moving from the problem domain to the solution domain. Starting
with what is needed, design takes us toward how to satisfy the
needs. The design of a system is perhaps the most critical factor
affecting the quality of the software. It has a major impact on the
later phases, particularly testing and maintenance.
19
The design activity is divided into two phases: System Design and
Detailed Design. In system design the focus is on identifying the
modules, whereas during detailed design the focus is on designing
the logic for each of the modules.
3) Coding
The goal of the coding phase is to translate the design of the system
into code in a given programming language. Hence during coding,
the focus should be on developing programs that are easy to read
and understand, and not simply on developing programs that are
easy to write.
4) Testing
Testing is the major quality control measure used during software
development. Its basic function is to detect errors in the software.
Testing not only uncover errors introduced during coding, but also
errors introduced during the previous phases. Thus, the goal of the
testing is to uncover requirement, design and coding errors in the
programs. Therefore, different levels of testing are used. Testing is
an extremely critical and time consuming activity. It requires proper
planning of the overall testing process. The output of the testing
phase is the test report and the error report. Test report contains
the set of test cases and the result of executing the code with these
test cases. The error report describes the errors encountered and
the action taken to remove the errors.
5) Implementation
It is the process of having systems personnel check out and put new
equipment into use, train users, install the new application and
construct any files of data needed to use it. This phase is less
creative than system design. Depending on the size of the
organization that will be involved in using the application and the
risk involved in its use, systems developers may choose to test the
operation in only one area of the firm with only one or two persons.
Sometimes, they will run both old and new system in parallel way to
compares the results.
Paradigm Applied
In this project,The Spiral Model is applied in order to provide rigid
efficiency and functionality in the overall working style of the
project.Moreover, In order to cater to new or modified requirements
of the user, Spiral model is very effective .I used “The Spiral model”
as it is best suited to those development environments where
probability of uncertainity is very high and chances of mistakes are
uncontrollable.
20
What about Spiral Model?
The spiral model is a software development process combining
elements of both design and prototyping-in-stages, in an effort to
combine advantages of top-down and bottom-up concepts. Also
known as the spiral lifecycle model, it is a systems development
method (SDM) used in information technology (IT). This model of
development combines the features of the prototyping model and the
waterfall model. The spiral model is intended for large, expensive
and complicated projects.
21
4. Constructing and testing the second prototype.
5. At the customer's option, the entire project can be aborted if the
risk is deemed too great. Risk factors might involve development
cost overruns, operating-cost miscalculation, or any other factor
that could, in the customer's judgment, result in a less-than-
satisfactory final product.
6. The existing prototype is evaluated in the same manner as was
the previous prototype, and, if necessary, another prototype is
developed from it according to the fourfold procedure outlined
above.
7. The preceding steps are iterated until the customer is satisfied
that the refined prototype represents the final product desired.
8. The final system is constructed, based on the refined prototype.
9. The final system is thoroughly evaluated and tested. Routine
maintenance is carried out on a continuing basis to prevent large-
scale failures and to minimize downtime.
Applications
The spiral model is used most often in large projects. For smaller
projects, the concept of agile software development is becoming a
viable alternative.
Advantages
22
SECTION 4
23
The Methodology:
I was assigned the duty for developing a computerized system for a
fitness center. The project time and resources were very limited .
The optimum use of practical time neccessiates that every session
and every activity is planned. For effective Planning ,Efficient Project
Managerial skils are required,Efficiant skills then trace out best
methodology to be used.
The methodology used by me includes the following things:
Topic Understanding:
It is vital that the field of application as introduced in the project
may be totally a new field. So as soon as the project was allocated
to me, I carefully went through the project requirements to identify
the requirements of the project.
MEMBER DETAILS
i. Member id
ii. Name
iii. Gender
MEMBERSHIP DETAILS
i. Membership type
ii. Expiration date
MEMBERSHIP DETAILS
i. Address
ii. Date of birth
iii. Phone number
ACCOUNT INFORMATION
24
i. Due date
ii. Amount Due
iii. Amount Paid
iv. Days late
v. Balance
After processing all this information records are saved and in this
module itself there is a provision for report generation for viewing
details of all the members.
There is also a provision for generating a receipt for an individual
member thus agin giving some of his relevant details.
25
It facilitates the owner to place an order and based on the
category of the product(apparels,beverages,supplements)
following information is displayed along includin the
provision for order placement:
a.Category
b.Id
c.Description
d.Brand
e.Supplier
f.Number of cases
g.Quantity in each case
h.Case Price
i.Sales Price
j.Order Date
3. PRODUCTS
Generates an inventory record of the product based on the
product category selected and displays the following
information:
a.Category
b.Id
c.Description
d.Brand
e.Supplier
f.Number of cases
g.Quantity in each case
h.Quantity ordered
i.Case Price
j.Sales Price
k.Order Date
l.Last ordered
m.Last inventory
It also provides the facility of generating reports of all the
products of a paticular category.
26
Principal Design Features
INTRODUCTION OF VISUAL BASIC
Visual Basic has the following traits which differ from C-derived
languages:
27
Variable array base. Arrays are declared by specifying the upper
and lower bounds in a way similar to Pascal and Fortran. It is also
possible to use the Option Base statement to set the default
lower bound. Use of the Option Base statement can lead to
confusion when reading Visual Basic code and is best avoided by
always explicitly specifying the lower bound of the array. This
lower bound is not limited to 0 or 1, because it can also be set by
declaration. In this way, both the lower and upper bounds are
programmable. In more subscript-limited languages, the lower
bound of the array is not variable. This uncommon trait does
exist in Visual Basic .NET but not in VBScript.
28
using the key phrase As (type). VB can also be set in a mode that
only explicitly declared variables can be used with the command
Option Explicit.
29
SECTION 5
DESIGN
30
5.1 DATA FLOW DIAGRAM (DFD)
DFD is a model, which gives the insight into the information domain
and functional domain at the same time. DFD is refined into
different levels. The more refined DFD is, more details of the
system are incorporated. In the process of creating a DFD, we
decompose the system into different functional subsystems. The
DFD refinement results in a corresponding refinement of data.
Following is the DFD of the “Proposed System”. We have refined the
system up to two levels. Each break-up has been numbered as per
the rule of DFD. We have tried to incorporate all the details of the
system but there is some chance of further improvisation because of
the study that is still going on for the project development.
Member details
Database Operations on
MEMBERS record
Member list
Database Operations on
GYM EMPLOYEES record
Reciept
CENTER’S Member’s Record
RECORD
MANAGEMEN- Database Operations on
T SYSTEM INVENTIRY record
Employee details
Employee schedule
IInventory(orders
and products)
31
5.2 DATABASE DESIGN
Introduction
Database
A Database is the systematic collection of logically related Data
with some inherent purpose to access and operate on various
different data stored in the form of records so as to raise the ease
and esfficiancy in data Handelling.
Relational database
It is one which works upon the specification of relational model
which is a database model based on first-order predicate logic,
first formulated and proposed in 1969 by Edgar Codd.
Its core idea is to describe a database as a collection of
predicates over a finite set of predicate variables, describing
constraints on the possible values and combinations of values.
The content of the database at any given time is a finite model
(logic) of the database, i.e. a set of relations, one per predicate
variable, such that all predicates are satisfied. A request for
information from the database (a database query) is also a
predicate.
The purpose of the relational model is to provide a declarative
method for specifying data and queries: we directly state what
information the database contains and what information we want
from it, and let the database management system software take
care of describing data structures for storing the data and
retrieval procedures for getting queries answered.
Database Tables
32
List of Tables in Database:
33
Table 3: RECIEPT GENERATION
34
Table 5: EMPLOYEE PAYROLL
35
Table 7: INVENTORY TABLE
36
5.3 ENTITY-RELATIONSHIP DIAGRAM
37
38
SECTION 6
SCREEN LAYOUTS
39
Login screen of the Fitness Club Management System
40
MEMBERSHIP FORM(AND DETAILS)
MEMBERSHIP RECORDS
41
MEMBERSHIP RECIEPT
42
Menu Interface of the Fitness Club Management
System(employees tab selected)
43
EMPLOYEE SCHEDULE
44
DELETING AN EMPLOYEE RECORD
45
46
Menu Interface of the Fitness Club Management
System(inventory tab selected)
47
INVENTORY FORM
ORDER FORM
48
49
PRODUCT FORM
50
SECTION 7
TESTING
51
Levels of Testing:
Systems are not designed as entire systems nor are they tested as
single systems. The analyst must perform both unit and system testing.
Unit Testing:
In unit testing the analyst tests the programs making up a
system. For this reason, unit testing is sometimes called program
testing. Unit testing gives stress on the modules independently of
one another, to find errors. This helps the tester in detecting
errors in coding and logic that are contained within that module
alone. The errors resulting from the interaction between modules
are initially avoided. The test cases needed for unit testing should
exercise each condition and option.
Unit testing can be performed from the bottom up, starting with
smallest and lowest-level modules and proceeding one at a time.
For each module in bottom-up testing a short program is used to
execute the module and provides the needed data, so that the
module is asked to perform the way it will when embedded within
the larger system.
System Testing:
The important and essential part of the system development
phase, after designing and developing the software is system
testing. We cannot say that every program or system design is
perfect and because of lack of communication between the user
and the designer, some error is there in the software
development. The number and nature of errors in a newly
designed system depend on some usual factors like
communication between the user and the designer; the
programmer's ability to generate a code that reflects exactly the
systems specifications and the time frame for the design.
52
Another reason for system testing is its utility as a user-oriented
vehicle before implementation.
1) Program Testing
A program represents the logical elements of a system. For a
program to run satisfactorily, it must compile and test data
correctly and tie in properly with other programs. it is the
responsibility of a programmer to have an error free program. At
the time of testing the system, there exists two types of errors
that should be checked. These errors are syntax and logic. A
syntax error is a program statement that violates one or more
rules of the language in which it is written. An improperly defined
field dimension or omitted key words are common syntax errors.
These errors are shown through error messages generated by the
computer. A logic error, on the other hand, deals with incorrect
data fields out of range items, and invalid combinations. Since
the logical errors are not detected by compiler, the programmer
must examine the output carefully to detect them.
When a program is tested, the actual output is compared with the
expected output. When there is a discrepancy, the sequence of
the instructions, must be traced to determine the problem. The
process is facilitated by breaking the program down into self-
contained portions, each of which can be checked at certain key
points.
2) String Testing
Programs are invariably related to one another and interact in a
total system. Each program is tested to see whether it conforms
to related programs in the system. Each part of the system is
tested against the entire module with both test and live data
before the whole system is ready to be tested.
3) System Testing
System testing is designed to uncover weaknesses that were not
found in earlier tests. This includes forced system failure and
validation of total system as it will be implemented by its user in
the operational environment. Under this testing, generally we
take low volumes of transactions based on live data. This volume
is increased until the maximum level for each transaction type is
reached. The total system is also tested for recovery and fallback
after various major failures to ensure that no data are lost during
the emergency. All this is done with the old system still in
operation. When we see that the proposed system is successful in
the test, the old system is discontinued.
53
4) System Documentation
All design and test documentation should be well prepared and
kept in the library for future reference. The library is the central
location for maintenance of the new system.
54
SECTION 8
IMPLEMENTATION
55
After completing the packaging process and produced distribution
media for the application, The application requires perfectly working
Microsoft Visual Studio 6.0 installed on the client system along with Ms
Offfice Access. It can run on all applicable operating systems.
56
IMPLEMENTATION
Conversion
Direct Implementation
57
SECTION 9
MAINTAINENCE
58
MAINTENANCE
59
SECTION 10
CONCLUSION
60
The objective of this project was to build a program for maintaining the
details of all the members,employees and inventory .The system
developed is able to meet all the basic requirements. The management
of the records (both members and employees)will be also benefited by
the proposed system, as it will automate the whole procedure, which
will reduce the workload. The security of the system is also one of the
prime concerns.
61
SECTION 11
BIBLIOGRAPHY
62
Bibliography
www.wikipedia.org
www.codeproject.com
Visual Basic 6.0 Resource Center |
http://msdn.microsoft.com/hi-in/vbrun/default(en-us).aspx
Visual Basic 6 Black Book By Steven Holzner
63