Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Chapter - 1

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 67

Chapter – 1

Introduction
1.1 Abstract

All know that the human body is the best Picture of the human soul. Physical fitness is a state
of well-being with low risk of premature health problems and energy to participates in a
variety of physical activities. This project “Gym Management System” is solution fitness
centers to manage the customers in an easier and more convenient way. The administrator, is
able to view all the members of fitness center as well as their details. The basic structure of
the system as follows. This project is a computer-based program and it manages the gym
members, the personal and the inventory. This system also maintains the client details, to
provide the valuable reports regarding the progress of the gym member.

Our Gym Management Software is a gym and health club membership management system.
You can keep records on your members, their memberships, and have quick and easy
communication between you and your members. Gym Management also includes a booking
system, point of sale, banking, accounting, concessions and has a range of reports that help in
the management of your club.
1.2 Introduction of the Gym Management System:

Our Gym Management Software is a complete gym and recreation facility system program
which looks after all of your members, memberships and activities. It is designed for gyms,
recreation centers, and health clubs.

Our Gym management Software provides lots of functions such data entry of customer,
keeping records of all the things about customer’s fees, plan, and physical fitness which help
to provide good quality of services to customer from Gym managers.

In this proposed system also provide the total information about machinery and data of
coaches is also stored in it. Services provided by Gym are also handled by this system.

This system structure is become very simple to understand because of Data Flow Diagram
provided by us. Context level Diagram and Some chart are also available in this case study.
The demo of using the software such as customer detail form, data base of software is also
provided by us.
1.3 Objective of the Gym Management System:

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

1.4 Limitation of Existing System:

• The existing System such as Gym Master is not as much as user (Customer) friendly
as compare to our Proposed System.
• The communication with members is not well in Existing System because all the data
is handled by Gym manager.
• Customers don’t get full accessibility to Gym center and all permissions are allowed
only for Gym manager.
• Today’s System cannot take effort out of finances and debt collection.
• Today’s systems are time taking software and cannot be easily install.
• Lot of memory space is required for installing existing software.
• Existing Gym management software cannot perform all operation expected by
manager such as keeping record of machinery maintenance and service data.
1.5 Abstract of the Project Gym Management System:
Gym Management System is an online service that can be setup for your gym to help
manage classes, memberships, receive payments (merchant and cash), keep track with
detailed statistics, customer management, surveys and it even has an online store so you can
sell products to your customers.

 Its simple, it’s effective and it’s the way customers want their gym!
 Here is our feature list which is continually growing:
 Manage customers
 Manage customer health question forms
 Manage customer surveys
 Screenshot of Customer Options
 Complete site statistics (graphs) membership lists
 Screenshot of User Statistics graphs
 Complete payment statistics with downloadable content to excel and

csv file format.


 Export functions; to download customer details to create mailing lists,

databases…
 Manage your trainers and class schedules.
 Class management
 Create recurring classes and class types
 Create multiple locations and trainers
 Create plans & passes
 Manage customer barcode/RFID/membership cards for customers.
 Customers can see their own statistics and payment history. Complete Online
Store for your products, membership plans & passes.
1.6 Some Salient Features Are …

1. Product and Component based

2. Creating & Changing Gyms at ease

3. Query Gym List to any depth

4. Reporting & Charting in more comprehensive way

5. User Accounts to control the access and maintain security

6. Simple Status & Resolutions

7. Multi-level Priorities & Severities.

8. Targets & Milestones for guiding the programmers

9. Attachments & Additional Comments for more information.


1.7 Modules

1. Authenticate User

The Gym Tracking System first activates the login form. Here the user enters the User name
and password and our system starts the authentication process in which the username and
password are matched with the existing username and password in the database. If the
password matches then it is allowed to the main page else it warns the user for Invalid User
name and password.
After successful authentication the system activates menus. The activity log also prepared
for failures and security.

2. Products

 List Of Products

After successful authentication the user is provided with the list


existing products. Here the user can view the details of products and
can modify the existing products. This project even provides the
facility of adding new projects.

 Product Versions

All the products are maintained in several versions. As it is not


possible to complete the whole project in a single version Features
required for the product are categorized into several version with
dead lines. And the versions are completed according to their dead
line dates. Here the user can add new versions to a product or can
modify the existing details of version.

 Product Users
