T.Y.B.

SC (CS) SEM-5 2022-2023

K.M.AGRAWAL COLLEGE OF ARTS, COMMERCE

AND SCIENCE

KALYAN

NAAC ACCREDITED B++

CERTIFICATE
This is to certify that Mr./Ms. _________________________________________ Exam Seat
No______________ has satisfactorily completed the Journal on
__________________________________________________ for partial fulfillment of the 3
yearFull Time Course Bachelor of Computer Science (SEM-V ) of the University of Mumbai for the
year 2022-2023.

Exam Seat No:___________

Place : KALYAN Date : ___/___/___

__________________ __________________ _______________________

Prof. In-Charge In-Charge External Examiner Signature
Self-Finance Department

K.M.AGRAWAL COLLEGE OF ARTS COMMERCE AND SCIENCE DEPARTMENT OF COMPUTER SCIENCE 2022-2023. 1
T.Y.B. SC (CS) SEM-5 2022-2023

UNIVERSITY OF MUMBAI

K.M.AGRAWAL COLLEGE OF ARTS, COMMERCE AND SCIENCE

KALYAN-421301

A PROJECT REPORT
ON
“ONLINE BOOK SELLING-MYBRARY”

PROJECT WORK SUBMITTED IN PARTIAL FULFILLMENT

OF THE REQUIREMENT FOR THE AWARD OF THE
DEGREE OF
T.Y.B.SC.(COMPUTER SCIENCE)

SUBMITTED BY:
SAYALI SAINATH ABHANG
2022-2023

PROJECT GUIDE:
PROF. VIJAY VASTAVA

K.M.AGRAWAL COLLEGE OF ARTS COMMERCE AND SCIENCE DEPARTMENT OF COMPUTER SCIENCE 2022-2023. 2
T.Y.B. SC (CS) SEM-5 2022-2023

ABSTRACT

This is report aims at introducing the “ONLINE BOOK SELLING-

MYBRARY”. This report provide facility for purchasing online books

This report maintains all the relevant information about public who
order books. These software is developed considering the needs of shop
for maintaining the customers.

This report depicts only the basic logic used for the software
development along with flowchart so that any reader may the understand
the logic applied. For further information readers may refer to the source
code provided along with this project.

K.M.AGRAWAL COLLEGE OF ARTS COMMERCE AND SCIENCE DEPARTMENT OF COMPUTER SCIENCE 2022-2023. 3
T.Y.B. SC (CS) SEM-5 2022-2023

ACKNOWLEDGEMENT

It is always difficult task to acknowledgement all those who helped

me a lot doing this project. Never the less I have made an attempt
through this report to express my deepest gratitude to all those who
have contributed in making this project either directly or indirectly.
I give me great pleasure to present my project on “ONLINE BOOK
SELLING-MYBRARY”.
This is my first milestone in B.Sc. (Computer science). I would like to
thanks to my sincere project guide Prof. VIJAY VASTAVA who
helped me throughout the project for acknowledgement the help to
guidance provided by him for my project in every situation and also
about presentation of the project.

I would like thanks our principal Prof. ANITA MANNA for her
support and facilities given to us for the same.

I would like to thank all my teacher of Computer Science

faculty who help me in complete of my Project.

SAYALI SAINATH ABHANG.

K.M.AGRAWAL COLLEGE OF ARTS COMMERCE AND SCIENCE DEPARTMENT OF COMPUTER SCIENCE 2022-2023. 4
T.Y.B. SC (CS) SEM-5 2022-2023

Phase Table
Sr. No. Phase Title Remarks

I ANALYSIS PHASE

Organizational Overview

Description System

Limitations of Present System

Proposed System and its advantages

Feasibility Study

Gantt Chart

II SYSTEM ANALYSIS

Fact Finding Techniques

Prototypes (if any)

Event Table

Use Case Diagram, Scenarios &

Use Case Description

ERD

Activity Diagram

Class Diagram

Object Diagram

Sequence Diagram/ Collaboration Diagram

State Diagram

III SYSTEM DESIGN.

Converting ERD to Tables

Design Class Diagram

K.M.AGRAWAL COLLEGE OF ARTS COMMERCE AND SCIENCE DEPARTMENT OF COMPUTER SCIENCE 2022-2023. 5
T.Y.B. SC (CS) SEM-5 2022-2023

