Agile System Development Methodologies for OZES Case Study

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.