CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

PART 1
Module Code : CT046-3-2-SDM –Systems Development Methods
Intake Code : ADP2F2106CS(DA)
Lecturer Name : Mr. Sivananthan Chelliah
Hand in Date : 29/06/2021 – 13/08/2021
Tutorial No. : T9
Group No. : 16
Group Leader : SUSHMITA A/P S THAMBITHURAI

Student ID Student Name

TP056555 SUSHMITA A/P S THAMBITHURAI
TP060272 LAU JAYXI
TP056719 PREETA A/P C. GANDHI
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

Table of Contents
1. Project Planning .......................................................................................................................... 1

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

1.2 Problem statement - PIECES Framework............................................................................. 2

1.2.1 Performance ................................................................................................................... 2

1.2.1.1 Throughput .................................................................................................................. 2

1.2.1.2 Response time ............................................................................................................. 2

1.2.2 Information .................................................................................................................... 2

1.2.2.1 Output ......................................................................................................................... 2

1.2.2.2 Input ............................................................................................................................ 2

1.2.2.3 Stored Data.................................................................................................................. 2

1.2.3 Economics ...................................................................................................................... 2

1.2.4 Control ........................................................................................................................... 2

1.2.5 Efficiency ....................................................................................................................... 3

1.2.6. Service........................................................................................................................... 3

1.3 Scope, Aim, Objectives......................................................................................................... 4

1.3.1 Scope .............................................................................................................................. 4

1.3.2 Aim ................................................................................................................................ 5

1.3.3 Objectives ...................................................................................................................... 5

1.4 Project Scheduling ................................................................................................................ 6

2. Agile Principles and IS Methodologies ...................................................................................... 7

2.1 Agile Principles..................................................................................................................... 7

2.1.1 Group Member 1 (Sushmita) ......................................................................................... 7

2.1.2 Group Member 2 (Lau Jayxi) ........................................................................................ 8

i
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.1.3 Group Member 3 (Preeta) .............................................................................................. 9

2.2 IS Methodologies ................................................................................................................ 10

2.2.1 Group Member 1 (Sushmita) ....................................................................................... 10

2.2.2 Group Member 2 (Lau Jayxi) ...................................................................................... 12

2.2.3 Group Member 3 (Preeta) ............................................................................................ 14

2.3 Justification of Selected Methodology................................................................................ 17

2.3.1 Group Member 1 (Sushmita) ....................................................................................... 17

2.3.2 Group Member 2 (Lau Jayxi) ...................................................................................... 18

2.3.3 Group Member 3 (Preeta) ............................................................................................ 19

3. System Analysis ........................................................................................................................ 20

3.1 Data Mining ........................................................................................................................ 20

3.2 Statistical Analysis .............................................................................................................. 22

3.3 List of Requirements ........................................................................................................... 25

4. References ................................................................................................................................. 26

5. Appendix ................................................................................................................................... 29

5.1 Detailed workload matrix ................................................................................................... 29

5.1 Workload matrix summary ................................................................................................. 30

ii
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

1. Project Planning
1.1 Introduction
MyCloths is a renowned Malaysian retailer and distributor of various types of traditional
Malaysian cloths. In their store at KLCC, they currently service walk-in customers. Customers can
also place orders via emails or telephone calls, and the cloths will be delivered right to their
doorstep. MyCloths sought to enhance the management of their orders, inventory, and customer
relationships as their company grows. MyCloths' vision is to be a market leader in the use of
technology to provide the best possible customer experience while offering the widest selection of
traditional Malaysian cloths. MyCloths plans to open an online store by July 2017 in accordance
with the growing number of customers.

Currently, the business process is done manually whereby several reports are time-consuming to
be generated. Therefore, MyCloths has engaged with a consultant to develop an online store
through which this project explores the areas that can be automated and include the following
functions as below:

Suppliers of traditional cloths send a list of inventories to the MyCloths store manager frequently.
The store manager compiles a list of required cloths and places a Purchase Order (PO) to the
respective suppliers. Upon receiving the PO, the supplier delivers the ordered cloths and raises a
Delivery Order (DO) to the warehouse. On receiving the DO, the store manager records the goods
received on a document called the Goods Received Note (GRN), along with the quantities of new
cloths that arrived at the warehouse. The store clerks update the inventory of the traditional cloths
based on the GRN received.

Customers who registered as members may view, add their selected cloths to the shopping cart
and purchase them using online payment methods. Members will also be entitled to discounts and
gifts for certain products. Upon making payment of their purchase, customers will receive a
shipping note whereby the cloths will be delivered within 7 working days. All necessary
information on the products including cloths and accessories, reviews and feedbacks of customers
will be stored for customers’ references. Cloth inventory management and customer delivery will
be managed by MyCloths’ staffs.

1
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

1.2 Problem statement - PIECES Framework

Currently MyCloths is facing problems regarding their business processes done manually. Hence,
the PIECES framework is utilized to analyse the problem in a more in-depth manner.

1.2.1 Performance
1.2.1.1 Throughput
MyCloths currently has a poor throughput in taking orders. The orders will be depending on the
number of telephone line owned by the company since the orders are taken manually. Assuming
the telephone lines are less than five, the number of orders taken currently is limited to the number
of telephone lines.

1.2.1.2 Response time

The response time taken by MyCloths is very poor. MyCloths handle their orders through calls
and emails only. Orders through emails will be taking a long time considering the customer service
has to read through the emails and respond to the customer. It might take days for the customer
service to read the order and reply with the details of the product.

