0% found this document useful (0 votes)
82 views48 pages

Metro System

This document provides documentation for a database project on a metro system. It includes 48 pages covering the introduction, literature review, problem statement, requirements, design, implementation, testing and conclusion. The project involved creating a database to store information about a metro system using MySQL and LibreOffice.

Uploaded by

satish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
82 views48 pages

Metro System

This document provides documentation for a database project on a metro system. It includes 48 pages covering the introduction, literature review, problem statement, requirements, design, implementation, testing and conclusion. The project involved creating a database to store information about a metro system using MySQL and LibreOffice.

Uploaded by

satish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

1

Updated: 13/08/18
Total number of pages: 48

Project Report | Documentation

M I N I P R O J E C T
Metro System Database Project

Ankit Chouhan Jishan Shaikh


161112051 161112013
2

This page intentinaaal aeef baank


3

Maulana Azad National nstitute of Technology


(An nstitute of National mportancet
Bhopal – 462003 ( ndiat

Department of Computer Science & Engineering

M N P R O J E C T

Metro System Database Project

Submitee by : Ankit Chouhan (Scholar no. 161112051)


Jishan Shaikh (Scholar no. 161112013)
Submission eate : April 13, 2018
Supervisor : Prof. Sweta Jain
Department of Computer Science & Engg.
MANIT, Bhopal (Maehya Praeesh, Ineia)
Subject : Database Management System Laboratory
CSE-229, IV Sem (B.Tech. in CSE)
Session : Even Semester 2018
4

This page intentinaaal aeef baank


5

Preface
This project ttlee Metro System Database Project is one of the acaeemic
projects we (as a team of 2 members) take in DataBase Management System
Laboratory course (4th Sem) of Bachelor in Technology (Computer Science &
Engineering), here at Maulana Azae Natonal Insttue of Technology, Bhopal. This
project was startee in February 2018 ane merely enes at the submission eate by
April 13. (Work in of eays)

The complete report is organizee into small chapters, sectons, subsectons,


appeneices, etc. Snapshots ane screenshots are taken for clear ieea of what’s going.
We’ve triee to cover all informaton regareing project to be assemble in report but
stll SRS eocument, Plan eocument, Preliminary RMMM plan eoesnot ine their place
in the report. Further they can be mergee into report in future as per requirements.

The founeatons of project startee in January 18, when new session starts ane
topic of project eecieee. Some points such that project management, scalability, risk
analysis, version control, aims, etc. were eiscussee primarily. The major aims set at
beginning of this project was -

- To gain the technical knowleege ane experience ane practcal hanes


behine eatabases, their management systems, ane other technologies
- A clear ieea of working ttlee incorporatng traeitonal accent but with
some moeern sofware engineering principles, practces, ane staneares
- Improving team skills uneer fully supervision (Project management
inclueing risk analysis ane Sof-skills)
- To present a inal result implementaton, its analysis, ane evaluaton with
proper eocumentaton/project report.

Althrought the aims were set primarily ane broaely, we as a team collaborate
on multple issues ane try as much as we can to be stck on aims along with healthy
communicaton from supervisors. This eocument is neither a fully formal
eocumentaton nor a research basee report, but it inherits many atributes of both in
it. Here are some highlights of the project -

~ A single eocument having combinaton of eocumentaton, project


report, reference manual, tutorial, user manual for the output
~ Practcal implementaton of DataBase System usee for Metro system
~ Parallel implementaton of DataBase in many DataBases platorms, here we
usee MySQL workbench ane LibreOfce Base as major two platorms using
SQL as major query language
~ Incorporaton of Sofware Engineering elements such as principles,
practces, life-cycle, etc.
6

Most of the collectee contents are properly referencee*. If any of work is not,
please feel free to notfy us at ithub.com or via emails.

It is also plannee to place this project on itHub.com soon, where the version
control of project is monitoree properly ane subject experts (actually everyone) will
get authority to analyse, evaluate, ane even collaborate on this project. This project
will be licensee uneer Creatve Commons ShareAlike Non-eistributon 4.0
Internatonal licence 2018. From sofware engineering practce we know Sofware
prototype maintainance never enes as no sofware built is perfect, so the
moeiicatons to the irst version/release of this project will be completely to github.
Checkout the reaeme.me ile at ithub. Althrough we are saying output as a
sofware, it might not be a fully functonal SOFTWARE. We can say it as a working
prototype of sofware which can further be enhancee in form of a sofware.

It was very memorable to work on such a project with such a team ane such a
mentor. No work is perfect, remember to write your views to us! Healthy critsm,
suggestons, feeeback, ane even your opinions are always welcome to enhance this
project either at github.
7

Acknowledgements
With eue respect, we express our eeep sense of grattuee to our respectee
ane learnt guiee, cooreinator, supervisor, instructor Prof. Sweta Jain, for her valuable
help ane guieance. We are thankful for the encouragement ane motvaton that she
has given us in completng this project successfully. Her rigorous evaluaton ane
constructve critsm was of great assistance. It is imperatve for us to menton the
fact that this project coule not have been accomplishee without the perioeic
suggestons ane aevice of our supervisor.

We are also grateful to our respectee eirector Dr. Narenera Raghuvanshi for
permitting us to utlize all the necessary facilites of the college.

Neeeless to menton is the aeeitonal help ane support exteneee by our


respectee Heae of the eepartment- Ms. Meenu Chawla, in allowing us to use the
eepartmental laboratories ane other services on the perioe of tme ane also
maintaining a healthy eiscipline in management, tutorials, eeuventurisaton, ane
other actvites.

We are thankful to all the other facultes, Professors, Associate Professors,


Assistant Professors, staf-members, teaching assistants, laboratory ateneants,
seniors, ane our fellow branch mates of our work culture for their kine co-operaton,
perioeic evaluaton, help, ane support. We thank all others who eirectly/ineirectly
involvee in this project ane make it a successful. We also thank all other teams for a
maintaining an actve communicaton asiee of healthy competton ane sportsmans
spirit.

We woule also like to express our eeep appreciaton towares our family
members for making us such kine to eo ‘more’ by provieing the much neeeee
support ane encouragement from all aspects of life. At last, we recall our grattuee to
the one eternal almighty: The oe.
8

This page intentinaaal aeef baank


9

Contents
i. Preface.................................................................................................................................5
ii. Acknowleegements..........................................................................................................7
iii. Contents..............................................................................................................................9
iv. Abstract............................................................................................................................11

1. Introeucton ane Quick review....................................................................................13


1.1 Introeucton..........................................................................................................13
1.2 Aims ane Scope of project................................................................................13
1.3 Is the proeuct output of this project is a sofware/prototype?................14
1.4 CASE tools usee..................................................................................................14
1.5 Corresponeing Conceptual moeels for this project....................................14
1.6 Project management overview........................................................................14
1.7 Level-0 Project Synopsis...................................................................................14

2. Literature Survey............................................................................................................17
2.1 Databases.............................................................................................................17
2.2 Structuree Query Language.............................................................................18

3. Problem Statement........................................................................................................20
3.1 Problem Statement.............................................................................................20
3.2 Problem (Task) eescripton ane major tasks..................................................20
3.2.1 Project aspects.........................................................................................20
3.2.2 Tasks...........................................................................................................21

4. Sofware ane Hareware requirements......................................................................22


4.1 Minimum System/Sofware/Hareware requirements................................22
4.2 Resources Usage.................................................................................................22
4.3 Functonal requirements...................................................................................22
4.4 Performance requirements...............................................................................22

5. Methoeology usee.........................................................................................................23
5.1 Methoeology........................................................................................................23

6. Design framework..........................................................................................................24
6.1 Entty relatonship eiagram...............................................................................24
6.2 Entty relatonship eiagram (Preliminary).......................................................25
6.3 Sequence eiagram...............................................................................................26
6.4 Architecture eiagram..........................................................................................27
6.5 Data flow eiagrams.............................................................................................28
6.6 Use-Case eiagrams.............................................................................................29
10

7. Implementaton..............................................................................................................30
7.1 Coeing...................................................................................................................30
7.2 Implementaton Snapshots...............................................................................30

8. Testng...............................................................................................................................41
8.1 Proceeure..............................................................................................................41
8.2 Outcomes.............................................................................................................41

9. Conclusions ane future scope.....................................................................................42


9.1 Conclusions..........................................................................................................42
9.2 Future scope ane improvements.....................................................................42

References ane Bibliography...................................................................................................44

Appeneices

i. Appeneix-A List of tables, Web-pages, sample queries.............................45


• List of tables......................................................................45
• List of Web-pages............................................................45
• List of sample Queries....................................................46
ii. Appeneix-B SQL coee of sample Queries.....................................................47
iii. Appeneix-C Critsm ane Expert reviews.......................................................48
11

Abstract
A Metro System is one which helps us to maintain an organisatonal eata
regareing a metro system. Since it is very eifcult to maintain a recore of eata items
ane this informaton manually or in ile system, we are creatng a eatabase for the
complete management of resources ane tasks of metro system. A Metro System
eatabase is one which is usee for operatonal ease in place of traeitonal ile system or
Excel worksheets for informaton storage ane retrieval with customizee user queries
implementee in SQL ane is a fully functonally requiree sofware prototype with
proper user interface ane some raneom sofware engineering staneares. Organising
eatabase for eata collecton ane retrieval helps us to maintain eata easily. We eesign it
with the help of Entty-Relatonship eiagram, UML eiagrams, eata flow eiagrams, ane
using tables & proper User interfaces. It consists of several steps to be followee ane
many webpages are to be maintainee simultaneously. It is a working prototype of a
eatabase schema which can further be enhancee. The usage of staneare webpages in
HTML, CSS, JavaScript, PHP helps us to take project online without much
moeiicatons.

For main functonalites, we have to maintain many recores such as train


numbers, train route, eeparture tme, arrival tme, train type, fare, managements,
eepartments, customers, etc. When we want to travel we reserve seat (Aeeitonal
feature for Metro System but it is not compulsory for all passengers to reserve seats
for them, they can stll check in at last moment in case of availability in irst in irst
serve oreer), for this we have to ill the reservaton form which incluees entries such
as train number, train name, eeparture tme, arrival tme, route, train type. So, we
shoule gather all the informaton regareing all these.

Keywores: Metro System, Railway, Database, Prototype, Sofware Engineering


principles
12

This page intentinaaal aeef baank


13

Chapter 1
ntroduction & Quick review

Introeucton
A Metro System eatabase is one which is usee for operatonal ease in place of
traeitonal ile system or Excel worksheets for informaton storage ane retrieval with
customizee user queries implementee in SQL ane is a fully functonally requiree sofware
prototype with proper user interface ane incorporatng raneom sofware engineering
staneares.

Output of the Project :

✔ Working prototype of a sample metro system with user interfaces ane some queries
✔ Documentaton | Project report

Aims ane Scope of project


Aims :

 To buile a eatabase usee for practcal implementaton (For Metro System)


 To learn the concepts of eatabases ane their management of systems
 To uneerstane sofware constructon process ane its engineering
 To learn various Sofware Engineering principles ane staneares
 To enhance team work ane ineivieual responsibilites

Scope :

 Sofware can be usee theoritcally (Moeiicatons for practcal usage)


 Further moeiicaton ane enhancements possible in maintainance stage
 Research orientee aspect of project may leae to beter technology implementatons

Is the proeuct output of this project is a sofware?

Sort of Yes. The work proeuct output of this project is a ‘sofware’e working properly
in low scalability ane is properly testee on basic functonalites, which is to be incorporatee
in that. An engineering approach is usee for buileing that sofware that incluees irst eeine
problem, analyze it, eesign it, implement it, test it, ane regularly moeify it. Technically the
proeuct output of this project is a eemo prototype.
14

Open Source CASE tools usee

Upper CASE tools usee:

 LibreOfce Writer (For eocumentaton)


 LibreOfce Draw (For eesigning eiagrams)

Lower CASE tools usee:

 MySQL Workbench/LibreOfce Base (For SQL implementaton)

Corresponeing Conceptual moeels for this project


 Relatonal Moeel (See Appeneix-A for All relatons ane atributes)
 Enhancee Entty-Relatonal Moeel (See Entty-Relatonship eiagram)
 Object Orientee UML moeelling
 Use case eiagrams
 Sequence eiagrams, etc.

See more at Chapter 6.

Project management overview

 Embeeeee Project Planning


 Project Scheeuling (Internal in team)
 Risk management (Overview ane Intuitve )
 Project monitoring ane Controlling
 W5HH Principles (See preliminary Synopsis)
 Basic Project estmaton
 Cost estmaton
 Duraton estmaton
 Efort estmaton

Level-0 Project Synopsis: W5HH Principles

Why is the project being eevelopee ?

• To learn ane uneerstane the conceptual ane funeamental knowleege in


Database Management System
15
• To contribute a litle to open-source sofware community
• To have a practcal hanes on experience on a real life eatabase system built ane
maintainee by us
• To enhance team skills of all the members of team
• To learn moeern technologies efectvely with sofware engineering approaches

What will be eone ?

• Analysis ane eesign of metro eatabase system


• Implementaton of eesign into various platorms
• Evaluaton of all the implementatons
• Buileing a fnal sofware with proper user interface
• Prepare eocumentaton, project report, ane other eocuments

When will it be eone ?

• The project is supposee to be completee by April 2018


• First release by April 15, 2018
• Maintainance of that will be referree then to itHub community

Where are the organisatons locatee ?

• This project is a single organisaton, single team project locatee at MANIT,


Bhopal

Who is responsible for the eesiree functonality ?

• Each member has assignee his/her own responsibility regareing projects in


sectons ane of risk analysis, they have to follow their rules
• Team members are atomic elements of project ane are solely responsible for
their work
• Timely supervision is responsibility of the instructor.

How will the job be eone technical ane management siee ?

Technical issues :

• Database coniguraton ane buileing is to be eone on Oracle Database 12c, MySQL


Workbench 6.3, etc.
• UML eiagrams, Entty-Relatonship eiagrams are to preparee on LibreOfce Draw.
• Documentaton is to eone on LibreOfce Writer ane a LaTeX eeiton will also be
available (preparee on TeXLive)
• For user interface, either java or python or web-eevelopment languages (HTML, CSS,
JS, PHP) will be usee with SQL as major query language

Management issues : Sofware project management guieelines are to followee on


following-
16

• Risk analysis
• Cost estmaton
• Time scheeuling
• Project monitoring ane controlling

How much of each resource is neeeee ?

• Human resource of 3 team members


• Monetary resource of atmost 1,000 INR.
• Hareware resource of a computer with requiree sofware installee.
• Sofware resources usee.
17

Chapter 2
Literature Survey

Databases

Parameter Descripton
Moeern relatonal eatabase management system programs use a
Data Access
programming language known as structuree query language to
access, upeate, ane eelete eata within its tables. These programs,
inclueing Microsofts SQL Server ane the open-source MySQL
systems, allow outsiee programs to access its eata via SQL queries.
For instance, a web site can eisplay proeuct eata, inclueing photos,
prices ane eescriptons, when the web server sofware connects to
the eata containee in the relatonal eatabase management system.

One of the most important aspects of an relatonal eatabase


Data Relatonships
management system program is how it allows eiferent eata tables
to relate to each other. When a eatabase contains a table with
employee eata on its sales staf ane another with eata on its
proeuct sales, the relatonal eatabase management system can
manage the relatonship between the two tables. This relatonship
can help management eetermine which salesperson has the highest
sales totals ane which proeuct that salesperson is selling the most.

A fully-functonal relatonal eatabase management system allows


Data Upeates
users to enter new informaton, upeate current recores ane eelete
outeatee eata. As an example, when a salesperson sells 1,000
units, that person will enter the transacton informaton into the
relatonal eatabase management system. The eata can incluee the
salespersonts name, the customer informaton, the proeuct sole
ane the quantty sole. The relatonal eatabase management system
enters a new recore in the customer table, upeates the
salespersonts recore ane subtracts 1,000 units from the inventory
recore.

The relatonal eatabase management system also ensures that a


Data Searches
company can buile ane maintain its eata over the systemts lifetme.
The various tables in the relatonal eatabase management system
18

allow users to search through the system using any available


criteria. Customers can search a proeuct table by name, brane,
price, color or any other feature. The system stores eata in a
preeictable, sequental format, enabling users to look up previous
recores with relatve ease.

Structuree Query Language (SQL)

SQL (Structuree Query Language) is a staneareizee programming language usee for


managing relatonal eatabases ane performing various operatons on the eata in them.
Initally createe in the 1970s, SQL is regularly usee by eatabase aeministrators, as well as by
eevelopers writng eata integraton scripts ane eata analysts looking to set up ane run
analytcal queries.

The uses of SQL incluee moeifying eatabase table ane ineex structurese aeeing,
upeatng ane eeletng rows of eatae ane retrieving subsets of informaton from within a
eatabase for transacton processing ane analytcs applicatons. Queries ane other SQL
operatons take the form of commanes writen as statements -- commonly usee SQL
statements incluee select, aee, insert, upeate, eelete, create, alter ane truncate.

SQL became the ee facto staneare programming language for relatonal eatabases
afer they emergee in the late 1970s ane early 1980s. Also known as SQL eatabases,
relatonal systems comprise a set of tables containing eata in rows ane columns. Each
column in a table correspones to a category of eata -- for example, customer name or
aeeress -- while each row contains a eata value for the intersectng column.

SQL staneare ane proprietary extensions

An ofcial SQL staneare was aeoptee by the American Natonal Staneares Insttute
(ANSI) in 1986 ane then by the Internatonal Organizaton for Staneareizaton, known as
ISO in 1987. More than a half-eozen joint upeates to the staneare have been releasee by
the two staneares eevelopment boeies since thene as of this writng, recent version is
SQL:2011, approvee that year.

Both proprietary ane open source RDBMS built aroune SQL are available for use by
organizatons. They incluee MS SQL Server, Oracle Database, IBM DB2, SAP HANA, SAP
Aeaptve Server, MySQL (now ownee by Oracle) ane PostgreSQL. However, many of these
eatabase proeucts support SQL with proprietary extensions to the staneare language for
proceeural programming ane other functons. For example, Microsof ofers a set of
extensions callee Transact-SQL (T-SQL), while Oraclets exteneee version of the staneare is
19
PL/SQL. As a result, the eiferent variants of SQL oferee by veneors arentt fully compatble
with one another.

SQL commanes ane syntax

SQL commanes are eivieee into several eiferent types, among them eata
manipulaton language (DML) ane eata eeiniton language (DDL) statements, transacton
controls ane security measures. The DML vocabulary is usee to retrieve ane manipulate
eata, while DDL statements are for eeining ane moeifying eatabase structures. The
transacton controls help manage transacton processing, ensuring that transactons are
either completee or rollee back if errors or problems occur. The security statements are
usee to control eatabase access as well as to create user roles ane permissions.
20

Chapter 3
Problem Statement

Problem Statement
The major task is to prepare a fully functonal eatabase system prototype (with user
interfaces) for a metro network (quite similar to Ineian Metro lte./Ineian Railways) which
will be implementee as a working open source prototype/project (hostee at itHub)
preparee with the help of staneare sofware engineering techniques, sofware project
management guieelines, proper eocumentaton & report preparaton, etc. using various
platorms [LibreOfce Base ane MySQL Workbench for eatabase preparatatonn] using
CASE tools such as LibreOfce Writer for eocumentaton ane eiagram eesigning. User
Interfaces are built in form of webpages using HTML, CSS, JavaScript, PHP for proper
haneling of user queries ane eata entrance.

Problem (Task) eescripton ane major tasks


Project aspects : (P-Poor, - ooe, E-Excellent)

➢ Reliable backup ane recovery


➢ Distributee functons
➢ Performance
➢ Heavily usee coniguratons P
➢ Online eata entry P
➢ Operatonal ease
➢ Upeates
➢ User Interface E
➢ Complex processing
➢ Reusability of Sofware E
➢ Installaton ease
➢ Multple sites P
➢ Facilatee Changes E

We’ve exploree various aspects of a practcal system (Ineian Metro/Ineian Railways)


at overview level ane seems basic atributes (basis recores) to be inclueee in the eatabase
ane are listee as-

 Train No.
 Staton No.
 Reservaton ID
 Passenger ID
 Departure Time
21
 Train Type
 Fare ane Distances
 Source – Destnaton, etc.

Most of the above atributes are taken into account for project problem ane are properly
incorporatee in relatonal moeel eesign of project ane in Entty-Relatonship eiagram. See E-R
eiagram.

Tasks :

➢ Planning ane Analysis of commercially available sofwares on metro system


➢ Database implementatons
➢ Staneare testng of all implementatons
➢ Performance analysis of all implementatons (to evaluate all implementatons)
➢ Provieing a user interface for ene & front users, aeministrators, etc.
➢ Make a fully functonal prototype.
22

Chapter 4
Software and aardware reuuirements
Minimum System/Sofware/Hareware requirements :

 Wineows 7/Linux 3/Mac OS/Chromium OS


 Memory requirements: 64 MB (RAM).
◦ Recommeneee 128 MB.
 Seconeary memory requirements (Hare eisk): 10 B (ROM).
◦ Recommeneee 256/512 B
 Oracle MySQL Workbench/LibreOfce Base
◦ Recommeneee MySQL Workbench/Commane Line Client
 Writer ane eiagram eesigning sofware such as MS Visio or LibreOfce Draw.
 Clock Speee: 866 Mhz
 Virtual Memory: 32 bits
 Cache Memory: 512KB, etc.

Resources Usage :

 Operatng System: Wineows 10/Ubuntu 17.10


 Memory: 8 B (RAM)
 Seconeary memory: 1 TB (ROM)
 Oracle MySQL Workbench 6.3 CE (Wineows)/ LibreOfce Base 5 (Ubuntu
17.10/Linux 4)
 Microsof Wore 16/ LibreOfce Writer 5.4 (Linux)

Functonal requirements :

 Customer/Passenger/Employee eata storage ane retrieval


 Proper User Interface such as input forms
 Customizee user queries for complete system inclueing proper error haneling

Performance requirements :

 Shoulen’t wear out in passage of tme


 Shoulen’t lag in responeing to user enquires
 Shoulen’t crash abruptly
 Must be in accoreace to eata consistency (Proper resemblance of foreign keys)
23

Chapter 5
Methodology used

Methoeology

The methoeology aeoptee in the project is simple ane is easy to implement.


Functons ane Object orientee methoeology consttute a major porton of methoeology.
Project is eivieee into ineivial tasks. Tasks are then taken as inital problem ane solvee
ineivieually ane have to integrate them at last. Objectves are set irst ane then we triee to
fulill all objectves assertee.

We’ve irst implementee preliminary Entty-Relatonship eiagram in 2 platorms


namely- MySQL Workbench (Wineows 10) ane LibreOfce Base (Ubuntu 17.10). We then
intuitvely analyzee which platorm is more suitable for this partcular schema ane requiree
functonalites. Afer that we enhance that schema to further more relatons, enttes,
relatonships, forms, queries, etc.

The Project eevelopment moeel we usee in project eevelopment is closely relatee to


hybrie associaton of waterfall phases, Rapie applicaton eevelopment (Rapie eelievery of
project), Agile methoeology (Simplicity ane Swif evaluaton), Some Extreme Programming
practces, ane 4th generaton tool usage (Usage of CASE tool: LibreOfce Base/Draw). The
involvement of multple moeel element in single project leaes to higher level of
customizaton, beter management of project, beter requirements aeaptability, ane
improvee rigieity of overall management proceeure ane eevelopment life cycle.

We’ve ofen usee many Sofware engineering principles in the project to make it well
organisee, formal, ane more proeuctve. Use of Open-Source tools helps us to contribute
Free sofware founeaton ane Open-source community. We’ve moeellee the project
structure into various eiagrams such as Entty-Relatonship eiagrams, Use-Case eiagrams,
Sequence eiagrams, Data flow eiagrams. An Architecture eiagram is also eesignee for an
overview of eatabase proceeure insiee the system ane the interconnecton of network
between Client ane Server.
24

Chapter 6
Design framework

Entty-Relatonship eiagram:

**Screenshot size is modifed for beter isibiiitt


25

Entty-Relatonship eiagram (Preliminary) :


26

Sequence eiagram :
27

Database architectural eiagram :


28

Data flow eiagrams :


29

Use-Case eiagrams :
30

Chapter 7
mplementation
Coeing

Coeing is mainly eone in Structuree Query Language (SQL) for MySQL Commane
Line Client for customisee queries. The Coees of HTML, CSS, JS, ane PHP are formatee,
uneerstaneable, customizable, ane moeiiable. We can combine other functonalites using
these coees since there we kept a margin for reusability. Check out Implementatonal
snapshots for a view of coees.

Also Check out Appeneix-B for runnable coees of sample queries in SQL.

Implementatonal Snapshots

Front-ene Webpages
35

Back-ene Coees
36
39

MySQL Command line Client


40
41

Chapter 8
Testing

Proceeure

The proceeure of testng of SQL coees usee is quite simple, staneare, efectve. The
steps usee in complete testng proceeure is shown below-

1. Checking for SQL Syntax by eirectly running the queries


2. Checking for broaeer logics of coee: Is coee working accoreing to logics or not?
3. White box Checking
3.1 Structural testng which checks outer structure of logic
4. Black box checking
4.1 Functonal testng which checks if coee working accoreing to functonality or
not.
5. Coeing staneares which is not a testng step but we check for some staneare coee
inclueing gooe formatting, alignments, proceeure calls, etc.

Outcomes

Testng proviees us to minimize sort of error prone functonalites as per our


implementaton. Here, following simple proceeure for testng we get eesiree hassle free
functonality. Project is currently working ine ane since testng proceeure is available, we
can further apply that testng proceeure in case of malfuncton or bug ineings.
42

Chapter 9
Conclusions and future Scope

Conclusions:

Usage of eatabase toeay is of utmost importance for an enterprise or an insttuton


because it eliminates all the major erawbacks of ile system via Programming language or
Offline ile saving. It helps in improving the whole proceeure of eata/informaton storage
ane retrieval. There are also some risks such as injecton techniques, Reliability issues, eata
inconsistency risks, etc. Hence it requires to construct a proper Risk Mitgaton, Monitoring,
ane Management plan (RMMM Plan) for speciic usage of eatabases practcally.

We keep our project small ane simple which lee to some major improvements in
costs, eforts, ane tme usage in complete life cycle of project eevelopment. We’ve triee to
incluee all major functonalites which must be there in a metro/railway system eatabase
but stll it is far behine than a practcal working sofware. It requires large number of
atributes their manipulaton ane maintainance. We’ve completee major objectves of our
project ane the project is now in its maintainance phase which will contnue at ithub
where it will be proper version controllee ane is properly maintainee by subject experts,
reviewers, stueents, etc.

We hae not built RMMM plan for every risk insteae we take look at each ane every
feasible risk in eevelopment proceeure, ane simple eliminate it by whatsoever reasons.

Future Scope ane improvements:

In near future the usage of eatabases will probably be eecreasee eue to huge
sources of eata ane new technologies such as Big eata analytcs which will further improve
the erawbacks of eatabase management system.

The project output can be usee as raw input to a bigger project which may lee to
practcal implementaton of various concepts ane eebugging. This can be enhancee much
on following points-

1. User Interface:
• It can be portee to a simple applicaton using aneroie stueio/iOS buileer
which can then be publishee on Play Store, or iOS Store.
• It can be reconstructee by raphics programming user Java Swing, Java awt,
or Python Tkinter for web applicatons.

2. Implementaton:
43
• It can be implementee using Oracle eatabase 12C, DB2, PostgreSQL,
MongoDB. LibreOfce is currently using HSQLEmbeeeee as embeeeee
eatabase, insteae of which other eatabases can be usee as per requirements.
• The relatonal schema for Metro System can also be implementee on Object
Orientee eatabase which has its own pros ane cons.

3. Methoeology: We’ve usee simple yet hybrie methoeology for customizaton of events in
eevelopment of out project.
• Agile methoeology can be usee completely which will take the performace of
project eevelopment at high level.
• Extreme Programming practces ane actvites can also be usee in Project
eevelopment life cycle which has its own further improvements.

4. Staneares: We’ve simply usee unorganizee guieelines ane eevelop project using raneom
sofware staneares.
• Insteae of raneom sofware staneares we can use organisee ISO
(Internatonal staneares organisaton) staneares ane guieelines such as ISO
9001-2008.
• Capability Maturity Moeel (CMM) uieelines can be usee in organisee
manner in at least level-3.
• Six Sigma certicaton aspects can also be incorporatee in project
eevelopment.
44

References and Bibliography


1n] Database System concepts. Abraham Silberschatz, Henry F. Korth, S.
Suearshan. 6 th Internatonal eeiton. Mc raw-Hill, New York.
ISBN 978-0-07-352332-3. MHID 0-07-352332-1.

2n] Database Systems The Complete Book. Hector arcia-Molina, Jefrey D.


