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 E XAMINATION 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 Our proj projec ectt guid guidee Mrs. Mrs.Mu Mugd gdha ha Kale Kale prov provid ided ed us exce excell llen entt 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. Fina inally we would ould like like to tha thanks nks our our Princ rincip iple le Dr. Dr. Uday day 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.
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 Our proj projec ectt guid guidee Mrs. Mrs.Mu Mugd gdha ha Kale Kale prov provid ided ed us exce excell llen entt 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. Fina inally we would ould like like to tha thanks nks our our Princ rincip iple le Dr. Dr. Uday day 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 o
Contents
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
Page No.
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 redu reduce ce the the comp comple lexi xity ty and and time time cons consum umpt ptio ion n we have have deci decide ded d 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 The main main obje object ctiv ivee of the the proj projec ectt is to deve develo lop p soft softwa ware re that 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: Address: -
Contact No: -
Marathon Gym Malwani Maa Co-op. Hsg Society, Plot No. 17, RAC-2, Malvani Mahada No. 8, Malad (W), Mumbai-400064. 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-bystep 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 O
c t
1
,
O
c t
3
e
c
1
,
e
a r n
i n
g
S
Q
e
p
1
,
S
e
p
2
n
1
o
d
i n
g
L
J S
a
0
C L
J
0
N
o
v
1
,
N
o
v
3
a
n
1
0
,
J
a
n
2
0
I n
R
e S
q p
u e
c
i r e m e n t s i f i c a t i o n
a n
d
D
s
O
c t
1
,
O
c t
3
e s i g n i n g D a n d F o r m s
t e g r a t i n a t a b a s eT e s t i n g
0 F
L
e
a r n
i n
g
V
B
. N
e
e
b
1
,
F
o
c
u
m
e
b
2
0
t D
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
e
n
t
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
R
e p
r e s e n
t
C
o n
R
e
C
o n
p
r e s e n
n
S
h
o
w
S
h
o
w
S
h
o
e c
s
s
w
s
t
t s
t h
t a
E
n
e c
e
P
t h
e
t w
O
O
n
e
T
O
n
e
t o
M
a
n
y
o
t i o n
E
M
o
d
a
l i t y - E
n
t i t i e
M
o d
a
l i t y - O
n
e
o f
a
n
o
M
t i t y
r o c
O
T
n
n
t i t i
n
y
e
O
s
e s s
R
n
a
t h
R
e
e
r
r e
e
l
m
e
n
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
D
a
t a
F
E
x
t e
r n
D
a
t a
S
S t e p - b i n p u t s
y
- s t e p i n s t r u c i n t o o u t p u t s .
D a t a f l o l o iwn p u t o r
a
t o
l T Eh
en
t s i ot y u
w o
r c
i n g u t p
f r o m u t t o
a
e
r
t i n
o
d
e
s
rD e a t a a t r e s t , b e i n g t o a d a t a e n t i t y o n
p p
s t o a 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 January July
S
e
p t
August February O c t
March September N o v
October DApril e c
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
November JMaya n
December F June e b
TABLE INFORMATION Name Type No. of fields Description Field Name Staff_id FName MName LName Address DOB Designation Gender Marital_Status Mobile_no Phone_no Email_id Dt_join Basic_Sal
: : : :
Data type Text Text Text Text Text Date/Time Text Text Text Number Number Text Date/Time Number
STAFF Master 13 Stores Staff information. Constraint Primary key -
Description It assigns the ID to the staff. Stores first name of the staff. Stores middle name of the staff. Stores last name of the staff. Stores address of the staff. Stores birth date of the staff. Stores the designation of the staff. Stores gender of the staff Stores marital status of the staff. Stores mobile number of the staff. Stores phone number of the staff. Stores email-id of the staff. Stores date of joining of the staff Stores the basic salary of the staff.
This table stores all the personal details of the staff. Name Type No. of fields Description
: : : :
EQUIPMENT Master 5 Stores information of all the equipments.
Field Name Equip_no Equip_name Manufact_dat e Service_date
Data type Text Text Date/Time
Constraint Primary key -
Date/Time
-
Service_name
Text
-
Description It assigns the ID to the equipment. Stores name of the equipment. Stores manufacturing date of the equipment. Stores last service date of the equipment. Stores name of the serviceman for the equipment.
This table stores the information about various equipments used by the customers.
Name Type No. of fields Description
: : : :
CUSTOMER Master 16 Stores Customer information.
Field Name Customer_id FName MName LName Address DOB Gender Marital_Status
Data type Text Text Text Text Text Date/Time Text Text
Constraint Primary key -
Mobile_no
Number
-
Phone_no
Number
-
Email_id Instructor_id
Text Text
Foreign Key
Dietician_id
Text
Foreign Key
Scheme_id
Text
Foreign Key
Schedule_id
Text
-
Dt_join
Date/Time
-
Description It assigns the ID to the customer. Stores first name of the customer. Stores middle name of the customer. Stores last name of the customer. Stores address of the customer. Stores birth date of the customer. Stores gender of the customer. Stores marital status of the customer. Stores mobile number of the customer. Stores phone number of the customer. Stores email-id of the customer. It assigns the Instructor ID to the customer. It assigns the Dietician ID to the customer. It assigns the Scheme ID to the customer. It assigns the Schedule ID to the customer. 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 Type No. of fields Description Field Name Username Password
Data type Text Text
: : : :
LOGIN Master 2 Stores Administrator Login & Password.
Constraint -
Description Stores username of administrator. Stores password of administrator.
This table stores the information about the administrator login and password Name Type No. of fields Description Field Name Firm_name Firm_details Firm_address Mobile Phone Emailid
: : : :
Data type Text Text Text Number Number Text
FIRM Master 6 Stores information of the firm.
Constraint Primary key -
Description Stores name of the firm Stores details about the firm Stores address of the firm. Stores mobile number of the firm. Stores phone number of the firm. Stores email-id of the firm.
This table stores the information about various firms from where different equipments were bought.
Name Type No. of fields Description
: : : :
SALARY Master 8 Stores Staff information.
Field Name Staff_id Attendance
Data type Text Number
Constraint Foreign Key -
Tax Basic Bonus Incentives
Number Number Number Number
-
Description It assigns the ID to the staff. Stores number of days attended by the staff member. Stores middle name of the staff. Stores the basic salary of the staff. Stores the bonus given to the staff. Stores birth date of the staff.
HRA Tot_salary
Number Number
Stores the designation of the staff. Stores the total salary for that staff member.
-
This table stores the information about the salary given to the staff in segregated form. Name Type No. of fields Description Field Name Locker_no ID Deposit
: : : :
Data type Number Text Number
LOCKER Master 3 Stores information about the locker. Constraint Primary key Foreign Key -
Description Stores the locker number Stores the ID of customer/staff. Stores amount deposited for the locker.
This table stores the information about the lockers used by customers and staff. Name Type No. of fields Description Field Name Customer_id Weight Height Chest Shoulder Waist Hips Fat_count Pulse_count Blood_group BMI
Data type Text Text Text Text Text Date/Time Text Text Number Number Text
Ailments
Text
: : : :
STATISTICS Master 12 Stores Customer Statistics. Constraint Foreign key -
Description It assigns the ID to the customer. Stores weight of the customer. Stores height of the customer. Stores chest of the customer. Stores shoulder of the customer. Stores waist of the customer. Stores hips of the customer. Stores fat count of the customer. Stores pulse count of the customer. Stores blood group of the customer. Stores BMI [body mass index] of the customer. Stores information about the ailments of the customer.
This table stores the statistic details of the customer.
Name Type No. of fields Description Field Name Scheme_ID Scheme_name Duration Rate Description
: : : :
Data type Text Text Number Number Text
SCHEME Master 5 Stores information of the firm. Constraint Primary key -
Description It assigns the ID to the scheme. Stores name of the scheme. Stores duration for that scheme. Stores amount for that scheme. Stores brief information of that scheme.
This table stores the information about various schemes incorporated in this gym.
Name Type No. of fields Description
: : : :
HEALTHY INTAKE Master 6 Stores information of various healthy products.
Field Name Health_id Food_court_id Name Grams
Data type Text Text Text Number
Constraint Primary key Foreign key -
Contents Price
Text Number
-
Description It assigns the ID to the product Stores food_court_id Stores Name of the product. Stores the weight in grams of the product. Stores the contents of the product. Stores the price of the product.
This table stores the information about the healthy products.
Name Type No. of fields Description
: : : :
FOOD COURT Master 9 Stores information of the food court.
Field Name Food_id Name Address Mobile Phone Email_id Quantity
Data type Text Text Text Number Number Text Number
Constraint Primary key -
Weight
Number
-
Price
Number
-
Description It assigns the ID to the product Stores name of the food supplier Stores address of the food supplier. Stores the mobile number. Stores the phone number. Stores the email_id of the supplier. Store the total number of products purchased. Stores the weight of the purchased products. 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.
Generation of report.
Adding all details of money transactions to generate the bill.
Providing a schedule for the staff.
2. Report
3. Bill
4. Schedule
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. 1.
Action Input Data Pressing button User name and password
Expected Result The user is authenticated and the main form appears.
Actual Result Objective achieved. If user is valid user, then the main form appears or else an error message is given to the user for entering valid user name or password or both.
Expected Result The user is directed to the form according to the menu selected.
Actual Result Objective achieved. The user is directed to the form depending on the selection of the menu item.
MAIN FORM: Sr. No. 1.
Action Selecting menu item from menu bar.
Input Data
TEST PLAN FOR BUTTONS THAT ARE COMMON IN ALL THE FORMS: Sr. No. 1.
2.
3.
4.
Action After pressing Save button, the particular record is saved in the database. After pressing Clear button, all fields are emptied.
Input Data Particulars for the fields are given.
Expected Result The record should be saved in the respective fields of the data table. All data fields should be emptied.
After pressing Delete button, the particular record is deleted from the database. After pressing Cancel button, the form is closed
Particular for The record the fields are should be retrieved. deleted from the database.
The form is closed and control goes back to main form.
Actual Result Objective achieved and user gets the message that record is saved. Objective achieved and if the user wishes to enter new data it is possible. Objective achieved and user can delete the existing data.
Objective achieved and user comes to the main form.
Test plan for Textboxes in all the forms Sr. No. 1.
2.
3.
Action Input Data Entering data Text in a text box in which only text is allowed Entering data Numbers and in a text box in special which only text characters is allowed Entering data Numbers
Expected Result Actual Result Data enters in Objective is textboxes. achieved and data gets entered.
Data should not get entered in textboxes. Data enters in
Objective is achieved and data does not get entered. Objective is
4.
5.
6.
in a text box in which only numbers are allowed Entering data in a text box in which only numbers are allowed Entering data in a text box in which only date is allowed Entering data in a text box in which only date is allowed
textboxes.
achieved and data gets entered.
Text and special characters
Data should not get entered in textboxes.
Objective is achieved and data does not get entered.
date
Date is entered in specified format.
Objective is achieved and date gets entered.
Text and special characters
Data is not entered.
Objective is achieved and data does not get entered.
Test plan for Combo boxes in all the forms Sr. No. 1.
Action Selecting data from combo boxes
Input Data Numeric Data, text, special characters
Expected Result Actual Result Data should not Objective be entered, Achieved. instead it should 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.