1.2.2 Information
1.2.2.1 Output
There is no output information because MyClothes uses paper-based system.

1.2.2.2 Input
Input are not being captured by MyCloths. Each data is manually written on papers. The orders
from calls and emails are not captured in any system.

1.2.2.3 Stored Data

MyCloths does not store any data in their files.

1.2.3 Economics
As the business is expanding the number of manpower and appliance needed increases. More
number of phones and pc leads to high cost of maintenance. The cost will be too high. Therefore,
the revenue of MyCloths eventually will start to drop.

1.2.4 Control
There is no proper control in the current manual system. The orders taken cannot be edited
including customer personal details which leads to a lot of errors and lack of control. Fraud also

2
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

can easily be held with current system. It cannot be checked that anything from the company has
been whether stolen. Ethics also will be breached on data since there is no data protection. There
is no tight security.

1.2.5 Efficiency
The people redundantly copy the data. For example, when there is an order, it will be written on a
piece of paper and be transmitted to the inventory as a photocopy or fax to process the order. There
might be too many papers with the same data. An excessive workforce is required to ensure smooth
operation flow, such as taking orders, replying to emails, updating inventory, and managing
deliveries. High number of materials also required for the manual process. For example, tools and
materials such as phones, computers, paperwork are needed during each process.
1.2.6. Service
Not available as currently the business is operating manually and does not have any existing system.

3
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

1.3 Scope, Aim, Objectives

1.3.1 Scope
1.3.1.1 Justification

MyCloths wanted to improve their customer service to the best level so that they could not be
losing their customers to their competitors. They wanted to have a better management order of
their inventory and to improve their customer relationship.

1.3.1.2 Objectives

The product will be the information system which will providing the services that fulfil current
business processes.

1.3.1.3 Product scope description

The features and functions of the information system is to automate the entire business whereby
customer will be able to purchase online, update inventory, keep the most updated inventory
getting from the suppliers, various type of management reports is produced.

1.3.1.4 Product acceptance criteria

The inventory will be managed at the optimal level. Orders and delivery will be performed without
any delay with a good response time so the customer satisfaction can be achieved.

1.3.1.5 Constraints

The performance of the product can be constrained by the Internet service provider (ISP).
Customers that chooses ISP which provides low bandwidth may result in slow response time. Also,
time taken for customer delivery is dependent on the delivery company. A longer time will taken
if the delivery company delivers the products to customers exceeding the shipping days stated.

1.3.1.6 Assumptions

There are a few assumptions made to minimize the conflict in the process of system
development. In this project, the constraints of cost and timescale are assumed as fixed variable so
that the cost does not exceed the budget and the online store can be established by July 2017 as
MyCloths planned. It is also assumed that the project is starting in April of 2017 which means the

4
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

time given is approximately three months. The team members of this project are assumed as the
three group members along with no more than five professional expertise.

It is also assumed that in the current manual system, the number of people handling the
calls and emails are less which resulted in limited possible sales per day to a certain maximum.
The time taken for whole operation could be long considering the process such as taking in the
order, checking stocks, confirming order have been done manually. It is also assumed that there is
possibility of multiple suppliers are supplying to MyCloths. Since the online store will require the
customers to register membership before placing order, it is assumed that all the existing and
previous customers of MyCloths does not have a membership. We assume the inventory is low
when there is less than 5 products.

1.3.2 Aim
To critically assess the existing business operations for MyCloths apparel retail and distributor to
identify factors, which contribute to customer satisfaction and operational efficiency.

1.3.3 Objectives
• To critically assess the existing business operations
• To manage the orders through online store with enhanced operation processes and
functions that supports the business
• To provide the best possible customer experience through the use of technology
• To update inventory and retrieve reports required in efficient system

5
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

1.4 Project Scheduling

Gantt Chart Task.mpp

https://cloudmails-
my.sharepoint.com/personal/tp056555_mail_apu_edu_my/Documents/Gantt%20Chart%20Task.
mpp

Figure 1: Gantt Chart of Workload

6
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2. Agile Principles and IS Methodologies

2.1 Agile Principles
2.1.1 Group Member 1 (Sushmita)
Agile principles are based on 'The Agile Manifesto' to use in software development as an outline
to prioritise the important things. Through a flexible, reactive system, the 12 agile principles can
help companies simplify their product development cycles and generate better results (What Are
Agile Principles? Definition and Examples & FAQ, 2021). The first agile principle that can be
implemented in the project to make it more agile is focusing on the customers' satisfaction with
early and continuous delivery of valuable software. The best way to keep the customers happy is
by delivering a working product early and iteratively rather than taking a long time to provide a
complete functioning system. Unlike other approaches, the agile principle minimises the time
between ideation and launch. Product managers can quickly release a minimum viable product
(MVP) into the world and utilise it to gather feedback from real customers. All the feedback will
be collected and used back in the following product development process. This frequent release of
products creates a feedback cycle between the customer and the products, making them more
engaged with the system. Iterations continue to make incremental changes to the product based on
customer and market feedback rather than releasing a final complete product (Agile Principles,
2021). The second principle is welcoming changing requirements, even late in development. This
principle is well suited for this modern world. It highly supports accepting and implementing
changes to adjust the plans for a better service to the customer and business need rather than
ignoring them. This principle enables developers to keep an eye on changing markets, consumer
needs, and other factors which could influence product direction. The development team of
MyCloth can respond to problems and make changes to the product to meet customer needs
anytime. The product strategy and tactical plans are reviewed, changed, and frequently shared
(Agile Principles, 2021).

