MARATHON GYM MANAGEMENT

SUBMITTED BY

PRIYA DESAI

ARSHEEN GONDEKAR

ACADEMIC YEAR: 2007-2008

UNDER THE GUIDENCE OF MRS.MUGDHA KALE

SUBMITED IN PARTIAL FULFILLMENT OF THE

REQUIREMENTS FOR QUALIFYING

B.Sc. (I.T.), SEMESTER-VI EXAMINATION

CHIKITSAK SAMUHA’S

PATKAR VARDE COLLEGE OF ARTS,

COMMERENCE AND SCIENCE.

GOREGAON (W), MUMBAI-400062.

 ACKNOWLEDGEMENT
This project itself is an acknowledgement to the efforts of many
individuals who have contributed to it. We got lot of guidance from the
various people at various stages of the project development.

Our project guide Mrs.Mugdha Kale provided us excellent

guidance through out the project development period. She tested and
suggested the necessary changes in the software from time to time.

Most of our teachers also helped us in many ways, some of them

had introduced us to programming, and some developed our
programming skill, while some helped us for analyzing the system and
designing it. We thank to all of them. We also thank Mr.C.A.Ludhani
for the support at Marathon Gym.

Finally we would like to thanks our Principle Dr. Uday C.

Mashelkar and Mrs. Mala Kharkar of I.T. Department for their constant
support.

This project is the result of our dedication, staff cooperation and

team work.
 INDEX

Sr.N Contents Page No.

o
1. Synopsis
2. Objective of the Project
3. Scope of the project
4. Organizational Profile
5. Description of existing work
6. Proposed System
7. Feasibility Study
8. Cost Analysis
9. PERT Chart
10. ERD
11. DFD
12. Input and Output Screen Design
13. Waterfall Model
14. Gantt Chart
15. Table Information
16. Data Dictionary
17. User Manual
18. Test Plan
19. Limitations of our System
20. Bibliography
 Synopsis
We are trying to make software for a Company to
computerize its daily office work which was manual up till now. Manual
work was too time consuming and required lot of paper work. So to
reduce the complexity and time consumption we have decided to
computerize it by making a Software Project on it.

The features that we are planning to incorporate are:-

 Staff Login
 Maintaining Staff Details
 Maintaining Customer Details
 Managing Lockers
 Maintaining Firm Details
 Bill calculations
 Bill printing
 Back up – Restore Facility
 OBJECTIVE OF THE PROJECT
 The main objective of the project is to develop software that
facilitates the data storage, data maintenance and its retrieval for the
gym in an igneous way.

 To store the record of the customers, the staff that has the privileges
to access, modify and delete any record and finally the service, gym
provides to its customers.

 Also, only the staff has the privilege to access any database and make
the required changes, if necessary.

 To develop easy-to-use software which handles the customer-staff

relationship in an effective manner.

 To develop a user friendly system that requires minimal user training.

Most of features and function are similar to those on any windows
platform.

 To provide validation for all operations.

 SCOPE OF THE PROJECT
 To keep information about all the customers.

 To keep information about all the money transactions

of the customers.

 To keep information of the staff and their various details.

 Timely generation of reports.

 Store all the information in a systematic way with features like

saves, delete, update, and retrieve options.
 ORGANIZATIONAL PROFILE

Name of Gym: - Marathon Gym

Address: - Malwani Maa Co-op. Hsg Society, Plot
No. 17, RAC-2, Malvani Mahada No. 8, Malad
(W), Mumbai-400064.
Contact No: - 9324411089

Gym History: -

This gym was keeping all records in a specific book/register.

It had many fields which were not organized sequentially and could not
be updated.
 DESCRIPTION OF EXISTING
WORK
The current process in Marathon Gym is done manually.
Some Limitations of current system are:

 Security features are not provided. Thus any person who knows
the data can do any type of manipulation.

 It does not prompt the user about wrong information going in

process.

 It is a very time consuming system.

 No further modifications are possible that the information may

require at later stages.

 Most records are maintained manually.

 PROPOSED SYSTEM

