Assignment Cover Sheet

Qualification Module Number and Title

Higher Diploma in Computing & Software CSE4004
Engineering System Analysis & Designing
Student Name & No. Assessor
M.Vihan Maljitha Costa (CLHDCSECMU9857)
Hand out date Submission Date

04/07/2021 20/08/2021
Assessment type Duration/Length of Weighting of Assessment
Assessment Type 100%

Assignment 2 WRIT1-Coursework: 75 %
( Individual )2250 words
equivalent

Learner declaration

I, …… M. Vihan Maljitha Costa …………………………………….<name of the student and registration

number>, certify that the work submitted for this assignment is my own and research sources are fully
acknowledged.

Marks Awarded
First assessor
IV marks
Agreed grade
Signature of the assessor Date

1
 FEEDBACK FORM

INTERNATIONAL COLLEGE OF BUSINESS & TECHNOLOGY

Module:

Student:

Assessor:

Assignment: Online Taxi (Vehicle) Booking System

Strong features of your work:

Areas for improvement:

2
 Marks Awarded:

Coursework

Learning outcomes covered

1. Demonstrate system designing methodologies, tools, and the techniques

2. Evaluate different systems development life cycle models
3. Analyze the system by using appropriate fact finding techniques.
4. Design the system by using appropriate system design techniques.

Scenario and Tasks

Introduction

System Analysis & designing is a very important subject domain related to Information
systems. Information systems’ durability, Validity, efficiency & accuracy depends on how well the system
investigation & designing activities are accomplished during the system development life cycle. Learning
& making use of the best tools such as Entity Relationship Diagram, Data Flow Diagram, Flowchart and
Unified Modelling Language Diagrams for aforementioned activities are very much essential for a system
analyst.

Clear understand ability of Software Development Life Cycle model stages & unique duties
assigned to those enables software development team to maintain product quality, track progress,
project budget and the nature of the product, according to higher satisfactory level. Selecting the best
Software development process model for an information system project is crucial since success or
failure of the product can be decided by the process model & its systematic approach.

3
When the subject domain is concerned it is always imperative to attention to be paid in applying
creativity and innovation for system designing in a manner that modern world man kind’s requirements
are supported by considering not only how their lives are further improved with sophistication but also
focusing on how ethical and professional issues does are mitigated as much as possible.

Scenario
The students are expected to use the information gathered and requirement identified from the Online
Vehicle (Taxi) Booking System which they have completed for the PRES1 to complete the below tasks.

Assignment 2

Individual – (Document Submission)

Tasks

1. Identify the advantage of using a standard software development lifecycle a model for
developing the software solution what is proposed for the organization/ institution. (LO2- 40
Marks)

2. Design the data model of the software solution that will be implemented in the organization /
institution by considering all required data / information requirements and explain briefly what
the best technique is to carry out data model designing of the system. (LO4- 25 Marks)

3. Design the functional model of the system software solution that will be implemented in the
organization / institution having concerned all the features /facilities, data collection,
transitions, transfers and dissemination requirements and explain briefly what the best
technique is to carry out functional model designing of the system. (LO4-35 Marks)

4
5
Assignment 2 (LO2 and LO4 – 100 Marks)

Task 1 (LO2 – 40 Marks)

Marks Marks
obtained
Criteria
by the
Out student
of 40 for the
answer
provided

poor

 System Development life cycle explained such as

Communication, planning, Designing, 0-9
Development & Testing, Implementation but no
mapping has been done with system
implemented.

Satisfactory

 At least Five stages of the System Development

life cycle explained such as Communication,
planning, Designing, Development & Testing,
Implementation. 10-19
 Every stage has been mapped with proposing
system development & designing activities.
 Standard documentation by including Harvard
referencing

Good 20-29

 At least Five stages of the System Development

life cycle explained such as Communication,
planning, Designing, Development & Testing,
Implementation.
 Every stage has been mapped with proposing