7
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.1.2 Group Member 2 (Lau Jayxi)

Agile Principles help in establishing the direction and foundation of the flexibility in the software
development process. To introduce and improve the agility of this project, there are two principles
that can be implement. First, the tenth principle of simplicity is essential as it emphasises on the
maximum outcome through the minimum amount of work done. This encourages thinking of doing
things that can have the most impact and focus on the priorities or requirements. (Product Plan,
2021) As the customers were looking for a solution to their problems, it is not necessary to have
complicated and sophisticated process. However, a strong purpose and strategy in the process will
lead to efficient solution through simplicity. (Product Plan, 2021) Therefore, priorities of this
project should be made clear and development focusing at the most impactful functions in this
system. To implement simplicity, the inventory can be managed in simplest visualization with the
basics requirement as it is handling a huge amount of data and information of the stocks. In terms
of online store, it is crucial to keep it user-friendly with minimum processes while making
purchases. This can accommodate the users of different age range and level of computing
knowledge to the system easily. Besides, the desired results of strengthen relationship with
customers can be achieved as customers have more opportunities or ability to make full use of the
system such as leaving reviews and ratings for the experience through a simple system.

Another essential agile principle that can be implied is the team should reflect on how to become
more effective and adjust accordingly at regular intervals based on the twelfth principle. From time
to time, the processes and decisions can be reviewed to ensure that they are the most effective
choices, or the better and improved choice compared to the previous. (Product Plan, 2021) Regular
retrospective provides platform and chances for the team to share their honest opinion on the
processes and corrective actions can be taken before it is too late to make changes. (Product Plan,
2021) This will help in building culture of the effective communication between the team and
customers as well through the process and make sure that everyone is on the same pages all the
time. Regular discussion and reflection among the team as well as meetings with clients can be
scheduled whenever moving into the next phase of system design.

8
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.1.3 Group Member 3 (Preeta)

The 5th agile principle states that projects are built around motivated individuals, who should be
trusted. The logic behind the fifth Agile principle is that projects will be completed faster and with
higher quality if micromanagement is reduced and motivated team members are empowered
(Kanban Software for Agile Project Management, 2021). In many environments, the higher-up
usually gives the green light for the next stage to get started. However, following the agile methods,
developers, designers, managers, and builders who are directly involved in the making of the
product should also be trusted. Motivated developers will feel empowered to do their work
professionally with the right environment, support and trust (Plutora, 2019). In this case study,
trusting the developers and designers to their job respectively will help to quicken the processes in
each stage. Hence, the time taken from one stage to another, for example, analysis stage to design
stage will be faster without any delay rather than waiting for the higher-up’s approval to move on
to the next stage of the MyCloths project.

The 6th principle states, “The most efficient and effective method of information to and within a
development is face-to-face conversation”. The number of ways humans can communicate has
increased because of technological advancements. However, none of these are as effective as a
face-to-face conversation. Asking a question and receiving an answer takes less time when
communicating in person. In this case, effective communication among developers is reducing
conversations via emails and encouraging more human interaction among one another (Plutora,
2019). Therefore, there will be no need of lengthy reports for simple enquiries explaining about
the system. Some strategies that can be implemented are stand-up meetings which are far more
effective as it only takes around 10 to 15 minutes to clarify and discuss on problems faced during
any of the stages. Many companies have employees who work remotely, even in different time
zones. Skype and Zoom allow the team to have remote face-to-face conversations. These meetings
are necessary for fostering communication that drives an agile project management Agile requires
quick responses to issues and voicing them in a public platform is a great way to empower cross-
team collaboration (Plutora, 2019).

9
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.2 IS Methodologies
2.2.1 Group Member 1 (Sushmita)

Figure 2: The scrum framework (What is Scrum?, 2021)

Scrum methodology can be suggested to use in this project. MyCloths prioritize developing the
methods if they want to see the product as soon as possible. MyCloths prefers an iterative model
rather than a linear one. MyCloths choose iterative because they want to deliver the products in
incremental. For example, they want to choose a theme for the website, so they want a homepage
first to get the customer's inputs. Next, MyCloths wants a customer registration to be done to pass
out to the customers to register and be so on. They want to deliver part of the whole inventory
every two weeks, so people get used to the system.
2.2.1.1 Features
Four main features can be found in scrum methodology. First, scrum has sprint sessions. This
method divides the entire team into smaller groups of 3-9 people who work together for a
maximum of a week or two weeks to achieve a common goal. They discuss the project's progress
at the end of the week and the progress that must be made before the next sprint session. These
meetings are generally successful since the planners are also the executors, and the team is driven
to keep working on the project because the plan is updated frequently. The next is display progress,
a chart that should be set up to make everyone's work visible. This chart can push slow workers to
work faster and encourage energetic workers to keep working at their current pace. A Burndown
Chart is also another feature of the scrum that should be displayed weekly. The chart should
include the number of remaining working days and the amount of work pending so that employees
know how many days they must work to complete the task. The last scrum methodology's feature

10
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

