FINAL YEAR PROJECT I

“SMIU STUDENT TRANSPORT MANAGEMENT SYSTEM”

GROUP MEMBERS:
• HAMZA ALTAF(CSC-17F-134)
• JAWAD NOONARI (CSC-17F-103)
COURSE SUPERVISOR: SIR KAMLESH KUMAR

1|Page
TABLE OF CONTENTS:

Chapter no: 1 ------------------------------------------------------------------------ 3 to 7

Introduction ---------------------------------------------------------------------- 3
Problem statement --------------------------------------------------------------- 3
Aims and objectives ---------------------------------------------------------------------------- 4
Project Scope ------------------------------------------------------------------------------------ 4 to 5
Project Methodology --------------------------------------------------------------------------- 6 to 7

Chapter no: 2 ------------------------------------------------------------------------ 7 to 10

Literature Review ---------------------------------------------------------------- 7
Existing websites ---------------------------------------------------------------- 7 to 10
Chapter no: 3 ----------------------------------------------------------------------- 11 to 22
Use Case ---------------------------------------------------------------------- 11
Basic notations of Use Case ------------------------------------------------ 11 to 12
Use Case of our project -------------------------------------------------------------------- 13
Entity Relationship diagram ---------------------------------------------------------------- 14
Common notations of ERD ----------------------------------------------------------------- 14 to 16
ERD of our Project -------------------------------------------------------------------------- 17 to 18
Data Flow Diagram ------------------------------------------------------------------------- 19
DFD Notations ------------------------------------------------------------------------------ 19 to 20
DFD of our Project -------------------------------------------------------------------------- 21 to 22

2|Page
 Chapter # 01
INTRODUCTION:
In this project we are making an application for the students of Sindh madressatul
Islam University (SMIU). This application are for those students that have issues in transport or
those students that want to take service of transport. The application must give easiest way for
students to get transport.
Basically the student have to first create an account. Then after signup successfully
the student have to login and then have further steps to follow:
• Students have to make profile.
• Students have to enter all details that are required for completing the profile.
• Students have to enter a correct details so the other student that have facilitate with the
service can have easily contact.
In this application there is a cash to cash payment system as it is easy and satisfaction
payment method for both that gives service and that take service.
In today’s era not everyone has its own vehicle for transport. So, those who have
issues of transport they have easily manage rides and get transport through this application.
This application gives advantage for those students that are coming with same area
so they both easily came with each other by using this application and contact with each other.
The student that comes lonely instead it have a seat to give someone ride so this application
gives the opportunity for the student to give and take service and make money and it is also
strong the bonding between students.

PROBLEM STATEMENT:
This application facilitate transport for students. The benefit is that Students that
have in same area are come together easily, the student that give transport have earn some money
and other student who get the transport service has easily reached on campus. There is cash to
cash payment which gives satisfaction to student of earn some money. The problem is that the
available students for giving transport facility may have a different timing for their classes as
compared to the other student who need a ride. So, there is a clash of timings in student’s classes.
There is issue to manage and give proper transport facility.

3|Page
AIMS AND OBJECTIVES:
The aim of this project is to help and give transport facility to the students. There are
followings aims of the project.
• The students that have issues for transport can easily get transport facility.
• The students that are using buses to other transport facility to come university and getting
late to reach university due to traffic can easily get rides of motorcycle to the nearest student
that have also same destination. So, we can overcome this issue easily and manage time
period and reach on time in university.

OBJECTIVES:
This project gives a desired result for students that have a transport issue. Following
are the results of this project to complete the project milestone.
• Student can facilitate with easiest way to get transport.
• In student’s profile there is overall description for seats and space that have a transport to
facilitate and other student’s that have need a ride can easily manage with chat or contacts
details.
• Student have not too much complexity as there is relation between student to student for
overall transport management.
• Students have one to one relation with each other as they both deal with cash to cash
payment after reach on destination.
The overall result is that the student can easily get transport and manage their timings
and reach on time in campus or destination for classes.
The project fulfills the student requirements and facilitate them with easiest way of
transport system.

PROJECT SCOPE:
Project scope is the part of project planning that involves determining and
documenting a list of specific project goals, deliverables, tasks, costs and deadlines. There are
some steps to define scope of the project.

1- Project needs: This project is clears that the application facilitate the transport for those
who have issues for transport.

2- Objectives and goals: The goals and objectives are clear for this project that follows
S.M.A.R.T guidelines.

4|Page
 ➢ Specific: The goal of this project is to facilitate the transport for needy