system development & designing activities.
 The description based on Prescriptive,
Incremental, Evolutionary, Agile & Specialized
Process Models
 Standard documentation by including Harvard
referencing

6
 Excellent

 At least Five stages of the System Development

life cycle explained such as Communication,
planning, Designing, Development & Testing,
Implementation.

 Every stage has been mapped with proposing

system development & designing activities.
 The description based on Prescriptive,
Incremental,Evolutionary,Agile & Specialized
Process Models
 Justifications have been done based on the
qualities of the proposing system.
 Standard documentation by including Harvard
referencing

30-40

Task 2 (LO4 – 25 Marks)

Marks Marks obtained

by the student for
Criteria
Out of 25 the answer
provided

Poor

 Use ER diagrams to design data model of the 0-6

proposing system but some errors exist.

Satisfactory 7-12

 Use ER diagrams to design data model of the

proposing system.

7
  Find entities, Attributes, relationships, Primary
keys, , different cardinalities, and other entities.

 Attributes, Entities, Relationships & Cardinalities

properly selected & illustrated.

Good

 Use ER diagrams to design data model of the

proposing system.

 Find entities, Attributes, relationships, Primary keys, 13-18

proper relationships with cardinality ratios.

 Attributes, Entities, Relationships & Cardinalities

properly selected & illustrated.

 Write a data dictionary for the ER diagram.

Excellent 19-25

 Use ER diagrams to design data model of the

proposing system.

 Find entities, Attributes, relationships, Primary keys,

proper relationships with cardinality ratios.

 Attributes, Entities, Relationships & Cardinalities

properly selected & illustrated.

8
  Write a data dictionary for the ER diagram.

 Has been used standard format for the Data

dictionary.

Task 3 (LO4 – 35 Marks)

Marks Marks obtained

by the student for
Criteria
Out of 35 the answer
provided

Poor

 Draw context level Data Flow Diagram to illustrate

functional model of the proposing system with some 0-8
errors.

Satisfactory 9-17

 Draw context level Data Flow Diagram to illustrate

functional model of the proposing system.
 External Entitles, Main Information System &
Information Initial flow between External Entities &
Main Information System have been identified &
illustrated.

 Proper Process & data flow labeling used

 Standard documentation by including Harvard

referencing

9
  Drawing USE CASE diagram by identifying relevant
actors and functions

Good 18-26

 Draw context level Data Flow Diagram to illustrate

functional model of the proposing system.

 External Entitles, Main Information System &

Information Initial flow between External Entities &
Main Information System have been identified &
illustrated.

 Draw Level 0 Data Flow Diagram to illustrate

functional model of the proposing system. showing
at least five different transaction processors

 External Entities, Major Processes, Data Storages &

initial Data Flows & Intermediate Data Flows in
between them have been Identified & illustrated.

 Draw a Level 1 Data Flow Diagram to illustrate

functional model of the proposing system
considering detailed analysis.
 External Entities, Sub Processes, Data Storages &
initial Data Flows & Intermediate Data Flows in
between them have been Identified & illustrated.

 Proper Process & data flow labeling used

 Drawing USE CASE diagram by identifying relevant

actors and functions and identifying dependencies
properly (Extend/ Include)

 Drawing an average level Class diagram by

identifying several classes related to the given
scenario.

10
Excellent

 Draw context level Data Flow Diagram to illustrate

functional model of the proposing system.

 External Entitles, Main Information System &

Information Initial flow between External Entities &
Main Information System have been identified &
illustrated.
 In order to further explain internal logic of the major
processes of the information system, Structured English,
Decision Trees & Decision Tables properly used for DFD
level 0 processes.
 Process specifications have been included using 27-35
standard process specification format
 Object type, Data Type, Data Inflow & Data Out Flow
have been described.
 Write a data dictionary for the DFD level 0 using
standard format.
 Top-down designing technique & the bottom up
designing technique should be properly explained
considering the functional design.
 Drawing USE CASE diagram by identifying relevant actors