is precise meetings which are daily meetings in short intervals. These meetings should last no
longer than 10-15 minutes. Instead of repeatedly discussing the entire project and various plans
for achieving the goal, only a few crucial questions should be asked and answered throughout the
meeting. The goal is to keep it short but effective (4 Features That Make Scrum Successful, 2019).
2.2.1.2 Advantages
Scrum methodology contains many advantages. Firstly, it is adaptive and flexible. Scrum is one
of the most adaptable frameworks available, as it is always ready for changes and can adapt to any
situation. Scrum is best suited to uncertain conditions or environments where requirements cannot
be precisely specified at the start of the project. Usually, as the project progresses, feedback and
other factors will influence the product development process. Since scrum is iterative, those
feedbacks will be used to improve the product in the next sprint. Flexibility also allows the
developers to be more innovative in designing the products also solve complex problems with
creative solutions. Scrum not only prioritise customer satisfaction but also focuses on the
satisfaction of the employees. Developers' decisions are essential in the Scrum approach, which
allows them to manage their teams and come up with unique solutions. Considering the developer's
opinions are more satisfying for employees because it will enable them to think and create instead
of the traditional "command and follow" method. In an Agile environment, the team takes
ownership of their work and collaborates to develop high-quality products (Advantages and
Disadvantages of Scrum | Pros and Cons of Scrum, 2021).
2.2.1.3 Disadvantages
Like other methodologies, scrum has some disadvantages that should be considered before
implementing it in the organisation. Scrum requires high skills and training. Before companies
successfully implement scrum, a significant amount of training is required for the new employee
to understand the whole process. If the company skip the training to save cost, there could be
difficulty proceeding to the following stages, and the project may lead to failure. It is essential that
employees need to put in an adequate amount of effort to run the process entirely. If the developers
don't have enough training and skill, they might develop a product without genuinely
understanding the principles behind the framework, which leads to ineffectiveness in the long run.
The second disadvantage is scrum is not suitable for plan-driven approach projects. Scrum is
designed for products that do not require extensive strategic planning before starting the
development process. It believes that the product development process may be figured out by using
customer feedback and other factors. On the other hand, scrum may not be the most suitable

11
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

solution for a plan-driven approach to project completion (Advantages and Disadvantages of

Scrum | Pros and Cons of Scrum, 2021).

2.2.2 Group Member 2 (Lau Jayxi)

The Spiral model is software development methodology that combines features of various
incremental prototyping methods with Waterfall model. Spiral model is known as best suited
model for large scale project that requires lots of planning and risk management. (Kienitz, 2017)
It has four stages of Planning Phase, Risk Analysis, Engineering Phase and Evaluation Phase that
are repeatedly passed through during the development processes in an iterative way that loops like
a spiral. (The Economic Times, 2021) The number of loops is not fixed but depending on the scale
of project. (Kienitz, 2017)

Figure 3: An example of detailed spiral cycle (Tech Receptives, 2021)

12
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.2.2.1 Features
In planning stage, the requirements are established with documentation of Business
Requirement Specifications ‘BRS’ and System Requirement Specifications ‘SRS’. The design
options are examined after understanding the goals of the project whilst considering the presence
of constraints such as costs, technology, and timescales. Next, the risk analysis involves identifying
which among different implementation approaches has lower risk but able to fulfil the goals within
the constraints. The engineering phase is the process where coding and integration take place with
Waterfall or incremental development processes. It has various testing and changes are made to
improve the system throughout the successive cycles and appraisals of the end product in each
cycle. The last stage, evaluation phase encompasses review of current output, the identification of
any critical issues, and the next spiral is continued to enhance the existing output or to take
corrective actions. (Kienitz, 2017)

2.2.2.2 Advantages and disadvantages

Since the number of spirals is depending on the evaluation of output, the model is
considered highly flexible and additional post-project functionality can be added easily. The risk
analysis phase in the loops will helps in avoiding risk and improve cost-effectiveness. It works
well for complex project and mission-critical developments with the repeating phases through the
iteration of loops. The end-product of spiral model is usually highly customised as it has strong
emphasis of customers’ approval. (Kienitz, 2017) However, the spiral model can be complicated
and costly to implement if spirals continue infinitely and resulted in heavy workload of
documentation. The risk analysis process may require specialist expertise and may affect greatly
on the success. The rules and protocols must be obeyed strictly throughout the stages and end
product is difficult to define before the final loop is executed. (Kienitz, 2017)

As MyCloths is establishing a completely new system from the manual system, the spiral
model can be implied to ensure the outcomes and details of functionality can satisfied the needs.
The functions can be developed part by part and several testing can be applied throughout the
spirals to keep improving the project output. Multiples meeting with MyCloths can be held for
reviewing the product part by part at the end of each spiral. The adjustment and corrective action
can be taken in the next spiral based on the feedback of MyCloths.

13
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.2.3 Group Member 3 (Preeta)

2.2.3.1 Features
The Waterfall Model is a sequential model for software development that divides the process into
pre-defined phases. Each phase must be completed before the next one can begin, and the phases
must not overlap. During the SDLC phase, each phase is designed to perform a specific activity
and conduce to the deliverables respectively. The focus is on planning, timelines, budgets, and the
simultaneous deployment of a whole system. Over the course of the project, rigorous control is
maintained thorough written documentation, formal evaluations as well as approval and signoff
by the user and information technology management at the end of most phases before moving on
to the next phase (ayanda hlongwane, 2016). The stages are always described by various names,
but the essential concept is that the first phase attempts to capture What the system will perform,
as well as its system and software requirements, while the second phase specifies How it will be
created. The developers begin writing code in the third stage, the system is tested in the fourth
stage, and the last stage focuses on implementation activities such as training and extensive
documentation (Awad, 2005).

Figure 4: The Waterfall Model (How to Use Task for Waterfall Project Management – A
Practical Guide for First Timers, 2019)

