ATMC ICT700 System Analysis and Design Report: OZES Case

This report provides a comprehensive analysis of the OZES case, an Australian Electric Supply company seeking a new system for standard reporting. It compares four Agile development methodologies: Scrum, Feature Driven Development (FDD), Lean Software Development, and Kanban. The report recommends Scrum due to its emphasis on customer satisfaction through constant involvement and its ability to prioritize software functionality via product backlog creation. The analysis includes an event table, use case diagram, use case description, domain model class diagram, and design class diagram. The report highlights the advantages and disadvantages of each methodology, ultimately concluding that Scrum is the most suitable approach for OZES to meet its requirements and achieve a valuable, functional solution. The report also acknowledges the importance of understanding the client's needs and the associated risks of each development methodology before choosing a particular approach.

SYSTEM ANALYSIS AND DESIGN 1
System Analysis and Design
Student Name
Institution
Date

SYSTEM ANALYSIS AND DESIGN 2
Executive Summary
This report has described the different approached that OZES can adopt in developing
the system by comparing the different Agile development methodologies. The papers have
compared four Agile techniques including Scrum, feature driven development, Lean software
development approach, and Kanban. All these approaches are applicable to the OZES case
but the report has recommended Scrum. This is because it ensures that customer satisfaction
due to constant involvement of the customer (product owner). Additionally, this approach
focuses on finding and prioritizing software functionality through creation of product backlog
which consists of all the activities that needs to be done on order to deliver a workable
product. As such, by employing this approach OZES will not only meet its requirements but
also achieve a highly valuable and functional solution.

SYSTEM ANALYSIS AND DESIGN 3
Table of Contents
Executive Summary...................................................................................................................2
Introduction................................................................................................................................4
Consultation...............................................................................................................................5
Feature Driven Development (FDD).....................................................................................5
Discussion..........................................................................................................................5
Advantages.........................................................................................................................5
Disadvantages of FDD.......................................................................................................6
Scrum.....................................................................................................................................6
Discussion..........................................................................................................................6
Advantages.........................................................................................................................6
Disadvantages....................................................................................................................6
Lean Software Development Approach.................................................................................7
Discussion..........................................................................................................................7
Advantages.........................................................................................................................7
Disadvantages....................................................................................................................7
Kanban Software Development Methodology.......................................................................8
Discussion..........................................................................................................................8
Advantages.........................................................................................................................8
Disadvantages....................................................................................................................8
Analysis of the Case...................................................................................................................9
Event Table............................................................................................................................9
Use Case Diagram................................................................................................................10
Use case description.............................................................................................................10
Domain Model Class Diagram.............................................................................................11
Design Class Diagram..........................................................................................................12
Conclusion................................................................................................................................12
References................................................................................................................................13
Appendix: Memo.....................................................................................................................15

SYSTEM ANALYSIS AND DESIGN 4
Introduction
Agile application development methodology is an iterative development approach that
has been adopted to substitute the traditional application development approaches that have
been for a very long time associated with overbudgeting and missing deadlines. In agile
system development solutions are improved and evolves by collaboration and cooperation
between cross-functional teams that organize themselves towards meeting the requirements
and goals of the client (Altameem, 2015). Whereas agile method offer numerous benefits
does not mean that the traditional techniques should not be used. Before choosing a particular
development methodology, it is important to first understand the client’s case and choose the
best method that fits that particular case. Additionally, it is necessary to have strong
knowledge on the various risks associated with the chosen method to enable the team to
prepare itself for any pitfalls that may arose during the project (Tasneem, Mahmoud and
Kholief, 2016).
This report aims at discussing the OZES case. OZES is an Australian Electric Supply
company that is growing and supplies electrical components across Australia. The company
wishes to have a system that will facilitate and provide a standard reporting capability o
commission earned and volume of sales at the end of every month and also provided
generation of custom reports. Currently, the associate brokers lack standard reporting
mechanism and this makes it difficult for the company to compile a comprehensive report
that will give meaningful information to the top management. The report will propose four
different Agile system development techniques that can be adopted by the company to build a
system that will meet its requirements. The diagram below illustrates the processes involved
in Agile development methodology.

