LMU ID: 22015190

London Metropolitan University, Faculty of Computing

CS6003ES Advanced Software Engineering

Individual Coursework, Semester 2 (part 2), 2022/23
Module Leader: Dr. Lochandaka Ranathunga

Part 2 weighting: 30% in total

STUDENT NAME Abdul Nazeer Zaid

ESOFT ID E101851
LMU ID 22015190

Submission deadline: 5th November 2022

The electronic version of your individual report must indicate ID number, Surname and First name in
the first page or at the beginning of program file (as comments).

If you think there is a good reason for late submission, such as illness, and you have supporting documentary
evidence then you should follow the “mitigating circumstance” procedures outlined in the Red Book, otherwise
assignments will NOT be accepted by the module Organizer after the due date .

DECLARATION
PLAGIARISM

You are reminded that there exist regulations concerning plagiarism. Extracts from these regulations
are printed overleaf. Please sign below to say that you have read and understand these extracts:

Signature : Zaid Abdul Nazeer

This header sheet should be attached to the assignment specification and to the work you submit. No
work will be accepted without it.
 LMU ID: 22015190

Extracts from University: Regulations on Cheating, Plagiarism and Collusion

Section 2.3: “The following broad types of offence can be identified and are provided as indicative
examples …..
(i) Cheating: including taking unauthorized material into an examination; consulting unauthorized
material outside the examination hall during the examination; obtaining an unseen examination
paper in advance of the examination; copying from another examinee; using an unauthorized
calculator during the examination or storing unauthorized material in the memory of a
programmable calculator which is taken into the examination; copying coursework.
(ii) Falsifying data in experimental results.
(iii) Personation, where a substitute takes an examination or test on behalf of the candidate. Both
candidate and substitute may be guilty of an offence under these Regulations.
(iv) Bribery or attempted bribery of a person thought to have some influence on the candidate’s
assessment.
(v) Collusion to present joint work as the work solely of one individual.
(vi) Plagiarism, where the work or ideas of another are presented as the candidate’s own. (vii) Other
conduct calculated to secure an advantage on assessment. (viii) Assisting in any of the above.

Some notes on what this means for students:

1. Copying another student's work is an offence, whether from a copy on paper or from a computer
file, and in whatever form the intellectual property being copied takes, including text and
computer programs.

2. Taking extracts from published sources without attribution is an offence. To quote ideas,
sometimes using extracts, is generally to be encouraged. Quoting ideas is achieved by stating an
author's argument and attributing it, perhaps by quoting, immediately in the text, his or her name
and year of publication, e.g. " e = mc2 (Einstein 1905)". A references section at the end of your
work should then list all such references in alphabetical order of authors' surnames. (There are
variations on this referencing system, which your tutors may prefer you to use.) If you wish to
quote a paragraph or so from published work then indent the quotation on both left and right
margins, using an italic font where practicable, and introduce the quotation with an attribution.
 LMU ID: 22015190

Hotel reservation SYSTEM

BENG IN SOFTWARE ENGINEERING

CS6004ES – Application Development

STUDENT NAME Abdul Nazeer Zaid

ESOFT ID E101851
LMU ID 22015190
MODULE LECTURER Dr. Lochandaka Ranathunga
MODULE NAME Advanced Software Engineering
MODULE NO CS6003ES

ACKNOWLEDGEMENT
 LMU ID: 22015190

This research was supported by the BEng software engineering. Well, I Might not have
completed the assignment successfully without the support of a few people and some forums.
Especially I would like to convey my sincere thanks to our module lecturer and as well as the
assignment assessor Dr. Lochandaka Ranathunga for supporting not only me, but our whole
batch impartially with the assignment tasks, Providing the necessary guidance, Assistance and
also sharing his immense knowledge with us. Concluding my Description, I would like to thank
our institute management and its workers for providing us the facilities we need, and I would
thank my fellow mates and my family for their support and the guidance that helped me to
complete the assignment successfully.

Thank you!

Table of Contents
DECLARATION..............................................................................................................................................1
1. GENERIC PLAN INFORMATION................................................................................................7
 LMU ID: 22015190

1.1 Date of issue and Status.............................................................................................................7

