Introducing
Your new presentation assistant.
Refine, enhance, and tailor your content, source relevant images, and edit visuals quicker than ever before.
Trending searches
METRO TICKET QR-CODE
13
Client Name
Mohamed Ahmed
Agenda
A
1-Introduction on project
2-Generation of ticket
3-motivation
4-similar studies
5-software development life cycle
6-U.M.L Diagram
7-Data Dictionary
Agenda
Summary
Problem :
1-For passenger :-take a lot of time for waiting in lines to get
to gets tickets from windows of tickets.
2-For metro Authority :- spend a lot of money for employee
to takes there wadges and print a lot of tickets daily that takes a lot of money for budget of metro Authority.
Solution :
Executive Summary
Using metro ticker QR-Code application.
Projected Result :
1-For passenger :- will be fasting the operation for passenger
that will not waiting and waste a lot of time in this lines.
2-For metro Authority:-the Authority not need to spend money
for employee for monthly wadges and not need to print
a ticket daily.
Project Intro
P
1-Over view
2-problem Description
3-Project objective
4-System Requirement
5-User Requirement
Project Intro
Over view
Over view
Metro is considered one of the most popular means of transport in the world and in many countries
of the world, it is considered as a basic means of transport and conductors
And is considered one of the most important means in our time because of its speed and high
efficiency in passenger transport,
There are many countries that use the subway from the most famous countries in the world of
Japan which is known
They have the fastest Metro in the world in our time, and many other countries like France,
England, America, and many more
In this regard, he answers that we are talking about the first African and Arab countries that used
the subway, the Arab Republic of Egypt.
problem Description
problem Description
The main purpose of the problem statement is to identify and explain the problem. This includes
describing the existing environment, where the problem occurs, and what impacts it has on users,
finances, and ancillary activities. Additionally, the problem statement is used to explain what the
expected environment looks like. Defining the desired condition provides an overall vision for the
process or product. It makes clear the purpose for initiating the improvement project and the goals
that it is meant to accomplish.
Project objective
Project objective
1-TO AUTOMATICALLY COMPUTE THE BILL
2-TIME AND ENERGY SAVING
3-AVAILABILITY
4-SECURITY
5- safety
System Requirement
System
(R.E.Q)
User Requirement
User
(R.E.Q)
W.i-F.i (/ˈw.a.ɪ.f.a.ɪ./) is technology for radio wireless local area networking of devices based on
the I.E.E.E 802.11 standards. W.i-F.i is a trademark of the W.i-F.i Alliance, which restricts the use
of the term W.i-F.i Certified to products that successfully complete interoperability certification
testing
Google Play (previously Android Market) is a digital distribution service operated and
developed by Google. It serves as the official app store for the Android operating system
comparative Study
- Similar Study
C
1.( U.B.E.R)
2. RAIL EGYPT
3. (M.w.a.s.a.l.t.e M.i.s.r)
4.CAIRO METRO
comparative Study
( U.B.E.R)
(U.b.e.r) Technologies Inc. is a
global transportation
technology company that
operates in more than 760
cities in more than 70
countries.
( U.B.E.R)
RAIL EGYPT
RAIL EGYPT
An application that allows search between any two train
stations from more than 500 stations in Egypt.
(M.w.a.s.a.l.t.e M.i.s.r)
(M.w.a.s.a.l.t.e M.i.s.r)
The Public Transport Authority to apply to a number of bus lines
of the Authority, stressing the importance of the application of
the electronic fleet management system
CAIRO METRO
CAIRO METRO
This application provides a lot of useful services which help
the Metro users and provide them with information about
the Metro lines and stations.
SYSTEM ANALYSIS
S
1. overview
2.Software Development Life Cycle
3.USE CASE DIAGRAM
4. ACTIVITY DIAGRAM
5.SEQUENCE DIAGRAM
SYSTEM ANALYSIS
overview
In this chapter we will shed a light on the software development life cycle and its phases, we will also discuss the software methodology that we is used in the project, and we will present multiple phases in software development cycle of the project, we will also present and explain the system analysis followed in this project
Software Development Life Cycle
Software Development Life Cycle
1.Requirements
2.Design
3.Implementation
4.Testing
5.Deployment
6.Maintenance
USE CASE DIAGRAM
USE CASE DIAGRAM
ACTIVITY DIAGRAM
ACTIVITY DIAGRAM
Example 1
Example 1
1. Initial node: The filled in circle is the starting point of the diagram.
2. Activity final node: The filled circle with a border is the ending point.
3. Activity: The rounded rectangles represent activities that occur. An activity may be physical,
such as Inspect Forms, or electronic.
4. Flow/edge: The arrows on the diagram. Although there is a subtle difference between flows
and edges.
5. Fork: A black bar with one flow going into it and several leaving it. This denotes the beginning
of parallel activity.
6. Join: A black bar with several flows entering it and one leaving it. All flows going into the join
must reach it before processing may continue.
7. Condition: Text such as [Incorrect Form] on a flow, defining a guard which must evaluate to
true in order to traverse the node.
8. Decision: A diamond with one flow entering and several leaving. The flows leaving include
conditions although some modelers will not indicate the conditions.
9. Merge: A diamond with several flows entering and one leaving
Example 2
Example 2
1. Initial node: The filled in circle is the starting point of the diagram.
2. Activity final node: The filled circle with a border is the ending point.
3. Activity: The rounded rectangles represent activities that occur. An activity may be physical,
such as Inspect Forms, or electronic.
4. Flow/edge: The arrows on the diagram. Although there is a subtle difference between flows
and edges.
5. Fork: A black bar with one flow going into it and several leaving it. This denotes the beginning
of parallel activity.
6. Join: A black bar with several flows entering it and one leaving it. All flows going into the join
must reach it before processing may continue.
7. Condition: Text such as [Incorrect Form] on a flow, defining a guard which must evaluate to
true in order to traverse the node.
8. Decision: A diamond with one flow entering and several leaving. The flows leaving include
conditions although some modelers will not indicate the conditions.
9. Merge: A diamond with several flows entering and one leaving
Example 3
Example 3
1. Initial node: The filled in circle is the starting point of the diagram.
2. Activity final node: The filled circle with a border is the ending point.
3. Activity: The rounded rectangles represent activities that occur. An activity may be physical,
such as Inspect Forms, or electronic.
4. Flow/edge: The arrows on the diagram. Although there is a subtle difference between flows
and edges.
5. Fork: A black bar with one flow going into it and several leaving it. This denotes the beginning
of parallel activity.
6. Join: A black bar with several flows entering it and one leaving it. All flows going into the join
must reach it before processing may continue.
7. Condition: Text such as [Incorrect Form] on a flow, defining a guard which must evaluate to
true in order to traverse the node.
8. Decision: A diamond with one flow entering and several leaving. The flows leaving include
conditions although some modelers will not indicate the conditions.
9. Merge: A diamond with several flows entering and one leaving
SEQUENCE DIAGRAM
Example 1
Example 1
Example 2
Example 2
Example 3
Example 3
Data Dictionary
D
1.CONTEXT DIAGRAM
2. (D.F.D) LEVEL 0
3.(D.F.D) LEVEL 1
4.process
5.Data stores
6.Data flow
Data
Dictionary
CONTEXT DIAGRAM
CONTEXT DIAGRAM
1-Passenger
2- Metro Authority
3- Bank
4- Telecoms companies
(D.F.D) LEVEL 0
(D.F.D) LEVEL 0
1-Data Passenger
2- QR-Code Data
3-Data Money
4-Data Mobile Number
5-Logan
6-Register ticket
7-Payment
8-manage passenger
9-Verify QR-code creator
10-Check QR-CODE
11-Checking money card
(D.F.D) LEVEL 1
(D.F.D) LEVEL 1
process
process
1-Logan
2-Register ticket
3-Payment
4-manage passenger
5-Verify QR-code creator
6-Check QR-CODE
7-Checking money card
8- Charge Money
Data stores
Data stores
1-Data Passenger
2- QR-Code Data
3-Data Money
4-Data Mobile Number