Module Code : CT046-3-2-SDM –Systems Development Methods

Intake Code : UC2F2006CS(DA)

Lecturer Name : Dr Dewi Octaviani
Hand in Date : 9th August 2020
Tutorial No. : 4&5
Group No. : 36
Group Leader : Abdallah Al-Habsi

Student ID Student Name

TP048907 Abdallah Al-Habsi
TP050920 Lee Jin Wei
TP049708 Priscilla Chok Xiao Wei
TP050803 Surraj Ramanathan
TABLE OF CONTENTS

1 PROJECT PLANNING...........................................................................................................1

1.1 Introduction.......................................................................................................................1

1.2 Problem Statements...........................................................................................................2

1.3 Scope and Objectives........................................................................................................3

1.4 Project Scheduling............................................................................................................4

2 AGILE PRINCIPLES AND IS METHODOLOGIES (INDIVIDUAL).................................6

2.1 TP048907 Abdallah Al-Habsi...........................................................................................6

2.1.1 Agile Principles.........................................................................................................6

2.1.2 IS Methodologies.......................................................................................................7

2.1.3 Selection of Methodology..........................................................................................9

2.2 TP050920 Lee Jin Wei....................................................................................................10

2.2.1 Agile Principles.......................................................................................................10

2.2.2 IS Methodologies.....................................................................................................11

2.2.3 Selection of Methodology........................................................................................14

2.3 TP049708 Priscilla Chok Xiao Wei................................................................................15

2.3.1 Agile Principles.......................................................................................................15

2.3.2 IS Methodologies.....................................................................................................16

2.3.3 Selection of Methodology........................................................................................19

2.4 TP050803 Surraj Ramanathan........................................................................................20

2.4.1 Agile Principles.......................................................................................................20

2.4.2 IS Methodologies.....................................................................................................21

2.4.3 Selection of Methodology........................................................................................24

3 SYSTEM ANALYSIS (GROUP TASK)..............................................................................25

3.1 Data Mining and Analysis...............................................................................................25

 3.2 Statistical Analysis..........................................................................................................27

4 REFERENCES......................................................................................................................28

5 APPENDIX............................................................................................................................30
CT046-3-2-SDM UC2F2006CSDA

1 PROJECT PLANNING

1.1 Introduction
Waiters on Wheels is a restaurant which was created by two students Sue and Tom Bickford,
they were students in a college and in the same time they were working in a restaurant part-time.
They have always dreamed of opening their own restaurant but unfortunately, the initial
investment was unavailable. They found several restaurants that were providing home delivery
service, they got the idea to open their own restaurant without much money, the idea came to
their mind after meeting a lot of people who wanted home delivery services with their whole
choice of food. In 1997, they launched the "Waiter on Wheels" Restaurant. This Restaurant
provides customers with food by collecting and delivering dishes from multiple restaurants under
one roof. This service was very liked to customers, and day by day “Waiter on Wheels" grew. As
the number of clients and their orders grew, they started to face some challenges in order to run
their company efficiently.

Current business process:

In order to place the order, the clientele calls "Waiter on Wheels”, “Waiter on Wheels” tells the
restaurants related and the driver to take the order and place it at the customer's requested
address, the client will then be informed of this. The driver picks up the order and delivers it to
the customer and then returns to waiter on wheels.

1
CT046-3-2-SDM UC2F2006CSDA

1.2 Problem Statements

The current system that is being used by the Bickfords has many limitations as it is a traditional
system, where information regarding orders is recorded on a piece of paper. The Bickfords face
the challenge of not knowing whether their assigned driver had completed the delivery or not. It
leads to uncertainty and may cause delay for the next orders to be delivered to customers. As the
orders stack up, Waiters on Wheels currently do not have a proper delivery tracking system to
manage the orders efficiently. Lastly, another problem that the Bickfords face is to alter orders
that have been made by customers. Currently, Sue will need to call the restaurant to alter the
original order, which can be very troublesome in the large scale. Customers will not be satisfied
with the service offered by Waiters on Wheels.

The existing system has affected the business tremendously. As an example, orders recorded on
papers are prone to human errors, for instance, Sue might make mistakes recording order from
customers. It could lead to a significant loss for the company and destroy its reputation if it keeps
continuing like this. Apart from that, it is time and cost consuming to amend the orders that have
been placed. Next, due to the uncertainty of driver status for delivery, the Bickfords lose many
customers as they have a long waiting time for their meal to be assigned to a driver. The
limitation on altering the order in the existing system had cause customer dissatisfaction, where
customers are not happy with the slow response from the current system.