In order to complete the project each product is allotted with Resources or users. First
all the employees with their names and qualifications are stored in the database. Each
user is allotted to the product based on their rating,
Qualification and designation. For each user Effective date is stored which specifies the total period a
user is valid for that product.
3. Gym Details

 Gym Details

In this module the user is provided with the facility for adding Gyms
or updating the existing Gyms. As the number of Gyms for a product
can be very large this system is provided with efficient filtering. The
user can filter the Gyms based on the priority, database, operating
system and status. After the user applies filter the list of Gyms are
displayed from the database.

 Gym History

Here the Gym history is maintained. All the solutions given for the
Gym resolution by various users are stored. As the Gym needs
several techniques or methods for resolution it is important to store
the history of the Gym.

 Gym Assignee

This displays the list of users for whom the Gym is assigned for
resolution. As the Gym need to be resolved for completing the
product several user are assigned to find a solution for the Gym. The
user can add this Gym to a new user or he can modify the existing
user details.

 Gym Attachments

This gives a list of attachments for a particular Gym. The Gym can be
of any type it can be a database Gym or a GUI Gym. So while you
add a Gym you need to provide with the details of Gym. So the file
attachments can be a document, database file or an image file. All
then attachments are stored in a location along with the size and type
of the file. Here the user can add a new attachment or can change the
details of existing files.
4. Gym Tracking

 Track Hierarchy

All the Gyms saved in the database will have a particular hierarchy. There might be
Gyms which can be related to the earlier Gyms saved in the database so our system is
provided with a hierarchy. And user can add child nodes in this hierarchy or he can
modify the existing values of the nodes. This hierarchy is based on the parent child
relation ship between the Gyms.

 Track Resolution

This displays a list of all solutions provided by the users allotted to a Gym. This stores
the action type and the necessary resolution provided by the user.

 Track Resources

This displays list of resources allotted to the project. As the Gyms need to be resolved
resources are provided for the Gyms. These Resources will be the resources allotted to
the project. The resources are allotted based on the rating of the employee.

5. View
 Product Gym Hierarchy

This module is just for displaying the hierarchy for the easy Look of the
Gyms. Here the Gyms are displayed in the form of parent child nodes. As it
is difficult for the user to look at the vast number of Gyms in the database.
And one cannot easily access the relation between the Gyms.

 Product User Hierarchy

This module if for displaying the users allotted to the Gym. The users along
with their name and designation are displayed in this module. Even in the
allotment of resources there can be hierarchy between the employees
depending on their designation. So this module simplifies the hierarchy
among the employees.
6. Search

Our system provides with the feature of advanced search technique. Generally Number
of Gyms for a project increased tremendously so if we want to know about a particular
Gym It takes much amount of time. With the search screen provided one can filter the
Gym’s base on priority, product, severity, database and type of operating system. He can
also list the Gyms between particular time based on the start date and end date. After
Searching it displays a list of Gyms. From this list the user can modify the existing
Gyms or can add a new Gym.

7. Admin

 Users

All the users of this system are displayed in this module. One can add new
user or can update the details of an existing user. Here the password provided
by the user is encrypted before saving them to the database for proper
security. This module saves the details like address, phone and email.

 Configuration

All the Values that we are using in this system are configurable. Values like
status, priority and others can be added dynamically on the screen. Suppose
if we limit these fields by hot coding them and if the user wants to add a new
value again he has to come to the developer of the product. So In order to
avoid this it is provided with the feature of adding values from the screen.
And the user can change the status to In Active whenever he wants.

 Log View

In order for the efficient Tracking of the system logs are maintained. As the
logs will be in vast it will be a problem for user for checking the database.
The Log View module can be searched based on the user and Records
between a start date and end date.
8. Logout

In this once the user clicks on Log out First the session variable is killed and then the
system is redirected to the login page.

9. Prepare Logs

At all the stages, whenever user performs an operation by clicking a button,


automatically the Gym Tracking System logs the activity.
Chapter - 2
System Analysis
2.1 Introduction To System Analysis
System analysis is a process of gathering and interpreting facts, diagnosing problems and
the information to recommend improvements on the system. It is a problem solving activity
that requires intensive communication between the system users and system developers.
System analysis or study is an important phase of any system development process. The
system is studied to the minutest detail and analyzed.