Component Diagram

Package Diagram

Deployment Diagram

Program Flow charts & System flow chart

IV SYSTEM IMPLEMENTATION

V PROJECT SUBMISSION

K.M.AGRAWAL COLLEGE OF ARTS COMMERCE AND SCIENCE DEPARTMENT OF COMPUTER SCIENCE 2022-2023. 6
T.Y.B. SC (CS) SEM-5 2022-2023

INDEX
Sr. No. Title Page
No.
1. Introduction to project 9-12
1.1. INTRODUCTION TO PROJECT
1.2. ORGANIZATION PROFILE
1.3. PURPOSE OF THE PROJECT
1.4. PROBLEM IN EXISTING SYSTEM
1.5. LIMITATIONS IN PRESENT SYSTEM

2. Feasibility Study 13-14

2.1. TECHNICAL FEASIBILITY
2.2. OPERATIONAL FEASIBILITY
2.3. ECONOMIC FEASIBILITY

3. Stake holders 15

4. Gantt Chart 16

5. System Analysis 17-41

5.1. INTRODUCTION
5.2. SYSTEM WORKFLOW
5.3. STUDY OF THE SYSTEM
5.4. HARDWARE & SOFTWARE REQUIRMENT
5.5. PROPOSED SYSTEM
5.6. INPUT & OUTPUT
5.7. PROCESS MODELS USED WITH JUSTIFICATION
5.8 EVENT TABLE
5.9 USE CASE DIAGRAM
5.10 ER DIAGRAM
5.11 ACTIVITY DIAGRAM
5.12 CLASS DIAGRAM
5.13 SEQUENCE DIAGRAM
5.14 STATE DIAGRAM

K.M.AGRAWAL COLLEGE OF ARTS COMMERCE AND SCIENCE DEPARTMENT OF COMPUTER SCIENCE 2022-2023. 7
T.Y.B. SC (CS) SEM-5 2022-2023

6. System Design 42-50

6.1. INTRODUCTION
6.2. DFD DIAGRAM
6.3. COMPONENT DIAGRAM
6.4. DEPLOYMENT DIAGRAM
6.5. SYSTEM FLOW CHART

7. System Testing and Implementation 51-53

7.1. INTRODUCTION
7.2. UNIT TESTING
7.3. TEST

8. Design and Coding 54-86

9. Database Table 87-91

10. System Security 92-93

10.1. INTRODUCTION
10.2. SECURITY IN SOFTWARE

11. Conclusion Future Improvement 94

12. Bibliography 94

K.M.AGRAWAL COLLEGE OF ARTS COMMERCE AND SCIENCE DEPARTMENT OF COMPUTER SCIENCE 2022-2023. 8
Computer
project

Name:-
Reg num:-
Topic:-

GYM MANAGEMENT SYSTEM

2
 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

3. Software Engineering Paradigm Applied

4. Software Project Development Methodology.

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

3
 SECTION 1

INTRODUCTION

1.1 Introduction to the Project

1.2 Objectives Of The Project

4
 INTRODUCTION TO THE PROJECT

This project is designed to facilitate a gymming and fitness

center to automate its operations of keeping records and
store them in form of a large and user friendly database
further facilitating easy access to the personnel.

5
OBJECTIVES OF THE PROJECT

 What was the Problem?

 Existing system was manual.

 Time consuming as data entry which include calculations took lot

of time.

 Searching was very complex as there could be 100’s of entry

every year.

 The proposed system is expected to be faster than the existing

system.

 The Project was made in order to effectively and efficiently cater

to requirements of the fitness center.Very frequently the person
who generally holds the tasks to manage the center needs to
keep records of all the transactions as well as data mannually .
Gennerally, In order to structure these tasks Separate Registers
are maintained.This whole process thus becomes quite
cumbersome for them to control manually.Moreover,Any wrong
data entered mistakenly can brings serious results.

 This Mannually Managed system of the store was also heavily

proned to data loss due to certain causes Misplacement of
Registers,Destruction of Registers ,Unauthorized access to
registers etc. which can bring in disasterous Consquences.

 The cost of maintaince of data and records of occurrence of

transactions is very high.

 Searching a particular data specific to particular requirements is

also very tedious in such system.In order to retrieve records,The
responsible person needs to manually locate the appropriate
register and locate the appropriate placement of that particular
record which may be very time consuming.

 Data Redundency is also a great issue in such kind of

