1

Assignment Cover Sheet

Qualification Module Number and Title

Higher National Diploma in Computing & SEC4203

System Development System Analysis & Designing
Student Name & No. Assessor
Mohammed Faizer Abdul Azeez Mr. Deshan Bulathsinghala
Hand out date Submission Date

02-10-2017 05-11-2017
Assessment type Duration/Length of Weighting of Assessment
Coursework Assessment Type 100%
4 weeks

Learner declaration

I am MOHAMMED FAIZER ABDUL AZEEZ, CL/HNDCOM/80/45, I 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

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 2

FEEDBACK FORM

INTERNATIONAL COLLEGE OF BUSINESS & TECHNOLOGY

Module:
Student:
Assessor:
Assignment:

Strong features of your work:

Areas for improvement:

Marks Awarded:

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 3

Coursework

Learning outcomes covered

1. Understand system designing methodologies, tools and the techniques

2. Evaluate different systems development life cycle models
3. Be able to perform a systems investigation
4. Be able to design a solution using appropriate system design methodologies, tools and
the 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.

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 does ethical and professional issues are mitigated as
much as possible.
Scenario

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 4

Today we are living in an era of technological advancements are taking place at a rapid phase.
People are keener on dealing with information technology enabled devices than just electronic &
electrical devices because of the fact that they are dealing with a world which already reached
Information age. Since the world is at information age, information now become as a very
essential commodity so that it can be sold & bought among the global customers in the world by
delivering the right information product at right time to the right person .

By looking at the global current trend, Sri Lankan Airlines has decided to implement a system
which automates their ticket booking process. The name of the software is “Online Airline
Reservation System”. This software provides options for viewing different flights available with
different timings for a particular date and provides customers with the facility to book a ticket,
modify or cancel a particular reservation but it does not provide the customers with details of
cost of the ticket and it does not allow the customer to modify a particular part of his reservation
and he/she can modify all his details. This system will help the company to sell the flight tickets
online. Unless like in the previous stage people as to walk into travel agency or this company
ticket counter to buy the tickets, and to check the flight timings. This problem is overcome by
introducing this solution.
Before there were manual systems people come to the airport reserve seats, find timing by asking
from the agents. While in propose system, the main purpose is to provide alternatives and
convenient way to passengers to reserve a seat. Assume that you have been assigned as a system
Analyst by the ICTA to prepare a fully descriptive documentation comprised of city Online
Airline Reservation System analysis & designing information. In order to begin with user
requirement gathering & system environment analysis you are free to choose any airline travel
agency to conduct interviews & site observations. In prior commencing with system
investigation activities proper approval should be given to you by authorized officials of the
ticketing agency that you are visiting. In order to get the approval you can forward ICBT
Campus official request letter to them.

Tasks

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 5

1. Conduct an organizational analysis and report the findings of the organization/ institution
to what the information system will be implemented. Further justify suitability of the
information system for the same according to the present situation. (20 Marks)
2. Identify the advantage of using a standard software development lifecycle a model for
developing the software solution what is proposed for the organization/ institution.
(20 Marks)
3. 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 is the best technique is to carry out data model designing of the
system. (20 Marks)
4. Design the proposed system by using proper Data Flow Diagrams (DFDs) which clearly
express all the external entities which associated with the system and express how the
data are coming to the system and which kind of information will come out as outputs.
(20 Marks)
5. Design the proposed system by using relevant UML Diagrams which express how actors
are interacting with the functionalities of the system and also which represent the static
part of the system ( 20 Marks)

General Guidelines for Students

1. With knowledge gain from the case study/Real world Scenario, analyse the facts
carefully and try to understand the association between each entity in the environment.
Also identify the data that is, needed to be stored for each entity and its relationships.
Any applicable assumptions made, should be clearly mention with proper justification.
2. Final report should be in professional manner and with proper formatting.
3. The student needs to give priority in designing the software product of the information
system.
4. Organizational visits & information gathering can be done in both individual and group
basis which not exceeding 4 members per group.
5. Before organizational / Work site visits students are expected to obtain ICBT official
letter requesting the relevant company for conducting information gathering work within
their premises.
6. Please note that students are expected to maintain backup copies of work in different
media. Due to any hardware, software malfunctions or virus attacks, assignment deadline
will not be lifted.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 6

Submission Guidelines

