1

iSYSTEM
PROJECT PLAN

IDENTIFICATION USER PRINCIPLE TIME MODE;

Team Work 2

Ghifari
Vira Prameswa
Yolanda ri
53416019
57416563

Sayidat
i Farisha
Karima
56416883 Irwayu
Eka 52416676
Setianings
ih
52416278
 3

iSYS
The understanding of the daily traffic pattern in Jakarta alone

TEM
is not enough for the system to generate the optimal solution
that has to be given for the users. We want to achieve the
system should be smart enough to predict which drivers are
taking every day to reach a certain destination, and also
understanding and knowing how to allocate and manage the
number of roads / routes.
 4
IDENTIFICATION
iSYSTEM

1 Identifying
Requirement

a. Informations b. Infrastructures c. People

• Social Feeds and Mobile Sense • Road Sensors • Computer Engineer
• Numbers of Each Vehicles in • CCTV • IT Technician
Roads • Vehicle Detector • Networking Engineer
• Others • Satellite
Example: weather condition, stop • Vehicular Network
signs • Signal
• BTS
 5

$
$

$
IDENTIFICATION $
$

iSYSTEM $

2 Identifying
Cost

a. Informations b. Infrastructures
• Traffic Monitoring : Rp. 50.000.000 Range per person : Rp. 4.000.000 - Rp.10.000.000
• Network : Rp. 40.000.000

3 Identifying
Challenges

a. Accurancy
b. Security and Privacy Violations
 6
ANALYSIS
iSYSTEM

Traffic Allocation
1 Management
To determine the maximum number
of vehicles that can go to certain
routes. Considering how many road
signs and stop signs in each route
can also help us to determine the
optimal solution or in this case, the
fastest route.

2 Security and Privacy

Protection
Ensuring information privacy and
security in iSystem is essential for all
involved people, transit agencies,
government, and so on. Since the data
may contain personal information and
can track people and vehicles, one key
challenge is the action of malicious
entities which can add or change route
generated by services.
 7

USER
iSYSTEM

This system can be

used by a
minimum age
range of 17 years We also want
old who has a iSystem to be
driving licencse. tourist-friendly
We want this
system can be used
by elderly people
 8
Application in Software
Principle
iSYSTEM

1 Modularity

a. Informations Gathering b. Control System c. Processing

Collect some information that will be Identify route according Processing data that has
used in making decisions initial start and been obtained in Information
- Numbers of Each Vehicles in Roads destination gathering to produce
- Road Quality information
- Weather Condition - Selected Routes
- Stop Sign - Shortest Route
 9
Application in Software
Principle
iSYSTEM
1 Modularity

d. Delivering
Provide interface in mobile
application
 10
Application in Software
Principle
iSYSTEM
2 Abstraction

The abstraction of our system design can be presented in four steps: Information Gathering, Control System,
Processing, and Delivering.

3 Incrementality

a. iSystem Version 1 b. iSystem version 2 c. iSystem version 3

- Guide to Navigation directions (turn by - Information on road - Map updating
turn) congestion
- Pronunciation of street names when - Supports many
navigating (Text to Speech / TTS) languages
- Toll avoidance options when navigating, - Help menu to make it
which are very useful for motorists easier for beginners
 11
TIME’s BUDGET
iSYSTEM
$
$
$ Based on our skill in modularity, the
project time budget that required to
complete the project is 1 months. To
complete the project in abstraction is
2 weeks. And to complete the project
in incrementality is 3 months.
 12
SUITABLE DEVELOPMENT
MODEL
iSYSTEM

The suitable development This model can continue to be

This model has a series of work
model for this system is a spiral used even though the software
that iterates (an increase in the
model. Because, every stage of has been sent because the
initial model) in the form of a
this model is always carried out process (cycle) can rotate again
prototype and then the next
risk analysis and verification or if there are changes to the
iteration will be the
testing. The spiral model is a software until there are no
development of the previous
process whose approach is requests for changes to the
model.
realistic in large software. software by the client.
 D
D
Thank you