Scope of the Proposed System:

 System should be window based, user friendly and efficient.

 System security must be implemented by preventing unauthorized

access to it.

 Appropriate master table must be present to record relevant data.

 Security features must exist in the system.

Statement of System Capabilities

 Security features user name and password authentication is

implemented.

 Appropriate database tables are maintained to record and store

validated information.

 Extra features like search facilities are provided.

 Report generation is implemented.

FEASIBILITY STUDY

The feasibility study can be categorized into

 Technical Feasibility

Marathon Gym is equipped with the following Hardware and

Software.

HARDWARE:

2.0 GHz PENTIUM IV

128 MB RAM
80 GB HDD
3.5 Inch FDD
DOT Matrix Printer

SOFTWARE:

Microsoft Windows 2000

Microsoft Windows XP
Microsoft Access 2000
 Visual Studio 2005

 Operational Feasibility

The new system will automate the existing manual system and
make it user friendly. With the required training, the staff will find the
system easier to operate. The system cuts down the paperwork and time
delay of existing manual system.

 Economic Feasibility
As the hardware and the some software are already
available and no investment is to be made in that direction, the only cost
involved is that of implementing the system.

 Cost Analysis
The software for VB.Net 2005 would cost around
Rs.10,000/- only.
The dot matrix printer would cost around Rs.2000/- and for
the cartridges would cost around Rs. 1000/- only.
 SYSTEM DESIGN
In this phase, the software’s overall structures are defined.
Analysis and design are very crucial in the whole development cycle.
Any glitch in the design phase could be very expensive to solve in the
later stage of the software development. Much care is taken during this
phase.

Design is a formation of a plan of activities to accomplish a

recognized need. The need may be well defined or ill defined. The
design process is a process of creative invention and definition; it
involves synthesis and analysis and thus is difficult to summarize in a
simple design formula.

Major Components and Levels of Design

Dividing software design methodologies into classifications called

approaches helps in the generalization, explanation and understanding of
software design methodologies, and guide in the selection of the
appropriate software design methodology to use. The main design
approaches are:

 The level Oriented

 Data Flow Oriented
 Data Structure Oriented
 Object Oriented Design

 The level Oriented

In the Level Oriented Design approach, there are two general or

broad strategies that can be used. The first strategy starts with a
general definition of a solution to the problem then through a step-by-
step process produce a detailed solution called as Stepwise
Refinement. This is basically dependent on the system requirements
and is a top-down process.

 Data Flow Oriented

In the Data Flow Oriented Design approach, often called as

Structured Design, information flow characteristic is used to derive
program structure. In the data flow oriented approach, emphasis is on
the processes or operations performed on the data. Design is
information driven. Information may be represented as a continuous
flow that is transformed, as it is processed from node to node in the
input output stream.
 Data Structure Oriented

The Data Structure Oriented Design approach utilizes the data

structures of the input data, internal data and output data to develop
software. In the data structure oriented design approach, the emphasis
is on the object which is the data. The structure of information called
data structure has an important impact on the complexity and
efficiency of algorithms designed to process information

 Approach adopted by us

We adopted the approach of structured design. First based on

the problem statement we identified the various processes that
constituted the system. Accordingly the data flow diagrams were the
designed. The requirements of the gym were that they wanted a
system which could handle the customer and staff data in an
automated format with the least possible trouble. They wanted to
design a system were the staff would feed the information of the
customer in the computer and also efficiently retrieve the data back
for reference.

 PERT Chart

PERT (Project Evaluation and Review Technique) Charts

consist of a network of boxes and arrows. The boxes represent
activity task dependencies. PERT Charts are a more sophisticated
form of activity chart.

There are not one but many critical paths, depending on the
permutations of the estimated for each task. A critical path in a
PERT Chart shown by using shaded boxes.
 PERT Chart incorporates additional information about the time
when an engineer does a task. PERT Chart is more useful for
monitoring the timely progress activities.

PERT Chart
 D e c 1 , J a n 1