The new system is targeted to increase the efficiency of the restaurant meal-delivery service,
where it will be able to manage orders via the website or telephone. A database will be used to
store all information regarding the order information, customer information and even the driver
information. Moreover, the system can track the current status of the driver, whether he is
available to deliver, on the progress of delivering or has completed delivery. Therefore, the
Bickford need not worry about the delivery progress as all data is stored on the system, and the
system can produce a summary of order for future analysis. The proposed system will also allow
customers to alter their orders on the website or telephone with the order ID that will be given to
customers when they make an order initially. Lastly, the system will be able to produce an end-
of-day deposit slip when there are no more orders left and end-of-week restaurant payments. It
can also be able to produce weekly sales reports for the company so that they can be able to
make better decisions to implement new strategies.

2
CT046-3-2-SDM UC2F2006CSDA

3
CT046-3-2-SDM UC2F2006CSDA

1.3 Scope and Objectives

Scope:

The scope of the project is to a food delivery system for Waiters on Wheels. There are several
constraints in this project. During peak hours, as the number of orders is higher than off-peak
hours, customers may face a lack of delivery drivers. Customers may also have
miscommunication if they use the website, as there may be people who require accessibility
features on the website to place an order. The new system should process orders placed by
customers via the company website or the telephone. When drivers complete their delivery, the
system should notify the restaurant. When a driver reports for work, the system should show that
he is available to deliver. Not only that, but the system should be able to generate end-of-day
deposit slips, end-of-week restaurant payments and weekly sales reports.

Objectives:
There are several objectives in this project. There are as listed below.
1. To determine the most appropriate system development methodology for this project.
2. To determine the project timeline.
3. To perform system analysis by compiling, analyse and present the gathered data.
4. To design the system for this project.
5. To create a simple prototype for the system.
6. To determine the most suitable testing methods for this project.
7. To determine the most appropriate 'system change over method' for the product.

4
CT046-3-2-SDM UC2F2006CSDA

1.4 Project Scheduling

Gantt Chart

4
CT046-3-2-SDM UC2F2006CSDA

5
CT046-3-2-SDM UC2F2006CSDA

2 AGILE PRINCIPLES AND IS METHODOLOGIES (INDIVIDUAL)

2.1 TP048907 Abdallah Al-Habsi

2.1.1 Agile Principles

A -Working software is delivered frequently (weeks rather than months)

Agile methodologies encourage splitting the development of a product into smaller parts;
Therefore, an agile approach will speed up the overall development of the product.

This principle suggests that the Agile team provide a new version of the software within a short
timescale. That means smaller updates, and smaller updates mean reducing the potential for
bugs. More frequent updates also offer more feedback from the consumer input. If you just get
feedback after several months about all your updates, you'll have a lot of work to handle.

B-Projects are built around motivated individuals, who should be trusted

Give the agile team the encouragement and support they need and give them confidence to get
the job done.

An important aspect of Agile methodologies is to motivate people and teams with confidence
and autonomy. In order to do the job, the agile team must be designed with care to include the
right people and expertise, and the tasks must be clearly identified before a project begins.

when a developer designing a project around people who are not inspired or demotivated because
of a lack of confidence or support, the project is unlikely to succeed.

6
CT046-3-2-SDM UC2F2006CSDA

2.1.2 IS Methodologies

Spiral Method

The Spiral Model is a sophisticated model, based on early detection and project risk
management. With this approach in software creation, developers begin on a small scale, then
analyse the risks inherent in the project, make a strategy to tackle the risks, and eventually
determine whether to take the next phase in the project and perform the next spiral iteration.

Spiral model suitable for large and high-risk projects, also it is used for projects which need cost
and time evaluation frequently. Spiral model helps to handle projects with unclear and
incomplete requirements. Spiral model allows the changes at any time, so the clients can request
changes during the system development time.

Figure 2.1.2.1 Spiral Method

7
CT046-3-2-SDM UC2F2006CSDA
Spiral Model Phases:

a- Planning phase: This process starts with the identification of business

requirements. At this point, the identification of system requirements and unit
requirements is carried out in subsequent spirals as the product matures. It also
involves understanding the program specifications through constant contact between
the customer and the analyst. The commodity is deployed at the end of the spiral.

b- Risk analysis phase: Risk analysis includes identifying, estimating, and

observing technical feasibility. After testing the build, at the end of the first iteration,
the user assesses the software and gives feedback. The development process starts
with the consumer evaluation and then follows the linear approach of integrating
observations from the user. The process of iterations takes place over the lifespan of
the program.