1.2 Issuing Organization.................................................................................................................7
1.3 Glossary......................................................................................................................................7
2. PROJECT OVERVIEW...................................................................................................................9
2.1 Introduction...............................................................................................................................9
2.1.1 Purpose................................................................................................................................9
2.1.2 Scope...................................................................................................................................9
2.1.3 Objective............................................................................................................................10
2.2 Assumptions and Constraints.................................................................................................10
2.3 Project deliverables.................................................................................................................11
2.4 Schedule and Budget...............................................................................................................11
3. PROJECT ORGANIZATIONAL STRUCTURE.........................................................................13
4. WORK BREAKDOWN STRUCTURE(WBS)..............................................................................16
4.1 Work Breakdown Structure...................................................................................................16
4.2 Rational for Work Breakdown Structure..............................................................................17
4.2.1 Phase-1 project planning....................................................................................................17
4.2.2 Phase-2 requirement gathering...........................................................................................18
4.2.3 Phase-3 designing..............................................................................................................18
4.2.4 Phase-4 implementation.....................................................................................................19
4.2.5 Phase-5 testing...................................................................................................................19
4.2.6 Phase-6 product delivery....................................................................................................19
4.3 Gantt chart...............................................................................................................................20
4.4 Milestones and Rationale for the set of Milestones................................................................21
4.4.1. Gathering of requirements.................................................................................................21
4.4.2. Validate expectation of requirements.................................................................................21
4.4.3. Designing...........................................................................................................................22
4.4.4. Implementation..................................................................................................................22
4.4.5. Quality assurance testing...................................................................................................22
4.4.6. Deployment.......................................................................................................................22
4.4.7. User Manual.......................................................................................................................22
4.5 Activity on Arrow Diagram....................................................................................................23
References.................................................................................................................................................24
 LMU ID: 22015190

TABLE OF TABLES

Table 1 Schedule.................................................................................................................................11
Table 2 Budget....................................................................................................................................12
Table 3 Project manager.....................................................................................................................13
Table 4 Requirement Analyst..............................................................................................................14
Table 5 Software and UI Engineer.......................................................................................................14
Table 6 Software Engineer 2...............................................................................................................15
Table 7 Software and UI Engineer 3....................................................................................................15
Table 8 QA Engineer............................................................................................................................16
Table 9 for Activity on Arrow Diagram................................................................................................23

TABLE OF FIGURES

Figure 1 Work Breakdown Structure...................................................................................................17

Figure 2 Gantt chart............................................................................................................................20
Figure 3 Activity on Arrow Diagram....................................................................................................23

1. GENERIC PLAN INFORMATION

 LMU ID: 22015190

1.1 Date of issue and Status

Date: 28th of July 2022
Status: Ongoing

1.2 Issuing Organization

Organization: software comany

1.3 Glossary

 Document Conventions
Entire document is Justified.
Line spacing for text 1.5
The references are given based on Harvard style.

 Convention for Main title

Font name: Time New Roman
Font style: Bold
Font Size: 16

 Convention for Subtitle

Font name: Time New Roman
Font style: Bold
Font size: 14

 Convention for Body

Font name: Time New Roman
Font Size: 12

ACRONYMS:

IEEE - Institute of Electrical and Electronics Engineers

 LMU ID: 22015190

PM – Project Manager
SE – Software Engineer
SSD – Senior Software Developer
GD – Graphic Designer
T - Tester
QAE – Quality Assurance Engineer
SD – Software Developer
AON – Activity on Node
SRS – Software Requirement Specification
WBS – Work Breakdown Structure
SDP – Software Development Plan
LS – Late Start
LF – late finish
ES – Early Start
EF – Early Finish

2. PROJECT OVERVIEW
 LMU ID: 22015190

2.1 Introduction

2.1.1 Purpose
The Internet innovation has been reached a critical accomplishment and we nearly
could get any data we really want by means of riding on the Web program at 7
whenever or anyplace where PC and Internet are accessible. The Online Hotel
Booking System offers a mimicked climate to allow clients to perform what they
could do in reality through its straightforward and easy to understand interface.
Online Hotel Booking System meets most of capabilities and effectiveness of a
genuine Web-based application of the genuine case and offers the expansion of future
advancement for additional finished capacities.

The hotel new view has moved to an online system from their old manual system.
Here customers can book their rooms and residential suites via the website. This
developed system is a very user-friendly system for the customers. When customers
reserve the rooms, they will receive an email in their mail and they can change or
cancel the rooms with the reference number attached to their mail. Same time with
these system customers can pay the payment via the online payment system as well
when booking rooms.