students.
➢ Measurable: The student give feedback that is accountable.
➢ Achievable: The resources available to achieve the project.
➢ Realistic: project is going according to the gantt chart if any problem occur it
will manage.
➢ Time frame: The project is going according to the time frame which is describe
in gantt chart and it is the key to meet deadlines.

3- Project scope description: The functions and features required for the project are using
in this project to improve the quality of the project.

Example: Feedback.
4- Expectations and Acceptance: The expectation is that the end-user of this project is
student they give feedback after using the application that shows the acceptance of the project.

5- Identify constraints: we can identify our project limitation which help us to minimize
our problems and we have working on that to improve project quality.

The scope of our project is in budget. This application has not complex. As it
have user friendly interface and easy to use. It has simple functionality that helped
the users that are using first time.

5|Page
PROJECT METHADOLOGY:
The methodology of the project is that to facilitate the student with transport in easiest way that
can help them.

Fig 1.1

The use case of this project is given above is describe the methodology of the project.
Following are the users of this applications:

Admin: The admin manage the all transport management as it can see the profiles of the
student and account details. It can also see the accounts that are register.

Student1: (rider) This is a student that can give the ride to the needy students. They can chat
with the other student and contact to give the facility.

6|Page
Student2: (need of ride) This is the student that have a need of ride.

Student1 and student2 have a one to one relation with each other as they are dealing
with own to own dealing and there is cash to cash payment method. As shown in the above fig
1.1.
Student also give feedback that help us to improve the quality of project.

CHAPTER # 02
LITERATURE REVIEW:
There are many websites available of different universities that facilitate their
students with transport to provide better service and that is helpful for students.

Existing websites:
(i)GC University Lahore:
The GC university Lahore have a website for their students to facilitate them with transport as
shown in figure 2.1 is given below:

Fig 2.1

7|Page
 Fig 2.2

Comparison with project:

The above details in fig 2.2 shows that student have to pay the fees per academic year.

GCC Lahore: (Payment method)

In above website you can see the details that student have to pay the fees per academic
year. This is the issue that not everyone afford the fee per year with in one time.

SMIU STUDENT TRANSPORT MANAGEMENT: (payment method)

In our website or application there is cash to cash payment method so the student can easy
pay the fees after getting the transport.
So, above comparison shows that our model of payment method is better facilitate the
students to easily pay the fees.

8|Page
(ii)UNIVERISTY OF PUNJAB:
The below figure 2.3 is the home page of website of university of Punjab.

Fig 2.3

Fig 2.4

9|Page
Comparison with project:
The above details in fig 2.4 shows that student have to pay the fees per academic year.

University of Punjab: (Payment method)

In above website you can see the details that student have to pay the fees per academic
year. This is the issue that not everyone afford the fee per year with in one time.

SMIU STUDENT TRANSPORT MANAGEMENT: (payment method)

In our website or application there is cash to cash payment method so the student can easy
pay the fees after getting the transport.
So, above comparison shows that our model of payment method is better facilitate the
students to easily pay the fees.

10 | P a g e
 Chapter # 03
Use Case diagram:
A use case diagram is a dynamic or behavior diagram in UML. Use case diagrams model the
functionality of a system using actors and use cases. Use cases are a set of actions, services, and functions
that the system needs to perform. In this context, a "system" is something being developed or operated,
such as a web site. The "actors" are people or entities operating under defined roles within the system.

Why Make Use Case Diagrams?

Use case diagrams are valuable for visualizing the functional requirements of a system that will
translate into design choices and development priorities.

They also help identify any internal or external factors that may influence the system and should
be taken into consideration.
They provide a good high level analysis from outside the system. Use case diagrams specify how
the system interacts with actors without worrying about the details of how that functionality is
implemented.

Basic Use Case Diagram Symbols and Notations:

There are some basic use case diagram symbols and notates described below:

(i)System:
Draw your system's boundaries using a rectangle that contains use cases. Place actors outside the
system's boundaries.

Fig 3.1
(ii)Use Case:
Draw use cases using ovals. Label the ovals with verbs that represent the system's
functions.

Fig 3.2

11 | P a g e
(iii)Actors:
Actors are the users of a system. When one system is the actor of another system, label the
actor system with the actor stereotype.

Fig 3.3
(iv)Relationships
Illustrate relationships between an actor and a use case with a simple line. For relationships
among use cases, use arrows labeled either "uses" or "extends." A "uses" relationship indicates
that one use case is needed by another in order to perform a task. An "extends" relationship
indicates alternative options under a certain use case.

Fig 3.4

12 | P a g e
USE-CASE OF OUR PROJECT:

Fig 3.5

The above use case shows the all functionality of application. The admin have
different working as the student have different functionality both have their own
functionality.