system.”Redundency” means repititon;Thus data modified or
updated at a particular place may not be data modified or
updated at the other related place which may create
inconsistencies in data handling,Destroys Data Integrity and
creates confusion for the owner.

6
  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.

 All the data pertaining to transactions or other important entities is

kept at central database from where its attributes can be easily
controlled.But,Such kind of technical details are hidden from the
standalone User. He just needs to type in correct details of the given
entity and then click the save button with the help of
mouse.However,That central repository of data can be easily
accessed if required.

 Data Redundency is no more the problem now.The data modified

from one particular data entry form will reflect the modifications at
the other related forms too.This has thus reduced the chances of
data inconsistency in our data storage.

 There is no need to manage bulky registers now as data stored in

the backend database can be radily retrieved either from the
frontend form itself or directly from the database.

 Requires one time investment of setting up required Hardware and

Software after which no more headache is required by the
Managers.Moreover,It also reduces dependence on Man Power.

 Effective Search measures are present at each and every data

transactional forms from where by just entering a Unique keyword
for that data its whole records can be readily seen within
microseconds.Moreover,Facillity of Updation and Deletion of data
through search is also available.

7
 SECTION 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.3.4 Behavioural Feasibility

2.4 Proposed System Functionality

8
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:

1. Identify the customer’s need.

2. Evaluate the system concept for feasibility.

3. Perform economic and technical analysis.

4. Allocate functions to hardware, software people, database and

other system elements.

5. Establish cost and schedule constraints.

6. Create a system definition that forms the foundation for all the
subsequent engineering work.

2.1 Identification of Customer’s Need

Before proceding further ,It becomes very necessary to accumilate
the valid and conviencing requirements of the project and
communicate the very same to various stakeholders of the project.
This step is initiation of System Analysis. An overview of the
client’s requirement has been done. The basic need of the client to
opt for such kind of project is analysed. As per current marketing
scenario, an entire system was required to track day-to-day
transactions.
Client was following a Manual Process, which is not at all
compatible with its current working conditions. It was not only time
consuming, but also lacks accuracy. Security point of view the
manual system was failed to hide the information from any
unauthenticiated staff or any outside person. Therefore, there was
an urgent requirement of such Computerised System which can
fullfill all of its current as well as future requirements. Further
more, data handling was also posing a serious problem for them.

9
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:

 Member’s Details Register:

This Register is maintained in liu to maintain the records of the
various members of the gymming center.The document contains
relevant information about the various members such as members’s
id, Name,Address,Telephone number.

 Employee’s Details Register:

This Register is maintained in liu to maintain the records of the
various employees of the gymming center.The document contains
relevant information about the various employees such as
employee’s id, Name,Address,Telephone number.

 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.

2.3 Feasibilty Study

Depending on the results of the initial investigation, the
survey is expanded to a more detailed feasibility study.
Feasibility study is a test of system proposal according to
its workability, impact on the organization, ability to meet
user needs, and effective use of resources. The objective
of the feasibility study is not to solve the problem but to
acquire a sense of its scope . During the study, the
problem definition is crystallized and aspects of the
problem to be included in the system are determined.
Consequently, costs and benefits are described with
greater accuracy at this stage.
It consists of the following:

1. Statement of the problem:

A carefully worded statement of the problem that
led to analysis.
2. Summary of finding and recommendations:
A list of the major findings and recommendations of
the study. It is ideal for the user who requires quick
access to the results of the analysis of the system
under study. Conclusion are stated , followed by a list
of the recommendation and a justification for them .

10
 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.

4. Recommendations and conclusions:

Specific recommendations regarding the candidate
system, including personnel assignments, costs, project
schedules, and target dates.

2.3.1 Technical Feasibility

Technical feasibility centers around the existing computer
system (Hardware and Software etc) and to what extend it
support the proposed addition. For example, if the current
computer is operating at 80 percent capacity - an arbitrary
ceiling - then running another application could overload the
system or require additional Hardware. This involves financial
considerations to accommodate technical enhancements. If the
budgets is a serious constraint ,then the project is judged not
feasible. In this project, all the necessary cautions have been
taken care to make it technically feasible. Using a key the
display of text/object is very fast. Also, the tools, operating
system and programming language used in this localization
process is compatible with the existing one.

