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

Overview of Technologies Used

3.1 Front End Technology

The Java Language

The Java language is a remarkable example of programming language evolution. Java

builds on the familiar and useful features of C++ while removing its complex, dangerous,
and superfluous elements. The result is a language that is safer, simpler, and easier to use.
The following subsections describe Java in contrast to C++. Appendix B, "Differences
Between Java and C++," provides a detailed identification of the differences between the
two languages.
Java Is Familiar and Simple

If you have ever programmed in C++, you will find Java's appeal to be instantaneous.
Since Java's syntax mirrors that of C++, you will be able to write Java programs within
minutes. Your first programs will come quickly and easily, with very little programming
overhead.

You will have the feeling that you have eliminated a lot of clutter from your programs-and
you will have. All the cryptic header files and pre-processor statements of C and C++ are
gone. All the arcane #define statements and typesets have been taken away. You will no
longer have to delve through several levels of header files to correctly reference API calls.
And no one will have to suffer to figure out how to use your software.

13
Java programs simply import the software packages they need. These packages may be in
another directory, on another drive, or on a machine on the other side of the Internet. The
Java compiler and interpreter figure out what objects are referenced and supply the
necessary linkage.

Java Is Object-Oriented

If you think C++ is an object-oriented programming language, you are in for a big
surprise. After using Java to write a few programs, you'll get a better feeling for what
object-oriented software is all about. I know I did.

Java deals with classes and objects, pure and simple. They aren't just more data structures
that are available to the programmer-they are the basis for the entire programming
language.

In C++, you can declare a class, but you don't have to. You can declare a structure or a
union instead. You can declare a whole bunch of loosely associated variables and use them
with C-style functions. In Java, classes and objects are at the centre of the language.
Everything else revolves around them. You can't declare functions and procedures. They
don't exist. You can't use structures, unions, or typedefs. They're gone, too. You either use
classes and objects or you don't use Java. It's that simple.

Java provides all the luxuries of object-oriented programming: class hierarchy,

inheritance, encapsulation, and polymorphism-in a context that is truly useful and
efficient. If you are new to object-oriented software, you can find a complete introduction
to these topics is provided in Chapter 5, "Classes and Objects." The main reason for
developing object-oriented software, beside clarity and simplicity, is the desperate hope
that somehow the objects you develop will be reused. Java not only encourages software
reuse, it demands it. To write any sort of Java program, no matter how simple, you must
build on the classes and methods of the Java API.

Once you have begun developing software in Java, you have two choices:
Build on the classes you have developed, thereby reusing them.
Rewrite your software from scratch, copying and tailoring useful parts of existing
software.

14
With Java, the temptation to start from scratch is no longer appealing. Java's object-
oriented structure forces you to develop more useful, more tailor able, and much simpler
software the first time around.
Java Is Safer and More Reliable

Java is safer to use than C++ because it keeps you from doing the things that you do badly,
while making it easier to do the things that you do well.

Java won't automatically convert data types. You have to explicitly convert from one class
to another. C++, under the most undesirable conditions, will automatically convert one
type to another. It has all the flexibility of assembly code. Java doesn't assume that you
know what you are doing. It makes sure that you do.

C++ pointers don't exist in Java. You can no longer access objects indirectly or by chance.
You don't need to. You declare objects and reference those objects directly. Complex
pointer arithmetic is avoided. If you need an indexed set of objects, you can use an array
of objects. The concept of "the address of an object" is eliminated from the programming
model, and another assembly language dinosaur is laid to rest. As a result, it becomes
much easier to do things correctly in Java.

Java's reliability extends beyond the language level to the compiler and the runtime
system. Compile-time checks identify many programming errors that go undetected in
other programming languages. These checks go beyond syntactic checking to ensure that
statements are semantically correct.

Runtime checks are also more extensive and effective. Remember your teacher or mom
telling you to "Check your work twice to make sure it's right"? The Java linker
understands class types and performs compiler-level type checking, adding redundancy to
reliability. It also performs bounds checking and eliminates indirect object access, even
under error conditions.
Java Is Secure