Report Structure:

 Executive Summery
 Table of contents ,Table of Figures, Table of Tables
 Introduction of the Organization & its operational environment
 Explanation of current System & Drawbacks
 New System / Modified System Explanation
 New System Design (Diagrams, Algorithms, Decision Trees, Decision Tables, System
development Life cycle etc.)
 Conclusion
 Future Recommendation
 Gantt chart & its Description
 Referencing
 Appendix (Appendix A, Appendix B, etc.) for Group meetings, Samples of Questionnaire

Report Format:

 Submission format Report

 Paper Size: A4
 Words: 3000 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
 Referencing should be done strictly using Harvard system

Assessment Criteria

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 7

Task (1) contains 20 marks.

Marks Marks obtained

Criteria by the student
Out of 20 for the answer
provided
Fail

 Provide clear idea about the organization to

which the information system is proposed based 0-8
on vision, mission, objectives, and goals of the
organization.

Pass
 Provide clear idea about the organization to
which the information system is proposed based
on vision, mission, objectives, and goals of the
8-12
organization.
 Management hierarchy of the organization is
included

Good 12-14

 Provide clear idea about the organization to

which the information system is proposed based
on vision, mission, objectives, and goals of the
organization.
 Management hierarchy of the organization is
included

 Description of the selected one of current

systems & its nature of operation
(Computerized/ manual/ Semi Computerized)
have been done that belongs to a specific
department/functional process of the
organization.

 Explanation has been done based on main

objectives expected by the organization from the
selected current system.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 8

Excellent
 Provide clear idea about the organization to
which the information system is proposed based
on vision, mission, objectives, and goals of the
organization.
 Management hierarchy of the organization is
included

 Description of the selected one of current

systems & its nature of operation
(Computerized/ manual/ Semi Computerized)
have been done that belongs to a specific
department/functional process of the
organization.

 Explanation has been done based on main

objectives expected by the organization from the
selected current system. 14-20

 Justification has been done based on the purpose &

relevancy of the tool/s selected for gathering
information.
 Samples of the Questionnaire & Interviews attached.
 The sample questioner contains open type & close type
questions in order to specifically gather information
relevant to current system.
 Standard questionnaire model like Pyramid, Funnel or
Diamond has been used to prepare questionnaire.
 At least economic, technical, operational, legal
feasibility study explained based on proposing system
 Proper justifications have provided for system
adaptation based on feasibility study.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 9

Task (2) contains 20 marks.

Marks Marks obtained

Criteria by the student
Out of 20 for the answer
provided
Fail

 System Development life cycle explained such

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

Pass
 At least Five stages of the System Development
life cycle explained such as Communication,
planning, Designing, Development & Testing, 8-12
Implementation.
 Every stage has been mapped with proposing
system development & designing activities.
Good
 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 12-14
system development & designing activities.
 The description based on
Prescriptive,Incremental,Evolutionary,Agile &
Specialized Process Models

Excellent

 At least Five stages of the System Development

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

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 10

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 14-20
qualities of the proposing system.

Task (3) contains 20 marks.

Marks Marks obtained

Criteria by the student
Out of 20 for the answer
provided
Fail
 Use ER diagrams to design data model of the
0-8
proposing system but some errors exists.

Pass
 Use ER diagrams to design data model of the
proposing system.

 Find entities, Attributes, relationships, Primary

keys, , different cardinalities, , composite keys,
and other entities. 8-12

 Attributes, Entities, Relationships &

Cardinalities properly selected & illustrated.

 Write a data dictionary for the ER diagram.

Good 12-14

 Use EER diagrams to design data model of the

proposing system.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 11

 Find entities, Attributes, relationships, Primary

keys, foreign keys, different cardinalities,
candidate keys, composite keys, and associate
entities.

 Attributes, Entities, Relationships &

Cardinalities properly selected & illustrated.

 Enhanced Entity Relationships have been

thought & illustrated.

 Write a data dictionary for the EER diagram.

Excellent

 Use EER diagrams to design data model of the

proposing system.

 Find entities, Attributes, relationships, Primary

keys, foreign keys, different cardinalities,
candidate keys, composite keys, and associate
entities.

 Attributes, Entities, Relationships &

Cardinalities properly selected & illustrated.
14-20
 Enhanced Entity Relationships have been
thought & illustrated.

 Write a data dictionary for the EER diagram.

 Enteritis’s Attributes described based on Data

Tyep,Size,Format,& Nature
([Link],Non Key)
 Has been used standard format for the Data