14
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.2.3.2 Strength
The waterfall model is suitable for most type of projects with well-defined requirements and needs.
The requirements document is regarded as the most important piece of documentation in traditional
software development. The key component of heavyweight techniques is based on the notion that
it is possible to capture all of a customer's needs upfront, prior to generating any code, making it
appealing to the software business. Gathering requirements, obtaining client approval, and then
ordering processes (additional documentation) to limit and control all changes gives the project a
predictability limit. Hence, it is also ideal for supporting less experienced project teams and project
managers, or project teams whose composition fluctuates (Awad, 2005). For the case study of
MyCloths, the team is new and the first to undertake this project. Since technical documentation
is a required component of the initial requirements phase, everyone must be clear about the goals.
Even during the maintenance phase, new developers or members can follow up with ongoing
processes rapidly.

Next is the definite determination of goals to be attained from the start. Committing to an end-
product or goal at the start is one of the Waterfall model’s strengths, and teams should resist
deviating from that commitment. For small projects with clear goals, the model ensures that the
team is aware of the general goal from the start, reducing the risk of going off-track in the specifics
as the project progresses. In the case study of this project, Waterfall, unlike agile methods, which
separates projects into distinct sprints, always bearing the overall goal in mind. Since our team has
a specific objective in mind with a deadline provided by MyCloths, Waterfall will help to avoid
becoming stymied as the team works toward it (Lucidchart, 2017)

Also, the transfer of information from on stage to another is precise and well-organized. Waterfall
is a highly methodical approach where each stage prioritises a clear transmission of information.
Every new phase in a software project involves a new group of employees, and even if this isn't
the case at one's organisation, the team should still strive to document information throughout the
project's lifecycle. As for the MyCloths project, different members are assigned in each stage of
the project. Therefore, the Waterfall model would be suitable as it prioritizes accessible
information for new team members to work along quickly if needed, whether it is passing projects
off at each phase or experiencing unexpected personnel changes. The orderly sequence of
development steps for ensuring the adequacy of documentation and design reviews helps ensure
the quality, reliability, and maintainability of the developed software (Lucidchart, 2017)

15
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.2.3.3 Weakness
Lack of flexibility is one of the biggest disadvantages for the waterfall model. There may be
challenges with the model's flexibility to accommodate new changes in requirements after the
initial consultation. When all planning is done up front, changes due to business strategies or
market factors may not have been taken into account. The approach allows little room for
unforeseen adjustments or changes. Pivoting will not be easy if the team has rigorously followed
the Waterfall phases nearly to the end of the project but then encounters an unforeseen obstacle
that needs a change in scope or goals (Lucidchart, 2017). Although MyCloths’ requirements are
pre-defined, it would be difficult to move back to the previous stage in case there is a sudden
change or additional requirements in the middle of the process as the waterfall model is rigid and
flows in a linear manner. Furthermore, changes can only be made during the maintenance stage,
after the product is deployed, making it cumbersome.

Secondly, the Waterfall methodology, being a process-oriented model, places very little emphasis
on the end user involvement in a project. Its primary goal has always been to assist internal teams
in moving more quickly through project phases, which is ideal for the software industry. Clients
in industries other than software, on the other hand, frequently want to be active throughout a
project, offering opinions and feedbacks as the project progresses (Lucidchart, 2017). There is a
high possibility of errors made while working on the product and problems are undetected until
the project is at the last stage, leaving huge and costly modifications as the only option. If
MyCloths project uses this methodology, the project is entirely dependent on the team with
minimal client involvement which may cause complications later on. In many cases, true two-way
communication between developers and clients does not begin until the client sees the actual model
in operation (Pal Kienitz, 2017).

Thirdly, waterfall methodology requires longer delivery time in a project. The waterfall paradigm
mandates long-term planning, which requires complete certainty of system’s requirements. At
every stage of the software development cycle, a detailed documentation is produced. For the
project to move forward from one phase to another, verification from the superiors after reading
all the documentation and deliverables at each stage is necessary (Smartsheet, 2019). Due to
waiting for their approval and signoff for each phase, longer time is taken to get the tasks done
causing a delay in the upcoming processes to commence. Using the waterfall methodology, the

16
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

project may take longer time to deliver which is inconvenient for the MyCloths as they wish for
quick production of the system within the time given.

2.3 Justification of Selected Methodology

2.3.1 Group Member 1 (Sushmita)
The methodology that is best suited for MyCloths is scrum methodology, while it falls under agile.
MyCloths has a strong vision of being the best in the market using technology to provide the best
possible customer service with the broadest range of traditional Malaysian cloths. The scrum
methodology strongly supports the vision of MyCloths. One of the strengths scrum holds is that it
adapts to changes and is very flexible. In traditional methods, it takes a long time to build a
functioning system entirely, so it might be out of the trend by the time the whole system is out to
the customer use. In this modern world, technology is rapidly evolving, and MyCloths would like
to stay on-trend. Scrum suits the criteria most because each sprint of scrum only takes from two to
four weeks. Even though the scrum team used a different tool previously, they have an opportunity
to change that if a new and better technology has been introduced. For example, if the developers
complete the web site's homepage in their first sprint and a new tool is launched during that period,
developers can use that to make the homepage look better in their next sprint. Not only that, but
the scrum team can also make changes based on the customer's feedback. MyCloths can publish
the part of the deliverable product at the end of the sprint and ask for feedback from the user. Since
the product is targeted at the customers, developers can change the looks and style of the webpage
based on customer's preferences. The customers will be engagement with MyCloths builds trust
and loyalty towards the company. It can draw more customers; therefore, MyCloths can easily be
the best in the market.