and functions and identifying dependencies properly
(Extend/ Include)
 Drawing Class diagram by identifying all the classes and
the different types of suitable relationships among the
classes

11
 Document Format:

 Submission format: Document

 Paper Size: A4
 Words: 2250 words
 Printing Margins: LHS; RHS: 1 Inch
 Binding Margin: ½ Inch
 Header and Footer: 1 Inch
 Basic Font Size: 12
 Line Spacing: 1.5
 Font Style: Times New Roman
 Reference Style: Harvard Referencing

Final Grading criteria:

Marks Final Grade

>=70 Distinction

69-55 Merit

54-40 Pass

<40 Fail

12
SYSTEM ANALYSIS AND DESIGN

Create by M. Vihan Maljitha Costa

(CL/HDCSE/CMU/98/57)

13
14
15
Table of Contents
Assignment Cover Sheet..............................................................................................................................1
SYSTEM ANALYSIS AND DESIGN......................................................................................................12
Table of figures..........................................................................................................................................16
Table of table.............................................................................................................................................16
Acknowledgement.....................................................................................................................................17
Introduction...............................................................................................................................................17
Task 01.......................................................................................................................................................18
System Development Life Cycle (SDLC).................................................................................................18
7 Stages in System Development Life Cycle...........................................................................................18
planning.................................................................................................................................................18
Analysis..................................................................................................................................................18
Designing...............................................................................................................................................19
Development.........................................................................................................................................19
Testing...................................................................................................................................................19
Deployment...........................................................................................................................................19
Maintenance.........................................................................................................................................19
SDLC methodologies..............................................................................................................................20
Water fall model....................................................................................................................................20
Agile model............................................................................................................................................21
V- shaped model....................................................................................................................................22
Iterative model......................................................................................................................................23
Spiral model...........................................................................................................................................24
Big bang model......................................................................................................................................25
Requirement gathering and planning about the taxi booking system...................................................27
Analysis..................................................................................................................................................28
Design....................................................................................................................................................29
Development.........................................................................................................................................29
Testing...................................................................................................................................................29
Deployment...........................................................................................................................................30
Maintenance.........................................................................................................................................30
Why I choose the waterfall model.........................................................................................................30
Task 02.......................................................................................................................................................31

16
 Data dictionary......................................................................................................................................32
Task 03.......................................................................................................................................................38
Context level diagram............................................................................................................................38
0th Level diagram....................................................................................................................................39
Decision tree..........................................................................................................................................40
Decision table........................................................................................................................................41
Use case diagram...................................................................................................................................42
Class diagram.........................................................................................................................................43
References.................................................................................................................................................44

Table of figures
Figure 1......................................................................................................................................................20
Figure 2......................................................................................................................................................21
Figure 3......................................................................................................................................................22
Figure 4......................................................................................................................................................23
Figure 5......................................................................................................................................................24
Figure 6......................................................................................................................................................25
Figure 7......................................................................................................................................................26
Figure 8......................................................................................................................................................32
Figure 9......................................................................................................................................................38
Figure 10....................................................................................................................................................39
Figure 11....................................................................................................................................................40
Figure 12....................................................................................................................................................42
Figure 13....................................................................................................................................................43

Table of table
Table 1.......................................................................................................................................................32
Table 2.......................................................................................................................................................33
Table 3.......................................................................................................................................................34
Table 4.......................................................................................................................................................35
Table 5.......................................................................................................................................................36
Table 6.......................................................................................................................................................37
Table 7.......................................................................................................................................................41

17
Acknowledgement
 First, I would like to thank my System Analysis and Designing lecturer Mr. Chathura
Warnasooriya. Because in making this assignment my lecturers gave us some guidance
and it is very support to me. Another thing is previous course activities were very support
to me for do this assignment. So finally, I thank you again and again to Mr. Chathura
Warnasooriya sir.

