Mini Project 2014

Mini Project 2014
CHAPTER 1
INTRODUCTION
1.1. PROJECT OVERVIEW
The project K.S.R.T.C MANAGEMENT maintains the arrival & departure of bus in
Calicut station. Application of bus management helps the station employees to do their
work in a simple and easy manner. The station master will have a record of the K.S.R.T.C
station employees which helps him /her to create the report efficiently. This project makes
the work in a K.S.R.T.C office more flexible and easier manner. He can assign the
employees to a trip after checking the availability of them.
1.2. OBJECTIVES
By doing this project the authorities of K.S.R.T.C can have the details of route
and time of the each bus in an easier and simple manner. This aims to:
Help to monitor the details of all employees.
Used to assign services and route.
Used to record the attendance details of employees.
Department of information technology
Page 1
Mini Project 2014
CHAPTER 2
SYSTEM ANALYSIS
2.1. EXISTING SYSTEM
There is no knowledge for station master about the duties of each employee by
checking existing system. He/she is unaware about the daily collections of each trip of
different bus to different route. It is very difficult to check the details of each employee for
updating, viewing and deleting the details.
2.1.1. Drawbacks
Some drawbacks for manual system
Time consumption
Error factor
Bulk volume of data cannot be handled
Difficult to maintain
Less security
2.2. PROPOSED SYSTEM

In this project all disadvantages of the existing system can be removed. Our system can be
guarantee security to the data as well as user information .All the particulars regarding the
members of a group are kept private. By doing this project the authorities of K.S.R.T.C can
have the details of route and time of the each bus in an easier and simple manner. Our
system has following features:
Advantages
High response time
Cost effective solution
Robustness
Possibility of upgrading
Easy of usage
Page 2
Mini Project 2014
Normalized forms helps to avoid data redundancy
High speed& accuracy
Enhanced security
2.3. FEASIBILITY STUDY

Feasibility study is a test of a system proposal, according to its workability, impact on
the organization, ability to meet the user needs and effective use of resources. Thus when a
new application is proposed, it normally goes through a feasibility study before it goes for
development. The main objective of feasibility study is not solving the problem but not 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. Every project is feasible,
given unlimited resources and infinite time. It is both necessary and prudent to evaluate the
project at the earliest possible time. So a detailed study is carried out to check the
workability of the system.
The result of feasibility is a formal proposal. This is simply a document detailing the
nature and scope of the proposed solution. The proposal summarizes what is known and
what is going to be done.
The three important test for feasibility are
Operational feasibility
Technical feasibility
Economic feasibility
2.3.1. Economical Feasibility

Economical analysis system is the most frequently used method for evaluating the
effectiveness of the candidate system. It is more commonly known as cost/benefit and
saving that are expected from the candidate system and compare them with costs. It benefits
outweigh costs; the decision is made to design and implement the system. Otherwise, further
justification or alteration in the proposed system will have to be made if it is having a chance
of being approved.
Page 3
Mini Project 2014
2.3.2. Operational Feasibility

Proposed projects are beneficial only if they can be turned into information system
that will meet the operating requirements of the organization. This test of feasibility asks if
the system will work when it is developed and installed. Some of the important questions
that are useful to test the operational feasibility of a project can be given below:
Is there sufficient support for the project from the management? From users? If the
present system is well liked and used to extent that the persons will not able to see
reasons for a change, there may be resistance.
Are current business methods acceptable to the users? If they are not? Users may
welcome a change that will bring about a more operational and useful system.
Are the users been involved in the planning and development of the project? If
they are involved at the earlier stage of the project developed, the changes of
resistance can be possibly reduced.
Issues that appear to be quite minor at the earlier stage can grow into major
problems after implementation. Therefore, it is always advisable to consider
operational aspects carefully.
2.3.3. Technical Feasibility

The assessment of technical feasibility must be based on outline design of system
requirements of input, outputs, files, programs, procedures and staff. This can be quantified
in terms of volumes of data , trends, frequency of updating , etc. having identified an outline
system , the investigator must go on to suggest the type of equipment required , methods of
developing the system, and methods of running the system.
With regard to the processing facilities, the feasibility study will need to consider the
possibility of using a bureau or, if in-house equipment is available the nature of the hardware
to be used for data collection, storage output and processing. On this system development
side, the feasibility study must consider the various ways of acquiring the system.
Page 4
Mini Project 2014