Furthermore, considering this is a brand-new experience for MyCloths, the scrum methodology
gives the freedom to MyCloths to adjust their requirements anytime. If MyCloths add a new
requirement to the product, it can be reviewed and added in the following sprint. Scrum also
provides flexibility to the developers and motivates them to be more innovative in building the
website. Since it is the first-ever website by MyCloths, the product must be unique and attractive
to customers. MyCloths can improve their quality of website at the end of each sprint with
flexibility.

17
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.3.2 Group Member 2 (Lau Jayxi)

The Agile Scrum Methodology is selected as it has effective cost control due to its processes with
approach of fixed timescales and gradual development of targeted goals. The output of the project
is released by functionality which ensure the productivity and efficiency considering the time and
cost spent. The structure of scrum that requires only a small team fulfils the criteria of this project
and with less people, the waste of cost can be reduced. The cost that requires to hire people is less
especially when scrum methodology works in a team that everyone is well equipped with
knowledge and skills for all aspects of the development processes. Since time is also crucial in
scrum methodology and cost is calculated by multiplying the cost per certain amount of time with
the time taken to release the output, the budget is easier to fixed under control. As the project
develops, the measurement of actual cost for the output at the moment will enable a more accurate
view of future cost estimation. This allows the cost-control of changing details of implementation
and project such as time or tools to keep cost under budget based on the future cost estimation.

In simpler terms, the approaches of Agile Scrum Methodology can enhance cost-effectiveness as
time taken to deliver the product is efficient and the cost is considered as minimum price
performance ratio based on the time taken and requirements of the development team. The
flexibility of Scrum allows cost controlling even in later stages of development which is the next
sprint. These properties of scrum can be used to handle the constraints of MyCloths to deliver the
system in fixed time and budget as mentioned.

18
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

2.3.3 Group Member 3 (Preeta)

The main reason Agile Scrum methodology is chosen for this project is because MyCloths wishes
to follow up with the development updates frequently for a faster product delivery. Hence this
methodology is suitable as the agile Scrum methodology aims to deliver a functional part of
the product to customers in every sprint which takes about 2 to 3 weeks each. Moreover, it
promises faster product delivery and it is scalable following the requirements compared to
structured and hybrid methodology. Like any other agile methodology, Scrum methodology is
iterative, involving frequent user feedback. It will become easier to deal with changes due to short
sprints and regular feedbacks from MyCloths’ manager and other stakeholders involved. This
strategy allows for rapid coding and testing of cutting-edge advancements (Brightlabs.com.au,
2021). Any errors present can be detected, and changes based on MyCloths feedback can be done
immediately without further delay. It is a minimally managed strategy that requires frequent
updates on work progress through regular meetings. As a result, the project's progress is clearly
visible for MyCloths’ stakeholders to review current updates through stand-up meetings that
occurs from time to time.

It is quicker to deliver a high-quality product on time compared to structured methodology which

may take around 6 to 9 months to start viewing the whole application of the online store. Since
scrum is based on self-organization, with the team itself deciding what to accomplish, there is no
need for higher-ups to intervene (Brightlabs.com.au, 2021). Being a people-oriented model, trusts
among the team developers and stakeholders of MyCloth is formed and the respective roles knows
best how to solve the problems posed. Therefore, the deliverables are produced at faster rate and
the project can be completed in the given timeline.

19
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

3. System Analysis
3.1 Data Mining
The science of analysing raw data in order to draw conclusions about it is known as data analytics.
Data analytics techniques and processes have been digitized into mechanical processes and
algorithms that operate on raw data. Trends and metrics that could otherwise be lost in a mass of
information can be discovered using data analytics techniques. Manufacturing firms, for example,
frequently recording the runtime and downtime, then analysing the data to better schedule
workloads for the machines to function at near-peak capacity. A company's performance can be
enhanced by using data analytics. Some of the data mining techniques include predictive analysis
and descriptive analysis (Investopedia, 2021).

Over the years, MyCloths has accumulated a number of historical data and therefore, data mining
and analysis is suitable by conducting a study to predict customer’s payment method preferences.
From the case study, the system should allow customers to be able to make payment for their
purchases online and be able to print or save the receipts once the payment has been made.

Figure 5: Pie chart – Using predictive analysis on customer’s payment methods (SaleCycle, 2019)

Hence, the predictive technique in data mining is used to analyse historical data pattern of
customers’ payment methods that is likely to arise again in the next few years (Investopedia, 2021).
Staff has to ensure the top payment methods that will be widely preferred should be included as
20
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

their customers’ online payment choices on the website. This analysis ensures that the diverse
payment methods can accommodate to customers different preferences all over Malaysia to offer
the best customer services nationwide.

Figure 6: A data analysis study on trend of sales during special occasions (Gesenhues, 2019)

Another example of utilising the same method is by studying the sales during festive season and
special occasions. From the graph, special occasions such as Thanksgiving and Black Friday
generates better sales compared to the normal weekend days over a period of 4 years. Therefore,
data mining will assist MyCloths in developing and implementing marketing strategies to forecast
sales for peak seasons, generating more profit than their competitors. This enables MyCloths’
stakeholder to re-allocate their resources in order to take advantage of potential future
developments and optimising operational efficiency (Investopedia, 2021). Thus, the inventory
management will ensure constant availability of all of their products during the peak seasons to
meet customers’ demands.