Introduction
 In this assignment shows how to design a Taxi booking system for MAL-KEY-RENT-A-
CAR. In the Task 01 I explain about SDLC, SDLC models, how to design taxi booking
system in the SDLC model. In the task 02 I explain about the data model of the software
and and it design with ER diagram. In the task 03 I have explained how to design this taxi
booking system use with DFD diagrams, UML diagrams, and decision tree.

18
Task 01
System Development Life Cycle (SDLC)
 SDLC means process of creating a system.
 The good SDLC give the high-quality system and it always satisfying customer
requirement.
 SDLC can apply for technical or non-technical systems. But its mostly use in IT
technology.
 A good SDLC work smoothly with given resources.
 There are 7 stages in SDLC.

7 Stages in System Development Life Cycle

1. Planning
2. Analysis
3. Designing
4. Development
5. Testing
6. Deployment
7. Maintenance

planning
 Identifying and define the project.
 Doing feasibility study and get the feasibility report.
 Get the approval for the project
 Decide budget, resources, personals, and technical support for do the project
 Start the project

Analysis
 Identify and define prototypes for new system
 Identify functional and nonfunctional requirements
 Determine the needs of end users
 Making the Software Requirement Specification (SRS) document, for determine required
software hardware and network requirements of the new project.

19
Designing
 Designing stage is very important to developing stage.
 Developers shows the details for overall application with the specific aspect.
 The specific aspects are
1. User interface
2. System interface
3. Network requirement
4. Databases
 Transform the SRS document into logical structure. There after it can be implemented in
a programming language.
 Create operation, training, maintenance, plans. So, developers can know what they need
to do in all stages.

Development
 In this stage developers write codes and build the application according to earlier design
documents and specifications.
 Static application security testing (SAST) starts in this stage.
 Developers are use any programming language define by the organization and they also
utilize different tools like compilers, debuggers, and interrupts. C++, PHP, and some
other languages using for this

Testing
 In this stage developers make sure there are no issues in the software building.
 There after developers check the software and note the issues. There after they will report
and fix it.

Deployment
 In this stage the project will give for install or use to end user.

Maintenance
 Now the product was with the end user. But the SDLC is not over because if end user
reports any issue in software, developers’ responsibility is solving that issue.
(Architects, 2021)

20
SDLC methodologies
 Lot of SDLC methodologies using in the present world. This SDLC methodologies are
very important to success projects. I have 6 common SDLC methodologies

Water fall model

 This is the oldest and simplest SDLC model.
 Finish one stage, then move to the next stage. If we complete one stage, then only we can
move to next stage. Because each stage depends on previous stage information, and it has
own project plan.
 This model is very easy to manage.
 But this model is not suitable for long term projects.

Figure 1

21
Agile model
 This model delivers a working product quickly and it is a realistic development approach.
 This model produces ongoing releases. Every release smaller than previous release.
 This model heavily depends on customer interaction. If customers requirement is not
clear the project will be going wrong way.

Figure 2

22
V- shaped model
 This model grew up from water fall model. This model also called by verification and
validation model.
 If start a new stage, previous stage must want to finish like water fall model.
 If there are no unknown requirements, this model is useful. So difficult to go back and fix
the changes in this model.

Figure 3

23
Iterative model
 This model is a repetition model.
 first, in this model implement a set of software requirements.
 This model gives working version earlier in the process.
 The cost is very low for doing changes.

Figure 4

24
Spiral model
 This is the one of flexible model.
 This model allows for building highly customized products. And users’ feedbacks can
add in any time (from the beginning of the project).

Figure 5

25
Big bang model
 This model does not follow specific process, and it get a little time for planning.
 Lot of resources going to the development and the client has no idea about the
requirement.
 This model is not recommended for complex projects.

Figure 6

(Roberthalf.com.au, 2021)

26
 Among these models I choose the waterfall model for design a taxi booking system.

 Design a taxi booking system for MAL-KEY-RENT-A-CAR according to waterfall