c- Engineering phase: This process helps the customer to assess the performance
of the project to date before the next spiral of the project begins.

d- Evolution phase: Technology is being developed in the Engineering Phase,

along with testing at the end of the phase. The development and testing is done at this
phase.

Advantages of Spiral Model:

- Frequent risk analysis, therefore avoidance of the expected or possible risk.

- customer can request changes in requirements, functions and features at a later stage

Disadvantages of Spiral Model:

- It is not suitable for small projects, because it might cost them a lot of money.

- Expensive considering time and money, so it might exceed the schedule or budget.

8
CT046-3-2-SDM UC2F2006CSDA

2.1.3 Selection of Methodology

Systems development is a large and wide field, and today there are many experts in this field.
Sometimes the developer's experience in this field may impose some restrictions. As beginners
in system development, the best way to develop a system is to use a simple and easy
methodology, the waterfall methodology is an easy methodology to understand and use; that is
one of the reasons for choosing (Waterfall methodology)

9
CT046-3-2-SDM UC2F2006CSDA

2.2 TP050920 Lee Jin Wei

2.2.1 Agile Principles

The 8th agile principle is "Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace indefinitely" (Beck, Grenning,
& Mellor, 2020). There are times where clients might want a project in an unrealistic timeline,
where the deadlines are almost impossible to meet. However, this could lead to an excessive
workload for the team, which will cause burnout. Therefore, it is vital to set realistic and
practical expectations. Doing so will reduce burnout and maintain high morale within a team.
Hence, there are measures that a team should practice. First, the team has to define the project
timeline with proper estimations accurately. The team should only promise what they can
deliver. Next, all team members should agree on the project timeline and workload.
Requirements should not be added unless in urgent circumstances. The team would communicate
with the Bickfords on a suitable timeline and what are the priorities for each requirement. It is
because there might be some requirements that they would like to release before the others. It
would also allow us to release the first version earlier to serve their customers.

The 9th agile principle is "Continuous attention to technical excellence and good design
enhances agility" (Beck, Grenning, & Mellor, 2020). It is vital to keep things organised, or else
problems will occur in the future. There might be new requirements coming in from the
stakeholders in the future. If not done correctly, it may incur technical debt. Technical debt may
add further workload in the future, as the team has to refactor the codebase to clear the technical
debt. Hence, it wastes time unnecessarily. There might be new requirements from the Bickfords
in the future. Hence, the team will use proper coding standards and processes for the
development of this project. It is to reduce the amount of technical debt which may occur that
will hinder any future development of the project.

10
CT046-3-2-SDM UC2F2006CSDA

2.2.2 IS Methodologies
Scrum

Figure 2.2.2.1 Scrum Framework (SystemsPlus, n.d.)

Scrum is one of the highly used process-oriented methodologies in teams. Scrum can be used in
many scenarios as not only it can be used in IT teams, but also HR and finance teams as well. In
the scrum methodology, it consists of several key roles, which includes, the Product Owner,
Scrum Master and the Development Team.

The Product Owner focuses on ensuring the business requirements are satisfied. He or she also is
responsible for maximising the efficiency of the development team and the value of the
functioning product. The Product Owner is responsible for the backlog. A Product Backlog is a
set of features to deliver and problems to solve in a project, to deliver a distinct result (Agile
Alliance). Stakeholders might have a set of features they would like to have first. The Product
Owner is responsible for prioritising the tasks in the Product Backlog. He or she has to clearly
define the tasks along with its priority in the Product Backlog. The Product Owner also
represents customers and stakeholders. He or she acts as a liaison between the stakeholders and
the team.

The Scrum Master focuses on ensuring scrum compliance within the team. There might be
situations where the members of a Scrum team may go off-track and do not follow specific
Scrum values, as they are not proficient in Scrum. Scrum Masters are here to solve that issue. He
or she must have a thorough understanding of the Scrum theory for this role. The Scrum Master
11
CT046-3-2-SDM UC2F2006CSDA
supports different parts of the team, which includes the Product Owner, the Development Team
and the organisation. The Scrum Master would be held accountable for ensuring the team
understands the goals, scope and domain of the project.

The development team work together to deliver a product at the end of the Sprint. A Sprint is a
series of iterations which breaks down big and complex problems. It may consist of developers,
designers and testers. Each of them has specific skills, but they are accountable to each other.
They are usually a small development team, as large teams are too complex to handle.

12
CT046-3-2-SDM UC2F2006CSDA
Advantages:

There are several benefits to using Scrum. First, Scrum allows the team to release a functioning
product faster compared to traditional methods, such as the Waterfall methodology. The team
incrementally releases features to customers. There is a lack of need to wait for an entire project
to be complete before delivering to the customers. Hence, Scrum will decrease the time to
market. It is significant because if the team can only deliver after the completion of the product,
competitors might have already released a similar product, which may render the product
outdated. As Waiters on Wheels is expanding quickly, they would like the system to be released
as soon as possible.

With Scrum, there is also a more precise line of communication. As there is a product backlog,
team members will be able to view the progress of the project at any given time. As the team
holds daily stand-up meetings, the team members will be able to have a brief update of the
project progress every day. It also allows the team members to help solve each other's issues
during the stand-up meetings. It also allows the Bickfords to track the project's progress, which
will show confidence to them on the system.

Compared to the other methodologies, Scrum also welcomes changes at any stage of the project.
It is because of the agility and flexibility of Scrum, where the team can add new requirements
into the product backlog at any time and develop it on the next Sprint. Therefore, the Bickfords
would be able to request for additional requirements in the future.

Disadvantages:

There are also several disadvantages when using Scrum. First, although Scrum is easy to
understand, it is challenging to master. It comes with a huge learning curve. Therefore, it
requires people to be proficient in Scrum. It is vital to train the team members to implement
Scrum. Scrum requires a group of experienced people to succeed. It also requires a strong
commitment from the team members. If not, it may lead to massive issues.

13
CT046-3-2-SDM UC2F2006CSDA

2.2.3 Selection of Methodology

We have selected the Waterfall methodology. One of the reasons includes the Waterfall
methodology encourages quality control of the process and product. In the Waterfall
methodology, as a structured methodology, it strictly follows the five stages, which are
Requirements, Design, Implementation, Verification and Maintenance. The team will not be able
to proceed to the next stage without completing the previous stage. Due to its linear and
sequential processes, the team will have to follow strict and structured guidelines. Hence, it
reduces the chance of bugs in the project.

As the Bickfords will use this system for their business, it is vital to ensure the quality of the
product. Any mishaps in the product may cause substantial financial loss for the company.
Therefore, the Waterfall methodology is the most suitable for this project.

14
CT046-3-2-SDM UC2F2006CSDA

2.3 TP049708 Priscilla Chok Xiao Wei

2.3.1 Agile Principles

According to the Agile Manifesto, the first principle states “Our highest priority is to satisfy the
customer through early and continuous delivery of valuable software” (Beck, et al.,2020). By
using agile methodology, the time between discovering new ideas and delivering the product
should be minimized. For instance, developers can break down the entire task into smaller
chunks and deliver them to the customers once each iteration is done. This is to let the customers
engage with the new features as soon as possible and get feedback from them for improvements.
Unlike some traditional methodologies, customers have to wait until the project is completely
done to know whether they are satisfied with the product or not. With this principle, it is more
important to offer value to the customers quicker than to get a better product. By then, the
developer team does not only able to get continuous feedbacks from the customers based on
frequent releases of the product, but also able to keep the team focused and efficient for future
releases.

Moving on, the sixth principle stated in Agile Manifesto is “The most efficient and effective
method of conveying information to and within a development team is face-to-face
conversation” (Beck, et al.,2020). This principle is basically meant by interacting with team
members in real time is way better than relying on emails or other messaging tools to
communicate. It is inefficient especially when team members require prompt responses to their
questions or demands. Having face-to-face interaction will potentially help to get things happen
faster. For instance, team members can get instant answers from their superior at the first place
for further development. By doing so, this can help to enhance the relationship and trust between
the team members and increase the efficiency and effectiveness of conveying message within the
development team.

15
CT046-3-2-SDM UC2F2006CSDA

2.3.2 IS Methodologies
Web Information Systems Development Methodology (WISDM)

The Web Information Systems Development Methodology (WISDM) is designed for building
dynamic web-based information systems. It involves seeking socio-technical solution through
the interaction between individuals and technology or complex infrastructure to solve business
difficulties. WIDSM is based on the “Multiview” framework where a scenario or business
problem is viewed from several angles and the user’s behaviour will be translated into tasks by
the developer. The developer will then develop the automated architecture based on the tasks
captured.

Figure 2.3.2.1 Multiview Framework

There are five phases in WISDM methodology as shown in the figure above. The first phase
which will be discussed is the organizational analysis phase which also stands for value creation.
The developers undergo this phase to understand how can the proposed system generate greater
value to the organization. In this phase, the developer will study about the organization such as
the business strategy of that organization, what products and services do the organization offer
and other criteria related to the business. Through this phase, the developers can have a better
understanding towards the organization when developing the proposed system.