21
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

3.2 Statistical Analysis

Another method to analyse the data collected is Statistical Analysis, a technique to quantify
and make use of the data through several statistical operations performed. It provides observable
visualisation and pattern of the data through the implication of tools such as SAS Statistical
Analysis System, SPSS Statistical Package for the Social Sciences, and Stat soft. (Arora, 2021)
For statistical analysis, both the qualitative and quantitative data can be analysed with distribution
of continuous data under probability density function while discrete data distributed under
probability mass function. (Tyagi, 2020) In terms of descriptive statistics, the basic techniques that
can be implied easily to have the approximate understanding on distribution of the data are such
as min, mode, median, mean, standard deviation and variance. (Tyagi, 2020) The distribution of
data can be discovered and illustrated such as figure 7 to predict the possible or desired outcomes
for same event in the future. The other type of statistical analysis is inferential statistics which
utilize a random sample of data taken from a population to come up with deduction about the
whole population. (Tyagi, 2020) The probability distribution, correlation testing and regression
analysis are the techniques that best represent inferential statistics. (Tyagi, 2020) Inferential
statistics provide the study of the relationship between the variables and the results are usually
displayed such as figure 8.

Figure 7: Example of Descriptive Statistics

22
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

Figure 8: Example of Inferential Statistics (Correlation Analysis)

In this project, the descriptive statistic can be implied to discover the pattern on how
variables are distributed and the correlation in between the data collected so that decisions making
on what and how the functions details will be are firmed. First, the type of cloth that majority of
the customer preferred can be figured through descriptive statistics, the study of mean, mode, and
standard deviation on the number of each cloth type sold every month. The extra function of
reminder for updating inventory can be append if the patterns of outcomes are not similar to one
another. This is due to similar opinions of the customer preference towards different type of cloths
that will result in consistent difference of sales for the cloths. The function helps to ensure there is
sufficient stock all the time for all the different type of cloths and manage the inventory easier
based on the possible sales and the risk of loses can be reduced. Looking from another perspective,

23
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

the inferential statistics of correlation testing can be implemented to evaluate the strength of
relationship in between the age group of customers and their adaption to the system. Since the
product of MyCloths are not considered as daily needs for all age group, the adaptability to the
new system or online store of the targeted customers has to be considered so that design of system
is user friendly and suitable whilst meeting the needs.

24
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

3.3 List of Requirements

These are the requirements have been gathered from the system analysis and problem statement
using PIECES framework.

1. System should have an inventory that can be managed by the staff. (Refer to 1.2.1.1
Throughput)
2. System should generate a purchase order when the inventory is low for respective suppliers,
delivery order and goods received note. (Refer to 1.2.2.1 Output)
3. The website should be free for the customers to browse the products. (Refer to 1.2.1.1
Throughput)
4. All the customers should be registered as a member to purchase. (Refer to 1.2.2.3 Stored
Data)
5. System should have features to allow the members to view the cloths, read and reviews
and compare the cloths with others. (Refer to 1.2.4 Control)
6. System should allow the members to write reviews once the product delivered. (Refer to
1.2.2.2 Input)
7. System should allow the members to add product they wish to purchase into the shopping
cart. (Refer to 1.2.5 Efficiency)
8. The website’s shopping cart should show the summary of selection and the total cost.
(Refer to 1.2.2.1 Output)
9. System should generate a receipt of the purchase. (Refer to 1.2.2.1 Output)
10. System should generate a shipping note after each purchase. (Refer to 1.2.2.1 Output)
11. System should be able to manage all the information about every product. (Refer to 1.2.5
Efficiency)
12. All the information regarding customer feedback and products ratings should be stored in
the system. (Refer to 1.2.2.3 Stored Data)
13. System should have a feature allowing to manage customer delivery. (Refer to 1.2.4
Control)
14. System should generate daily, weekly, monthly, and yearly reports of sales based on
different types of cloths. (Refer to 1.2.2.1 Output)
15. System should generate report of members who are entitled to all the benefits given. (Refer
to 1.2.2.1 Output)

25
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

4. References

1. 2021. Advantages and Disadvantages of Scrum | Pros and Cons of Scrum. [online]
Available at: https://kandra.pro/blog/advantages-and-disadvantages-of-scrum/ [Accessed
5 August 2021].
2. Airfocus.com. 2021. What Are Agile Principles? Definition and Examples & FAQ. [online]
Available at: <https://airfocus.com/glossary/what-are-agile-principles/> [Accessed 3
August 2021].
3. Arora, S. K., 2021. What is Data Analysis? Methods, Techniques & Tools. [Online]
Available at: https://hackr.io/blog/what-is-data-analysis-methods-techniques-tools
[Accessed 9 8 2021].
4. Awad, M.A. (2005). A comparison between agile and traditional software development
methodologies. [online] University of Western Australia, 30. Available at:
https://d1wqtxts1xzle7.cloudfront.net/58993716/10.1.1.464.609020190422-13963-
j0ju8a-with-cover-page-v2.pdf?Expires=1628766953&Signature=Bg~zLoz-
ThOvAa3SAeum0xUdMX6DK96dxBAN0WxUJSVe9gXvWV2fmX7xJz2FYxguF5K5D
Ad7X60vX0p~1oG1OMWXU2iTKLQtmLXpH0zL4RtpRpEHKzqPefTMJ3SJ3N4Kln~
3j~5lSlk7cPV-
g3ki3wtfTwzqQVXbFBhWCpghrj62zxdrI4JrlwJqDkbYDCgxse6p4aqCKSJQdmDT129I
qivBWBtLerw7WqkYTAIpHTmsusAd1hsJs5vRywEcDbarze1mLm9Du6IgldS-g-
NKHZrHukrpFL~IHrjw7L0S5X41edR7X5zmBxnSicbTnh3BIQ~sFMbBqm6nMqT7D5
M0Uw__&Key-Pair-Id=APKAJLOHF5GGSLRBV4ZA.
5. ayanda hlongwane (2016). SELECTING A DEVELOPMENT APPROACH. [online]
Academia.edu. Available at:
https://www.academia.edu/22583615/SELECTING_A_DEVELOPMENT_APPROACH
[Accessed 10 Aug. 2021].
6. Brightlabs.com.au. (2021). SCRUM methodology in web development. [online] Available
at: https://www.brightlabs.com.au/insights/scrum-methodology-in-web-development
[Accessed 10 Aug. 2021].