model.

Figure 7

27
Requirement gathering and planning about the taxi booking system

 First, need to identify what is the customer requirement. So, when design the taxi
booking system need to do the feasibility study and get the feasibility report. There are 4
types of feasibility study

 Technical feasibility
1. In this type we can identify, are the existing technical resources enough for this taxi
booking project.
2. We can give the attention about what is the software language we must develop for this
project.
3. What are the databases using for this project?

 Economic feasibility
1. In this type we can give the attention for hardware and software expenses for this project
and software development cost.
2. Another thing is giving the attention for benefits of this project like profit.

 Operational feasibility
1. In this type we consider about the staff allocation, working load and working hours for do
this project.

 Legal feasibility
1. In this stage we can give the attention for legal requirements for this project like getting
permission from government for start taxi service.

 Calculate the budget and get the decision about workers, technical resources.

 Finally get the approval from the company management for this project.

 So, when we complete all the works in this stage, there after we have to move to the next
stage.

28
Analysis

 In this stage we want to know about the customer requirements. So, we want to know
what type of taxi booking system customer expect.
 Are there some prototypes for the new project? we can define it. By this way customer
can get the idea about the system.
 Identify the functional and nonfunctional requirements

 Functional requirements
1. In this requirement means what are the main features expecting by this system
a) how many times go to connect with the driver
b) What are the types of vehicles select with the system
c) Can customer contact with the driver over the system
d) Navigation system in the system

 Nonfunctional requirements
1. In this requirement means what are the requirements support to functional requirements
a) Login for the taxi booking system
b) Efficiency and reliability of the system
c) Outlook of the system

 In this stage we make the Software Requirement Specification (SRS) document. In this
document we show what are the features in the new project. And we only add these
features for the system. We always guaranteed for these features
 Features according to SRS
a) Automatically contact with the nearest driver
b) If there are no driver in the near area contact with the office. So, they can provide
a driver very soon.
c) Customer can choose 4 categories of vehicles (car, van, lorry, threeweel)
d) Calling system add for the system.
e) Add onboard navigation system.

 when we do all works, we have to move to next stage.

29
Design

 In this stage we design the system. So, we use flow charts, context level diagrams, DFD
diagrams and UML diagrams to design this system.
 In this stage developers show specific aspects and overall application details.
 The specific aspects
a) User interface
b) System interface
c) Databases
d) Navigation areas

 Another thing is in the analysis stage we had to made SRS document, in this stage we
turn it into logical structure.
 In this stage all the allocated developers training to do this project.
 There after we can move to next stage.

Development

 Basically, in this stage developers use a programming language (like C++, PHP, JAVA)
to build a taxi booking system
 In this stage we build this system according to design. We add features in SRS document.
Because we are only responsible with SRS features.
 Developers do static application security testing (SAST) in this stage. By this SAST we
can scan the code before it compiled.
 So, when we end the coding part we have to move to next stage

Testing

 In this stage we can compare customer requirements and software output. If the taxi
booking system works with SRS documents features, there are no problem because all the
features add to the SRS
 If there are some issues in the software developers must fix it.

30
Deployment

 In this stage the taxi booking system give for MAL-KEY-RENT-A-CAR.

 Developers have to give some training about this system for MAL-KEY-RENT-A-CAR
staff members and install software to MAL-KEY-RENT-A-CAR company computers.
 There after they can launch the system.

Maintenance

 If there are any problem or any issue in the software, the software company must go and
fix the problem
 Examples for maintenance purpose
a) In the system down
b) Virus attacking

Why I choose the waterfall model

 Waterfall model is the simple and easy model to create a system. So, by the waterfall
model we can create a taxi booking system easily and quickly.
 In this model before going to next phase, must need to complete previous phase. So, if
there any problem found in any phase, must need to fix the problem then only you have
to move to next phase.
 This model s very suitable for small/single projects. So, this taxi booking system is the