Moving on, the information analysis phase in which refers to the requirement specifications. In
this phase, the developer will construct a detailed requirements specification based on the initial
study from the organizational analysis. The user requirements can be documented as a business
report or strategy planning. UML model such as use case diagram can also be used to represent

16
CT046-3-2-SDM UC2F2006CSDA
the new proposed system (farahat, 2015). For instance, developers can conduct questionnaires to
collect more information based on the feedback given by other users or designers can do research
related to website development during the development process.

Furthermore, work design represents user satisfaction. This phase is where the developers
establish relationship with the stakeholders and employees. After conducting the analysis,
developers can design the user interface of the proposed system in terms of their usability,
accessibility, information quality and other requirements stated by the users. The developers
need to ensure that the user requirements are met. For instance, the functionality of the proposed
system is able to complete all the tasks in different department.

Moreover, the technical design phase which is also known as the software model. This phase
includes software system design in terms of programming, data structures and others which can
support the website development. The data design, architectural design and other elements of the
design model will be produced in this phase. The proposed design model will fit into the physical
website during deployment. Lastly, it is the human computer interface. From the diagram above,
it can be seen that the HCI is located between the work design and technical design phase. It acts
as a connection between these two design phases to ensure that the proposed system matches
both the components in terms of its usability and other principles.

Advantages of WISDM:

One of the advantages of WISDM is that this methodology is more flexible and lower in cost to
maintain as compared to other methodologies. This is because no step-by-step phases are
required to be followed when developing the system. For instance, various online services or
web applications are needed to be integrated in one project. Hence, this methodology is versatile
enough to allow the developers to make changes in order to fit in the current situation with a
reasonable cost. Moving on, WISDM is also beneficial in terms of its multidimensionality.
WISDM provides certain wider organizational and human perspective aspects and not just the
technological perspective. Hence, this methodology is able to tackle critical elements of the web-
based system development such as its user interface problems.

17
CT046-3-2-SDM UC2F2006CSDA
Disadvantages of WISDM:

WISDM requires strong cooperation with team members and user involvement. This is because
this methodology is used when there are a lot of uncertainty towards the system from the users.
Without user involvement, it will be difficult to develop a satisfied information system for the
users since this methodology supports socio-technical view. Furthermore, WISDM is also
unsuitable for inexperienced developers. This is because this methodology is flexible and might
require experts to follow up or make changes anytime. Inexperienced developers who need to
follow procedure throughout the development might unable to handle the complexity of the
project. In addition, lacking complete system design is also one of the drawbacks of WISDM
which causes system architecture irrationality. This is said so as this methodology defines the
human-computer interface (HCI) as its design stage. There is no design stage that clearly focuses
on personalisation and customisation using this methodology.

18
CT046-3-2-SDM UC2F2006CSDA

2.3.3 Selection of Methodology

Our group has selected waterfall model because there are clear requirements towards the
proposed system. As it can be shown that the Bickfords are very clear about what they need their
delivery tracking system to accomplish such as recording orders, changing orders, creating
deposit slips and other functionalities. With clear requirements, the development team is able to
proceed with the planning phase and start to work on the proposed system as soon as possible.
This model also uses clear structures as the requirements stated are well-documented which
enables the team to get the clearest steps to begin the project. The development team is able to
complete each phase on time using this methodology. It will also be helpful for the team as
problems can be solved right away in each phase before proceeding for further development. By
then, a completely functional system can be delivered to the client with quality assurance.

19
CT046-3-2-SDM UC2F2006CSDA

2.4 TP050803 Surraj Ramanathan

2.4.1 Agile Principles

Agile principles are not a set of guidelines for agile implementation, but instead a collection of
concepts that help instil agile thinking. Firstly, the second principle in the Agile Manifesto states
"Welcome changing requirements, even late in development. Agile processes harness
change for the customer's competitive advantage." (Beck, Grenning, & Mellor, 2020). This
principle emphasizes on accommodating new requirements at any time of the project
development cycle to deliver the latest trend of product in the market. One strategy to implement
the principle is to involve the client more in system development. Feedback from clients assists
the team to build the system according to their requirements. As an example, an appointment will
be set up between the Bickfords and the internal team to discuss the latest development on the
project. When there is progress, clients may have new ideas to be implemented for the system. It
can highly increase the quality of the system instead of following predefined requirements.