dictionary.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 12

Task (4) contains 20 marks.

Marks Marks obtained

Criteria by the student
Out of 20 for the answer
provided
Fail

 Draw context level Data Flow Diagram to

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

Pass
 Draw context level Data Flow Diagram to
illustrate functional model of the proposing
system.
 External Entitles, Main Information System &
Information Initial flow between External 8-12
Entities & Main Information System have been
identified & illustrated.

 Proper Process & data flow labeling used

Good 12-14
 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

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 13

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

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 14-20
Tables properly used for DFD level 0 processes.
 Process specifications have been included using
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.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 14

Task (5) contains 20 marks.

Marks Marks obtained
Criteria by the student
Out of 20 for the answer
provided
Fail
 Draw use-case diagram which illustrate the
interaction between all the actors and the system 0-8
functionalities with some errors.

Pass
 Conclusion should be given based on the
proposing information system’s functionalities 8-12
& those benefits for the organization’s goals to
achieve.
Good
 Draw the class diagram which illustrates object
orientation of the proposed system.
 Conclusion should be given based on the
proposing information system’s functionalities
& those benefits for the organization’s goals to 12-14
achieve.

 Clearly explain how does business system

options supported by technical system options

Excellent
 Draw the class diagram which illustrates object
orientation of the proposed system.
 Conclusion should be given based on the
proposing information system’s functionalities
& those benefits for the organization’s goals to
achieve.
 Explanation has been given by incorporating
BSO (Business System Options) and TSO 14-20
(Technical System Options).
 Clearly explain how business system options
supported by technical system options does.

 Future recommendations should be given based

on the possible enhancements of the proposing
information system.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 15

Contents
Introduction................................................................................................................................18
Vision.....................................................................................................................................18
Mission..................................................................................................................................18
Objective................................................................................................................................18
Goals......................................................................................................................................18
Current System..........................................................................................................................19
Draw back of the system............................................................................................................19
Feasibility Study Report............................................................................................................19
Organizational Structure............................................................................................................20
Task 2.........................................................................................................................................21
System Development Life Cycle (SDLC).................................................................................21
Introduction............................................................................................................................21
Planning and Requirements Analysis....................................................................................21
Designing...............................................................................................................................21
Implementation......................................................................................................................22
Maintenance...........................................................................................................................22
Life Cycle of System Analysis and Design,..........................................................................22
System Development Life Cycle Models..................................................................................23
Waterfall model.....................................................................................................................23
Iterative Model.......................................................................................................................25
Spiral Model..........................................................................................................................27
V shape model.......................................................................................................................29
Task 3.............................................................................................................................................31
Entity Diagram...............................................................................................................................31
Relational Schema.....................................................................................................................32
Assumptions..............................................................................................................................32
Data Dictionary..........................................................................................................................33
Task 4.............................................................................................................................................35
Context Level Diagram..............................................................................................................35
DFD Level – 0 Diagram............................................................................................................36
DFD Lower Level Diagram.......................................................................................................37
DFD Level – 0 Dictionary.........................................................................................................38

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 16

Task 5.............................................................................................................................................40
System Use Case Diagram.........................................................................................................40
Class Diagram............................................................................................................................41
Sequence Diagram.....................................................................................................................42
Conclusion.....................................................................................................................................43
Gantt chart.....................................................................................................................................44
References......................................................................................................................................45

Figure 1- Waterfall model ............................................................................................................23

Figure 2- Iterative Model...............................................................................................................25
Figure 3- Spiral Model...................................................................................................................27
Figure 4- v shape Model................................................................................................................29

Waterfall Model - [Link]

Iterative model - [Link]
Spiral Model - [Link]
V shape - [Link]

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 17

Task - 1

Introduction

Avows Airline was established in 1990. The airline has more than 55,000 employees as
of July 2017 and operates more than 4,000 departures a day during peak travel season This
airline reservation system is broad set of merchandise to rearrange for a system that supports
with spread of airline management tasks and client wants commencing the time of primary
reservation through action of the flight. A best travel is traveling by air.

Vision
To become the most competitive and leading aviation group in the world by providing
safe, market driven and customer focused passenger and cargo transport, aviation training, flight
catering, MRO and ground services. And to be the most preferred airline in the world. A
dynamic team provides the best customer services, Distribute and sales costs average, Customer
satisfaction and Profitable airlines

Mission