15
If you gave a skilled hacker a program written in C or C++ and told him to find any
security flaws, there are half a dozen things that he would immediately look for: gaining
access to the operating system, causing an unexpected return of control, overwriting
critical memory areas, acquiring the ability to spoof or modify other programs, browsing
for security information, and gaining unauthorized access to the file system.

Why is C or C++ more vulnerable than Java? When a programmer develops software, he
or she usually focuses on how to get the software to work correctly and efficiently. C and
C++ do not constrain the programmer from meeting these goals and provide a number of
flexible features that enable the programmer to meet his end. The hacker is also able to
take advantage of these features and use them in ways that weren't originally intended,
causing the undesirable consequences identified in the previous paragraph. In short, C and
C++ provide a great offense, but no defense. Java, on the other hand, is defensive by
nature. Every time a Java-enabled browser downloads a compiled Java class, such as an
applet, it runs the risk of running Trojan horse code. Because of this ever-present threat, it
subjects the code to a series of checks that ensure that it is correct and secure.

The Java runtime system is designed to enforce a security policy that prevents execution
of malicious code. It does this by remembering how objects are stored in memory and
enforcing correct and secure access to those objects according to its security rules. It
performs bytecode verification by passing compiled classes through a simple theorem
prover that either proves that the code is secure or prevents the code from being loaded
and executed. The class is Java's basic execution unit and security is implemented at the
class level.

The Java runtime system also segregates software according to its origin. Classes from the
local system are processed separately from those of other systems. This prevents remote
systems from replacing local system software with code that is less trustworthy.

Java-enabled browsers, such as HotJava, allow the user to control the accesses that Java
software may make of the local system. When a Java applet needs permission to access
local resources, such as files, a security dialog box is presented to the user, requesting
explicit user permission. This "Mother may I?" approach ensures that the user always has
the final say in the security of his system.

16
Java security is covered in detail in Chapter 39, "Java Security."
Java Is Multithreaded

Java, like Ada, and unlike other languages, provides built-in language support for
multithreading. Multithreading allows more than one thread of execution to take place
within a single program. This allows your program to do many things at once: make the
Duke dance, play his favorite tune, and interact with the user, seemingly all at the same
time. Multithreading is an important asset because it allows the programmer to write
programs as independent threads, rather than as a convoluted gaggle of intertwined
activities. Multithreading also allows Java to use idle CPU time to perform necessary
garbage collection and general system maintenance, enabling these functions to be
performed with less impact on program performance.

Writing multithreaded programs is like dating several people concurrently. Everything

works fine until the threads start to interact with each other in unexpected ways. Java
provides the support necessary to make multithreading work safely and correctly. Java
supports multithreading by providing synchronization capabilities that ensure that threads
share information and execution time in a way that is thread safe. These capabilities are
illustrated with several programming examples in Chapter 8, "Multithreading."

Java Is Interpreted and Portable

While it is true that compiled code will almost always run more quickly than interpreted
code, it is also true that interpreted code can usually be developed and fielded more
inexpensively, more quickly, and in a more flexible manner. It is also usually much more
portable.

Java, in order to be a truly platform-independent programming language, must be

interpreted. It does not run as fast as compiled native code, but it doesn't run much slower,
either. Chapter 36, "The Java Source Code," provides some Java performance
benchmarks. For the cases where execution in native machine code is absolutely essential,
work is underway to translate Java bytecode into machine code as it is loaded.

17
The advantages of being interpreted outweigh any performance impacts. Because Java is
interpreted, it is much more portable. If an operating system can run the Java interpreter
and support the Java API, then it can faithfully run all Java programs.

Interpreted programs are much more easily kept up-to-date. You don't have to recompile
them for every change. In Java, recompilation is automatic. The interpreter detects the fact
that a program's bytecode file is out-of-date with respect to its source code file and
recompiles it as it is loaded.

Because of Java's interpreted nature, linking is also more powerful and flexible. Java's
runtime system supports dynamic linking between local class files and those that are
downloaded from across the Internet. This feature provides the basis for Web
programming.
Java Is the Programming Language of the Web

Java has become the de facto programming language of the Web. It is being licensed by
nearly every major software company. It has some offshoots and potential competition,
such as JavaScript, VBScript, and Bell Labs's Inferno, but it remains the first Web
programming language and the most powerful language for developing platform-
independent software.