2.1.2 Scope
 Clients can enlist at hotel and afterward they can see or alter the individual
profile.
 Clients can book a room on a particular date.
 Clients can see all their booking history at hotel.
 Clients can change the booking whenever 3 days before the appearance date.
 Clients can drop the booking whenever 3 days before the appearance date.
 Clients can really look at the room accessibility at before they book a room.
 Directors can change the amount and cost on each of the four kinds of rooms.
 Directors can change a particular booking subtlety.
 Executives can drop a particular booking.

2.1.3 Objective
This task is a Web-based application that gives an easy to use and straightforward
point of interaction to effortlessly let clients book lodgings and perform booking
 LMU ID: 22015190

exercises through Web. The records are imparted to not just Web clients yet in
addition with overseers to the site. The task utilizes a standard Web program with
HTML (Hyper Text Markup Language) as the essential connection point language.
Clients can perform booking exercises through the Web program. The organizations
likewise can see all clients' documents and keep up with the Web webpage on it. The
Web pages are written in PHP (Hypertext Pre-processor) and put away in Apache
server.
Every one of the information is put away in a MySQL data set and got to by PHP.

2.2 Assumptions and Constraints

Assumptions
If the central Database System changes to Distributed Database System, then system
requirements affect and it should be changed accordingly
 User has computer with Windows 7 or Above OS and Internet/Intranet
Connection.
 Database transactions are assumed to be secure and reliable.
 This application depends on the server. So it is assumed that server is working
correctly.
 The user knows the basic functionalities of using a computer.

Constraints
 The project has to be finished within 3 months.
 The system should be fully operational at any given time. The system will
generate an appropriate error message if there are any problems occurred.
 The system will generate error messages when the user attempts to enter invalid
data.
 The system will reject invalid user input without crashing.
 The system will display appropriate messages when the database is down.
 The system will be recoverable within a day if it is down.

2.3 Project deliverables

This project was started on July 28, 2022 and estimated completion date will be 3 months
from the issued date. According to the scheduled Gantt chart, documents and resources
are to be provided to the customers within the scheduled date.
 LMU ID: 22015190

The deliverables are,

 Web based hotel management system and User Manual
 Technical Documentation

2.4 Schedule and Budget

Project schedule is prepared by the project manager and assigned team members for each
and every task mentioned in the below table. The schedule has been created according to
complete the project within the 3 months of period (12 weeks).

TASK START DATE END DATE

1. Project planning 29th AUG 2022 1ST SEP 2022

2. Requirement gathering 1ST SEP 2022 7TH SEP 2022

3. Design 7TH SEP 2022 26TH SEP 2022

4. Implementation 26TH SEP 2022 28TH OCT 2022

5. Testing 28TH OCT 2022 11TH NOV 2022

6. Product delivery 11TH NOV 2022 18TH NOV 2022

Table 1 Schedule

The salary of the project manager is 25$ per hour and two members of the team with part
time earn 35$ per hour and rest of the members who work full time earn 50$ per hour.
Hence, total budget for the project is 100,000$.
 LMU ID: 22015190

Member Earning Per hour Hours Salary

Project Manager 25$ 480h 12000$

Requirement Analyst 35$ 180h 6300$

(Part time worker)

Software Engineer 50$ 480h 22500$

(UI Designer)

Software Engineer 50$ 480h 22500$

Software Engineer 50$ 480h 22500$

QA Engineer(testing) 35$ 180h 6300$

(Part time worker)

Total salary 92100$

Table 2 Budget

3. PROJECT ORGANIZATIONAL STRUCTURE

The project structure provides a formal environment for project managers to use to
persuade team members to do their best in carrying out their duties and assignments. This
 LMU ID: 22015190

structure should be designed to aid in the development of team member collaboration

while minimizing overlaps and duplication of efforts.
One of the primary benefits of this structure is that it makes it simple for the team to stay
up to date on daily tasks and communicate because they are part of the same
organizational team and report to the same administrator or manager. Another significant
advantage is that the group or team has a strong sense of identity because they are all
focused on achieving the same goal and the successful completion of the project.
(Giles, 2015)

Position Project Manager