26
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

7. Digite. 2021. What Is Scrum Methodology? & Scrum Project Management. [online]
Available at: <https://www.digite.com/agile/scrum-methodology/> [Accessed 5 August
2021].
8. How to Use nTask for Waterfall Project Management – A Practical Guide for First Timers
(2019). How to Use nTask for Waterfall Project Management - A Practical Guide for First
Timers - nTask. [online] nTask. Available at: https://www.ntaskmanager.com/blog/how-
to-use-ntask-for-waterfall-project-management-a-practical-guide-for-first-timers/
[Accessed 10 Aug. 2021].
9. Investopedia. (2021a). Data Analytics Definition. [online] Available at:
https://www.investopedia.com/terms/d/data-analytics.asp [Accessed 11 Aug. 2021].
10. Investopedia. (2021b). Predictive Analytics Definition. [online] Available at:
https://www.investopedia.com/terms/p/predictive-analytics.asp [Accessed 11 Aug. 2021].
11. Kanban Software for Agile Project Management. (2021). The 12 Agile Project
Management Principles Explained. [online] Available at:
https://kanbanize.com/agile/project-management/principles [Accessed 10 Aug. 2021].
12. Kienitz, P., 2017. The pros and cons of Spiral Software Development. [Online] Available
at: https://www.dcsl.com/pros-cons-spiral-software-development/ [Accessed 8 8 2021].
13. Knowledgehut.com. 2019. 4 Features That Make Scrum Successful. [online] Available at:
<https://www.knowledgehut.com/blog/agile/4-features-that-make-scrum-successful>
[Accessed 5 August 2021].
14. Lucidchart. (2017). The Pros and Cons of Waterfall Methodology. [online] Available at:
https://www.lucidchart.com/blog/pros-and-cons-of-waterfall-methodology [Accessed 10
Aug. 2021].
15. Plutora. (2019). The 12 Agile Principles: What Are They and Do They Still Matter? -
Plutora. [online] Available at: https://www.plutora.com/blog/12-agile-principles
[Accessed 9 Aug. 2021].
16. Product Plan, 2021. Agile Principles. [Online] Available at:
https://www.productplan.com/glossary/agile-principles/ [Accessed 6 8 2021].
17. Productplan.com. (2020). Agile Principles. [online] Available at:
https://www.productplan.com/glossary/agile-principles/ [Accessed 10 Aug. 2021].
18. Productplan.com. 2021. Agile Principles. [online] Available at:
<https://www.productplan.com/glossary/agile-principles/> [Accessed 3 August 2021].

27
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

19. SaleCycle. (2019). Which Ecommerce Payment Options do Customers Want? - SaleCycle.
[online] Available at: https://www.salecycle.com/blog/strategies/which-ecommerce-
payment-options-do-customers-want/ [Accessed 11 Aug. 2021].
20. Scrum.org. (2019). Where Does the Efficiency and Speed from Agile Come From? [online]
Available at: https://www.scrum.org/resources/blog/where-does-efficiency-and-speed-
agile-come [Accessed 10 Aug. 2021].
21. Scrum.org. 2021. What is Scrum?. [online] Available at:
<https://www.scrum.org/resources/what-is-scrum> [Accessed 5 August 2021].
22. Smartsheet. (2019). Waterfall. [online] Available at: https://www.smartsheet.com/content-
center/best-practices/project-management/project-management-guide/waterfall-
methodology [Accessed 10 Aug. 2021].
23. Tech Receptives, 2021. Spiral Methodology. [Online] Available at:
https://techreceptives.com/development-methodology-spiral [Accessed 10 8 2021].
24. The Economic Times, 2021. Definition of 'Spiral Model'. [Online] Available at:
https://economictimes.indiatimes.com/definition/spiral-model [Accessed 8 8 2021].
25. Tryqa.com. (2021). What is Waterfall model- Examples, advantages, disadvantages &
when to use it? [online] Available at: http://tryqa.com/what-is-waterfall-model-
advantages-disadvantages-and-when-to-use-it/#Disadvantages_of_waterfall_model
[Accessed 10 Aug. 2021].
26. Tyagi, N., 2020. Introduction to Statistical Data Analysis. [Online] Available at:
https://www.analyticssteps.com/blogs/introduction-statistical-data-analysis [Accessed 9 8
2021].

28
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

5. Appendix
5.1 Detailed workload matrix

29
CT046-3-2 SDM – SYSTEM DEVELOPMENT METHODS APU DEGREE – LEVEL 2

5.1 Workload matrix summary

30