Java is also evolving beyond the Web and becoming a key component in distributed
application development. Sun's release of the NEO and JOE products emphasizes Java's
importance to distributed object-based software development. Several other vendors have
introduced products that enable Java to be integrated into the Common Object Request
Broker Architecture (CORBA), which is the framework for distributed object
communication.

The Java API

The Java API is what makes Java attractive and useful. It consists of a set of packages that
are distributed with the JDK as class libraries. These packages provide a common
interface for developing Java programs on all Java platforms. The Java API furnishes all
the capabilities needed to develop console programs, window programs, client and server
networking software, applets, and other applications. It is the difference that takes Java

18
from being a really good programming language to making it a very powerful and efficient
programming environment.

The Java API consists of eight major development packages and a supporting debug
package, as shown in Figure 2.9. Packages are collections of related objects. For example,
there are separate packages for developing window programs, applets, and networking
software.

19
Eclipse
Eclipse is an integrated development environment (IDE) for developing primarily
with Java, but also with other languages, in particular PHP, C/C++, and HTML5. It is also
an application platformframework for Java desktop applications and others.
The Eclipse IDE is written in Java and can run on Windows, OS X, Linux, Solaris
and other platforms supporting a compatible JVM.
The Eclipse Platform allows applications to be developed from a set of modular
software components called modules. Applications based on the Eclipse Platform
(including the Eclipse IDE itself) can be extended by third party developers.
The Eclipse Team actively support the product and seek future suggestions from
the wider community. Every release is preceded by a time for Community testing and
feedback

BACK END TECHNOLOGY:

About My SQL Server 2000

My SQL Server is a Structured Query Language (SQL) based, client/server

relational database. Each of these terms describes a fundamental part of the
architecture of SQL Server.

Database

A database is similar to a data file in that it is a storage place for data. Like a
data file, a database does not present information directly to a user; the user
runs an application that accesses data from the database and presents it to the
user in an understandable format.

A database typically has two components: the files holding the physical
database and the database management system (DBMS) software that

20
applications use to access data. The DBMS is responsible for enforcing the
database structure, including:
 Maintaining the relationships between data in the database.
 Ensuring that data is stored correctly and that the rules defining data
relationships are not violated.
 Recovering all data to a point of known consistency in case of system
failures.

Relational Database

There are different ways to organize data in a database but relational databases
are one of the most effective. Relational database systems are an application of
mathematical set theory to the problem of effectively organizing data. In a
relational database, data is collected into tables (called relations in relational
theory).
When organizing data into tables, you can usually find many different ways to
define tables. Relational database theory defines a process, normalization,
which ensures that the set of tables you define will organize your data
effectively.
Client/Server:-
In a client/server system, the server is a relatively large computer in a central
location that manages a resource used by many people. When individuals need
to use the resource, they connect over the network from their computers, or
clients, to the server.
Examples of servers are: In client/server database architecture, the database
files and DBMS software reside on a server. A communications component is
provided so applications can run on separate clients and communicate to the
database server over a network. The SQL Server communication component
also allows communication between an application running on the server and
SQL Server.

Server applications are usually capable of working with several clients at the
same time. SQL Server can work with thousands of client applications

21
simultaneously. The server has features to prevent the logical problems that
occur if a user tries to read or modify data currently being used by others.

While SQL Server is designed to work as a server in a client/server network, it

is also capable of working as a stand-alone database directly on the client. The
scalability and ease-of-use features of SQL Server allow it to work efficiently
on a client without consuming too many resources.

Structured Query Language (SQL)

To work with data in a database, you must use a set of commands and
statements (language) defined by the DBMS software. There are several
different languages that can be used with relational databases; the most
common is SQL. Both the American National Standards Institute (ANSI) and
the International Standards Organization (ISO) have defined standards for
SQL. Most modern DBMS products support the Entry Level of SQL-92, the
latest SQL standard (published in 1992).

SQL Server Features

My SQL Server supports a set of features that result in the following benefits:

Ease of installation, deployment, and use

SQL Server includes a set of administrative and development tools that

improve your ability to install, deploy, manage, and use SQL Server across
several sites.

Scalability