2.3.2 Economical Feasibility

Economic analysis is the most frequently used method for
evaluating the effectiveness of the candidate system. More
commonly known as cost/benefit analysis, the procedure is to
be determining the benefits and savings that are expected from
a candidate and compare them with costs. If benefits outweigh
costs, then the decision is made to design and implement the
system.

A systems financial benefit must exceed the cost of developing

that system. i.e. a new system being developed should be a
good investment for the organization. Economic feasibility
considers the following:
i. The cost to conduct a full system investigation.
ii. The cost of hardware and software for the class of
application.
iii. The benefits in the form of reduced cost or fewer
costly errors.

11
 iv. The cost if nothing changes (i.e. The proposed system
is not developed).

The proposed SYSTEM is economically feasible because

i. The system requires very less time factors.
ii. The system will provide fast and efficient automated
environment instead of slow and error prone manual
system, thus reducing both time and man power
spent in running the system.
iii. The system will have GUI interface and very less user
training is required to learn it.
iv. The system will provide service to view various
information if required for some decision making.

2.3.3 Operational Feasability

This Application is very easy to operate as it is made user
friendly with the help of very effective GUI tools . Main
consideration is user’s easy access to all the functionality of the
Application.Another main consideration is here is that whether
user organization is trained enough to use the newer
application. Here every functionality is As per previous
operational strategy which is not expected to be cumbersome to
the potential clients.

2.3.4 Behavioural Feasibility

People are inherently resistant to change, and computers have

been known to facilitate change. An estimate should be made of
how strong a reaction the user staff is likely to have toward the
development of a computerized system. Therefore it is
understandable that the introduction of a candidate system
requires special efforts to educate and train the staff.The
software that is being developed is user friendly and easy to
learn.In this way, the developed software is truly efficient and
can work on any circumstances ,tradition ,locales.
Behavioral study strives on ensuring that the equilibrium of the
organization and status quo in the organization are nor
disturbed and changes are readily accepted by the users.

12
2.4 Proposed System Functionality

The proposed system will be designed to support the following

features:-

 The proposed system has a user friendly Interface for porting

of data to server.

 The proposed system provides the facility to pull the data from
the server using a key (such as id) and get the desired report.

 The proposed system provides the no replication of data

13
 SECTION 3

SOFTWARE ENGINEERING PARADIGM

APPLIED

14
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.

The basic approach that software engineering takes is to separate the

development process from the software. The premise is that the
development process controls the quality, scalability, consistency, and
productivity. Hence to satisfy the objectives, one must focus on the
development process. Design of proper development process and
their control is the primary goal of the software engineering. It is this
focus on the process that distinguishes it from most other computing
desciplines. Most other computing disciplines focus on some type of
the product-algorithms, operating systems, databases etc. while
software engineering focuses on the process for producing products.
To better manage the development process and to achieve
consistency, it is essential that the software development be done in
phases.

Different Phases Of The Development Process:

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.

15
 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.

16
 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.

The steps in the spiral model can be generalized as follows:

1. The new system requirements are defined in as much detail as

possible. This usually involves interviewing a number of users
representing all the external or internal users and other aspects
of the existing system.

2. A preliminary design is created for the new system.

3. A first prototype of the new system is constructed from the

preliminary design. This is usually a scaled-down system, and
represents an approximation of the characteristics of the final
product.

4. A second prototype is evolved by a fourfold procedure:

17
 1. Evaluating the first prototype in terms of its strengths,
weaknesses, and risks;

2. Defining the requirements of the second prototype;

3. Planning and designing the second prototype;

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

 Estimates (i.e. budget, schedule, etc.) become more realistic as

work progresses, because important issues are discovered earlier.

 It is more able to cope with the changes that software

development generally entails. Software engineers can get their
hands in and start working on the core of a project earlier.

18
 SECTION 4

Software Project Development Methodology

19
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.

 Modular Break –Up Of The System:

 Identify The Various Modules In The System.
 List Them In The Right Hierarchy.
 Identify Their Priority Of Development.

Different Modules In Computerised System

Modules – This project consists of different interfaces which will

be accessed through a MDI (Multiple Document Interface) window.
Different modules that makeup this system have already been a
described in system analysis.

 Module 1: Member’s Module

In this module,Owner can see the membership details which
includes:

 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