O c t 1 , O c t 3 0

C o d i n g

L e a r n i n g S Q L

J a n 1 0 , J a n 2 5
S e p 1 , S e p 2 0 N o v 1 , N o v 3 0

I n t e g r a t i n g a n
R e q u i r e m e n t s a n d D e s i g n i n g D a t a b a s eT e s t i n g
S p e c i f i c a t i o n s a n d F o r m s

O c t 1 , O c t 3 0

F e b 1 , F e b 2 0

L e a r n i n g V B . N e t
D o c u m e n t a t i o n

ENTITY RELATIONSHIP DIAGRAM

A graphical model of the data needed by a system, including things
about which information is stored and relationships among them,
produced in structured analyses and information engineering.

The traditional approach to system development places a great deal

of emphases on data storage requirements for the new system. Data
storage requirements include the data entities, their attributes and the
relationships among the data entities. The model used to define the data
storage requirements is called the entity relationship diagram (ERD)

On the Entity Relationship Diagram, rectangles represent data

entities, and the lines connecting rectangles show the relationship among
the data entities.
R e p r e s e n t D a t a E n t i t y

R e p r e s e n t C o n n e c t i o n

R e p r e s e n t t h e P r o c e s s r e l a t i

C o n n e c t s t h e t w o E n t i t i e s

S h o w s O n e T O M a n y R e l a t i

S h o w s O n e t o O n e R e l a t i o n s

S h o w s M a n y T o O n e r e l a t i o

M o d a l i t y - E n t i t i e s a r e m u s t i

M o d a l i t y - O n e o f t h e e n t i t y i
 DATA FLOW DIAGRAM
A Data Flow Diagram (DFD) is graphical system model that
shows all the main requirements for an information system in one
diagram; inputs and outputs, processes, and data storage. Everyone
working on a development project can see all aspects of the system
working together at once with the DFD.

DFD is easy to read because it is graphical model and there

are only five symbols.

P r o c e s s S t e p - b y - s t e p i n s t r u c t i o
i n p u t s i n t o o u t p u t s .

D a t a f l o w i n g f r o m p l a c
D a t a F l o i wn p u t o r o u t p u t t o a p r o

E x t e r n a Tl hE e n ts i o t y u r c e o r d e s t i n a t i

D a t a S t o Dr e a t a a t r e s t , b e i n g s t o r e
t o a d a t a e n t i t y o n a n e n
 WATERFALL MODEL
The Software Development Life Cycle includes models such as
Waterfall Model, Prototype Model, and Object-oriented Model etc. for
developing the correct software. The Waterfall Model is the earliest
method of structured system development. It is attributed with providing
the theoretical basis for the Process Models, because it most closely
resembles a “Generic” model for software development.

This is also called as linear sequential model. This model

suggests a systematic, sequential, approach to software development that
begins at the system level and progresses through analysis, design,
coding and testing and support.

Problem
Definition

Analysis

Design

Coding

Testing

Maintenance
1. SYSTEM/ INFORMATION ENGINEERING AND MODELING

• System engineering and analysis encompass requirements

gathering at the system level with a small amount of top level
design and analysis.
• Information engineering encompasses requirements gathering at
the strategic business level and at the business area level.
• This system view is essential when software must interact with
other element such as hardware, people and database.

2. SOFTWARE REQUIREMENT ANALYSIS

• The requirement gathering process is intensified and focused

specifically on software.
• To understand the nature of the programs to be built, the
software engineer must understand the information domain for
the software as well as required function, behavior performance
and interface.
• Requirement for both the system and the software are
documented and reviewed with the customer.

3. DESIGN

• Software design is actually a multistep process that focuses on

four distinct attributes of a program data structures software
dubitative, interface representations and procedural detail.
• The design process translates requirements into a
representation of the software that can be assessed for quality
before coding begins.
 • Like requirements, the design is documented and becomes part
of the software configuration.

4. CODE GENERATION

• The design must be translated into a machine-readable form.

• If design is detailed, code generation can be done easily.

5. TESTING