These include the purchase of the package the use of consultancy organization or
software house to design the system and write the programs. There are a number of technical
issues, which are generally raised during the feasibility stage of the investigation.
They are as follows:
Does the necessary technology exists to do what is suggested (and can it be

acquired)?
Does the proposed equipment have the technical capacity to hold the data required
to use the new system?
Can the system be upgraded if developed?
Are there technical guarantees of accuracy, reliability, ease of access and security?
Page 5
Mini Project 2014
CHAPTER 3
SYSTEM SPECIFICATION
Hardware and software requirements for the installation and smooth functioning of this
product could be configured based on the requirements needed by the component of the
operating environment that works as front-end system here we suggest minimum
configuration for the both hardware and software components.
Working off with this software is requirements concrete on system environments. It
includes three phases.
Hardware Requirements
Software Requirements
3.1. HARDWARE REQUIREMENTS
Pentium 4 processor
512 RAM
40 GB HDD
1024*768 Resolution Color Monitor
3.2. SOFTWARE REQUIREMENTS
Java Platform Standard Edition(JAVA SE)1.6
Net Beans 8.0 IDE
MYSQL
Page 6
Mini Project 2014
CHAPTER 4
SOFTWARE DESCRIPTION
4.1. FRONT END: JAVA
.
Java is a general-purpose computer programming language that is concurrent, classbased, object-oriented, and specifically designed to have as few implementation
dependencies as possible. It is intended to let application developers "write once run
anywhere" (WORA), meaning that code that runs on one platform does not need to be
recompiled to run on another. Java applications are typically compiled to byte code that can
run on any java virtual machine (JVM) regardless of computer architecture. Java is, as of
2014, one of the most popular programming languages in use, particularly for client-server
web applications, with a reported 9 million developers. Java was originally developed by
James Gosling at Sun Microsystems (which has since merged into Oracle Corporation) and
released in 1995 as a core component of Sun Microsystems' java platform. The language
derives much of its syntax from C and C++, but it has fewer low level facilities than either
of them.
The original and reference implementation Java compiler, virtual machines, and class
libraries were originally released by Sun under proprietary licenses. As of May 2007, in
compliance with the specifications of the java community process, Sun relicensed most of
its Java technologies under the GNU general public license. Others have also developed
alternative implementations of these Sun technologies, such as the GNU compiler for
java (byte code compiler), GNU class path (standard libraries), and iced-tea-Web (browser
plug-in for applets).
4.1.1 Java platform
The main goal of Java is portability, which means that programs written for the Java
platform must run similarly on any combination of hardware and operating system with
adequate runtime support. This is achieved by compiling the Java language code to an
intermediate representation called java byte code, instead of directly to architecturespecific machine code. Java byte code instructions are analogous to machine code, but they
are intended to be executed by a virtual machine (VM) written specifically for the host
hardware. End users commonly use a java runtime environment (JRE) installed on their own
machine for standalone Java applications, or in a web browser for Java applets.
Standardized libraries provide a generic way to access host-specific features such as
graphics, threading and networking.
A major benefit of using byte code is porting. However, the overhead of interpretation
means that interpreted programs almost always run more slowly than programs compiled to
Page 7
Mini Project 2014