Member Name Zaid
Salary per hour 25$
Working hours 480h
Roles and Responsibilities  The project manager is the person in charge of
completing the project. The individual leads and
manages the project team, with authority and
responsibility from the project board to oversee
the day-to-day operations of the project.
Table 3 Project manager

Position Requirement Analyst

Member Name Ashfaq
Salary per hour 35$
Working hours 480h
Roles and Responsibilities  A requirements analyst determines a project's
requirements by acting as an intermediary
between managers, stakeholders, and software
development teams. Job duties include analyzing
project requirements, reconciling competing
interests, and determining how to translate the
designer's vision into a plan that developers can
implement.
Table 4 Requirement Analyst

Position UI designer
Member Name Amri
 LMU ID: 22015190

Salary per hour 50$

Working hours 480h
Roles and Responsibilities  Consider design briefs to better understand
requirements.
 Creating style guides, design systems, design
patterns, and appealing user interfaces from
requirements.
 Creating a screen visualization within a prototype
framework.
 Identifying design issues and creating elegant
solutions
 Presenting ideas, concepts, and design solutions
to a variety of stakeholders and incorporating
feedback into your designs
 Creating and maintaining style guidelines
documentation.

Table 5 Software and UI Engineer

Position Software Engineer

Member Name Sathya
Salary per hour 50$
Working hours 480h
Roles and Responsibilities  Complete the entire software development life
cycle (SDLC)
 To identify requirements and solutions, create
flowcharts, layouts, and documentation.
 Create testable code that is well-designed.
 Create specifications and assess operational
feasibility.
 Combine software components to create a fully
functional software system.
 Create software verification plans and procedures
for quality assurance.
 Maintain and document software functionality
 Existing systems should be troubleshooted,
debugged, and upgraded.
 Programs should be deployed and user feedback
should be evaluated.

 Observe project plans and industry standards

 LMU ID: 22015190

Ensure that your software is up to date with the

most recent features.

Table 6 Software Engineer 2

Position Software Engineer

Member Name Safwan
Salary per hour 50$
Working hours 480h
Roles and Responsibilities  Complete the entire software development life
cycle (SDLC)
 To identify requirements and solutions, create
flowcharts, layouts, and documentation.
 Create testable code that is well-designed.
 Create specifications and assess operational
feasibility.
 Combine software components to create a fully
functional software system.
 Create software verification plans and procedures
for quality assurance.
 Maintain and document software functionality
 Existing systems should be troubleshooted,
debugged, and upgraded.
 Programs should be deployed and user feedback
should be evaluated.
 Observe project plans and industry standards
 Ensure that your software is up to date with the
most recent features.

Table 7 Software and UI Engineer 3

Position QA Engineer(testing)
Member Name Aznar
Salary per hour 35$
 LMU ID: 22015190

Working hours 180h

Roles and Responsibilities  Executes test cases under varying conditions
 Test results are documented and evaluated.
 Identifies, logs, and reports program bugs and
flaws.
 Tracks defects and assists in error resolution.
 Examines test procedures and creates test scripts
 Collaboration with engineers to drive QA efforts

Table 8 QA Engineer

4. WORK BREAKDOWN STRUCTURE(WBS)

4.1 Work Breakdown Structure

WBS (work breakdown structure) is a technique for making large projects more
manageable. It entails breaking down a project into tasks and subtasks in order to avoid
future confusion. work breakdown structure is commonly used to simplify the task
execution process during the project's scope.
For several reasons, a work breakdown structure is an effective project management tool.
 It divides the project into smaller components, making it less overwhelming and
more manageable.
 Individuals and teams can concentrate on their specific tasks and deliverables
while also seeing how their contribution fits into the overall project.
 Tool for tracking project progress, identifying milestones, and allocating budget
resources
(christine-organ, 2022)
(wbs, 2022)
 LMU ID: 22015190

Figure 1 Work Breakdown Structure

4.2 Rational for Work Breakdown Structure

This work breakdown structure is intended to build and introduce a web-based Hotel
Reservation system for a single hotel chain. This application will aid in the management
of information relating to rooms, reservations, customers, reservations, generating
reports, and billing. The project deadline for completing this web application is in 12
weeks.

4.2.1 Phase-1 project planning