13 | P a g e
ENTITIY RELATIONSHIP DIAGRAM: (ERD)

An entity relationship diagram (ERD) shows the relationships of entity sets stored in a
database. An entity in this context is an object, a component of data. An entity set is a collection
of similar entities. These entities can have attributes that define its properties.

By defining the entities, their attributes, and showing the relationships between them, an ER
diagram illustrates the logical structure of databases.

ER diagrams are used to sketch out the design of a database.

Common Entity Relationship Diagram Symbols:
An ER diagram is a means of visualizing how the information a system produces is
related. There are five main components of an ERD:

• Entities, which are represented by rectangles. An entity is an object or concept about which
you want to store information.

Fig 3.6

• A weak entity is an entity that must defined by a foreign key relationship with another entity as
it cannot be uniquely identified by its own attributes alone

Fig 3.7

• Actions, which are represented by diamond shapes, show how two entities share information in
the database.

Fig 3.8
In some cases, entities can be self-linked. For example, employees can supervise other employees.

14 | P a g e
 Fig 3.9

• Attributes, which are represented by ovals. A key attribute is the unique, distinguishing
characteristic of the entity. For example, an employee's social security number might be the
employee's key attribute.

Fig 3.10

• A multivalued attribute can have more than one value. For example, an employee entity can
have multiple skill values.

Fig 3.11

• A derived attribute is based on another attribute. For example, an employee's monthly salary is
based on the employee's annual salary

Fig 3.12

• Connecting lines, solid lines that connect attributes to show the relationships of entities in the
diagram.
• Cardinality specifies how many instances of an entity relate to one instance of another entity.
Ordinality is also closely linked to cardinality. While cardinality specifies the occurrences of a
relationship, ordinality describes the relationship as either mandatory or optional. In other
words, cardinality specifies the maximum number of relationships and ordinality specifies the
absolute minimum number of relationships.

15 | P a g e
 Fig 3.13

16 | P a g e
ENTITY RELATIONSHIP DIGRAM OF OUR PROJECT:
STUDENT PANEL:

Fig 3.14

17 | P a g e
ADMIN PANEL:

Fig 3.15

The above both panel diagrams and functionality is clear the working of
student and admin.
Student have one to one relation with other student both students have
dealing with each other by contacting with each other.Admin manages records and
see the account details of students.

18 | P a g e
DATA FLOW DIAGRAM: (DFD)

A picture is worth a thousand words. A Data Flow Diagram (DFD) is a traditional way to
visualize the information flows within a system. A neat and clear DFD can depict a good
amount of the system requirements graphically. It can be manual, automated, or a combination
of both.

It shows how information enters and leaves the system, what changes the information and
where information is stored. The purpose of a DFD is to show the scope and boundaries of a
system as a whole. It may be used as a communications tool between a systems analyst and any
person who plays a part in the system that acts as the starting point for redesigning a system.

It is usually beginning with a context diagram as level 0 of the DFD diagram, a simple
representation of the whole system. To elaborate further from that, we drill down to a level 1
diagram with lower-level functions decomposed from the major functions of the system. This
could continue to evolve to become a level 2 diagram when further analysis is required.
Progression to levels 3, 4 and so on is possible but anything beyond level 3 is not very
common. Please bear in mind that the level of detail for decomposing a particular function
depending on the complexity that function.

DFD Diagram Notations

Now we'd like to briefly introduce to you a few diagram notations which you'll see in the
tutorial below.

(i)External Entity:
An external entity can represent a human, system or subsystem. It is where certain data comes
from or goes to. It is external to the system we study, in terms of the business process. For this
reason, people used to draw external entities on the edge of a diagram.

Fig 3.16

19 | P a g e
(ii)Process:
A process is a business activity or function where the manipulation and transformation of data
take place. A process can be decomposed to a finer level of details, for representing how data
is being processed within the process.

Fig 3.17

(iii)Data Store:
A data store represents the storage of persistent data required and/or produced by the process.
Here are some examples of data stores: membership forms, database tables, etc.

Fig 3.18

(iv)Data Flow:
A data flow represents the flow of information, with its direction represented by an arrowhead
that shows at the end(s) of flow connector.

Fig 3.18

20 | P a g e
ZERO LEVEL DFD:

Fig 3.19

FIRST-LEVEL DFD:

Fig 3.20

21 | P a g e
SECOND-LEVEL DFD:

Fig 3.21

The above all level of DFD’S describe the functionality of student and
admin in detail as the level increase the all functions described in detail.
Admin manages records of student and see the student’s account details.
Student can take rides my making an account and then maintain their portfolio and
students take service by contacting with each other.

22 | P a g e