The same database engine can be used across platforms ranging from laptop
computers running Microsoft Windows® 95/98 to large, multiprocessor
servers running Microsoft Windows NT®, Enterprise Edition.

Data warehousing

22
SQL Server includes tools for extracting and analyzing summary data for
online analytical processing (OLAP). SQL Server also includes tools for
visually designing databases and analyzing data using English-based questions.

System integration with other server software

SQL Server integrates with e-mail, the Internet, and Windows.

Databases

A database in My SQL Server consists of a collection of tables that contain

data, and other objects, such as views, indexes, stored procedures, and triggers,
defined to support activities performed with the data. The data stored in a
database is usually related to a particular subject or process, such as inventory
information for a manufacturing warehouse.

SQL Server can support many databases, and each database can store either
interrelated data or data unrelated to that in the other databases. For example, a
server can have one database that stores personnel data and another that stores
product-related data. Alternatively, one database can store current customer
order data, and another; related database can store historical customer orders
that are used for yearly reporting. Before you create a database, it is Important
to understand the parts of a database and how to design these parts to ensure
that the database performs well after it is implemented.

Normalization theory:

Relations are to be normalized to avoid anomalies. In insert, update and delete

operations. Normalization theory is built around the concept of normal forms.
A relation is said to be in a particular form if it satisfies a certain specified set
if constraints. To decide a suitable logical structure for given database design
the concept of normalization, which are briefly described below.

23
 1. 1 st Normal Form (1 N.F): A relation is said to be in 1 NF is and
only if all unaligned domains contain values only. That is the fields of
an n-set should have no group items and no repeating groups.
2. 2 nd Normal Form (2 N.F) : A relation is said to be in 2 NF is and
only if it is in 1 NF and every non key attribute is fully dependent on
primary key. This normal takes care of functional dependencies on
non-key attributes.
3. 3 rd Normal Form (3 N.F) : A relation is said to be in 3 NF is and
only if it is in 2 NF and every non key attribute is non transitively
dependent on the primary key. This normal form avoids the transitive
dependencies on the primary key.
4. Boyce code Normal Form (BCNF) : This is a stronger definition than
that of NF. A relation is said to be in BCNF if and only if every
determinant is a Candidate key.
5. 4 th Normal Form (4 NF) : A relation is said to be in 4 NF if and
only if whenever there exists a multi valued dependency in a relation
say A->->B then all of the relation are also functionally dependent
on A(i.e. A->X for all attributes x of the relation.).
6. 5 th Normal Form (5 NF) OR Projection Join Normal Form (PJNF):
A relation R is in 5 NF .if and only if every join dependency in R is
implied by the candidate key on R. A relation can’t be non-loss split
into two tables but can be split into three tables. This is called Join
Dependency.

Client-side Script (JAVASCRIPT):

JavaScript:

JavaScript is a new scripting language for WebPages. Scripts written with java
script can be embedded into your HTML pages. With java script you have
many possibilities for enhancing your HTML page with interesting elements.
For example you are able to respond to user-initiated events quite easily.
Some effects that are now possible with java script were some time ago only

24
possible with CGI. So you can create really sophisticated pages with the helps
of java script on the Internet.

How can Java Script scripts run?

The first browser to support java script was the Netscape Navigator 2.0 of
course the higher versions do have java script as well. You might know that
java does not run on all Netscape Navigators 2.0 (or higher versions) versions.
But this is not true for java script -although there are some problems with the
different versions.

The Mac version for example seems to have many bugs. In the near future
there are going to be some other browsers, which support java script. The
Microsoft Internet explorer 3.0 is going to support java script. JavaScript
enabled browsers are going to spread soon - it is worth learning this new
technique now. You might realize that is really easy to write Java Script
scripts. We have to know is some basic techniques and some work-around for
problems you might encounter. Of course we need a basic. Understanding
HTML before reading this tutorial you can find many really good online
resources about HTML. Best you make an online search about ‘html’ at yahoo
if you want to get informed about HTML. Now I want to show some small
scripts so you can learn how they are implemented into HTML-documents and
to show which possibilities you have with the new scripting language. The
following is a very small script, which will only print a text into an HTML
document.

<html>
<head>
My first JavaScript
</head>
<body><br>