20
 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.

 Module 2:Employee’s Module

In this module owner can see the employee details including the
fields:
1. ID
2. Name
3. Gender
4. Wage
5. Address
6. Date of birth
7. Phone number
8. Payroll calculation
i. Pay date
ii. ID
iii. Name
iv. Hours worked
v. Gross pay
vi. Tax
vii. Net pay
Along with this there is a provision for setting the schedule of the employees
with information like time and day provided and the owner can view the
schedule or even change it.

 Module 3: Inventory module

It is further divided into three components:
1. INVENTORY
Gives description about a product based on its category and
includes:
a.Category
b.Id
c.Description
d.Brand
e.Quantity
f.Date
2. ORDER

21
 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.

22
 Principal Design Features
INTRODUCTION OF VISUAL BASIC

Visual Basic (VB) is a third-generation event-driven

programming language and associated development environment
(IDE) from Microsoft for its COM programming model. Visual Basic
was derived from BASIC and enables the rapid application
development (RAD) of graphical user interface (GUI)
applications, access to databases using Data Access Objects DAO,
Remote Data Objects RDO, or ActiveX Data Objects ADO and creation
of ActiveX controls and objects. Scripting languages such as VBA and
VBScript are syntactically similar to Visual Basic, but perform
differently.

A programmer can put together an application using the components

provided with Visual Basic itself. Programs written in Visual Basic can also
use the Windows API, but doing so requires external function declarations.
Characteristics present in Visual Basic

Visual Basic has the following traits which differ from C-derived
languages:

 Boolean constant True has numeric value −1.This is because the

Boolean data type is stored as a 16-bit signed integer. In this
construct −1 evaluates to 16 binary 1s (the Boolean value True),
and 0 as 16 0s (the Boolean value False). This is apparent when
performing a Not operation on a 16 bit signed integer value 0
which will return the integer value −1, in other words True = Not
False. This inherent functionality becomes especially useful when
performing logical operations on the individual bits of an integer
such as And, Or, Xor and Not. This definition of True is also
consistent with BASIC since the early 1970s Microsoft BASIC
implementation and is also related to the characteristics of
microprocessor instructions at the time.

 Logical and bitwise operators are unified. This is unlike all the C-
derived languages (such as Java or Perl), which have separate

23
 logical and bitwise operators. This again is a traditional feature of
BASIC.

 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.

OPTION BASE was introduced by ANSI, with the standard for

ANSI Minimal BASIC in the late 1970s.

 Relatively strong integration with the Windows operating

system and the Component Object Model.

 Banker's rounding as the default behavior when converting real

numbers to integers with the Round function.

 Integers are automatically promoted to reals in expressions

involving the normal division operator (/) so that division of an
odd integer by an even integer produces the intuitively correct
result. There is a specific integer divide operator (\) which does
truncate.

 By default, if a variable has not been declared or if no type

declaration character is specified, the variable is of type Variant.
However this can be changed with Deftype statements such as
DefInt, DefBool, DefVar, DefObj, DefStr. There are 12 Deftype
statements in total offered by Visual Basic 6.0. The default type

24
 may be overridden for a specific declaration by using a special
suffix character on the variable name (# for Double, ! for Single,
& for Long, % for Integer, $ for String, and @ for Currency) or
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.

INTRODUCTION OF Microsoft Access-2003

Microsoft Office Access, previously known as Microsoft Access, is a
relational database management system from Microsoft that combines
the relational Microsoft Jet Database Engine with a graphical user
interface and software development tools. It is a member of the 2007
Microsoft Office system.
One of the benefits of Access from a programmer's perspective is its
relative compatibility with SQL (structured query language) —queries
may be viewed and edited as SQL statements, and SQL statements can
be used directly in Macros and VBA Modules to manipulate Access
tables. Users may mix and use both VBA and "Macros" for
programming forms and logic and offers object-oriented possibilities.

MSDE (Microsoft SQL Server Desktop Engine) 2000, a mini-version of

Microsoft SQL Server 2000, is included with the developer edition of
Office XP and may be used with Access as an alternative to the Jet
Database Engine.

Unlike a modern RDBMS, the Jet Engine implements database triggers