We are in the air transportation business. We provide our customers with a reliable and pleasant
travel experience. We provide our business partners with a variety of innovative, professional
and mutually profitable services. We are a competent, proactive and diligent team. Our
contribution is recognized and rewarded.

Objective

Where a customer can request all flight information as per their journey dates. They can get
details regarding time, cost, etc. at the same time and same place.

Goals

Provide the best customers service and Employee’s safety process and to become the best
airlines in the world.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 18

Current System

Avows Airline system created on-line reservation system terribly nicely. This on-line
reservation system is incredibly enticing and user friendly. This organization is presently
exploitation enticing Image Gallery to draw in the client. enticing “Book Now” Button
Eye catching (button) Use words that tell them what to try to next (User friendly).
Master Card Storage choices is permitting customers to store their master card data in
safe and secure manner. Currency and Language Settings. During this organization
desires world customers, therefore booking methodology is displayed in alternative
language conjointly. And that they maintaining on-line Support and Phone Support.

Draw back of the system

 Avows Airlines have a problem, when the customer inquiries to a phone representative
who gives you an answer that doesn’t seem quite right and give them another ring.
 Lack of security
 Large ongoing staff training cost

Feasibility Study Report

Feasibility Studying can be considered as the basic investigations which help the management to
decide whether they are in a situation to develop the given scenario.

There are 4 different feasibility,

 Economic Feasibility
 Technical Feasibility
 Operational Feasibility
 Behavioral feasibility

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 19

Organizational Structure

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 20

Task 2

System Development Life Cycle (SDLC)

Introduction
System development life cycle is a conceptual model which includes policies and procedures for
developing or altering systems throughout their life cycles.
SDLC is used by analysts to develop an information system. SDLC includes the following
activities.
 Planning and Requirements Analysis
 Designing
 Implementation
 Testing
 Deployment
 Maintenance

Planning and Requirements Analysis

 Requirement analysis is that the most significant and basic stage in SDLC. It is
performed by the senior members of the team with inputs from the client, the sales force,
market surveys and domain specialists within the trade. This data is then accustomed set
up the essential project approach and to conduct product practicability study within the
economical, operational and technical areas.
 A software requirements specification (SRS) document, which specifies the software,
hardware, functional, non-functional and network requirements of the system is prepared
at the end of this phase.
Designing

 It means includes the design of application, network, database, user interfaces and system
interfaces
 Transformation of SRS document into logical (conceptual) structure.
 Create a contingency, planning, training, maintenance and operation plan.
 Review the propose design
 Finally prepare a design document which will be use during next of SDLC.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 21

Implementation

 Implementation the design into source code through coding

 Combine all the modules together into training environment that detects errors and
defects.
 A test report which contains errors is prepared through test plan that includes test related
tasks such as test case generation, testing criteria and resource allocation for testing.
 Integrate the information system into its environment and install the new system.

Maintenance

 Include all the activities such as phone support or physical on – site support for users that
is required once the system is installing.
 Implement the changes that software might undergo over a period at time, or implement
any new requirements after the software is deployed at the customer location.
 It also includes handling the residual errors and resolve any issues that may exist in the
system even after the testing phase.
 Maintenance and support may be needed for a longer time for large systems and for a
short time for smaller systems.

Life Cycle of System Analysis and Design,

Requirement Feasibility System

Determination & Analysis Specification
specification Analysis

System
evaluation and System System
maintenance Implementation Design

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 22

System Development Life Cycle Models

Waterfall model

Figure 1- Waterfall model

The waterfall model was the first process model to be introduced. It is also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In waterfall model each
phase must be completed before the next phase can begin and there is no overlapping in the
phases.

 Requirement Analysis – All possible requirements of the system to be developed are

captured in this phase and documented in a requirement specification document.
 System Design – The requirement specifications from first phrase are studied in this
phase and the system design is prepared.
 Implementation – With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase.
 Testing – All the units developed in the implementation phase are integrated into a
system after testing of each unit.
 Deployment – Once the functional and non-functional testing is done. The product is
deployed in the customer environmental or released into the market.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 23

 Maintenance – There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.

Advantages

1. Simple and easy to understand and use.

2. Easy to manage due to the rigidity of the model. Each phase has specific deliverables
and a review process.
3. Phases are processed and completed one at a time.
4. Works well for smaller projects where requirements are very well understood.
5. Easy to arrange tasks.

Disadvantages

1. No working software is produced until late during the life cycle.