25
This is a normal HTML document
<br>
<script language=”JavaScript”>
Document.write (“this is a java script”)
</script><b r>
Backing HTML again
</body>
</html>

If you are using a java script enabled-browser at the moment then you will
have the possibility to see this script working. If your browser doesn’t support
Java Script then this output might be some kind of strange…
This is a normal HTML document
This is java script!
Back in HTML again.

Functions

Functions are bet declared between the <Head> tag of HTML page. Functions
are called by user-initiated events. Seems reasonable to keep the functions
between the <Head> tags. They are loaded first before a user can do anything
that might call a function. Scripts can be placed between inside comment
fields to ensure that older browser do not display the script itself.
<html>
<head>
<script language=”JavaScript”>
function pushbutton ()
{
alert (“Hello!”);
}
</script>

26
</head>
<body>
<form>
<input type=”button” name=”Button1” value=”push me” onclick=”pushbutton
()”>
</form>
</body>
</html>

If we want to test this one immediately and you are using a Java Script
enabled browser then please go ahead and push the button.
This script will create a button and when you press it a window will pop up
saying “hello!” In fact we have a lot of possibilities just by adding functions to
our scripts.
The common browsers transmit the form information by either method:
here’s the complete tag including the GET transmission method attribute for
the previous form

Example

<Form method =GET action=http://www.mycompany.com/cgi-bin/upfdate.pl>

………
</form>

Input elements.

Use the <input> tag to define any one of a number of common form elements
including text fields multiple choice lists click able images and submission
buttons. There are many attributers for this tag only that types and name
attributes are required for each element, each type of input element uses only a
subset of the followed attributes. Additional <input> attributes may be
required based upon which type of the form element you specify.

27
Submit button:

The submit button (<input type=submit>) does what its name implies, settings
in motion the form’s submission to the server from the browser. We many
have more than submit buttons will be added to the parameter list the browser
sends along to the server.

Example
< Input type =”submit”>
<Input type=”submit” value=”submit” name=”name”>

Reset button:

The reset button if firm <input> button is nearly self- explanatory; it lets the
user reset erase or set to some default value all elements in the form. By
default the browser displays a reset button worth the label “reset”. We can
change that by specifying a value attribute with tour own button label.

FEASIBILITY STUDY:

Feasibility study is conducted once the problem is clearly understood.

Feasibility study is a high level capsule version of the entire system analysis
and design process. The objective is to determine quickly at a minimum
expense how to solve a problem. The purpose of feasibility is not to solve the
problem but to determine if the problem is worth solving.

The system has been tested for feasibility in the following points.
1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.

28
Technical Feasibility
The project entitles "Courier Service System” is technically
feasibility because of the below mentioned feature. The project was developed
in Java which Graphical User Interface.

It provides the high level of reliability, availability and compatibility.

All these make Java an appropriate language for this project. Thus the existing
software Java is a powerful language.

Economical Feasibility

The computerized system will help in automate the

selection leading the profits and details of the organization. With this
software, the machine and manpower utilization are expected to go up by 80-
90% approximately. The costs incurred of not creating the system are set to be
great, because precious time can be wanted by manually.

Operational Feasibility

In this project, the management will know the details of each project
where he may be presented and the data will be maintained as decentralized
and if any inquires for that particular contract can be known as per their
requirements and necessaries.

Implementation:

Implementation is the stage where the theoretical design is turned into a

working system. The most crucial stage in achieving a new successful system
and in giving confidence on the new system for the users that it will work
efficiently and effectively.

29
The system can be implemented only after thorough testing is done and if it is
found to work according to the specification.

It involves careful planning, investigation of the current system and its

constraints on implementation, design of methods to achieve the change over
and an evaluation of change over methods a part from planning. Two major
tasks of preparing the implementation are education and training of the users
and testing of the system.

The more complex the system being implemented, the more involved will be
the systems analysis and design effort required just for implementation.

The implementation phase comprises of several activities. The required

hardware and software acquisition is carried out. The system may require some
software to be developed. For this, programs are written and tested. The user
then changes over to his new fully tested system and the old system is
discontinued.

TESTING:
The testing phase is an important part of software development. It is the
computerized system will help in automate process of finding errors and
missing operations and also a complete verification to determine whether the
objectives are met and the user requirements are satisfied.