The system analyst plays the role of the interrogator and dwells deep into the working of the
present system. The system is viewed as a whole and the input to the system are identified.
The outputs from the organizations are traced to the various processes. System analysis is
concerned with becoming aware of the problem, identifying the relevant and decisional
variables, analyzing and synthesizing the various factors and determining an optimal or at
least a satisfactory solution or program of action.

2.2 Detailed study


A detailed study of the process must be made by various techniques like interviews,
questionnaires etc. The data collected by these sources must be scrutinized to arrive to a
conclusion. The conclusion is an understanding of how the system functions. This system is
called the existing system. Now the existing system is subjected to close study and problem
areas are identified. The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as proposals. The proposal is
then weighed with the existing system analytically and the best one is selected. The proposal
is presented to the user for an endorsement by the user.

The proposal is reviewed on user request and suitable changes are made. This is loop that
ends as soon as the user is satisfied with proposal. Preliminary study is the process of
gathering and interpreting facts, using the information for further studies on the system.
Preliminary study is problem solving activity that requires intensive communication
between the system users and system developers. It does various feasibility studies. In these
studies a rough figure of the system activities can be obtained, from which the decision
about the strategies to be followed for effective system study and analysis can be taken.
2.3 Existing System
In the existing system the exams are done only manually but in proposed system we have to
computerize the exams using this application. In gym management system, if we take the
current system and compare with the proposed it is far behind. Every work in the existing is
manual and done on the paper.

There might be a computer used somewhere for the work but it’s is not doing exactly it’s is
supposed which is reducing the manual work. Entering everything manual to the computer
by creating a file is not exactly we are talking in computerization.

The existing system requires a lot of manual work which results in taking more time than it
should. The operations like updating and synchronizing data are also done manually in the
existing system that is not automated and again time-consuming process.

These practices are not at all reliable as the one wrong entry can take a lot of time in
detection and then there is a correction. Humans are prone to errors and can mistakes often
unless it has some inbuilt programs which can take check the input and save from error.

We introduced the system to reduce the manual work effectively as there is the backend of
the system which will take care of synchronizing and updating of the data for the system.

2.4 Proposed System


The aim of proposed system is to develop a system of improved facilities. The proposed
system can overcome all the limitations of the existing system. In gym management system,
after the planning and analysis phase of the system gets completed. Then the next phase
required to transform the collected required system information into structural blueprint
which will serve as a reference while constructing the working system.

It is a phase when most of the risks and error unveiled so it’s is good practices to take care
of this thing from the start.

This is a fully fledged system which will be the backbone of the while management of the
gym so ignoring the risk or error is not an option as later it can make a greater form of itself.

So, it is better to minimize the problems faced by both staff and the manager in the
Organization. Let’s discuss the system in detail:
Chapter - 3

Feasibility Study
3.1 Feasibility Study

Feasibility study is made to see if the project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study
lets the developer foresee the future of the project and the usefulness. A feasibility study of
a system proposal is according to its workability, which is the impact on the organization,
ability to meet their user needs and effective use of resources. Thus when a new application
is proposed it normally goes through a feasibility study .The document provide the
feasibility of the project that is being designed and lists various areas that were considered
very carefully during the feasibility study of this project such as Technical, Economic and
Operational feasibilities. The following are its features:

3.2 Technical Feasibility


The system must be evaluated from the technical point of view first. The assessment of this
feasibility must be based on an outline design of the system requirement in the terms of
input, output, programs and procedures. Having identified an outline system, the
investigation must go on to suggest the type of equipment, required method developing the
system, of running the system once it has been designed.
Technical Gyms raised during the investigation are:

 Does the existing technology sufficient for the suggested one?

 Can the system expand if developed?

The project should be developed such that the necessary functions and performance are
achieved within the constraints. The project is developed within latest technology. Through
the technology may become obsolete after some period of time, due to the fact that never
version of same software supports older versions, the system may still be used. So there are
minimal constraints involved with this project. The system has been developed using PHP
the project is technically feasible for development.
3.3 Economic Feasibility
The developing system must be justified by cost and benefit. Criteria to ensure that effort is
concentrated on project, which will give best, return at the earliest. One of the factors, which
affect the development of a new system, is the cost it would require.
The following are some of the important financial questions asked during preliminary
investigation:

 The costs conduct a full system investigation.

 The cost of the hardware and software.

 The benefits in the form of reduced costs or fewer costly errors.