and stored procedures in a non-standard way. Stored Procedures are
implemented in VBA, and Triggers are only available from embedded
Forms. Both Triggers and Stored procedures are only available to
applications built completely within the Access database management
system. Client applications built with VB or C++ are not able to access
these features. Starting in Access 2000 (Jet 4.0), there is a new syntax
for creating queries with parameters, in a way that looks like creating
stored procedures, but these procedures are still limited to one
statement per procedure.Microsoft Access does allow forms to contain
code that is triggered as changes are made to the underlying table (as
long as the modifications are done only with that form), and it is
common to use pass-through queries and other techniques in Access to
run stored procedures in RDBMSs that support these.

Why I Used Ms Access?

I used Ms Access because it is simply available in almost all the

machines that is normally using Ms Office.

 The Ms Access is easily portable from one machine to other Machine.

25
 The MS Access has a good & Highly Interactive Graphic User
Interface.

 MS Access is less costlier than other RDBMSs’ for small scale use.

SECTION 5

DESIGN

5.1 Data Flow Diagram (DFD)

5.2 DataBase Design

5.3 Entity Relationship Diagram

26
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.

Context Level or Zero Level DFD

This level shows the overall context of the system and it's operating
environment and shows the whole system as just one process.

The Context Diagram or the Zero Level DFD.

Member details
Database Operations on
MEMBERS record
Member list

Database Operations on
Reciept
GYM EMPLOYEES record
CENTER’S Member’s Record
RECORD
MANAGEMEN Database Operations on
Employee details
-T SYSTEM INVENTIRY record

Employee schedule

IInventory(orders
and products)

27
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

A table is a set of data elements (values) that is organized using

a model of vertical columns (which are identified by their name)
and horizontal rows. A table has a specified number of columns,
but can have any number of rows.

28
 List of Tables in Database:

Name of Database is “Gym_members.mdb”

Table 1: LOGIN VALUES

Table 2: MEMBER DETAILS

29
Table 3: RECIEPT GENERATION

Table 4: EMPLOYEE DETAILS

30
Table 5: EMPLOYEE PAYROLL

Table 6: EMPLOYEE SCHEDULE

31
Table 7: INVENTORY TABLE

32
5.3 ENTITY-RELATIONSHIP DIAGRAM

33
34
 SECTION 6

SCREEN LAYOUTS

35
Login screen of the Fitness Club Management System

Menu Interface of the Fitness Club Management

System(members tab selected)

36
MEMBERSHIP FORM(AND DETAILS)

MEMBERSHIP RECORDS

37
MEMBERSHIP RECIEPT

38
Menu Interface of the Fitness Club Management
System(employees tab selected)

39
EMPLOYEE SCHEDULE

EMPLOYEE DETAILS FORM

40
DELETING AN EMPLOYEE RECORD

EMPLOYEE PAYROLL CALCULATION FORM

41
Menu Interface of the Fitness Club Management
System(inventory tab selected)

42
INVENTORY FORM

ORDER FORM

43
PRODUCT FORM

44
SECTION 7

TESTING

45
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.

Theoretically, a newly designed system should have all the parts

or sub-systems are in working order, but in reality, each sub-
system works independently. This is the time to gather all the
subsystem into one pool and test the whole system to determine
whether it meets the user requirements. This is the last change
to detect and correct errors before the system is installed for user
acceptance testing. The purpose of system testing is to consider
all the likely variations to which it will be subjected and then push
the system to its limits.

Testing is an important function to the success of the system.

System testing makes a logical assumption that if all the parts of
the system are correct, the goal will be successfully activated.

46
Another reason for system testing is its utility as a user-oriented
vehicle before implementation.

System testing consists of the following five steps:

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.

47
 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 .

5) User Acceptance Testing

An acceptance test has the objective of selling the user on the
validity and reliability of the system. It verifies that the system's
procedures operate to system specifications and that the integrity
of important data is maintained. Performance of an acceptance
test is actually the user's show. User motivation is very important
for the successful performance of the system. After that a
comprehensive test report is prepared. This report shows the
system's tolerance, performance range, error rate and accuracy.

Special Systems Tests:

There are other six tests which fall under special category. They are
described below:

 Peak Load Test: It determines whether the system will handle

the volume of activities that occur when the system is at the peak
of its processing demand. For example, test the system by
activating all terminals at the same time.
 Storage Testing: It determines the capacity of the system to