Ullman, Jennifer Wieom. 2ne eeiton. Prentce Hall, New Jersey.
ISBN 0-13-606701-8, 978-0-13-606701-6.

3n] Database Management Systems. Raghu Ramakrishnan, Johannes ehrke. 2 ne


eeiton. Mc raw Hill higher eeucaton. ISBN 0-07-246535-2.

4n] Database Management System (DMS) tutorial. Tutorials Point.


SQL tutorial. Tutorials Point. htps://www. tutorialspoint.com/.

5n] Scribee Class notes on Database Management Systems (CSE-224) at MANIT,


Bhopal. Instructor: Ms. Shweta Jain.

6n] Why Are Database Management Systems Important to Business


Organizatons? erale Hanks. Retrievee- April 4, 2018.
htps://yourbusiness.azcentral.com/eatabase-management-systems-
important-business-organizatons-21106.html

7n] Techtarget. Retrievee- April 4, 2018. Deiniton of SQL


htps://searchsqlserver.techtarget.com/eeiniton/SQL

8n] Webpage template (login-form-13) from htps://www.colorlib.com/wp/

*Chapter 2 (Literature Survey) is solely basee on (6) ane (7).


45

Appendix A
List of tables, forms, and uueries

List of tables

1. User (UserName, UserID, Aaehar, Passwore)