Since the system is developed as part of project work, there is no manual cost to spend for
the proposed system. Also all the resources are already available, it give an indication of the
system is economically possible for development.
3.4 Product Perspective
In gym management system, after the planning and analysis phase of the system gets completed.
Then the next phase required to transform the collected required system information into
structural blueprint which will serve as a reference while constructing the working system.

It is a phase when most of the risks and error unveiled so it’s is good practices to take care of
this thing from the start.

This is a fully fledged system which will be the backbone of the while management of the gym
so ignoring the risk or error is not an option as later it can make a greater form of itself.

So, it is better to minimize the problems faced by both staff and the manager in the
Organization. Let’s discuss the system in detail:

The gym is working manually. The current system is time consuming and also it is very costly,
because it involves a lot of paperwork. To manually handle the system was very difficult task.
But now-a-days computerization made easy to work.

3.5 Product Functions


Web traffic is the amount of data sent and received by visitors to a web site. It is a large
portion of Internet traffic. This is determined by the number of visitors and the number of
pages they visit. Sites monitor the incoming and outgoing traffic to see which parts or pages
of their site are popular and if there are any apparent trends, such as one specific page being
viewed mostly by people in a particular country. There are many ways to monitor this traffic
and the gathered data is used to help structure sites, highlight security problems or indicate a
potential lack of bandwidth — not all web traffic is welcome. Some companies offer
advertising schemes that, in return for increased web traffic (visitors), pay for screen space
on the site. Sites also often aim to increase their web traffic through inclusion on search
engines.
3.5.1 User Interface

3.5.1.1 HTML has been used for developing the User Layout for the

3.5.1.2 system
3.5.1.3 PHP Script has been used for creating all the
validations and client side scripting functionality
3.5.1.4 CSS has been used for designing the web pages of the system

3.5.2 HARDWARE INTERFACE:

3.5.2.1 Processor: Intel Pentium IV or more


3.5.2.2 Ram : 512 MB or more
3.5.2.3 Cache : 1 MB
3.5.2.4 Hard Disk : 10 GB recommended
3.6 Classes and Objects of the Project
 Login Class: Used for performing all the operations of the login functionality.
 Page Class: Class for managing all the operations of the page.
 Traffic Class: Class for managing the traffic of the website
 IP Class: It has been used for storing all the IPs which hits the website
 Users Class: Class for managing all the user operations
 Permission Class: This class has been used for managing all the
permissions level operations.

3.7 Non-Functional Requirements


 Performance: System should be able handle multiple users at a time
using any of the web browsers.
 Reliability: Database updating should follow transaction processing to avoid data
inconsistency.
 Availability: The project will be deployed on a public shared server so it will be
available all the time and will be accessible anywhere of the world using internet.
 Security: We have implemented a lot of security mechanism to avoid
to hack the system by outer world.
3.7.1 Maintainability: It is very easy to maintain the system. The system
has been developed on HTML so anyone who has the knowledge of
HTML, can easily maintain the system Portability: Yes this system is
portable and we can switch the servers very easily.

3.7.2 Browser Compatibility: The project being web based required


compatibility with at least the popular web browsers. Microsoft
Windows XP and above, Linux and Macintosh being the current
popular operating.
3.8 Security Testing of the Project

Testing is vital for the success of any software. no system design is ever
perfect. Testing is also carried in two phases. first phase is during the software
engineering that is during the module creation. second phase is after the
completion of software. this is system testing which verifies that the whole set
of programs hanged together.

3.8.1 White Box Testing:


In this technique, the close examination of the logical parts through the
software are tested by cases that exercise species sets of conditions or loops.
all logical parts of the software checked once. errors that can be corrected
using this technique are typographical errors, logical expressions which should
be executed once may be getting executed more than once and error resulting
by using wrong controls and loops.

When the box testing tests all the independent part within a module a logical
decisions on their true and the false side are exercised , all loops and bounds
within their operational bounds were exercised and internal data structure to
ensure their validity were exercised once.

3.8.2 Black Box Testing:

This method enables the software engineer to device sets of input techniques
that fully exercise all functional requirements for a program. black box testing
tests the input, the output and the external data. it checks whether the input
data is correct and whether we are getting the desired output.
3.8.3 Alpha Testing:
Acceptance testing is also sometimes called alpha testing. Be spoke systems
are developed for a single customer. The alpha testing proceeds until the
system developer and the customer agree that the provided system is an
acceptable implementation of the system requirements.

3.8.4 Beta Testing:


On the other hand, when a system is to be marked as a software product,
another process called beta testing is often conducted. During beta testing, a
system is delivered among a number of potential users who agree to use it.
The customers then report problems to the developers. This provides the
product for real use and detects errors which may not have been anticipated by
the system developers.

3.8.5 Unit Testing:


Each module is considered independently. it focuses on each unit of software
as implemented in the source code. it is white box testing.

3.8.6 Integration Testing:


Integration testing aims at constructing the program structure while at the
same constructing tests to uncover errors associated with interfacing the
modules. modules are integrated by using the top down approach.

3.8.7 Validation Testing:


Validation testing was performed to ensure that all the functional and
performance requirements are met.
3.8.8 System Testing:
It is executing programs to check logical changes made in it with intention of finding errors. a
system is tested for online response, volume of transaction, recovery from failure etc. System

testing is done to ensure that the system satisfies all the user requirements.
Chapter 4
Implementation And Software Specification
Testing
4.1 Detailed Design of Implementation
This phase of the systems development life cycle refines hardware and
software specifications, establishes programming plans, trains users and
implements extensive testing procedures, to evaluate design and operating
specifications and/or provide the basis for further modification.

4.2 Technical Design


This activity builds upon specifications produced during new system design,
adding detailed technical specifications and documentation.

4.3 Test Specifications and Planning


This activity prepares detailed test specifications for individual modules and
programs, job streams, subsystems, and for the system as a whole.

4.4 Programming and Testing


This activity encompasses actual development, writing, and testing of
program units or modules.

4.5 Project Category


Relational Database Management System (RDBMS) : This is an RDBMS
based project which is currently using MySQL for all the transaction
statements. MySQL is an opensource RDBMS System.
Brief Introduction about RDBSM :
A relational database management system (RDBMS) is a database
management system (DBMS) that is based on the relational model as invented
by E. F. Codd, of IBM's San Jose Research Laboratory. Many popular
databases currently in use are based on the relational database model.

RDBMSs have become a predominant choice for the storage of information in


new databases used for financial records, manufacturing and logistical
information, personnel data, and much more since the 1980s. Relational
databases have often replaced legacy hierarchical databases and network
databases because they are easier to understand and use. However, relational
databases have been challenged by object databases, which were introduced in
an attempt to address the object- relational impedance mismatch in relational
database, and XML databases.
Chapter - 5
System Design
5.0 Objective of project
The main objectives of Gym Management are:

Budget Management
The budget of a exercise department is subjective--classes are usually included in the price of
membership and can go a long way in winning new members and retaining them.

The Budget management makes sure the gym is making a profit each month.

Department Management
Gyms are divided into several departments, which are overseen by the Department
management. Departments include membership, front desk, personal training, group exercise,
housekeeping, facilities and massage. Some gyms have more departments, such as those with
on-site cafes or in-house salons. The Department management holds frequent one-on-one
meetings with department directors as well as meetings with all departments present. The
Management’s principal duty is to listen to departmental needs and concerns and put them in
balance with those of the club.

Member Communications
Management between the club and its members in important communication matters. Even
though the membership, front desk and fitness departments play crucial roles in developing
relationships with members, it’s the good management who takes the ultimate responsibility.

Facility Upkeep
Fitness club managers oversee every aspect of a club, including the daily cleanliness of the
front desk, locker rooms, fitness floor and pool area. Management are also responsible for
supervising the maintenance of current equipment and ordering new equipment.

Gym Objectives
Main objective of our project is provide the better fitness and gain proper profit by the good
management. Management sees all aspects of the gym and is in a position to set short- and
long-term objectives, which are essentially goals.
5.1 Data Flow Diagram
5.2 Use Case Diagram
5.3 ER Case Diagram
Chapter - 6
Data Dictionary & Output Screens
6.1 Data Dictonary