• The testing process focuses on the logical internals of the

software. It ensures that all statements have been tested.
• It focuses on the functional externals. here tests are conducted
to uncover errors and ensure that defined input will produce
actual result that agree with required results

6. SUPPORT

• Software will undoubtedly undergo change after it is delivered to the

customer.
• Change will occur because errors have been encountered because
changes in is external environment.
• Software support/ maintenance reapply each of the proceeding phases to
n existing program rather than a new one.

ADVANTAGES:
 • The basic life cycle paradigm has definite and important place is
software engineering work.

• It provide a template into which methods for analysis, design,

coding, testing and support can be placed.

• The classic life cycle remain a widely used procedural model for
software engineering

DISADVANTAGES:

• Real projects rarely follow the sequential flow that the model
proposes. Although the model can accommodate iteration, it dose so
indirectly. As a result, change ear fusion as the project team
proceeds.

• It is often difficult for the customer to state all requirements

explicitly. This model requires this and has difficulty
accommodating the natural uncertainty that exists at the beginning
of many projects.

• The customers must have patience. A working version of the

programs will not be available until late is the project time-span. A
major blunder if undetected until the working program is received
can be disastrous.

GANTT CHART
 Gantt Chart

2 0 2007
0 7 - 2 0 0 8
Task
July
S e p t
January August
O c
February t September
N o v
March October
D e
April c JMaya n
November December
FJunee b
Project Planning
Define Business problem & Scope

Produce detail project schedule

Conform Project feasibility

Launch project

Milestone(Scope defined)

Analysis Phase
Gather Information

Define System requirements

Build Prototype for requirements

Prioritize requirement

Generate & Evaluate alternatives

Review Recommendations with
management
Milestone(Details of module)

Design Phase
Design & integrate Networks

Design Application architecture

Design user interface

Design System interface

Design & integrate the system controls

Milestone(All document created)

Implementation Phase
Design & Construct software
components
Verify & test

Train & Document

Install System
Milestone(source code generated &
testing successful)

Legend

Milestone marker

Estimated Time

Required time for Planning Phase

Required time for Anlysis Phase

Required time for Design Phase

Required time for Implementation Phase

 TABLE INFORMATION
Name : STAFF
Type : Master
No. of fields : 13
Description : Stores Staff information.

Field Name Data type Constraint Description

Staff_id Text Primary key It assigns the ID to the staff.
FName Text - Stores first name of the staff.
MName Text - Stores middle name of the staff.
LName Text - Stores last name of the staff.
Address Text - Stores address of the staff.
DOB Date/Time - Stores birth date of the staff.
Designation Text Stores the designation of the staff.
Gender Text - Stores gender of the staff
Marital_Status Text - Stores marital status of the staff.
Mobile_no Number - Stores mobile number of the staff.
Phone_no Number - Stores phone number of the staff.
Email_id Text - Stores email-id of the staff.
Dt_join Date/Time - Stores date of joining of the staff
Basic_Sal Number - Stores the basic salary of the staff.

This table stores all the personal details of the staff.

Name : EQUIPMENT
Type : Master
No. of fields : 5
Description : Stores information of all the equipments.

Field Name Data type Constraint Description

Equip_no Text Primary key It assigns the ID to the equipment.
Equip_name Text - Stores name of the equipment.
Manufact_dat Date/Time - Stores manufacturing date of the
e equipment.
Service_date Date/Time - Stores last service date of the
equipment.
Service_name Text - Stores name of the serviceman for
the equipment.
This table stores the information about various equipments used by the
customers.

Name : CUSTOMER
Type : Master
No. of fields : 16
Description : Stores Customer information.

Field Name Data type Constraint Description