native executables would. Just-in-Time (JIT) compilers were introduced from an early stage
that compilebytecodes to machine code during runtime.
4.1.2 Implementation
Oracle Corporation is the current owner of the official implementation of the Java SE
platform, following their acquisition of Sun Microsystems on January 27, 2010. This
implementation is based on the original implementation of Java by Sun. The Oracle
implementation is available for Microsoft Windows, Mac OS X, Linux and Solaris. Because
Java lacks any formal standardization recognized by Ecma International, ISO/IEC, ANSI, or
other third-party standards organization, the Oracle implementation is the de facto standard.
The Oracle implementation is packaged into two different distributions: The Java Runtime
Environment (JRE) which contains the parts of the Java SE platform required to run Java
programs and is intended for end users, and the java development kit (JDK), which is
intended for software developers and includes development tools such as the java
compiler, javadoc, jar, and a debugger.
Open JDK is another notable Java SE implementation that is licensed under the GNU GPL.
The implementation started when Sun began releasing the Java source code under the GPL.
As of Java SE 7, Open JDK is the official Java reference implementation.
The goal of Java is to make all implementations of Java compatible. Historically, Sun's
trademark license for usage of the Java brand insists that all implementations be
"compatible". This resulted in a legal dispute with Microsoft after Sun claimed that the
Microsoft implementation did not support RMI or JNI and had added platform-specific
features of their own. Sun sued in 1u997 and in 2001 won a settlement of US$20 million, as
well as a court order enforcing the terms of the license from Sun. As a result, Microsoft no
longer ships windows with Java.
Platform-independent Java is essential to java EE, and an even more rigorous validation is
required to certify an implementation. This environment enables portable server-side
applications.
4.1.3 Performance
Programs written in Java have a reputation for being slower and requiring more
memory than those written in C++. However, Java programs' execution speed improved
significantly with the introduction of just-in-time-compilation in 1997/1998 for java 1.1, the
addition of language features supporting better code analysis (such as inner classes, the
String Builder class, optional assertions, etc.), and optimizations in the Java virtual machine,
such as Hotspot becoming the default for Sun's JVM in 2000.
Page 8
Mini Project 2014
4.2. BACK END: MYSQL

There are many databases that support the use of SQL to access their data, among them
MYSQL and PostgreSQL. In other words, MYSQL is just the brand of one database
software, one of many. The same goes for PostgreSQL. These two databases are very
popular among programs that run on websites (probably because they are free), which is
why you often see one or both of them being advertised in the feature lists of web hosts, as
well as being listed as one of the "system requirements" for certain web software (like blogs
and content management systems).
Page 9
Mini Project 2014
CHAPTER 5
PROJECT DESCRIPTION
5.1. PROBLEM DEFINITION

K.S.R.T.C MANAGEMENT is a system that can help the station master to
manage their daily activity. This system help reduce the problems occur when using
the manual system. This project covers all aspects of management and operations of
a K.S.R.T.C office.
5.2. MODULE DESCRIPTION

There is only one module in the system design for the project. This is the only person
who can login the system.
5.2.1. Module
5.2.1.1. Admin Module
The admin here indicates the administrator for our application i.e., station master.
The admin for the application is the head of the K.S.R.T.C office. The admin has control
over the entire activity. The admin has the provision to verify the workers, employees and
divide the work among the teams etc. The major functions of admin are:
Registration
Login
Add users
View, Update &Delete staff details
Page 10
Mini Project 2014
5.3. DATAFLOW DIAGRAM
CONTEXT LEVEL
LEVEL 1
Page 11
Mini Project 2014
5.4 DATABASE DESIGN
5.4.1. LOGIN TABLE
5.4.2. BUS TABLE
5.4.3. ROUTE TABLE
Page 12
Mini Project 2014
5.4.4. STAFF TABLE
Page 13
Mini Project 2014
CHAPTER 6
SYSTEM TESTING
Test Plan
The Software Test Plan describes plans for qualification testing of Computer
Software configuration Items and software systems. It describes the Software test
environment to be used for the testing, identifies the test to performed, and provides
schedules for test activities.
Testing strategy
The overall strategy for Software testing is described in the following section. We
will use four different methods to test our software.
6.1. UNIT TESTING
In unit testing, the analyst tests the programs making up a system. This is also called
program testing. The software units that make up the system are modules and the routines,
which are assembled and integrated to perform a specific function in a large system. Many
modules at different levels are needed. Unit testing, independent of one another, focuses on
modules to locate error. This enables the tester to detect error in coding and logic that are
contained within that module alone. Those resulting from the interaction between modules
are initially avoided. Unit Test comprises the test of performed prior to integration of the
unit into the entire project. Four categories of test are performed on each unit.
Functional Test
The code is exercised with nominal input values for which the expected results are
shown, as well as boundary values (Minimum values, Maximum values) and values on
and just outside the functional boundaries and special values such as logically related
inputs.
Page 14
Mini Project 2014
Performance Test
Performance test is done to determine the amount of execution time spent in various
parts of the unit, program throughput, and response time and device utilization by the
program unit. Some time is taken initially to link to the SQL.
Stress Test
Stress Test has been done to intentionally break the unit. This helps in the learning
about the strength and limitations of the program by examining the manner in which a
program unit breaks.
Structure Test
Structure test are done to test the internal logic of a program and traversing particular
exercise, deriving test data to exercise those paths, determining the test coverage criteria to
be used.
6.2. ACCEPTANCE TESTING
After the developers complete the system testing successfully acceptance testing is
done at the customer end. It is the customer or the end user who knows designs the test
cases. in this type of testing emphasis is on the usability of the product. Acceptance testing
is supported through alpha and beta testing. Alpha testing is done when the software is made
operational for the first time to be tested by the users at developers site. Hence it is possible
that it will involve making lot of changes to program code. Beta testing follows alpha testing
but now the testing is done at the customers site that validates the product after using it for
few days. At this stage few changes as compared to alpha testing would make to the product.
6.3. TEST CASES
The evaluation of test cases is done through test case review. And for any review, a
formal document or work product is needed. This is the primary reason for having the test
case specification in the form of document. The test case specification document is
reviewed, using a formal review process, to make sure that the test cases are consistent with
the policy specified in the plan, satisfies the chosen criteria, and in general cover the various
aspect of the unit to be tested.
Page 15
Mini Project 2014