2. High amounts of risk and uncertainty.
3. Not a good model for complex and object-oriented projects.
4. Poor model for long and ongoing projects.
5. It is difficult to measure progress within stages.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 24

Iterative Model

Figure 2- Iterative Model

In the iterative model process starts with a simple implementation of a small setup. Software
requirements and iterative an answer evolving versions until the complete the system is be
implemented.

Iterative model (Application)

Like other SDLC models iterative and incremental development has some specific application in
the software industry this model in most often used in the following scenarios.
 Requirements of the complete system are clearly defined an understood.
 Major requirements must be defined; however some functionalities or request
enhancement is may evolve with time.
 A new technology is being used and is being learnt. The development team while
working on the project.
 Resources with needed skill sets not available and are planned to be used on contract
basis for specific iteration.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 25

Advantages

1. Some working functionality can be developed quickly and early in the life cycle.
2. Results are obtained early and periodically.
3. Parallel development can be planned.
4. Progress can be measured.
5. Less costly to change the scope/requirements.
6. Testing and debugging during smaller iteration is easy.
7. Risks are identified and resolved during iteration; and each iteration is an easily managed
milestone.

Disadvantages

1. Some working functionality can be developed quickly and early in the life cycle.
2. Results are obtained early and periodically.
3. Parallel development can be planned.
4. Progress can be measured.
5. Less costly to change the scope/requirements.
6. Testing and debugging during smaller iteration is easy.
7. Risks are identified and resolved during iteration; and each iteration is an easily managed
milestone.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 26

Spiral Model

Figure 3- Spiral Model

The spiral model combines the idea of iterative development with the systematic, controlled
aspects of the waterfall model. This spiral model is a combination of iterative development
process model and sequential linear development model. The waterfall model with a very high
emphasis on risk analysis. It allows incremental releases of the product or incremental through
each iteration around the spiral.

 Identification – this phase starts with gathering the business requirements in the baseline
spiral. In the subsequent spirals as the product matures, identification of system
requirements, subsystem requirements and unit requirements are all done in this phase
 Design – this design phase starts with the conceptual design in the baseline spiral and
involves architectural design, logical design of modules, physical product design and the
final design in the subsequent spirals.
 Construct or Build – The construct phase refers to production of the actual software
product at every spiral. In the baseline spiral, when the product is just thought of and the
design is being developed in this phase to get customer feedback.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 27

 Evaluation and Risk analysis – Risk analysis includes identifying, estimating and
monitoring the technical feasibility and management risks, such as schedule slippage and
cost overrun. After testing the build, at the end of first iteration, the customer evaluates
the software and provides feedback.

Advantages

1. Changing requirements can be accommodated.

2. Allows extensive use of prototypes.
3. Requirements can be captured more accurately.
4. Users see the systems early.
5. Development can be divided into smaller parts and the risky parts can be developed
earlier which helps in better risk management.

Disadvantages

1. Management is more complex.

2. End of the project may not be known early.
3. Not suitable for small or low risk projects and could be expensive for small projects.
4. Process is complex.
5. Spiral may go on indefinitely.
6. Large number of intermediate stages requires excessive documentation.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 28

V shape model

Figure 4- v shape Model

Waterfall and v shape model are look similar. But v shape model first stage will be the planning.
This type of model will be use when requirements are clearly identifying and also when tools and
technologies are very well identify.

Advantages

1. This is a highly-disciplined model and Phases are completed one at a time.

2. Works well for smaller projects where requirements are very well understood.
3. Simple and easy to understand and use.
4. Easy to manage due to the rigidity of the model. Each phase has specific deliverables and
a review process.
5. The disadvantages of the V-Model method are as follows −
6. High risk and uncertainty.
7. Not a good model for complex and object-oriented projects.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 29

Disadvantages

1. High risk and uncertainty.

2. Not a good model for complex and object-oriented projects.
3. Poor model for long and ongoing projects.
4. Not suitable for the projects where requirements are at a moderate to high risk of
changing.
5. Once an application is in the testing stage, it is difficult to go back and change a
functionality.
6. No working software is produced until late during the life cycle.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 30

Task 3

Entity Diagram

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 31

Relational Schema

 Airlines (Name, Location, [Link], Phone NO.)

 Travels (Name, [Link], Phone NO., Address)
 Passenger (Name, Passenger ID, Age, Address)
 Employee (Name, Employee ID, Phone NO., Address)
 Ticket (Seat NO., Class Type, Travel Date, Travel Time)