Customer_id Text Primary key It assigns the ID to the customer.
FName Text - Stores first name of the customer.
MName Text - Stores middle name of the customer.
LName Text - Stores last name of the customer.
Address Text - Stores address of the customer.
DOB Date/Time - Stores birth date of the customer.
Gender Text - Stores gender of the customer.
Marital_Status Text - Stores marital status of the
customer.
Mobile_no Number - Stores mobile number of the
customer.
Phone_no Number - Stores phone number of the
customer.
Email_id Text - Stores email-id of the customer.
Instructor_id Text Foreign Key It assigns the Instructor ID to the
customer.
Dietician_id Text Foreign Key It assigns the Dietician ID to the
customer.
Scheme_id Text Foreign Key It assigns the Scheme ID to the
customer.
Schedule_id Text - It assigns the Schedule ID to the
customer.
Dt_join Date/Time - Stores date of joining of the
customer.

This table stores all personal details of the customer as well as other
gym details related to customer.
 Name : LOGIN
Type : Master
No. of fields : 2
Description : Stores Administrator Login & Password.

Field Name Data type Constraint Description

Username Text - Stores username of administrator.
Password Text - Stores password of administrator.

This table stores the information about the administrator login and
password

Name : FIRM
Type : Master
No. of fields : 6
Description : Stores information of the firm.

Field Name Data type Constraint Description

Firm_name Text Primary key Stores name of the firm
Firm_details Text - Stores details about the firm
Firm_address Text - Stores address of the firm.
Mobile Number - Stores mobile number of the firm.
Phone Number - Stores phone number of the firm.
Emailid Text Stores email-id of the firm.

This table stores the information about various firms from where
different equipments were bought.

Name : SALARY
Type : Master
No. of fields : 8
Description : Stores Staff information.

Field Name Data type Constraint Description

Staff_id Text Foreign Key It assigns the ID to the staff.
Attendance Number - Stores number of days attended by
the staff member.
Tax Number - Stores middle name of the staff.
Basic Number - Stores the basic salary of the staff.
Bonus Number - Stores the bonus given to the staff.
Incentives Number - Stores birth date of the staff.
 HRA Number Stores the designation of the staff.
Tot_salary Number - Stores the total salary for that staff
member.

This table stores the information about the salary given to the staff in
segregated form.
Name : LOCKER
Type : Master
No. of fields : 3
Description : Stores information about the locker.

Field Name Data type Constraint Description

Locker_no Number Primary key Stores the locker number
ID Text Foreign Key Stores the ID of customer/staff.
Deposit Number - Stores amount deposited for the
locker.

This table stores the information about the lockers used by customers
and staff.

Name : STATISTICS
Type : Master
No. of fields : 12
Description : Stores Customer Statistics.

Field Name Data type Constraint Description

Customer_id Text Foreign key It assigns the ID to the customer.
Weight Text - Stores weight of the customer.
Height Text - Stores height of the customer.
Chest Text - Stores chest of the customer.
Shoulder Text - Stores shoulder of the customer.
Waist Date/Time - Stores waist of the customer.
Hips Text - Stores hips of the customer.
Fat_count Text - Stores fat count of the customer.
Pulse_count Number - Stores pulse count of the customer.
Blood_group Number - Stores blood group of the customer.
BMI Text Stores BMI [body mass index] of the
customer.
Ailments Text Stores information about the
ailments of the customer.
This table stores the statistic details of the customer.

Name : SCHEME
Type : Master
No. of fields : 5
Description : Stores information of the firm.

Field Name Data type Constraint Description

Scheme_ID Text Primary key It assigns the ID to the scheme.
Scheme_name Text - Stores name of the scheme.
Duration Number - Stores duration for that scheme.
Rate Number - Stores amount for that scheme.
Description Text - Stores brief information of that
scheme.

This table stores the information about various schemes incorporated in

this gym.

Name : HEALTHY INTAKE

Type : Master
No. of fields : 6
Description : Stores information of various healthy products.

Field Name Data type Constraint Description

Health_id Text Primary key It assigns the ID to the product
Food_court_id Text Foreign key Stores food_court_id
Name Text - Stores Name of the product.
Grams Number - Stores the weight in grams of the
product.
Contents Text - Stores the contents of the product.
Price Number - Stores the price of the product.

This table stores the information about the healthy products.

Name : FOOD COURT