For this process, the reason for selecting the test case and the expected output are also
given in the test case specification document. By looking at the conditions being tested by
the test cases, the reviewer can check if all the important conditions are being tested. As
conditions can also be based on the output, by considering the expected output of the test
cases it can also be determined the production of all the different types of output the unit is
supposed to produce are being tested.
Page 16
Mini Project 2014
CHAPTER 7
SYSTEM IMPLEMENTATION
Implementation is the process of converting a new or revised system design into an
optional one. It is the key stage in achieving a successful new system because usually it
involves a lot of upheaval in the user department. It must therefore be carefully planned and
prepared. Once the software is fully developed and implemented, the department starts to
use the software. The department also grows and more divisions may be attached, or the
database of the department can grow in size. So after sometime the software, this has to be
installed need some modification. If the software need modification all the needed to
develop new software has to be executed. The need has to be studied, the design has to be
made and the coding has to be done. The new module has to be connected to the existing
software modules Even if the software working perfectly also we have to do routine testing
and new bug if found out, has to be fixed. No software ever developed will be bug free
forever.
Page 17
Mini Project 2014
CHAPTER 8
APPENDIX
8.1 SCREEN SHOT
Page 18
Mini Project 2014
Page 19
Mini Project 2014
Page 20
Mini Project 2014
Page 21
Mini Project 2014
Page 22
Mini Project 2014
Page 23
Mini Project 2014
Page 24
Mini Project 2014
Page 25
Mini Project 2014

CHAPTER 9
CONCLUSION
This application provides a user friendly approach towards the system. The system
has been well developed and is found to satisfy all of the requirements. There is a hope that
this software will be utilized to its maximum and will do a good job in long run. This phase
gives me a good idea on developing full-fledge software satisfy the user requirements. The
programming technique used in the design of the system provides scope for further
expansion and implementation of any changes which may occur in future. The design was
developed in a NETBEANS IDE 8.0 platform with JAVA it is expected to leave up to the
objective for which it was designed.
Application of bus management helps the station employees to do their work in a simple and
easy manner. The station master will have a record of the K.S.R.T.C station employees
which helps him /her to create the report efficiently .
Page 26
Mini Project 2014

REFERENCE
Programming with Java-Headfirst
Elements of system analysis -Fourth Edition, By Marvin Gore & John W Stubbe
Elias M Awed ,System Analysis and design 2,Galgotia publication 1997
Fundamentals of database Systems-Elmasri & Navathe-3/e, Addison-Wesley
Software Engineering-Ian Somerville-Pearson Education
Page 27

Mini Project 2014

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Mini Project 2014

Загружено:

Авторское право:

Доступные форматы

Mini Project 2014

Help to monitor the details of all employees.

Used to assign services and route.

Used to record the attendance details of employees.

Department of information technology