Software testing is carried out in three steps:

1. The first includes unit testing, where in each module is tested to

provide its correctness, validity and also determine any missing operations and
to verify whether the objectives have been met. Errors are noted down and
corrected immediately. Unit testing is the important and major part of the
project. So errors are rectified easily in particular module and program clarity
is increased. In this project entire system is divided into several modules and is
developed individually. So unit testing is conducted to individual modules.

30
 2. The second step includes Integration testing. It need not be the
case, the software whose modules when run individually and showing perfect
results, will also show perfect results when run as a whole. The individual
modules are clipped under this major module and tested again and verified the
results. This is due to poor interfacing, which may results in data being lost
across an interface. A module can have inadvertent, adverse effect on any other
or on the global data structures, causing serious problems.

3. The final step involves validation and testing which

determines which the software functions as the user expected. Here also some
modifications were. In the completion of the project it is satisfied fully by the
end user.

Maintenance and environment:

AS the number of computer based systems, grieve libraries of computer
software began to expand. In house developed projects produced tones of
thousand soft program source statements. Software products purchased from
the outside added hundreds of thousands of new statements. A dark cloud
appeared on the horizon. All of these programs, all of those source statements-
had to be corrected when false were detected, modified as user requirements
changed, or adapted to new hardware that was purchased. These activities were
collectively called software Maintenance.
The maintenance phase focuses on change that is associated with error
correction, adaptations required as the software's environment evolves, and
changes due to enhancements brought about by changing customer
requirements. Four types of changes are encountered during the maintenance
phase.

Correction
Adaptation
Enhancement
Prevention

31
Correction:

Even with the best quality assurance activities is lightly that the customer
will uncover defects in the software. Corrective maintenance changes the
software to correct defects.

Maintenance is a set of software Engineering activities that occur after

software has been delivered to the customer and put into operation. Software
configuration management is a set of tracking and control activities that began
when a software project begins and terminates only when the software is taken
out of the operation.

We may define maintenance by describing four activities that are undertaken

after a program is released for use:

Corrective Maintenance
Adaptive Maintenance
Perfective Maintenance or Enhancement
Preventive Maintenance or reengineering

Only about 20 percent of all maintenance work are spent "fixing mistakes".
The remaining 80 percent are spent adapting existing systems to changes in
their external environment, making enhancements requested by users, and
reengineering an application for use.

ADAPTATION:

Over time, the original environment (E>G., CPU, operating system,

business rules, external product characteristics) for which the software was
developed is likely to change. Adaptive maintenance results in modification to
the software to accommodate change to its external environment.

ENHANCEMENT:

32
 As software is used, the customer/user will recognize additional functions
that will provide benefit. Perceptive maintenance extends the software beyond
its original function requirements.

PREVENTION:

Computer software deteriorates due to change, and because of this,

preventive maintenance, often called software re engineering, must be
conducted to enable the software to serve the needs of its end users. In essence,
preventive maintenance makes changes to computer programs so that they can
be more easily corrected, adapted, and enhanced. Software configuration
management (SCM) is an umbrella activity that is applied throughout the
software process.

SOFTWARE METHODOLOGY

The software methodology followed in this project includes the object-

oriented methodology and the application system development methodologies.
The description of these methodologies is given below.

Application System Development – A Life cycle Approach

Although there are a growing number of applications (such as decision

support systems) that should be developed using an experimental process
strategy such as prototyping, a significant amount of new development work
continue to involve major operational applications of broad scope. The
application systems are large highly structured. User task comprehension and
developer task proficiency is usually high. These factors suggest a linear or
iterative assurance strategy. The most common method for this stage class of
problems is a system development life cycle modal in which each stage of
development is well defined and has straightforward requirements for
deliverables, feedback and sign off. The system development life cycle is

33
described in detail since it continues to be an appropriate methodology for a
significant part of new development work.

The basic idea of the system development life cycle is that there is a
well-defined process by which an application is conceived and developed and
implemented. The life cycle gives structure to a creative process. In order to
manage and control the development effort, it is necessary to know what
should have been done, what has been done, and what has yet to be
accomplished. The phrases in the system development life cycle provide a
basis for management and control because they define segments of the flow of
work, which can be identified for managerial purposes and specifies the
documents or other deliverables to be produced in each phase.