admin
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
Username Varchar 255 -

Password Varchar 255 -

Add Account
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
Gym_name Varchar 255 -

Gym_mob Bigint 20 -

Gym_tele Bigint 20 -

Gym_email Varchar 265 -


Gym_open Time 6 -

Gym_close Time 6 -

Gym_city Varchar 20 -

Gym_address Varchar 75 -

Owner_name Varchar 60 -

Owner_mob Int 20 -

Owner_email Varchar 65 -

Owner_city Varchar 20 -

Owner_address Varchar 75 -

uname Varchar 200 -

pass Varchar 200 -


Equipment
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
Equip_name Varchar 100 -

Equip_qty Int 10 -

OID Int 11 -

image Varchar 100 -

Gym Faclitiy
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
Facili_name Varchar 300 -

Facili_price Int 6 -

OID Int 11 -
Services
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
name_service Varchar 300 -

service_info Varchar 50 -

OID Int 11 -

Type
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
gym_type Varchar 200 -
Member attendance

Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
mem_id Int 11 -

In_time Varchar 100 -

out_time Varchar 100 -

OID Int 11 -

Owner
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
uname Int 11 -

pass Varchar 100 -

Add member
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
Firstname Varchar 30 -

Lastname Varchar 40 -

DOB Date -

Occupation Varchar 60 -

Mobile Bigint 20 -

Emergency_mobile Bigint 20 -

Health_issue Varchar 100 -

Email Varchar 65 -

In_time Time 6 -

Out_time Time 6 -

City Varchar 20 -

Address Varchar 60 -
Gender Varchar 6 -

OID Int 10 -

image Varchar 100 -

Add Staff
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
firstname Varchar 30 -

Lastname Varchar 40 -

DOB Date -

Occupation Varchar 60 -

Mobile Bigint 20 -

Emergency_mobile Bigint 20 -

experience Varchar 10 -
email Varchar 65 -

duty start Time 6 -

duty End Time 6 -

City Varchar 50 -

Address Varchar 200 -

Gender Varchar 10 -

OID Int 10 -

image Varchar 100 -

Attendance
Field Name Data Type Size Key

ID Int 11 Auto-increment,
Primary Key
staff_id Int 10 -

In_time Time -

Out_time Time -

OID Int 10 -

Output Screens
Website Home

About
Services
Equipment
Admin Login

Add Type
Add Account
View Account

Owner Home Page


Add Member
View Member
Add Mem Attendance
View Mem Attendance
Staff Account
Add Facility
View Facility
Add Services
View Services
Add Equipment
View Equipment
Chapter - 7
Conclusion

7.1 Conclusion
The old manual system was suffering from a series of drawbacks. Since whole
of the system was to be maintained with hands the process of keeping,
maintaining and retrieving the information was very tedious and lengthy. The
records were never used to be in a systematic order. there used to be lots of
difficulties in associating any particular transaction with a particular context.
If any information was to be found it was required to go through the different
registers, documents there would never exist anything like report generation.
There would always be unnecessary consumption of time while entering
records and retrieving records. One more problem was that it was very
difficult to find errors while entering the records. Once the records were
entered it was very difficult to update these records. In present, work done in
the electricity board is performed manually which is a great headache for the
department .The reason behind it is that there is lot of information to be
maintained and have to be kept in mind while running the business .For this
reason we have provided features Present system is partially automated
(computerized), actually existing system is quite laborious as one has to enter
same information at three different places.

7.2 Following points should be well considered:

 Documents and reports that must be provided by the new system: there
can also be few reports, which can help management in decision-
making and cost controlling, but since these reports do not get required
attention, such kind of reports and information were also identified and
given required attention.

 Details of the information needed for each document and report.


 The required frequency and distribution for each document.

 Probable sources of information for each document and report.

 With the implementation of computerized system, the task of keeping


records in an organized manner will be solved. The greatest of all is
the retrieval
 of information, which will be at the click of the mouse. So the proposed system helps
in saving the time in different operations and making information flow easy giving
valuable reports.
References and Bibliography:

 http://www.bluedart.com/

 http://www.wampserver.com/en/

 http://www.HTML.net/

 http://www.tutorialspoint.com/mysql/

 httpd.apache.org/docs/2.0/misc/tutorials.html

You might also like