SYSTEM ANALYSIS AND DESIGN 5
Figure 1: Agile Development Methodology (Tasneem, Mahmoud and Kholief, 2016)
Consultation
This section will discuss the various Agile techniques that the report recommends to
be used by OZES while developing its system. There are a number of Agile methods but the
report will limit the discussion to only four of them including Feature Driven Development,
Scrum, Lean Software Development (LSD), and Kanban. Other Agile approaches that may
be relevant to the case but will not be discussed include adaptive software development,
Agile Unified Process, Crystal, Agile Modelling, Dynamic System Development Method,
and extreme programming (XP. Each of these method fits specific cases.
Feature Driven Development (FDD)
Discussion
Feature-driven development method focuses on quality aspects and puts more
emphasis on design and building stages throughout the development cycle and involves
regular and feasible deliveries together with accurate monitoring of the project progress. It is
powerful but easy to understand approach of developing software solutions (Carrera, Iglesias
and Garijo, 2013). FDD can be a good approach for OZES because t best works for small to
medium sized teams.
Advantages
There are several befits that FDD offers to the development team including:

SYSTEM ANALYSIS AND DESIGN 6
 Best suits situations where regular update of the product is required and where value
delivery is necessary.
 The development team can easily identify their roles in the project because FDD has
one of the best and well-documented development practices. This enables successful
delivery of the project objectives.
 Better products are iteratively produced than the previous ones
Disadvantages of FDD
Some of the cons associated with feature-driven development approach include:
 It is not applicable in situations where the development process is a one-man show or
is made up of a smaller team of two to three people.
 Also, it cannot be used in small projects with tight schedules and deadlines
 The success of the project is fully dependent on the skills of the team
Scrum
Discussion
This is a practical method to product development. This approach uses iterative
technique with a minimum viable product (MVP) always tested after every iteration process
which normally takes 14 to 28 days (Alam, 2012). New functions and features are added after
very iteration until the product has met the business requirements completely and is ready for
release. OZES can adopt this approach because it allows the customer to adjust the business
requirements during the development process when need arises.
Advantages
Some of the advantages associated with Scrum include:
 It is recommended for project that requirements may change during the development
cycle because it is highly adaptive to changes in requirements (Qureshi, 2012).
 There is a greater level of transparency because the customer or the owner of the
product being developed is constantly involved in the project.
 Unnecessary features and bugs are removes and addressed quickly because testing is
done after every iteration.
Disadvantages
Some of the disadvantages associated with Scrum include:

SYSTEM ANALYSIS AND DESIGN 7
 Changes in requirements are rarely documented meaning that the project can take a
different direction than the one intended during the inception of the project.
 This approach requires that a skilled Scrum master be present to control a project and
ensure that all the developers are moving in the right direction.
 There is constant adjustment of project schedule and timelines because of regular
changes in requirements which may lead to delayed delivery of the product.
Lean Software Development Approach
Discussion
This is a software development approach that requires adding requirements that offers
the most value if the requirements need to be changed. Additionally, the added requirements
should use the least budget and effort and can only take 30% of the expected time (Ibrahim
Alzoubi, Qumer Gill and Al-Ani, 2015). This methodology traces its roots to TOYOTA
which has facilitated the company to create a workflow to use the same constructing
conveyors to build different car models. The same case applies to OZES, the approach can
help in developing a system that has consistent design but producing different results.
Advantages
Some of the advantages associated with Lean development methodology include:
 It is cheaper as compared to the first two approaches because the expenses are
relatively low (Mukhopadhyay and Gupta, 2019).
 Fast delivery of minimum viable product
 The team is focused not only on accomplishing the objectives but making each feature
of the product perfect.
Disadvantages
This approach is faced with some disadvantages including:
 This approach required precise documentation and a product analyst that is skilled to
make sure that the requirements are fully understood.
 This approach can only apply for developers who are highly skilled and have
sufficient knowledge in the discipline (Memmel and Obendorf, 2013).
 The developers may lose focus by focusing more on delivering high quality product
that focusing on meeting the user requirements.

SYSTEM ANALYSIS AND DESIGN 8
This approach works well when the project being undertaken is aimed at improving an
existing product.
Kanban Software Development Methodology
Discussion
Kanban is an Agile approach to software development that is aimed at complementing
other development methodologies. This approach emphasizes on identifying the most crucial
features on the current development process, pinpoint the areas that requires improvement,
and show the effort that has already been placed on the project (Kim, 2016). This is aimed at
finding and seeking perfection in each future of the product being developed. The
development team can select one of the approaches discussed above and complement it with
Kanban approach to achieve the most ideal results and solution.
Advantages
Kanban has a number of advantages including:
 The work in progress (WIP) is limited to only the most crucial features so a to keep
the number of requirements changes minimal and increase the speed of the process of
development (Lee, 2010).
 No additional training or investment tools is required by the development team.
 This approach ensures that the development team is on track and helps maintain the
hand on the product development pulse.
Disadvantages
 This approach is less practical in projects with longer deadlines because sticky notes
cannot predict time frames.
 Does not support prioritization of project tasks because every task is equally essential.
This approach works best when smaller teams are involved in polishing the software
where regular updates is needed and drives value.

SYSTEM ANALYSIS AND DESIGN 9
Analysis of the Case
Event Table
Event Trigger Source Activity Response Destination
Store
manager
registers
customer
Customer’s
registration
details
customer Register
customer
Confirmation of
registration
Store
manager
Sell second
hand item
Customer
wants to buy
the item
Associate
broker
Sell item Item sold Associate
broker
Update
trust
account
Customer
makes payment
to trust account
run by OZES
Customer Process
payment
Successful
payment. Email
sent to broker
Associate
broker
Contact
OZES
Customer
recommended
by other users
Customer Contact
the
company
Communication
established
Associate
broker

SYSTEM ANALYSIS AND DESIGN 10
Use Case Diagram
Figure 2: Use case diagram (Satzinger, Burd and Jackson, 2016)
Use case description
Use case name Sell second hand item
Scenario Sell item to interested customer
Triggering event Customer wants to buy item
Brief description The associate broker promotes the item on
various channel, and when a customer
shows interest to buy the item, he/she
contacts OZES to check for the availability
of the item. Associate broker is notified that
the customer has purchased and paid for the
item
Actors Associate broker
Stakeholders Sales, marketing, warehouse manager
Preconditions Customer must express interest to buy the
item

SYSTEM ANALYSIS AND DESIGN 11
Customer must be willing to pay for the
mentioned price
The item must exist
Post Conditions Item is sold to the interested customer
Broker is notified via email that the item has
been sold and paid for.
Associate broker updates his/her records
Trust account is updated
Domain Model Class Diagram
Figure 3: Domain Model Class Diagram (Satzinger, Burd and Jackson, 2016)

SYSTEM ANALYSIS AND DESIGN 12
Design Class Diagram
Figure 4: Design Class Diagram for Associate broker and order (Satzinger, Burd and Jackson,
2016)
Conclusion
This report recommends Scrum methodology to be used because it ensures that
customer satisfaction due to constant involvement of the customer (product owner).
Additionally, this approach focuses on finding and prioritizing software functionality through
creation of product backlog which consists of all the activities that needs to be done on order
to deliver a workable product. As such, by employing this approach OZES will not only meet
its requirements but also achieve a highly valuable and functional solution.