Project Management Plan - Project planning is the initial phase of any project and includes
problem specifying, identifying key individuals, project scheduling, specifying scope, and
agreement of deliverable process. This project planning phase took 3 days in total.
Scheduling and Assigning member - If the task is defined in order to solve the constraints
and successfully complete the project, everyone in the team must be aware of their roles and
responsibilities, while the project manager must ensure that the assigned tasks are assigned to
the most appropriate individuals. Zaid will be the project manager for this project, and
Ashfaq will be the Requirement Engineer who will handle all of the client's requirements.
Amri, Sathya, and Safwan will be the developers, and they will work full-time. Amri was
assigned as UI Designer to design all of the necessary components in the user interface, and
Aznar was assigned as Tester to test and ensure the system's functionality.
 LMU ID: 22015190

Agreement Process - During this phase, the client and project manager should make
decisions about the project's outcome and deliverables. This process took one day, and the
deliverables included the entire system, technical documentation, and user documentation.
Risk Management - the process of identifying, monitoring and managing potential risks in
order to minimize the negative impact they may have on a project.
Budget Management- Budget management is the process of creating and managing the
project budget. Budget management is an accounting management method that assists a
project in forecasting unpaid expenses in order to reduce the risk of going over budget. To
ensure that costs remain consistent with the Budget Management Plan, all costs must be
documented and tracked throughout the project.

4.2.2 Phase-2 requirement gathering

Requirement Gathering- Requirement gathering is a method of collecting all of the
necessary requirements to effectively execute this project, and all of the requirements for this
project are gathered using various methods such as questionnaires, conferences, and
interviews. The specifications were gathered over the course of five days.
Preparing SRS- The Software Requirements Specification (SRS) is a detailed summary of
the intended function and environment for applications in development. The SRS explains in
detail what the hotel reservation system program will do and how it is supposed to work.
This procedure will take five days to complete.

4.2.3 Phase-3 designing

Architectural Design - The design of the system architecture is a collection of protocols,
guidelines, and standards used in the technical context of the computer system, as well as
customer requirements and specifications, that the architecture designer of the system follows
when designing the various components of the system (such as hardware, software, and
networks). The development of system architecture takes three days.
User Interface Design- All of the required interfaces for the proposed project must be
designed under user interface design phase, and the deadline is in eight days.
Database Design- The process by which the proposed system creates a comprehensive data
model for the database is known as database design. The database architecture includes all of
the necessary logical and physical architecture options, as well as physical storage
parameters, which can then be used to build a database. This process took nine days to
complete.
UML design- UML diagrams such as class, use case, sequence, and component diagrams
can help developers understand the proposed project better. UML diagrams take two days to
create.
 LMU ID: 22015190

Prototype Design- Prototyping is an experimental process where design teams implement

ideas into tangible forms from paper to digital. Teams build prototypes of varying degrees of
fidelity to capture design concepts and test on users. This process took four days to complete.

4.2.4 Phase-4 implementation

Coding- The Managing and Reservation Process will be coded in this location. Because the
proposed system is a web-based application, the coding will be done in PHP, HTML, CSS,
and JavaScript, with MySQL as the database. This process took twenty-four days to
complete.

4.2.5 Phase-5 testing

Test Plan- A plan must be created in order to effectively test the system, and it took three
days to create and evaluate the scenario. The time allocated for developing the test plan is
two days.
Test Configuration- The Configuration Management is a process of establishing and
maintaining a product’s performance, functional and physical attributes with its
requirements, design, and functionalities through its life. The time allocated for developing
the test plan is six days.
User Acceptance Testing- User acceptance development is the final stage of the software
development process (UAT). At UAT, real software users are used, which means that the
program is tested by the management of the individual hotel chain to ensure that it can
perform the organization's necessary tasks in accordance with the requirements. Three days
have been set aside for user acceptance testing.

4.2.6 Phase-6 product delivery

Handing over the deliverable to the client, sending the documents to the client,
canceling contracts with suppliers, releasing staff and equipment, and informing
stakeholders about the project's closure are all part of the delivery process. A Post
Implementation Review is carried out after the project has been completed to assess
the project's progress.
 LMU ID: 22015190

4.3 Gantt chart

Figure 2 Gantt chart

There are six main tasks according to this project and each task has its own sub- tasks.
Project planning is the very first task of the project. The start date of the project
planning
is 8/29/22and the end date is 9/1/22. The main role of project planning is to identify
challenges and, along with that, the project plan must proceed, assign key person,
agreement of deliverables, risk management and budget management.

