Nakul Thesiespdf PDF
Nakul Thesiespdf PDF
Sr.No Pg .No
INTRODUCTION.
1 • problem statement
• scope
• project Features
• Overview of report
OBJECTIVES.
2
PRELIMINARY SYSTEM ANALYSIS
3 • Preliminary Investigation
• Present System in Use
• Feasibility Study
• Project Category
SOFTWARE ENGINEERING PARADIGM APPLIED
4 • Modules
• System / Modules Chart
SOFTWARE & HARDWARE REQUIREMENT SPECIFICATION
5
DETAILED SYSTEM ANALYSIS
6 • Data Flow Diagram.
• Numbers of Modules and process Logic.
• Data Structures and Tables.
• Entity-Relationship Diagram.
SYSTEM DESIGN
7 • Form Design.
• Source Code.
• Input Screen and Output Screen
Vehicle Parking management system (vpms) for managing the records of the
incoming and outgoing vehicles in a parking house
It’s an easy for Admin to retrieve the data if the vehicle has been visited through
number he can get that data
Now days in many public places such as malls, multiplex system, hospitals, offices,
market areas there is a crucial problem of vehicle parking. The vehicle parking area
has many lanes/slots for car parking. So to park a vehicle one has to look for all the
lanes. Moreover this involves a lot of manual labour and investment. Instead of
vehicle caught in towing the vehicle can park on safe and security with low cost.
Parking control system has been generated in such a way that it is filled with many
secure devices such as, parking control gates, toll gates, time and attendance
machine, car counting system etc. These features are hereby very necessary
nowadays to secure your car and also to evaluate the fee structure for every vehicles
entry and exit
The objective of this project is to build a Vehicle Parking management system that
enables the time management and control of vehicles using number plate
recognition. The system that will track the entry and exit of cars, maintain a listing
of cars within the parking lot, and determine if the parking lot is full or not. It will
determine the cost of per vehicle according to their time consumption.
1.1 Problem Statement
New road parking had challenges concerning its safety of data in the store since they
currently use paper based system, physical struggle for parking by drivers wastage
of time, congestion and collision. There was also a problem of monitoring the profit
made for the company whereby the company was losing money to its workers who
receive the money (fraud). This system majorly solved the congestion, collision and
save time during parking activities.
1.2 Scope
• Keeping track of the total number of parking spaces available, the number of
vehicles currently parked, and the remaining spaces
Actually speaking, the word SYSTEM is itself derived from the Greek word
‘Systema’ meaning organized relationship among functioning units or components
with a central objective and these components are called as sub-units of the system.
From the above definition it is clear that every system has some common/ similar
factors such as:
Hence, it is justified to say that every system needs to be properly analysed. Each
system should be taken into consideration and also necessarily investigate in
particular.
Following steps should be kept in mind while carrying out a preliminary
investigation:
Many parking places such as The New road parking still use the manual or the
paper based system for customers „parking reservation, data storage and
payments.
It would also relieve the workers who have offices in the parking places the hustle
of trying to locate a parking space every time they report working. This means
their productivity would be enhanced since they do not waste energy so early in
the day.
The level of safety in such a parking lot may be compromised since the user may
not be in a position to navigate the congested parking damaging other user‟s
property. Developing an online vehicle parking reservation system will alleviate
the problem of time wastage on the side of the users of the parking lots included in
the system (Whapples 2005).
3.3 FLAWS IN PRESENT SYSTEM
Now a days in parking like valet parking they maintain just with the tokens and they
have records the vehicle details in books so that during some critical situations like
police enquiry of terrorist car or vehicle roberrer that case it is difficult to find the
details of particular vehicle but in this case is easy to find in 1to 2 seconds
• By parking the vehicle in public place the vehicle can be claimed by towing
person but in this case there is no towing problems and no need to give fine
for anything we can park our vehicle with securely.
• Long queues: Traditional parking systems often require customers to take a
ticket upon entry and pay for their parking upon exit. This can result in long
queues, especially during peak hours or busy periods, which can be frustrating
for customers and deter them from parking at your business.
• Risk of fraud: Traditional parking systems are susceptible to fraud, as
customers can lose their tickets, and it can be challenging to verify the validity
of the tickets presented upon exit. This can result in lost revenue for your
business.
• Inconvenient for customers: Customers need to keep track of their parking
tickets, which can be lost, and result in them paying for additional parking
time. Additionally, traditional parking systems often require customers to
handle cash, which may not be convenient for customers.
• Maintenance and management: Traditional parking systems require regular
maintenance, including ensuring that ticket machines are functioning
correctly and restocking tickets. This can result in additional costs and
management time.
• Limited parking information: Traditional parking systems do not provide real-
time information on parking spaces, which can result in inefficient use of
parking spaces and frustrated customers who cannot find a parking spot.
Overall, these disadvantages can negatively impact customer experience, reduce
revenue for your business, and result in inefficient use of parking spaces.
3.4 NEED OF NEW SYSTEM
Feasibility Constraints
In feasibility analysis, there are three key considerations and they are as follows:
➢ Economic Feasibility
➢ Schedule feasibility
➢ Operational Feasibility
➢ Technical Feasibility
Economic feasibility
Economic feasibility attempts to weigh the cost of developing and implementing a
new system, against the benefits that would accurate from having the new system in
place. This feasibility study gives the top management the economic justification for
the new system
A simple economic analysis which gives the actual comparison of costs and benefits
are much more meaningful in this case. In addition, this proves to be a useful point
of reference to compare actual costs as the project progresses. There could be various
types of intangible benefits of account of automation. These could include increased
customer satisfaction, improved accuracy of operation, better documentation and
record keeping, faster retrieval of information.
Schedule feasibility
Operational feasibility
Proposed project is beneficial only if it can be turned into information systems that
will meet the organization operating requirements. Simply stated, this test of
feasibility asks if the system will work when it is developed and installed. What are
major barriers to implementation? Here are questions that will help test the
operational feasibility of a project
Technical feasibility
Technical feasibility centers on the existing computer system(hardware, software,
etc. ) and to what extent it can support the proposed addition. For example, if the
current computer is operating at 80% 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
budget is a serious constraint, then the project is judged but not feasible.
3.6 PROJECT CATEGORY
Process Model
Iterative Model
Iterative process starts with a simple implementation of a subset of the software
requirements and iteratively enhances the evolving versions until the full system is
implemented. At each iteration, design modifications are made and new functional
capabilities are added. Iterative and Incremental development is any combination of
both iterative
design or iterative method and incremental build model for software development.
The combination is of long standing and has been widely suggested for large
development efforts. For example, the 1985 DOD-STD-2167 mentions (in section
4.1.2): "During software development, more than one iteration of the software
development cycle may be in progress at the same time." and "This process may be
described as an 'evolutionary acquisition' or 'incremental build' approach." The
relationship between iterations and increments is determined by the overall software
development methodology and software development process. The exact number
and nature of the particular incremental builds and what is iterated will be specific
to each individual development effort.
An iterative life cycle model does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing just part
of the software, which can then be reviewed in order to identify further requirements.
This process is then repeated, producing a new version of the software for each cycle
of the model.
Implementation Methodology:
Mode View Controller or MVC as it is popularly called. is a software desian pattern
for developing web applications. A Model View Controller pattern is made up of the
following three parts:
• Model - The lowest level of the pattern which is responsible for maintaining
data
• view - This IS responsible for displaying all or a portion of the data to the
user.
• Controller - Software Code that controls the interactions between the Model
and View.
MVC is popular as it isolates the application logic from the user interface layer and
supports separation of concerns. Here the Controller receives all requests for the
application and then works with the Model to prepare any data needed by the View.
The view then uses the dala prepared by the controller to generate a rinal presentable
response. The MVC abstraction can be araphically represented as follows
Hard Disk 40 GB
Monitor LCD, LED
Keyboard Standard wind0ows keyboard
, Mouse Two or three button mouse
Printer Any
6 DETAILED SYSTEM ANALYSIS
6.1 DATAFLOW DIAGRAM
Data flow diagram is the starting point of the design phase that functionally
decomposes the requirements specification. A DD consists of a series of bubbles
joined by lines. The bubbles represent data transformation and the lines represent
data flows in the system. A DD describes what data flow rather than how they are
processed, so it does not hardware, software and data structure.
The data flow diagram is a graphical description of a system's data and how to
Process transform the data is known as Data Flow Diagram (DFD).
Unlike details flow chart, DDs don't supply detail descriptions of modules that
graphically describe a system's data and how the data interact with the system. Data
flow diagram number of symbols and the following symbols are of by DeMarco.
There are seven rules for construct a data flow diagram.
• I Arrows should not cross each other..
• Squares, circles and files must wears names.
• Decomposed data flows must be balanced.
• No two data flows, squares or circles can be the same names.
• Draw all data flows around the outside of the diagram.
• Choose meaningful names for data flows, processes & data stores.
• Control information such as record units, password and validation
requirements are not penitent to a data flow diagram.
On a DFD, data items flow from an external data source or an internal data store to
an internal data store or an external data sink. via an internal process. It is common
practice to draw a context-level data flow diagram first, which shows the interaction
between the system and external agents, which act as data sources and data sinks.
On the context diagram (also known as the Level O DFD*), the system's interactions
with the outside world are modeled purely in terms of data flows a cross the system
boundary
.
The context diagram shows the entire system as a single process, and gives no
clues as to its internal organization.
This context-level DFD is next "exploded", to produce a Level 1 DFD that shows
some of the detail of the system being modeled. The Level 1 DFD shows how the
system is divided into sub-systems (processes), each of which deals with one or
more of the data flows to or from an external agent, and which together provide all
of the functionality of the system as a whole. The level 1 DFD is further spreaded
and split into more descriptive and detailed description about the project as level 2
DFD. The level 2 DFD can be a number of data flows which will finally show the
entire description of the software project.
The number of modules and processing logic required to build a vehicle parking
management system can vary depending on the specific requirements and design of
the system. Some examples of modules that can be included in a vehicle parking
management system are:
A security reservation module that handles the reservation of specific parking lots
.
A parking space monitoring module that provides vehicle efficient and accurate
tracking facility
A admin module
A user module
An administrator module
A booking module
Algorithm
Step 1: - Start
Step 2: - Choose Vehicle type
Step 3: -Book a parking space
Step 4: -Display Notice
Step5: -Stop
ER Diagram:
Entity Relationship Diagram
E-R Model is a popular high level conceptual data model. This model and its
variations are frequently used for the conceptual design of database application and
many database design tools employ its concept.
• Attributes
• Relations
• Many-to-many
• Many-to-one
• One-to-many
o One-to-one
• Weak entities
• Sub-type and super-type
The entities and their relationshops between them are shown using the following
conventions.
ER Diagram
Activity Diagram
For User
7 SYSTEM DESIGN
7.1 FORM DESIGN
SOURCE CODE
if(isset($_POST['submit']))
{
$fname=$_POST['firstname'];
$lname=$_POST['lastname'];
$contno=$_POST['mobilenumber'];
$email=$_POST['email'];
$password=md5($_POST['password']);
<link rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/normalize.css@8.0.0/normalize.min.css">
<link rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/bootstrap@4.1.3/dist/css/bootstrap.min.css">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/font-awesome@4.7.0/css/font-
awesome.min.css">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/gh/lykmapipo/themify-
icons@0.1.2/css/themify-icons.css">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/pixeden-stroke-7-icon@1.2.3/pe-icon-
7-stroke/dist/pe-icon-7-stroke.min.css">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/flag-icon-css/3.2.0/css/flag-
icon.min.css">
<link rel="stylesheet" href="../admin/assets/css/cs-skin-elastic.css">
<link rel="stylesheet" href="../admin/assets/css/style.css">
<link href='https://fonts.googleapis.com/css?family=Open+Sans:400,600,700,800'
rel='stylesheet' type='text/css'>
<script type="text/javascript">
function checkpass()
{
if(document.signup.password.value!=document.signup.repeatpassword.value)
{
alert('Password and Repeat Password field does not match');
document.signup.repeatpassword.focus();
return false;
}
return true;
}
</script>
<div class="login-form">
<form method="post" onsubmit="return checkpass();">
<div class="form-group">
<label>First Name</label>
<input type="text" name="firstname" placeholder="Your First Name..." required="true"
class="form-control">
</div>
<div class="form-group">
<label>Last Name</label>
<input type="text" name="lastname" placeholder="Your Last Name..." required="true"
class="form-control">
</div>
<div class="form-group">
<label>Mobile Number</label>
<input type="text" name="mobilenumber" maxlength="10" pattern="[0-9]{10}"
placeholder="Mobile Number" required="true" class="form-control">
</div>
<div class="form-group">
<label>Email address</label>
<input type="email" name="email" placeholder="Email address" required="true" class="form-
control">
</div>
<div class="form-group">
<label>Password</label>
<input type="password" name="password" placeholder="Enter password" required="true"
class="form-control">
</div>
<div class="form-group">
<label>Repeat Password</label>
<input type="password" name="repeatpassword" placeholder="Enter repeat password"
required="true" class="form-control">
</div>
<div class="checkbox">
<label class="pull-right">
<a href="forgot-password.php">Forgotten Password?</a>
</label>
<label class="pull-left">
<a href="login.php">Signin</a>
</label>
</div>
<button type="submit" name="submit" class="btn btn-success btn-flat m-b-30 m-t-
30">REGISTER</button>
</form>
</div>
</div>
</div>
</div>
<script src="https://cdn.jsdelivr.net/npm/jquery@2.2.4/dist/jquery.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/popper.js@1.14.4/dist/umd/popper.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/bootstrap@4.1.3/dist/js/bootstrap.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/jquery-match-
height@0.7.2/dist/jquery.matchHeight.min.js"></script>
<script src="../admin/assets/js/main.js"></script>
</body>
</html>
User login
<?php
session_start();
//error_reporting(0);
include('includes/dbconnection.php');
if(isset($_POST['login']))
{
$emailcon=$_POST['emailcont'];
$password=md5($_POST['password']);
$query=mysqli_query($con,"select ID,MobileNumber from tblregusers where (Email='$emailcon'
|| MobileNumber='$emailcon') && Password='$password' ");
$ret=mysqli_fetch_array($query);
if($ret>0){
$_SESSION['vpmsuid']=$ret['ID'];
$_SESSION['vpmsumn']=$ret['MobileNumber'];
header('location:dashboard.php');
}
else{
echo "<script>alert('Invalid Details.');</script>";
}
}
?>
<!doctype html>
<html class="no-js" lang="">
<head>
<title>VPMS-Login Page</title>
<link rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/normalize.css@8.0.0/normalize.min.css">
<link rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/bootstrap@4.1.3/dist/css/bootstrap.min.css">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/font-awesome@4.7.0/css/font-
awesome.min.css">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/gh/lykmapipo/themify-
icons@0.1.2/css/themify-icons.css">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/pixeden-stroke-7-icon@1.2.3/pe-icon-
7-stroke/dist/pe-icon-7-stroke.min.css">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/flag-icon-css/3.2.0/css/flag-
icon.min.css">
<link rel="stylesheet" href="../admin/assets/css/cs-skin-elastic.css">
<link rel="stylesheet" href="../admin/assets/css/style.css">
<link href='https://fonts.googleapis.com/css?family=Open+Sans:400,600,700,800'
rel='stylesheet' type='text/css'>
<div class="form-group">
<label>Registered Email or Contact Number</label>
<input type="text" name="emailcont" required="true" placeholder="Registered Email or Contact
Number" required="true" class="form-control">
</div>
<div class="form-group">
<label>Password</label>
<input type="password" name="password" placeholder="Enter password" required="true"
class="form-control">
</div>
<div class="checkbox">
<label class="pull-right">
<a href="forgot-password.php">Forgotten Password?</a>
</label>
</div>
<button type="submit" name="login" class="btn btn-success btn-flat m-b-30 m-t-30">Sign
in</button>
</div>
<div class="checkbox" style="padding-bottom: 20px;padding-top: 20px;">
</div>
</form>
</div>
</div>
</div>
</div>
<script src="https://cdn.jsdelivr.net/npm/jquery@2.2.4/dist/jquery.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/popper.js@1.14.4/dist/umd/popper.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/bootstrap@4.1.3/dist/js/bootstrap.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/jquery-match-
height@0.7.2/dist/jquery.matchHeight.min.js"></script>
<script src="../admin/assets/js/main.js"></script>
</body>
</html>
Testing is vital for the success of any software. no system design is ever perfect. Testing is also
carried in two phases. first phase is during the software engineering that is during the module
creation. second phase is after the completion of software. this is system testing which verifies
that the whole set of programs hanged together.
Alpha Testing:
Acceptance testing is also sometimes called alpha testing. Be spoke systems are developed for a
single customer. The alpha testing proceeds until the system developer and the customer agree
that the provided system is an acceptable implementation of the system requirements.
Beta Testing:
On the other hand, when a system isto be marked as a software product, another process called
beta testing is often conducted. During beta testing, a system is delivered among a number of
potential users who agree to use it. The customers then report problems to the developers. This
provides the product for real use and detects errors which may not have been anticipated by the
system developers.
Unit Testing:
Each module is considered independently. it tocuses on each unit of sottware as implemented
in the source code. it is white box testing
Integration Testing:
Integration testing aims at constructing the program structure while at the same constructina
tests to uncover errors associated with interfacing the modules. modules are integrated by using
the top down approach.
Validation Testing:
Validation testing was performed to ensure that all the functional and performance requirements
are met.
System Testing:
It is executing programs to check logical changes made in it with intention of finding errors. a
system is tested for online response, volume of transaction, recovery from failure etc. System
testing Is done to ensure that the system satisties all the user requirements
This phase of the systems development life cycle refines hardware and software specifications,
establishes programming plans, trains users and implements extensive testing procedures, to
evaluate design and operating specifications and/or provide the basis for further modification.
Technical Design
This activity builds upon specifications produced during new system design, adding detailed
technical specifications and documentation.
User Training
This activity encompasses writing user procedure manuals, preparation of user training materials,
conducting training programs, and testing procedures.
Acceptance Test
A final procedural review to demonstrate a system and secure user approval before a system
becomes operational.
Installation Phase
In this phase the new Computerized system is installed, the conversion to new procedures is
fully implemented, and the potential of the new system is explored
Test cases
Test case id
1
Test case description
User Registration
Prerequisites
1.Enter all fields
2.Click register
Test scenario 1
User enter existing email
Test data
Full name: sujta
Contact:1234567890
Vehicle MH 31 EE 1122
Email:test@123.com already
exist in database)
Password:1234
Confirm password:1234
Step
Expected output
Actual result
Pass/fail
1
Already exists
Email exist
already
SCREEN SHOTS
11 FUTURE SCOPE OF THIS PROJECT
In a nutshell, it can be summarized that the future scope of the project circles around maintaining
information regarding:
We can add printer in future.
We can give more advance software for Car Parking System including more facilities
We will host the platform on online servers to make it accessible worldwide
Integrate multiple load balancers to distribute the loads of the system
Create the master and slave database structure to reduce the overload of the database queries
Implement the backup mechanism for taking backup of codebase and database on regular basis
on different servers
The above mentioned points are the enhancements which can be done to increase the
applicability and usage of this project. Here we can maintain the records of Car and Parking.
Also, as it can be seen that now-a-days the players are versatile, i.e. so there is a scope for
introducing a method to maintain the Car Parking System.
Enhancements can be done to maintain all the Car, Parking, Parking Space, Parking Slot, Parking
Area.
We have left all the options open so that if there is any other future requirement in the system
by the user for the enhancement of the system then it is possible to implement them.In the last
we would like to thanks all the persons involved in the development of the system directly or
indirectly. We hope that the project will serve its purpose for which it is develop there by
underlining success of process.
2. The Joy of PHP: A Beginner’s Guide to Programming Interactive Web Applications with
PHP and MySQL by Alan Forbes
Links:
These books and links cover various aspects of using PHP, HTML, CSS and MySQL to develop
web applications