System Analysis

System Development Process

This section describes the system development process to be used. Project Planning and oversight,
System requirement analysis and system modeling.

Project Planning and oversight

A methodology is a collection of strategies for planning , structuring, controlling the
development of an information system. Over the years, a wide range of documented
development approaches have emerged, each with its own set of strengths and weaknesses.
Various sorts of system projects employ available approaches that are best suited to a certain
project’s technical development process. The sorts of methodologies used in project
development are listed below.

Selected methodology for the development

Specially for this project, waterfall model was selected as the development methodology. This
method was selected because it displays the flow of the processes in a logical manner. It is
mostly used in the software development projects and it is simple to comprehend. Waterfall
model works for projects with well-defined requirements, which is one of the benefits that will
help this project.

Waterfall Methodology

The waterfall model is software devloppment process that is seperated into successive phases and
requires that "each step be finished before the next phase may begin". This model which has unique
goals for each development phase,is frequently refffered to as the conventional approach to SDLC.

1.Requirement Gathering -

This is the first step in the waterfall model.During this phase, all user requirements for the project and
system to be developed are gathered and recorded.
2.System Design

In the waterfall model, the second step is the designing the system.

3.System Implementation

In this phase, after the system design, the generation of codes begins. During this phase, each need will
be produced and evaluated for functionality.

4.Testing-

The developed system is then put to test with actual users to check that it fits the requirements.

5.Deployment

After the program has been fully developed, it is released into the market for clients, but only after it has
been throughly tested for both functional and non-functional requirements.

6. Maintenance

When the users encounter problems with the systems, maintenance is frequently performed. To address
these concerns, a system upgrade has been published.

Benefits of the waterfall model

 Errors in designs are captured before any software is built, saving time during the
implementation phase.
 Excellent technical documentation, allowing programmers to work more quickly throughout the
maintenance phase.
 The development of the software system is quantifiable.

Drawbacks of the waterfall model

 Difficult to respond to changes that arise later in the software development process.
 Errors are frequently undetected unless stem testing is performed.'
  It is difficult to repair or make modifications to software once it has entered the testing phase.

Functional requirements of the system

Functional requirements are what the system must do or provide for its users. Following are the
functional requirements of the system.

 Only admins can update the data & information.

 Users can only view the data & information.

 Admin can assign employees.

 Admin can manage the bus details.

 Admin can manage the schedules.

 Admin can manage the transactions.

 Users and passengers can make complaints for the services.

 Customers/ Passengers can reserve the bus or seats for their requirements.

Non functional requirements of the system

Non- functional requirements are behaviors in the system. Following are the non functional
requirements of the system.

● Usability measures how simple a system is to use.

● Availability denotes that the system will function and provide the requested services.

● Performance changes in response to particular user actions while handling a particular workload.
● Security is the ability to fend off attacks from outside sources that aim to harm the system or the data
it contains.

● Efficiency is the ability to achieve goals while using minimal energy.

Hardware Requirements

i.Quad core 2GHz+ CPU

ii.4GB or above RAM

iii.Hard Disk 1TB.

iv.Minimum database space: 10GB

Software Requirements

i.Operating System:Windows

ii.Front- End:HTML,CSS, Javascript

iii.Back- End : PHP, MYSQL

iv.Web Server: apache

Table of Contents
Type chapter title (level 1) 1
Type chapter title (level 2) 2
Type chapter title (level 3) 3

Type chapter title (level 1) 4

Type chapter title (level 2) 5
Type chapter title (level 3) 6

System Design
This chapter should included describing the forms of the proposed system. The system design
chapter is the most important phase in the SDLC. This phase is called “the blueprint of the system.”

Design forms and reports

Please note that these are prototypes and additional features and user interfaces may be vary with the
actual system.