Type : Master
No. of fields : 9
Description : Stores information of the food court.
 Field Name Data type Constraint Description
Food_id Text Primary key It assigns the ID to the product
Name Text - Stores name of the food supplier
Address Text - Stores address of the food supplier.
Mobile Number - Stores the mobile number.
Phone Number - Stores the phone number.
Email_id Text - Stores the email_id of the supplier.
Quantity Number - Store the total number of products
purchased.
Weight Number - Stores the weight of the purchased
products.
Price Number - Stores the amount of purchased
product.

This table stores the information about the Food Court.

DATA DICTIONARY

Data Dictionary for Entities

1) Entity name: Customer

Scope: Full project
Type: Internal
Input: Personal details, selection, amount
Output: Report
Logic Summary: This entity contains all the information related to
customer.
2) Entity name: Staff
Scope: Full project
Type: Internal
Input: Query
Output: Report, query results
Logic Summary: This entity contains all the information related to staff.

Data Dictionary for Processes

1) Process name: Enquiry
Summary: It will process all kinds of Enquiries.
Entities: Customer, Staff

2) Process name: Billing

Summary: It will process all kinds of bills
Entities: Customer, Staff

Data Dictionary for Tables

1) Table name: Customer
Size: 1 Lac records
Primary key: Customer_id
Foreign key: Instuc_id,Diet_id
Attributes: Name, Age, Phone no.
Summary: Stores all information about customer.

2) Table name: Equipment

Size: 1000 records
Primary key: Equip_no
Foreign key: Firm_id
Attributes: Equipment Name, Manufacture Date
 Summary: Stores all information about Equipments.

3) Table name: Firm

Size: 1000 records
Primary key: Firm_Number
Foreign key: -
Attributes: Firm Name, Firm Details
Summary: Stores all information about Firm.

Data Dictionary for Data Flow

1) Data Flow name: Cancels scheme
Inbound: Customer entity
Outbound: Cancellation process
Details: It cancels the scheme taken by customer.

2) Data flow name: Refund

Inbound: Cancellation process
Outbound: Customer entity
Details: It gives refund to the customer.

Data Dictionary for Data

1) Data name: Age

Size: 2
Type: Number
Range: 18-60
Table: Customer
Details: Is a field, which stores age of customer.

2) Data name: Equipment Name

Size: 20
Type: Alphabets
Range: A-Z and a-z.
Table: Equipment
 Detail: Is a field, which stores name of various Equipments.

3) Data name: Phone Number

Size: 8
Type: 0-9
Range: Number
Table: Staff
Detail: Is a field which stores phone numbers of the staff

USER MANUAL
 Getting Started

1. Know Your System

2. Security aspects of the System

 How to use the system?

Login form

Sign In
 Main form

1. Details

a. Customer

 Adding a new customer details.

 Searching and editing a customer record.

b. Staff

 Adding a new staff details.

 Searching and editing a staff record.

2. Report
 Generation of report.

3. Bill

 Adding all details of money transactions to generate

the bill.

4. Schedule
 Providing a schedule for the staff.

5. Scheme

 Adding a new scheme.

 Searching and viewing for scheme.

6. Salary
 Adding various details of salary to calculate the total
salary.
7. Statistics
 Adding the details of measurements for the customer.

8. Miscellaneous

a. Firm

 Adds a new firm record.

 Search and edits firm record.

b. Equipment

 Adds a new equipment record.

 Search and edits equipment record.

c. Locker

 Adds a new locker for staff and customer record.

 Search and edits locker record.

d. Healthy Intake

 Providing various healthy products for the

customers.

e. Food Court

 Details of various food suppliers are maintained.

GETTING STARTED

To start the application, click Start-Program-MARATHON GYM

After the application has loaded please wait until splash screen ends,
afterwards a screen will pop which will allow you to login to the system. This is
like entry door for the system.

KNOW YOUR SYSTEM

This application would help you to keep records of customer, staff, scheme,
schedule, locker, equipment, etc.

SECURITY ASPECTS OF THE SYSTEM