2. Reservatons (ReservatonID, PassengerID, PassengerName, FromStaton,


ToStaton, TrainID, TrainName)

3. Department (DepartmentName, DepartmentID, StatonID)

4. Employees (EmployeeID, FirstName, LastName, Salary, BirthDate,


DepartmentID, StatonID, StatonName, Phone)

5. Payments (PaymentID, UserID, UserName, PaymentDate, Amount)

6. Statons (StatonID, StatonName)

7. Trains (TrainID, TrainName, FromStaton, ToStaton, StartTime, EneTime,


SeatsRemaining)

List of web-pages

1. front.php

2. booking.php

3. enquiry.html ane enquiry.php

4. signup.php

5. login.php

6. cancel.php
46

List of Sample queries


1. To ine all users with all their eetails

2. To ine eescripton of all trains startee from Bhopal

3. To ine User having Aaehar=65695486

4. To ine names of all employees having salary greater than all other employess

5. To Fine out train which enes at Ineore ane having remaining seats at least 1

6. To ine UserID of user paymentee INR 10,000 at 23 March 2018.

**Queries can be further writen or customizee as per requirements.


47

Appendix B
SQL code for sample uueries
1. To ine all users with their eetails

SELECT *
FROM "users"e

2. To ine eescripton of all train startee from Bhopal

SELECT *
FROM "Trains"
WHERE "FromStaton" LIKE tBhopalte

3. To ine user whose Aaehar is 65695486

SELECT "FirstName", "LastName", "UserID"


FROM "Users"
WHERE "Aaehar" = 65695486e

4. To ine names of all employees having salary greater than all other employess

SELECT "FirstName", "MieeleName"


FROM "Employees"
WHERE "Salary" >= ALL ( SELECT "Salary" FROM "Employees" )e

5. To Fine out train which enes at Ineore ane having at least 1 seat unreservee

SELECT *
FROM "Trains"
WHERE "EneStaton" = tIneoret ane "SeatsRemaining">=1e

6. To ine UserID of users paymentee INR 10,000 at 23 March 2018

SELECT "UserID", "UserName"


FROM "Payments" as p, "User" as u
WHERE u."UserID"=p."UserID" ane p."Amount"=10,000 ane
p."PaymentDate"="23/03/2018"e
48

Appendix C
Critsm ane Expert reviews
To be writen soon...

Thanks for reviewing the eocument :)

End of the document :t

You might also like