The phases in the life cycle for information system development are
described differently by different writers, but the differences are primarily in
the amount of necessity and manner of categorization. There is a general
agreement on the flow of development steps and the necessity for control
procedures at each stage.
The information system development cycle for an application consists of three
major stages.
Definition.
Development.
Installation and operation.

The first stage of the process, which defines the information requirements for
a feasible cost effective system. The requirements are then translated into a
physical system of forms, procedures, programs etc., by the system design,
computer programming and procedure development. The resulting system is
test and put into operation. No system is perfect so there is always a need for
maintenance changes. To complete the cycle, there should be a post audit of
the system to evaluate how well it performs and how well it meets the cost and
performance specifications. The stages of definition, development and
installation and operation can therefore be divided into smaller steps or phrases
as follows.

34
Definition

Proposed definition : preparation of request for proposed applications.

Feasibility assessment: evaluation of feasibility and cost benefit of proposed
system.
Information requirement analysis: determination of information needed.

Design

Conceptual design : User-oriented design of application development.

Physical system design: Detailed design of flows and processes in applications
processing system and preparation of program specification.

Development

Program development : coding and testing of computer programs.

Procedure development : design of procedures and preparation of user
instructions.

Installation and operation

Conversion : final system test and conversion.
Operation and maintenance: Month to month operation and maintenance
Post audit : Evaluation of development process, application
system and results of use at the completion of the each phase, formal approval
sign-off is required from the users as well as from the manager of the project
development.

35
 SECTION 3

SOFTWARE ENGINEERING PARADIGM

APPLIED

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

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

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

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

40
 SECTION 4

Software Project Development Methodology

41
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

42
 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

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

44
 SECTION 5

DESIGN

5.1 Data Flow Diagram (DFD)

5.2 DataBase Design

5.3 Entity Relationship Diagram

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

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

47
5.3 ENTITY-RELATIONSHIP DIAGRAM

48
SECTION 6

SOURCE CODE

49
50
 SECTION 7

SCREEN LAYOUTS

51
Homepage

AboutPage

52
Services

Gallery

53
AdminLogin

StaffLogin

54
UserLogin

NewUserPage

55
ContactPage

AdminMainPage

56
AddStaffPage

AddPlanPage

57
AdminViewReportsPage

AdminViewUsersPage

58
ADMINVIEWSTAFFSPAGE

Adminviewplanspage

59
AdminViewContactsPage

60
SECTION 8

TESTING

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

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

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

64
 SECTION 9

IMPLEMENTATION

9.1 Hardware Requirement

9.2 Software Requirement

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

REQUIREMENT ANALYSIS
HARDWARE REQUIREMENTS

 Hardware :Processor Intel dual core and above

 Clock speed :3.0 GHz

 RAM size :512 MB

 Hard Disk capacity :400 GB

 Monitor type :15 inch color monitor

SOFTWARE REQUIREMENTS

 Operating System :Windows XP, Windows 7, Windows

8,Windows 10

 Application :HTML, CSS, JS, JSP, SERVLET

 Browser :Google chrome, Firefox

 Database :MySQL.

 Documentation :MS-Office

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

67
SECTION 10

MAINTAINENCE

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

69
SECTION 11

CONCLUSION

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

71
 SECTION 12

BIBLIOGRAPHY

72
 Bibliography

[1]C.Larman, Applying uml and patterns an introduction to object-oriented

analysis and design and iterative development, 3rd Massachusettes Perason
Education,2005
[2]D.Carrington,CSSE3002 Course Note,School of ITEE University of
Queensland,2008.
[3]IEEE Recommended Practive for Software Requirements
Specifications,IEEE Standard 830,1998 [4]Nutr, “Recipe Menu Dev”, 2005
[5]Bayou and Bennet, “Profitability analysis for seat reservation
system”,1992
[6]Software Engineering of Airline Reservation Systems by Web Services
[7]GHIRS: Integration of Airline Reservation Systems by Web Services
[8]V.Swapna.M.Fridouse Ali Khan “Design and Implementations of Airline
Reservation Systems in International Journal of Engineering Research &
Technology

73