Next, the fourth principle in the Agile Manifesto states "Business people and developers must
work together daily throughout the project." (Beck, et al.,2020) The principle focuses on
communication between the business side and the technical side of the organization to deliver the
best solution available. Moreover, it builds trust and transparency by making sure both sides are
aligned on the requirements for the project. For instance, both the business side and the
development team can have daily stand-up meetings to ensure that all members of the project are
updated with the latest project requirements. Daily stand-up meetings can be used as a platform
to share problems and improvements on the project (Yip,2016), where team members will
support each other when someone encounters a difficulty or finds a better way to solve a problem
raised. As a result, the team will be more comfortable working on the project as they will readily
have team members that support each other which will lead to the development of a high-quality
product.

20
CT046-3-2-SDM UC2F2006CSDA

2.4.2 IS Methodologies

Waterfall Model

Waterfall model is the earliest Systems Development Life Cycle (SDLC) approach that is used
for software development. In this model, there are six phases, which are requirement Analysis,
System Design, Implementation, Testing, Deployment and Maintenance.

Figure 2.4.2.1 Waterfall Model

In this model, each phase must be completed before the next phase begins. In short, each phase
acts as an input for the next phase. Thus, there is no overlapping between phases.

The first phase in the model is requirement gathering and analysis. In this phase, all possible
requirements will be documented and will serve as a basis for future developments. As an
example, Waiters on Wheels have specific requirements such as a customer must be able to order
via telephone or website. Next, the system must notify the admin when the driver has completed
a delivery as well as reporting to the system when the driver is available for delivery. As a result,
this phase will produce System Requirements Specification (SRS), which will act as an input for
the next phase, system design phase.

System design phase consists of specifying hardware and system requirements and help define
the overall system architecture. This stage covers the technical design requirements such as
programming language to be used, data layers and use cases of the system itself. The output of

21
CT046-3-2-SDM UC2F2006CSDA
this phase is the System Design Specification (SDS). System design is one of the vital phases
because it provides clear instructions on the intent, performance and the construction of the
system itself (Pringle, 2017). By being clear and concise of all information that needs to be
designed, it saves the project team so much time when they are implementing the system.

Furthermore, there are two main types of system design, physical design and logical design. The
physical design is a graphical representation of a system displaying the internal and external
entities of the system and the data flows to and from those entities. (Tutorialspoint,2020). For
instance, database design can provide precise requirements on how to store customer data, driver
information and restaurant information. Logical design is an abstract representation of data
flows, input and outputs of the system. An Entity-Relationship Diagram (ERD) can be used to
represent the logical design.

After that, the next phase is the implementation phase, where the system is first developed into
small programs called units, which will then be integrated into one primary system. Each unit
will undergo Unit Testing, where the purpose is to validate each unit of the software to perform
as designed. After successfully testing each unit, all the units developed in the implementation
phase are integrated into a system. This process will happen in the integration and testing phase.
The system is tested for any faults or errors before proceeding to the next stage, deployment of
the system. Once the system is proved to have no failures, the system will then be deployed to
the customer for utilization. Finally, the system will be undergoing the maintenance phase where
the developers will fix any issues that have been faced by the clients and enhance the product to
a better version for the client.

Advantages:

Waterfall method forces a structured organization. Every aspect of the project is properly
documented in the requirement gathering and analysis phase. Every project includes detailed
procedures to fulfil client’s requirements from design and development to testing and
implementation. Next, the waterfall method determines the end goal of the project early (Lucid
chart, n.d.). It ensures the team are well aware of the end goals and avoid the tendency to lose
crucial details towards developing the system itself. Lastly, information is transferred well in the
waterfall method, due to the highly methodical approach. In the development environment, each

22
CT046-3-2-SDM UC2F2006CSDA
phase might require a different group of people, so waterfall prioritizes accessible information to
them to ensure they are aware of the objectives and goals.

Disadvantages:

On the contrary, a disadvantage of the waterfall model is that it cannot accommodate changing
requirements as client requirements are finalized in the beginning stages. Accepting new
requirements will not only be expensive but also not completing the project in the agreed
duration. Next, the waterfall method excludes the client from being involved in the project. The
waterfall method is mainly focused on assisting the internal team to be more efficient through the
phases of a project. Thus, clients will not be updated on the project and might not get a clear
perception on the system that is being developed. Finally, the waterfall method has a delayed
testing period, where the system will be tested nearly the last phases of the waterfall model. As a
result, most bugs and UI/UX issues would not be discovered until very late in the process, and it
is expensive and time-consuming to handle those issues.