The second main task is to collect and analyze requirements which consist of
gathering requirements and preparing the SRS. This stage period will be five
days, beginning on 9/1/22 and ending on 9/7/22
 LMU ID: 22015190

The third key task is system design including the sub-tasks, design UML
diagram, database design, UI design, prototype design and architectural design.
Beginning on 9/7/22and ending on 9/26/22in thirteen days total allocated for
this process.

The fourth major phase is Implementation where the coding process starts. The
total duration is 22 days which starts on 9/26/22and ends on 10/28/22.

Testing is the fifth phase of the project and will begin on 10/28/22 and finish
on 11/11/22 This process consists of drawing up the test plan, testing for
system integration and testing for user acceptance. That will take ten days to
complete this process.

The last task is project deliver and it will be starting on 11/11/22 and end on 11/18/22.
During this process, user manual and technical documents need to be prepared and
submitted. The project manager is responsible for project deliver and duration is five
days.

4.4 Milestones and Rationale for the set of Milestones

4.4.1. Gathering of requirements

Before beginning the project, first at a high level and then as granularly as possible.
Business requirements can be presented in a variety of formats, ranging from a list on a word
document to user stories for agile teams. What you ultimately want to understand is a
complete representation of what the software needs to do.

4.4.2. Validate expectation of requirements

Next, make sure to engage technical resources so they can translate the requirements into
more specifics about how they will be met. For instance, if our general requirement is to
create a hotel reservation system, the end result may not be what the client desires. In other
words, the requirement is overly broad. As a result, the developers would use the most
appropriate software to create the required system with the required specifications.
 LMU ID: 22015190

4.4.3. Designing
At the end of design milestone, UML diagrams, database and User Interface will be
delivered while the duration of 10 days and it is 45% of the whole project.

4.4.4. Implementation
At this milestone, our teams will begin working on all of the phases we outlined in the
planning stages. Once we begin development, implementation will be broken down into a
series of iteration deliverables that will result in more than one milestone. We recommend
creating deliverables that can be reviewed weekly.

4.4.5. Quality assurance testing

There are two methods for ensuring quality. One at the end of development, which is not
recommended unless the project is small, or it can be done throughout the project. We did
this at the end of the project once after the implementation was completed to ensure that there
is end-to-end testing validating that the entire system works as expected.

4.4.6. Deployment
Deployment milestone is the process of making the application operational. This
milestone includes the creation of an environment in which you upload the code, perform a
quick test to ensure that everything is functioning properly in your test environment, and then
push to production. Other exercises for making a site live include redirecting an existing
URL or an email link to the new server.

4.4.7. User Manual

This milestone is reached after deployment and testing phases have been completed.
 LMU ID: 22015190

4.5 Activity on Arrow Diagram

21 30

du
3

mm
=1
9

y1
1 2 3 6 7 8
A=3 B=5 E=10 F=5
0 0 3 3 8 8 30 30 40 40 45 45

0 0 0 0 0 0

1
my
D=

m
2 5

du
2

30 30

Figure 3 Activity on Arrow Diagram

ACTIVITY DURATION ES EF LS LF SLACK

A= PLAN 3 0 3 0 3 0

B= REUIREMENT
GATHERING 5 3 8 3 8 0

C= DESIGNING 13 8 21 17 30 9

D= 22 8 30 8 30 0
IMPLEMENTATION

E= TESTING 10 30 40 30 40 0

F= DELIVERY 5 40 45 40 45 0

Table 9 for Activity on Arrow Diagram

The purpose of doing this activity on arrow diagram is to find the essential paths and critical
path by calculating the float.
CRITICAL PATH = A > B > D > E > F
 LMU ID: 22015190

References
christine-organ. (2022, 3 25). Work Breakdown Structure (WBS) In Project Management. Retrieved from
forbes advisor: https://www.forbes.com/advisor/business/what-is-work-breakdown-structure/

Giles, W. (2015, 5 22). Project Structure. Retrieved from science direct:

https://www.sciencedirect.com/topics/computer-science/project-structure#:~:text=A
%20project%20structure%20provides%20the,of%20the%20local%20development
%20landscape.

wbs. (2022). work break down structure. Retrieved from work break down structure:
https://www.workbreakdownstructure.com/