store transaction data on a disk or in other files. For example,
verify documentation statements that the system will store
10,000 records of 400 bytes length on a single flexible disk.
 Performance Time Testing: it determines the length of time
system used by the system to process transaction data. This test
is conducted prior to implementation to determine how long it
takes to get a response to an inquiry, make a backup copy of a
file, or send a transmission and get a response.
 Recovery Testing: This testing determines the ability of user to
recover data or re-start system after failure. For example, load
backup copy of data and resume processing without data or
integrity loss.
 Procedure Testing: It determines the clarity of documentation
on operation and use of system by having users do exactly what
manuals request. For example, powering down system at the end
of week or responding to paper-out light on printer.
 Human Factors Testing: It determines how users will use the
system when processing data or preparing reports.

48
 SECTION 8

IMPLEMENTATION

8.1 Hardware Requirement

8.2 Software Requirement

49
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.

8.1 Hardware Requirement

Hardware is the term given to machinery itself and to various individual
pieces of equipment. It refers to the physical devices of a computer
system. Thus the input, storage, processing control and output devices
are hardware.
Minimum Hardware Requirement Of Client Side:
Processor: Any Pentium or Equivalent Machine
RAM: 256 MB
HDD: 1.2 GB
CD-ROM: 32X
14 inches Color Monitor
104 Keys Keyboards
Printer: DeskJet 670 C

8.2 Software Requirement

Software means a collection of program where the objective is to

enhance the capabilities of the hardware machine.
Minimum Software Requirement Of Client Side:
Operating System : Windows 9x/NT/2000/Xp
Database : Microsoft Office Access
Front-end : Visual Basic 6.0

50
 IMPLEMENTATION

Once the system was tested, the implementation phase started. A

crucial phase in the system development life cycle is successful
implementation of new system design. Implementations simply mean
converting new system design into operation. This is the moment of
truth the first question that strikes in every one’s mind that whether
the system will be able to give all the desires results as expected from
system. The implementation phase is concerned with user training and
file conversion.
The term implementation has different meanings, ranging from the
conversion of a basic application to a complete replacement of
computer system Implementation is used here to mean the process of
converting a new or revised system design into an operational one.
Conversion is one aspect of implementation. The other aspects are the
post implementation review and software maintainence. There are
three types of implementation:

 Implementation of a computer system to replace a manual

system
 Implementation of a new computer system to replace an existing
one.
 Implementation of a modified application to replace an existing
one.

 Conversion

Conversion means changing from one system to another. The

objective is to put the tested system into operation while holding
costs, risks and personnel irritation to a minimum. It involves
creating computer compatible files; training the operational staff;
installing terminals and hardware. A critical aspect of conversion is
not disrupting the functioning of organization.

 Direct Implementation

In direct implementation; the previous system is stopped and new

system is started up coincidentally. Here there is a direct change
over from manual system to computer-based system. In direct
change over implementation; employess can face the problems.
Suppose our software is not working much efficiently as manual one
then we can’t find the defects in our software. It will not be
beneficial in finding errors.

The proposed system is fully implemented using Direct

Implementation.

51
 SECTION 9

MAINTAINENCE

52
 MAINTENANCE

Once the software is delivered and developed, it enters the

maintenance phase. All systems need maintenance. Software needs to
be maintained because there are often some residual errors or bugs
remaining in the system that must be removed as they are discovered.
Many of these surfaces only after the system has been in operation
sometimes for a long time. These errors once discovered need to be
removed, leading to the software getting changed. Though Maintenance
is not a part of software development, it is an extremely important
activity in the life of a software product.

Maintenance involves understanding the existing software (code and

related documents), understanding the effects of change, making the
changes-to both the code and documents-testing the new parts and
retesting the old part.

53
SECTION 10

CONCLUSION

54
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.

There is always a room for improvement in any software, however

efficient the system may be. The important thing is that the system
should be flexible enough for future modifications. The system has been
factored into different modules to make system adapt to the further
changes. Every effort has been made to cover all user requirements
and make it user friendly.

 Goal achieved: The System is able provide the interface to the

owner so that he can replicate his desired data. .

 User friendliness: Though the most part of the system is

supposed to act in the background, efforts have been made to
make the foreground interaction with user(owner) as smooth as
possible. Also the integration of the existing system with the
project has been kept in mind throughout the development
phase.

55
 SECTION 11

BIBLIOGRAPHY

56
 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

57