23
CT046-3-2-SDM UC2F2006CSDA

2.4.3 Selection of Methodology

The waterfall model has a crucial advantage, where it transfers information well. Waterfall
model emphasizes on the documentation such as the requirement documents, design documents
and the source code for the project. Thus, every phase in the waterfall model is documented
precisely. It is essential for the project accomplishment as if team members leave, new members
that are part of the team can get up to speed by reading the documentation. They will be well
aware of the requirements and the goals of the system itself. If not documented, knowledge
regarding the project might be lost if a member leaves the team.

The proposed system for Waiters on Wheels is a food delivery system, where all requirements
are gathered to produce the System Requirements Specification. As an example, the Bickfords
needs to know when the driver is available for delivery. These functional requirements provide a
guideline to the developers to build the system. Proper documentation saves time for developers
as they will know precisely what the client is looking for. Therefore, the waterfall model ensures
a highly reliable system for the client.

24
CT046-3-2-SDM UC2F2006CSDA

3 SYSTEM ANALYSIS (GROUP TASK)

3.1 Data Mining and Analysis

Data mining is a method of identifying similarities and relationships from massive volumes of
data to predict future outcomes (SAS, n.d.). This method is being widely used in various fields
such as business and research. It can address business problems which are too time consuming to
be manually solved. There are various data mining techniques being used to analyze data such as
regression, clustering, correlation and etcetera. The observations or findings gathered can be
used to forecast what is more likely to happen in the future and to take measures in affecting the
business performance. Data mining can offer profound benefits over competitors if it is being
utilized accurately such as businesses are able to study about their customers and also come out
with more effective business functions strategies (Pearlman, 2020).

An advantage of data mining in this project is that it helps in decision making. It is said so
because data mining can find various patterns in a dataset (Reddy ,2019). In this project, data
mining techniques can predict the most preferred type of cuisine ordered by customers. Thus, the
Bickfords can use this information to find new restaurants to be in contact with, as well as
increasing their business opportunities to increase revenue. For instance, if the most preferred
type of cuisine is western, then the Bickfords should explore restaurants that offer western
cuisines and sign a contract.

Next, data mining is used to predict accurate sales volumes from the dataset, thus predicting the
profit of the company. Utilizing techniques such as regression provides vital insights into the
company. As an example, data mining can produce information regarding the preferred days for
food delivery as per the figure below.

25
CT046-3-2-SDM UC2F2006CSDA

Figure 3.1.1 Preferred days for food delivery

According to the figure above, most customers opt for food delivery on Sunday, which means
the Bickfords should have more drivers available for delivery to reduce the waiting time of
customer. It will improve customer satisfaction rapidly, as well as increasing the company sales.

26
CT046-3-2-SDM UC2F2006CSDA

3.2 Statistical Analysis

Statistical analysis is where we use numeric data to explore the underlying patterns and trends
(SAS, n.d.). There are several advantages to statistical analysis. It allows business owners to
make better decisions. As there are correlations between several variables, it provides insights on
how to improve sales further. For example, there might be a high demand for ice cream products
during evening hours, but a low demand in the morning. The company can reduce the amount of
ice-cream produced in the morning but increase the amount of ice-cream produced in the
evening. For the use case of Waiters on Wheels, such analytics can be shown to restaurants as
well, which will further optimise their resources, such as the number of employees and number
of foods and drinks to prepare. It will also avoid wastage of resources, which will reduce costs
for the restaurants.

With tools such as Microsoft Excel or SAS, graphs and charts can be generated to provide
valuable insights. Microsoft Excel and SAS can also offer forecasts. With the low barrier of
entry, easy-to-use applications such as Microsoft Excel allows the business owners to access
such forecasts without the need for a professional data analyst.

27
CT046-3-2-SDM UC2F2006CSDA

4 REFERENCES

