Time Series Analysis On Flight Passengers

A mini Project Report submitted

To
SRI PADMAVATI MAHILA VISVAVIDYALAYM
(women’s university)
In Partial fulfilment of the requirements of
MASTER OF COMPUTER APPLICATIONS
(vi semester )
By

P.Harsha ( Reg:2019MCA16090L)
P .Arathi (Reg:2019MCA16091L)
Under the guidance of
Dr.P.Bhargavi (Assistant professor)

DEPARTMENT OF COMPUTER SCIENCE

SRI PADMAVATHI MAHILA VISVAVIDYALAYAM
NAAC WITH “A” GRADE
(Women’s University)
TIRUPATI-517502, ANDHRA PRADESH,MARCH-2021.

1
Time Series Analysis On Flight Passengers
A mini Project Report submitted
To

SRI PADMAVATI MAHILA VISVAVIDYALAYAM

(women’s university)
In Partial fulfilment of the requirements of
MASTER OF COMPUTER APPLICATIONS
(vi semester)
By

P.Harsha (Reg:2019MCA16090L)
P.Arathi (Reg:2019MCA16091L)
Under the guidance of
Dr.P.Bhargavi (Assistant professor)

DEPARTMENT OF COMPUTER SCIENCE

SRIPADMAVATHI MAHILA VISVAVIDYALAYAM
(Women’s University)NAAC WITH “A” GRADE
TIRUPATI-517502, ANDHRA PRADESH,MARCH-2021.

2
DEPARTMENT OF COMPUTER SCIENCE
SRI PADMVATHI MAHILA VISVAVIDYALAYAM
(Women’s University)

NAAC WITH “A” GRADE

TRUPATI-517502, ANDHRA PRADESH

CERTIFICATE
This is to certify that the project work entitled “ Time Series Analysis On Flight
Passengers” is a benefited record of work carried out by
P. Harsha (Reg.No: 2019MCA16090L)
P.Arathi (Reg.No: 2019MCA16091L)
in the department of Computer Science, SRI PADMAVATHI MAHILA VISVAVIDYALAYAM,
Tirupati in partial fulfilment of the requirements for the award of MASTER OF COMPUTER
APPLICATIONS. The content of the project Report has not been submitted to any other University/institute
for the award of the Post-Graduation.

(Signature of Guide) (Signature of the Head)

(Signature of External Examiner)

3
DECLARATION

We declare that the MCA Vi semester Mini project entitled “ Time

Series Analysis On Flight Passenger” was done at “Department of
Computer Science”
Tirupati in the year 2021 under the guidance of Dr.P.BHARGAVI,
Department of Computer Science, SRI PADMAVATHI MAHILA
VISVAVIDYALAM,TIRUPATHI in partial fulfilment of requirements
of MCA V semester.
We also declare that this project is our original contribution of the best of
our knowledge and belief. We further declare that this work has not been
submitted by either in full or part award of any other degree at other
university.

P.Harsha

P.Arathi

4
ACKNOWLEDGEMENT

We are greatly indebted to our guide Dr.P.BHARGAVI for taking keen

interest on our project work and providing valuable suggestions in all the
possible areas of improvement.
We express our sincere thanks to teaching staff of the Department of
Computer Science,for extending support and encouragement to us in all
the stages of project work.
We express heartful thanks to the Head of the Department Prof.S.JYOTHI
for her valuable suggestions and devices for completion of our project.
In the last,we gratefully acknowledge and express our gratitude to the
technical and non technical faculty of Department of computer
Science,who supported us in preparing this project.

P.Harsha

P. Arathi

5
Index
SL.No. Content Page No.

1 ABSTRACT 9

6
ABSTRACT

7
1.ABSTRACT
The Vehiclemanagement software system will track the checkin and chec
Software Requirements:
• Angular
• Visual studio code editor

Hardware Requirements:
• Intel Processors
• Hard disk-500GB
• RAM-4G
• Operating system – windows 10.

8
INTRODUCTION

2.INTRODUCTION
Introduction:
The VMS application is used to log details of the employee entry and exit
timings.
Using the login credentials, the security guards will login to application
and will check the timings of vehicles that are entering and exiting. These
checkIn andcheckout details will be stored to database based on the
vehicle number and employee ID.

9
The employee can login with his credentials and can view their checkin
timings and checkout timings.
By storing the checkIn and checkout details, we can track the employee
details i.e., these check in and check out details will be organized.
Modules:
ADMIN MODULE:

Admin module can access the data of an employee and store in a

database,it can update,post,read and delete the employee data,it can access
the data of an all employees.

Features of admin module:

● Admin can register both Employee and Security

● Can also update and delete details of Employee and Security

● Can view the log of all Employees

II. EMPLOYEE MODULE:

The Employee module can only view his entry and exit log details. And
this module can deal with modification of his profile picture.Features of
employee module:
● Employee can update his profile picture

● Employee can also check his log details III. SECURITY MODULE:

The Security module will manage the checkin and checkout timings of
employees based on the vehicle number and employee ID.Features of
security module:

● Security module can access all the details of employees.

● And also stores the checkin and checkout details of employees

10
COMPONENTS USED:

1. HEADER COMPONENT:

Header component contains the main view of application from which we

can navigate to other components.

2. HOME COMPONENT:

Home component contains the overall view of the application.

3. LOGIN COMPONENT:

Login component will be accessible to Admin , Employee and Security

Team. By logging in, the users will be navigated to their respective

dashboards.

4. CONTACTUS COMPONENT:

ContactUs component contains the contact information about the admin.

PROBLEM
STATEMENT
11
3.PROBLEM STATEMENT
3.1. Problem Statement
In companies it is hard to check the details of every vehicle coming in
and going out.So we designed this project in such a way by creating the
modules like admin,employee,security.Vehicle Management System is an
software application which fulfills the requirement of a typical
management of details of vehicles, staff.Vehicle Management System will
track the check in and checkout status of the registered employees Vehicle
based on the employee Id and vehicle number.The VMS application is
used to log details of the employee entry and exit timings. To log the
timing details, the security people should be given access to employee
details by the admin.Using the login credentials, the security guards will
login to application and will check the timings of vehicles that are
entering and exiting. These checkIn and checkout details will be stored to
database based on the vehicle number and employee ID.The employee can
login with his credentials and can view their checkin timings and checkout
timings.By storing the checkIn and checkout details, we can track the

12
employee details i.e., these check in and check out details will be
organized.

3.2 Background
In the offices ,it will be difficult to manage the vehicles which are
coming in and going out.No one will be responsible for the theft of
vehicles which are not protected.So it requires someone to check the
vehicles details and checkin and checkout details .These work should be
done by the security and the registration should be done by admin.So it
requires a software,to do all of this.

13
SYSTEM ANALYSIS

4.0 SYSTEM ANALYSIS

4.1 EXISTING SYSTEM:
The existing system doesn’t has token based authentication while signing
in.It wont provide the security to the users details .

DISADVANTAGES:

14
The system is not fully automated, it needs up to date of work.

4.2 PROPOSED SYSTEM:

We proposed a new solution for privacy preserving user profile. we have

provide that authentication to the user profile through generating the
token.

Advantages:

The proposed system has high accuracy because of the authentication

provide to the modules and high performance regading the checkin and
checkout details.

4.3 FEASIBILITY STUDY:

Economic feasibility attempts to weigh the costs of developing and
implementing a new system, against the benefits that would come 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 on
account of automation. These could include increased customer
satisfaction, expediting activities, improved accuracy of operations, better
documentation and record keeping, faster retrieval of information, better
employee morale.
4.3.1 OPERATIONAL FEASIBILITY:

15
Proposed project is beneficial only if it can be turned into information
systems that will meet the organizations operating requirements. Simply
stated, this test of feasibility asks if the system will work when it is
developed and installed. Are there major barriers to implementation?
Are the current methods acceptable to the user? If they are not, users may
welcome a change that will bring about a more operational and useful
systems.
Have, the user been involved in the planning and development of the
project?Early involvement reduces the chances of resistance to the system
and in general and increases the likelihood of successful project.
Since the proposed system was to help reduce the hardships encountered.
In the existing manual system, the new system was considered to be
operational feasible.
4.3.2 TECHNICAL FEASIBILITY:
This study is carried out to check the technical feasibility, that is, the
technical requirements of the system. Any system developed must not
have a high demand on the available technical resources. This will lead to
high demands on the available technical resources. This will lead to high
demands being placed on the client. The developed system must have a
modest requirement, as only minimal or null changes are required for
implementing this system.

4.3.3 ECONOMICAL FEASIBILITY:

The economic feasibility is affordable to launch this kind of project into
a company for better results and better management of the vehicles details
& data of checkin and checkout.

16
ANGULAR
FRAMEWORK

5. ANGULAR FRAMEWORK
5.1 INTRODUCTION TO ANGULAR FRAMEWORK:
Angular is a platform and framework for building single-page client
applications using HTML and TypeScript. Angular is written in
TypeScript. It implements core and optional functionality as a set of
TypeScript libraries that you import into your apps.

The architecture of an Angular application relies on certain fundamental

concepts. The basic building blocks of the Angular framework are
Angular components that are organized into NgModules. NgModules
collect related code into functional sets; an Angular app is defined by a set
of NgModules. An app always has at least a root module that enables
bootstrapping, and typically has many more feature modules.

17
Components define views, which are sets of screen elements that Angular
can choose among and modify according to your program logic and data.
Components use services, which provide specific functionality not

The metadata for a service class provides the information Angular needs to
make it available to components through dependency injection (DI).

An app's components typically define many views, arranged

hierarchically. Angular provides the Router service to help you define
navigation paths among views. The router provides sophisticated
inbrowser navigational capabilities.

6.SYSTEM REQUIREMENTS
The requirements specification is a technical specification of requirements
for the software products. It is the first requirements of a particular
software system including functional performance and security
requirements. The requirements also provide usage scenario from a user,
an operational and an administrative perspective. The purpose of software
requirements specification is to provide a detailed overview of the
software project, its parameters and goals. This describes the project target
audience and its user interface, hardware and software specifications. It
defines how the client team and audience see the project and its
functionality.

6.1. SOFTWARE REQUIREMENTS:

Operating system: windows XP/7/10

Coding language: Typescript,Angular

18
Tools: VS code

Database: Sqlite3.

6.2. HARDWARE REQUIREMENTS:

Device: intel processors

Hard disk: 500GB

RAM: 4G (minimum)

Processor: i3 (minimum)

SYSTEM DESIGN

19
7.SYSTEM DESIGN
7.1. UML DIAGRAMS:
UML stands for Unified Modeling Language. UML is a
standardized general-purpose modelling language in the field of
objectoriented software engineering. The standard is managed, and was
created by, the object management Group.
The goal is for UML to become a common language for creating models
of object oriented computer. In its current form UML is comprised of two
major components: a Meta-model and a notation. In the future, some form
of method or process may also be added to; or associated with, UML.
The Unified modelling language is a standard language for specifying,
Visualization, constructing and documenting the aircrafts of software
system, as well as for business modelling and other non-software system
1. Provide a formal basis for understanding the modelling language.
2. Encourage the growth of OO tools market.
3. Support higher level development concepts such as collaborations,
frameworks, patterns and components.
4. Integrate best practices.
7.2USE CASE DIAGRAM:
A use case diagram in the Unified modelling Language (UML) is a type of
behaviour diagram defined by and created from a USE-case analysis. Its
purpose is to present a graphical overview of the functionality provided by
a system in terms of actors, their goals (represented as use cases), and any

20
dependencies between those use cases. The main purpose of a use case
diagram is to show what system functions are performed for which actor.
Roles of the actors in the system can be depicted.
operations (or met holds), and the relationships among the classes. It
explains which class contains information.

FlowCharts:
Activity diagram:

An activity diagram illustrates dynamic nature of system by modelling

flow of control from activity to activity.An activity represents an
operation on some class in the system.

Fig: Activity diagram

21
Class diagram:
It is an abstraction of entities with common characteristics .Associations
represents relationship between classes.

Fig:class diagram

22
SYSTEM IMPLEMENTATION

8. IMPLEMENTATION
8.1. Data collection and dataset preparation:
This will involves collecting the details of vehicles and employees who
are working in a company.
8.2. Developing UI:
Javascript ,Angular are used for the frontend to develop the UI.
8.3. Deployment and analysis on real life scenario:
This online book management in a real life scenario made by the human
experts & will be leveraged for further improvement in the methodology
and will follow the above architecture.
Rule 1: Need of good internet connection.

23
Rule 2: Basic computer knowledge.
Rule 3: Book knowledge is also needed (not mandatory).
8.4:Source code:

SOURCE CODE:
Login.ts: import { Component, OnInit } from
'@angular/core'; import { Router } from
'@angular/router'; import { LoginService } from
'../login.service';
@Component({
selector: 'app-login', templateUrl:
'./login.component.html', styleUrls:
['./login.component.css']
})
export class LoginComponent implements OnInit {
constructor(private ls: LoginService, private router: Router) { }
ngOnInit(): void { setTimeout(() => { this.ls.logout();
}, 0);
}

submitform(a) { if (a.role == "Admin") { if

(a.name = "admin" && (a.password = "admin")) {
this.router.navigate(["/admindashboard"])
}

24
} else if (a.role == "Security") { if (a.name =
"security" && (a.password = "security")) {
this.router.navigate(["/securitydashboard"])
} } else { if (a.role == "Employee") { if
(a.name = "employee" && (a.password = "employee")) {
this.router.navigate(["/employeedashboard"])
}
}
}
}
}

Admin.api.js:
const exp = require('express') const adminapp = exp.Router()
adminapp.use(exp.json()) var dbo; const mc =
require("mongodb").MongoClient; const dburl =
"mongodb://admin:admin@cluster0-shard-00-
00xvqqz.mongodb.net:27017,cluster0-shard-00-
01xvqqz.mongodb.net:27017,cluster0-shard-00-02-
xvqqz.mongodb.net:27017/test?ssl=true&replicaSet=Cluster0-
shard0&authSource=admin&retryWrites=true&w=majority"

mc.connect(dburl, { useNewUrlParser: true, useUnifiedTopology: true }, (

err, clientobj) => { if (err) { console.log("err is", err);

25
} else { dbo =
clientobj.db("empdb")
console.log("connected to db"); }
});

adminapp.post('/register', (req, res) => {

console.log(req.body)
dbo.collection("admincollection").findOne({Employeeid: req.body.Em
ployeeid }, (err, empobj) => {
if (err) { console.log("err is
occured ", err)
}
else if (empobj == null) {
dbo.collection("admincollection").insertOne(req.body, (err, succes s) =>
{
if (err) {
console.log("err is occured", err)
}
else {
res.send({ message: "emp is created successfully" })
}

})
}

26
if (empobj !== null) {
res.send({ message: "emp is already created" })
}
})
})

module.exports = adminapp;

adminapp.get('/readall', (req, res) => {

console.log(req.body)
dbo.collection("admincollection").find().toArray((err, empArray) => {
if (err) { console.log("err is occured ", err)
}
else if (empArray == 0) {
alert("emp is not found"); res.send({
message: "no data found" })
}
else { res.send({ message:
empArray })
}
})
})

27
adminapp.delete('/remove/:i', (req, res) => { console.log(req.params.i)
dbo.collection("admincollection").deleteOne({Employeeid:req.params.i
},(err, delobj) => {
if (err) { console.log("err is
occured", err)
} else {
res.send({message:"deleted successfully"})
}
})

})

SYSTEM TESTING

28
9. SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of
trying to discover every conceivable fault or weakness in a work product.
It provides a way to check the functionality of components, sub
assemblies and/or a finished product. It is the process of exercising
software with the intent of ensuring that the software system meets its
requirements and user expectations and does not fail in an unacceptable
manner. There are various types of test. Each test type addresses a specific
testing requirement.

9.1 TYPES OF TESTING:

9.1.1. UNIT TESTING:
All decisions branches and internal code flow should be validated. It
is the testing of individual software units of the application. It is done after
the completion of an individual unit before integration.

29
Flow of running Test

30
Fig:Software Testing Ice-Cream Cone

CONCLUSION

31
10. CONCLUSION
This project vehicle management system has been developed using
technologies like Mongodb, Express, Angular and NodeJS
The main purpose of this project is to log the details of check in and check
out timings of employee vehicles.
The project totally built at admin and employee because the employee given
to the details to the admin,based on this details provides security of the
vehicles.
This project will keep track of the numerous vehicles coming in and out of
the company.It reduce the manual effort needed to manage the vehicles
details of the employees.

32
BIBILOGRAPHY

11.REFRENCES:
BOOKS:
[1] A theory of vehicle management system by Michael D. Watson. [2] A
theory of vehicle management system by Stephen B.johnson.
[3] Improvement of vehicle management system by falah Y.H ahmad

WEB RESOURCES:

1) https://angular.io
2) https://udemy.com
3) https://coursera.com

33
EXPERIMENTAL
DESIGN

34
12. EXPERIMENTAL DESIGN OUTPUTS:

35
36
37
38
39
40