The security for the system is to prevent an unauthorized access to data or

any illegal use of the system. The system has in-built security system in form of
Login prompt. Unless and until the user enters proper login he/she cannot gain
access to any part or module of the system. So it is responsibility of the
corresponding user to remember and taking care of there login name and password.
The username and password can be 8 characters long.
 TEST PLAN
LOGIN FORM:

Sr. No. Action Input Data Expected Result Actual Result

1. Pressing button User name The user is Objective
and password authenticated achieved. If user is
and the main valid user, then the
form appears. main form appears
or else an error
message is given
to the user for
entering valid user
name or password
or both.

MAIN FORM:

Sr. No. Action Input Data Expected Result Actual Result

1. Selecting menu The user is Objective
item from directed to the achieved. The user
menu bar. form according is directed to the
to the menu form depending on
selected. the selection of the
menu item.
TEST PLAN FOR BUTTONS THAT ARE COMMON IN ALL THE FORMS:

Sr. No. Action Input Data Expected Result Actual Result

1. After pressing Particulars The record Objective
Save button, for the fields should be saved achieved and user
the particular are given. in the respective gets the message
record is saved fields of the data that record is
in the database. table. saved.
2. After pressing All data fields Objective
Clear button, should be achieved and if the
all fields are emptied. user wishes to
emptied. enter new data it is
possible.
3. After pressing Particular for The record Objective
Delete button, the fields are should be achieved and user
the particular retrieved. deleted from the can delete the
record is database. existing data.
deleted from
the database.
4. After pressing The form is Objective
Cancel button, closed and achieved and user
the form is control goes comes to the main
closed back to main form.
form.

Test plan for Textboxes in all the forms

Sr. No. Action Input Data Expected Result Actual Result

1. Entering data Text Data enters in Objective is
in a text box in textboxes. achieved and data
which only text gets entered.
is allowed
2. Entering data Numbers and Data should not Objective is
in a text box in special get entered in achieved and data
which only text characters textboxes. does not get
is allowed entered.
3. Entering data Numbers Data enters in Objective is
 in a text box in textboxes. achieved and data
which only gets entered.
numbers are
allowed
4. Entering data Text and Data should not Objective is
in a text box in special get entered in achieved and data
which only characters textboxes. does not get
numbers are entered.
allowed
5. Entering data date Date is entered Objective is
in a text box in in specified achieved and date
which only format. gets entered.
date is allowed
6. Entering data Text and Data is not Objective is
in a text box in special entered. achieved and data
which only characters does not get
date is allowed entered.

Test plan for Combo boxes in all the forms

Sr. No. Action Input Data Expected Result Actual Result

1. Selecting data Numeric Data should not Objective
from combo Data, text, be entered, Achieved.
boxes special instead it should
characters be selected from
the combo box
 LIMITATIONS OF OUR SYSTEM
 Our system is not Web-enabled.
 Receptionist or a staff member should be always present to enter
the data of the customer.
 Generation of new passwords is not possible.
 Too many details to be filled for some entities.

BIBLIOGRAPHY

The Complete Reference SQL – James R Groff and Paul n. Weinberg

(Tata Mc Graw Hill)

The Complete Reference VB.NET- Jeffrey R Shapiro

(Tata Mc Graw Hill)
This is login form. If valid user id and password are entered then only
you can login to the system.
This is the splash screen. This is displayed for few seconds so that the
system loads itself.

This is the MDI [Menu Driven Interface]. It is used to access all the
other details of the system.
This is attendance form for staff and customer.
This shows the path to enter a new customer record.
This path shows the user to access the various sub-menus from the menu
Miscellaneous.
This is customer form. It is used to enter new Customer entry as well as
to delete record.
This is staff form. It is used to enter new staff entry as well as delete
staff record.
This is form is used to enter new firm record as well as delete old firm
record.
This form is used is used to enter the weekly statistic details of the
customer.
This form is used to enter new equipment details as well as to delete old
record.

This form is used to calculate the monthly salary of the staff.