1. Pringle, T., 2017. 15 Reasons Why Specifications Are Still Important. [online]
Manufacturers.thenbs.com. Available at:
https://manufacturers.thenbs.com/resources/knowledge/15-reasons-why-specifications-
are-still-important[Accessed 28 July 2020].
2. Tutorialspoint.com. 2020. System Analysis & Design - System Design - Tutorialspoint.
[online] Available at:
https://www.tutorialspoint.com/system_analysis_and_design/system_design.htm
[Accessed 19 July 2020].
3. Software Testing Fundamentals. 2020. Unit Testing - Software Testing Fundamentals.
[online] Available at: http://softwaretestingfundamentals.com/unit-testing/ [Accessed
21 July 2020].
4. Lucidchart.com. n.d. The Pros And Cons Of Waterfall Methodology. [online] Available
at: https://www.lucidchart.com/blog/pros-and-cons-of-waterfall-methodology [Accessed
24 July 2020].
5. Yip, J., 2016. It's Not Just Standing Up: Patterns For Daily Standup Meetings. [online]
martinfowler.com. Available at:
https://martinfowler.com/articles/itsNotJustStandingUp.html [Accessed 28 July 2020].
6. Productplan.com. 2020. What Are The 12 Agile Principles? | Definition And Overview.
[online] Available at: https://www.productplan.com/glossary/agile-principles/ [Accessed
29 July 2020].
7. Reddy, C., 2019. Data Mining: Purpose, Characteristics, Benefits & Limitations -
Wisestep. [online] WiseStep. Available at: https://content.wisestep.com/data-mining-
purpose-characteristics-benefits-limitations/ [Accessed 6 August 2020].
8. Beck, K., Grenning, J., & Mellor, S. (2020, July 28). Agile Manifesto. Retrieved from
https://agilemanifesto.org/principles.html

9. Agile Alliance. (n.d.). What Is A Backlog? Retrieved August 2, 2020, from

https://www.agilealliance.org/glossary/backlog

10. SAS. (n.d.). Statistical Analysis - What is it? | SAS. Retrieved August 5, 2020, from
https://www.sas.com/en_my/insights/analytics/statistical-analysis.html

28
CT046-3-2-SDM UC2F2006CSDA
11. SystemsPlus. (n.d.). SystemsPlus-Scrum-Image-.jpg. Retrieved August 5, 2020, from
http://1.bp.blogspot.com/-5EC7uXfIxR8/VlhTFG2O2uI/AAAAAAAAXg0/eAT3wtpDk
3s/s1600/SystemsPlus-Scrum-Image-.jpg

12. farahat, a., 2015. Web IS Development Methodology (WISDM):The WISDM Matrix |
Business Information Management. [online] Engineering-bachelors-degree.com.
Available at: <http://www.engineering-bachelors-degree.com/business-information-
management/uncategorized/web-is-development-methodology-wisdmthe-wisdm-
matrix/> [Accessed 30 July 2020].
13. Shaffi, A. and Al-Obaidy, M., 2013. Analysis And Comparative Study Of Traditional And
Web Information Systems Development Methodology ( WISDM ) Towards Web
Development Applications. [online] Semanticscholar.org. Available at:
<https://www.semanticscholar.org/paper/Analysis-and-Comparative-Study-of-
Traditional-and-(-Shaffi-Al-Obaidy/
1c90ff663058bde0f39c5cf1f27700aa10eb5c6e#paper-header> [Accessed 30 July 2020].
14. What-when-how.com. n.d. Accommodating End-Users' Online Activities With A Campus
Portal. [online] Available at: <http://what-when-how.com/portal-technologies-and-
applications/accommodating-end-users-online-activities-with-a-campus-portal/>
[Accessed 4 August 2020].
15. Scanlon, S., 2019. How To Apply The 12 Agile Principles To L&D Project Management -
Elearning Industry. [online] eLearning Industry. Available at:
<https://elearningindustry.com/apply-12-agile-principles-ld-project-management>
[Accessed 4 August 2020].
16. Pearlman, S., 2020. What Is Data Mining? Definition And Examples. [online] Talend
Real-Time Open Source Data Integration Software. Available at:
<https://www.talend.com/resources/what-is-data-mining/> [Accessed 6 August 2020].
17. Plutora. 2020. The 12 Agile Principles: What Are They And Do They Still Matter? -
Plutora. [online] Available from: <https://www.plutora.com/blog/12-agile-principles>
[Accessed 1 August 2020].

29
CT046-3-2-SDM UC2F2006CSDA

5 APPENDIX

Student 1 Student 2 Student 3 Student 4

Name Abdallah Al- Lee Jin Wei Priscilla Chok Surraj

Habsi Xiao Wei Ramanathan

TP Number TP048907 TP050920 TP049708 TP050803

Group Component

Student 1 Student 2 Student 3 Student 4

Tasks CONTRIBUTIO CONTRIBUTIO CONTRIBUTIO CONTRIBUTION

N PERCENTAGE N PERCENTAGE N PERCENTAGE PERCENTAGE

1.1 Introduction 100% - - -

1.2 Problem - - - 100%

Statements

1.3 Scope, Objectives - 100% - -

1.4 Project Scheduling - - 100% -

3.0 System Analysis 25% 25% 25% 25%

30