Assumptions

 I assumed the Airlines, Travels, Passenger, Employee and the Tickets are the entities.

 According to the diagram I assumed between Airlines and the Travels are many to many
relationship because a travels can connect with many airlines and also an airlines can
connect with many Travels.

 And between Employee and the Tickets I assumed many to many relationship because an
employee can make many tickets and also many tickets can make by an employee.

 I assumed between the Travels and the Employee as One to many relationship because
one employee can work for a one travels but travels can have many employees.

 And between Employee and the Airlines I assumed as one to many relationship because
an employee can works for one airline but an airlines can have more employees in their
company.

 I assumed between Passenger and the Ticket as one to one relationship because one ticket
can book by a one passenger at the same time one ticket can have only one Owner.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 32

Data Dictionary

Airlines
NO DATA NAME DESCRIPITION [Link]
CHARACTERS
1 Name Name of the Airlines 25
2 Location Address of the 40
Airlines
3 Reg. NO. Airlines Registration 15
Number
4 Phone NO. Contact Number of 10
Airlines

Travels
NO DATA NAME DESCRIPITION [Link]
CHARACTERS
1 Name Name of the Travels 20
2 Reg. ID Travels Registration 15
Number
3 Phone NO. Contact Number of 10
the Travels
4 Address Address of the 40
Travels

Passenger
NO DATA NAME DESCRIPITION [Link]
CHARACTERS
1 Name Full name of the 20
Passenger
2 Passenger ID ID of the Passenger 15
3 Age Date of birth and 25
current age of the
Passenger
4 Address Address of the 40
Passenger

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 33

Employee
NO DATA NAME DESCRIPITION [Link]
CHARACTERS
1 Name Full Name of the 20
Employee
2 Employee ID ID of the Employee 15
3 Phone NO. Contact number of 10
the Employee
4 Address Address of the 40
Employee

Ticket
NO DATA NAME DESCRIPITION [Link]
CHARACTERS
1 Seat NO. Seat number 05
2 Class Type Type of the class 10
3 Travel Time Travelling time 15
“am/pm”
4 Travel Date Travelling Date 25
“Year, Month and
Day.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 34

Task 4

Context Level Diagram

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 35

DFD Level – 0 Diagram

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 36

DFD Lower Level Diagram

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 37

DFD Level – 0 Dictionary

Process Name Check Availability

Process Number 1.0

Purpose Provide a feedback to the

user based upon Ticket
Information Available
Package
Input Data Flows Travel date, Travel Time

Output Data Flows Providing the list of

packages and Price
Process Will check whether flight
rate or not related to user
input
Notes -

Process Name Produce Reservation

summary
Process Number 2.0

Purpose Provide a feedback about

flight package choices In
order to generate
reservation summary
Input Data Flows Flight choice

Output Data Flows Reservation summary

Process Calculate the payment

details based upon user
flight choose and
reservation requirement
Notes

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 38

Process Name Process payment

Process Number 3.0

Purpose Provide the financial part

of system
Input Data Flows Reserved package
information
Output Data Flows Invoice cheque declined
notification
Process Do the all financial parts
based upon user
requirement
Notes

Process Name Produce Reservation

summary
Process Number 4.0

Purpose Confirm the reservation

of chosen flight package
Input Data Flows Customer booking

Output Data Flows Reservation notification

Process Confirm reservation and

the provide details to the
management based upon
customer reservation
Notes

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 39

Task 5

System Use Case Diagram

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 40

Class Diagram

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 41

Sequence Diagram

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 42

Conclusion

To conclude the objectives of the system I have designed ER diagram, context level diagram,
and use case diagram, class and sequence diagram. I have explained about the Airlines and their
vision, missions and goals. And I have fully explained about SDLC.

For this Assignment, I have gathered information from Internet and Books. In addition, I convert
all that information into my words to put in this. I mentioned the References, bibliography and
picture figures for the requirements what I gathered. I have put my full effort to finish this
assignment, and it was a good experience to me. I am very Thankful to ICBT College and My
lecture Mr. Deshan Bulathsinghala for giving me a good knowledge.

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 43

Gantt chart

References

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45
 44

Airline, s., 2017. slide share. [Online]

Available at: [Link]
[Accessed 10 10 2017].

[Link]

Task 2 – ICBT notes 2017

Mohammed Faizer Abdul Azeez

CL/HNDCOM/80/45