single project that’s why I choose this model.
 In this model the project is completely depends on project team and the customer
intervention is very low. So, developers can do their work easily.
 If you want to do any changes in software during the process of development, you have
to do it with this model.

(Guru99.com, 2021)

31
Task 02

32
 Figure 8

Data dictionary

Entity - customer
Entity description – details of customer
Data type Primary Not null Unique
Colum name Colum description (length) key key

C_ID Customer Identification Integer True True True

C_Name Customer name Varchar False True False

(100)

C_NIC Customer contact Varchar False True False

number (15)

C_Tel Customer location Varchar False True False

(15)

C_Email Customer email Varchar False False False

(50)

Table 1

33
Entity – Trip
Entity description – Trip details
Data type Primary Not null Unique
Colum name Colum description (length) key key

T_ID Trip identification Integer True True True

C_ID Customer identification Integer False True False

V_NO Vehicle number Varchar False True False

(10)

CO_ID Coordinator Integer False False False

identification

Destination Trip destination Varchar False True False

(50)

B_Time Booking time Varchar False True False

(5)

P_Location Pickup location Varchar False True False

(50)

D_ID Driver identification Integer False True False

Table 2

34
Entity – Vehicle
Entity description – Vehicle details
Data type Primary Not null Unique
Colum name Colum description (length) key key

V_NO Vehicle number Varchar True True True

(10)

V_Type Vehicle type Varchar False True False

(10)

L/I License/ Insurance Varchar False True False

(30)

D_ID Driver identification Integer False False False

V_Brand Vehicle brand Varchar False False False

(50)

Table 3

35
Entity – Coordinator
Entity description – Coordinator details
Data type Primary Not null Unique
Colum name Colum description (length) key key

CO_ID Coordinator Integer True True True

identification

CO_Name Coordinator name Varchar False True False

(100)

Table 4

36
Entity – Payment
Entity description – Payment details
Data type Primary Not null Unique
Colum name Colum description (length) key key

P_ID Payment identification Integer True True True

T_ID Trip identification Integer False True False

P_Type Payment type Varchar False True False

(5)

Fee Trip fee Decimal False True False

Table 5

37
Entity – Driver
Entity description – Driver details
Data type Primary Not null Unique
Colum name Colum description (length) key key

D_ID Driver identification Integer True True True

D_Name Driver name Varchar False True False

(100)

D_L Driving license Varchar False True False

(15)

D_NIC Driver NIC Varchar False False False

(15)

Table 6

38
Task 03

Context level diagram

Figure 9

39
0th Level diagram

Figure 10

40
 Decision tree

Find nearest Start your trip

driver

Provide any
Taxi booking system
available driver
in
MAL_KEY_RENT_
A_CAR

Connect to
coordinator

Hold customer
Can’t find a driver
until one
driver release

Deny your
request

Figure 11

41
Decision table

Find nearest driver Y

Can’t find a driver Y Y Y

Connect to coordinator Y Y Y

Deny your request X

Start your trip X

Provide any available driver X

Hold customer until one driver release X

Table 7

Use case diagram

42
Customer Coordinator

Figure 12

Class diagram

43
 Figure 13

References

44
Architects, I., 2021. SDLC: Seven Phases of the System Development Life Cycle. [Online]
Available at: https://www.innovativearchitects.com/KnowledgeCenter/basic-IT-systems/system-
development-life-cycle.aspx
[Accessed 18 08 2021].

Guru99.com, 2021. What is Waterfall Model in SDLC? Advantages and Disadvantages. [Online]
Available at: https://www.guru99.com/what-is-sdlc-or-waterfall-model.html
[Accessed 18 08 2021].

Roberthalf.com.au, 2021. 6 basic SDLC methodologies: Which one is best? | Robert Half. [Online]
Available at: https://www.roberthalf.com.au/blog/employers/6-basic-sdlc-methodologies-which-one-
best
[Accessed 18 08 2021].

45