ATMC ICT700: System Analysis Report on Agile Methods for OZES

This report provides a system analysis of Australian Electric Supply (OZES), focusing on agile methodologies for system development. It discusses Extreme Programming (XP), Lean Software Development, Agile Scrum, and Dynamic System Development Method (DSDM), outlining the advantages and disadvantages of each. The report recommends the Scrum methodology for OZES, highlighting its diverse team skills and adaptability to project changes. It includes an event table, use case diagram, use case description, domain model class diagram, and design class diagram. The memo also touches upon User-Centered Design (UCD) and Human-Computer Interaction (HCI) principles for system design, emphasizing user experience and visual appeal. The document concludes with references and an appendix detailing the memo regarding UCD and HCI design techniques.

Australian Electric Supply (OZES)
Agile Methods and Memo
6/3/2019

Australian Electric Supply
Table of Contents
Agile & Iterative Systems Development...............................................................................................2
Extreme Programming (XP)..............................................................................................................2
Discussion.....................................................................................................................................2
Set of Advantages..........................................................................................................................2
Set of Disadvantages.....................................................................................................................2
Lean Software Development.............................................................................................................2
Discussion.....................................................................................................................................2
Set of Advantages..........................................................................................................................3
Set of Disadvantages.....................................................................................................................3
Agile Scrum.......................................................................................................................................3
Discussion.....................................................................................................................................3
Set of Advantages..........................................................................................................................3
Set of Disadvantages.....................................................................................................................3
Dynamic System Development Method (DSDM).............................................................................4
Discussion.....................................................................................................................................4
Set of Advantages..........................................................................................................................4
Set of Disadvantages.....................................................................................................................4
Recommended Methodology.............................................................................................................4
Event table.............................................................................................................................................5
Use case diagram...................................................................................................................................6
Use case description..............................................................................................................................6
Domain model class diagram.................................................................................................................8
Design class diagram.............................................................................................................................9
References...........................................................................................................................................10
Appendix.............................................................................................................................................11
1

Australian Electric Supply
Agile & Iterative Systems Development
There are a number of system development methodologies that have been defined which may
be considered by the leaders and senior managers of OZES. The methodology that is
recommended for the project is agile and iterative for developing the system. There are
numerous techniques and sub-methods defined under these. These agile methods are
recommended for the OZES case as they provide adaptive procedures that can be followed
and utilized for system development.
Extreme Programming (XP)
Discussion
It is thee agile procedure in which the software code or package is developed with enhanced
quality and the time to develop is less. It is certain that there are some modifications
requested by the customers during the development phase. The XP method allows the
incorporation of the change and there is increased collaboration maintained with the
customers for obtaining their feedback. The method considers communication and feedback
as the two basic pillars for any project (Kunwar, 2018).
Set of Advantages
 The changes during the development phases can be easily included.
 Maintenance of increased transparency with the customers.
 The time to develop and deploy is less and there are quick deliveries involved.
Set of Disadvantages
 There is lesser focus on the product design and a lot of priority is given to the code.
 Quality assurance is an activity that emerges late in the lifecycle.
Lean Software Development
Discussion
Lean development is also a method that is included in the set of agile methods. It is the
development methodology that applies the lean concepts to the software development
activities to achieve the desired results. The development tasks are conducted as per the value
streams and these are used to determine the project objectives and processes. There are lean
concepts, such as elimination of wastes, enhancement of quality, and customer collaboration
2

Australian Electric Supply
included so that the development work is streamlined and meets the customer expectations
(Akella and Rao, 2016).
Set of Advantages
 The customers are collaborated to make sure that the overall quality of the product is
improved.
 The elimination of the waste processes and activities is done so that time and
resources are not wasted.
 There are cross-functional teams involved.
Set of Disadvantages
 The overall complexity of the development work and activities may be high.
 The lack of explicit schedule definition may lead to the emergence of ambiguities in
the project (Ko and Chung, 2014).
Agile Scrum
Discussion
Scrum is one of the most popular methods under the agile methodology that offers iterative
development of the software. There is incremental approach followed and the project
requirements are defined and included in the Product Backlog. The project runs in a series of
sprints. The duration of these sprints is two to four weeks and the number of members in the
agile team is 4 to 7. There is a Scrum Master that is responsible for the streamlined execution
of the development process (Ashbacher, 2010).
Set of Advantages
 The members involved in the agile teams have diverse and cross-functional set of
skills.
 The changes in the project can be handled and tackled and there is customer
interaction processes conducted at the end of the sprint.
 There are limited roles and teams members included so that the distribution of the
roles is carefully done.
Set of Disadvantages
 There are cases wherein the inadequate skills of the Scrum Master lead to the
significant issues in the project and may also lead to the project failures.
3

Australian Electric Supply
 The changes in the project cannot be handled during the sprint lifecycle. They can be
incorporated in the next sprint only (Rajasekaran, 2015).
Dynamic System Development Method (DSDM)
Discussion
DSDM is the agile method in which it is made sure that the project runs on time and the
project budget is also adhered with. The development process in this case is based on eight
management and development principles. The priority is given to the customer requirements
and customer needs. It is made sure that the customer expectations are always fulfilled and
the schedule and budget is adhered with at all times (Sharma, 2019). The methodology also
ensures that the dynamic development is synced with the managerial tasks and processes so
that the adherence with the best practices and project guidelines is always maintained.
Set of Advantages
 There are numerous risks normally associated with the estimated project schedule and
budget. Such risks are prevented with this methodology.
 There are specific guidelines shares with the project team members along with the
information on best practices and principles to follow.
 There is detailed communication process used in this case.
Set of Disadvantages
 The methodology may take longer to accomplish the project activities as compared to
the rest of the methods.
 There are cases wherein the inadequate skills of the project resources lead to the
significant issues in the project and may also lead to the project failures. .
Recommended Methodology
The methodology that is recommended for this case is the Scrum agile methodology for
system development.
The methodology has been recommended because the members involved in the scrum teams
have diverse and cross-functional set of skills. As a result, there is optimum distribution and
utilization of the resources that can be done with ease. The changes in the project can be
handled and tackled and there is customer interaction processes conducted at the end of the
sprint. In these interaction processes, the customers are provided with the working set of the
products and are asked for their feedback. The feedback provided is included in the next
4

Australian Electric Supply
sprint so that the customer expectations can be fulfilled. There are limited roles and teams
members included so that the distribution of the roles is carefully done. All of the members in
the team are aware of the tasks they need to perform.
The set of disadvantages associated with the methodology can also be avoided using the
adequate approach and analysis in advance for the project. The use of scrum methodology
will provide OSEZ with the required development framework and will also ensure that the
ad-hoc development is carried out.
Event table
Event Event
Type
Trigger Source Activity/Use
Case
System
Response/
Output
Destination
New
customer
wants to
register
Internal New
customer
Custome
r
Register New
customer
has been
added
OZES,
Customer
OZES
management
wants to add
broker
Internal New broker OZES Add broker New broker OZES ,
broker
OZES
management
sells
second-
handed item
Internal New sale OZES Sell Second-
handed item
New sale of
second hand
item has
been
recorded
OZES,
Broker
OZES wants
to calculate
broker’s
commission
Internal Create
commission
record
Associate
broker
Calculate
commission
Commission
of the
broker has
been
calculated.
OZES,
broker
5

Australian Electric Supply
Use case diagram
6

Australian Electric Supply
Use case description
7
Use Case Sell second-handed item
Scenario Associate broker finds a second hand item to sell.
Triggering Event OZES decides to sell the received second handed
item.
Description OZES sells a second-hand item received from the
associate broker.
Actors OZES employee, associate broker, broker
Related Use Case N/A
Stakeholders 1. OZES employee
2. Associate broker
Pre-Condition Customer is able to view all items
Post-Condition Second-Handed item got purchased successfully.
Flow of activities
Actor System
1) Customer selects items from second-
hand category.
3) Customer chooses an item and click
on “purchase” button.
5) Customer provides payment details.
2) System displays second-hand item list.
4) System takes customer to payment confirmation
step.
6) Returns newly created order no.
Alternate Course of Action 5.1 Incorrect details shows error message and asks
customer to re-enter them.

Australian Electric Supply
Domain model class diagram
8

Australian Electric Supply
Design class diagram
9

Australian Electric Supply
References
Akella, P. and Rao, K. (2016). An approach for using lean process in agile software
development. International Journal of Latest Trends in Engineering and Technology, 8(1).
Ashbacher, C. (2010). Succeeding With Agile: Software Development Using Scrum, by Mike
Cohn. The Journal Of Object Technology, 9(4). doi: 10.5381/jot.2010.9.4.r1
Javaid, M. (2013). Review and Analysis of Human Computer Interaction (HCI) Principles.
SSRN Electronic Journal. doi: 10.2139/ssrn.2333608
Ko, C. and Chung, N. (2014). Lean Design Process. Journal of Construction Engineering and
Management, 140(6), p.04014011.
Kunwar, S. (2018). Scenario Based Requirement Engineering (SBRE) in eXtreme
Programming (XP) through Agile Modelling (AM). SCITECH Nepal, 13(1), 9-15. doi:
10.3126/scitech.v13i1.23496
Natda, K. (2013). Responsive Web Design. Eduvantage, 1(1). doi: 10.11635/2319-
9954/1/1/18
Proctor, R. and Vu, K. (2015). Principles for Designing Interfaces Compatible With Human
Information Processing. International Journal of Human-Computer Interaction, 32(1), pp.2-
22.
Rajasekaran, V. (2015). Issues in Scrum Agile Development Principles and Practices in
software development. Indian Journal Of Science And Technology, 8(35). doi:
10.17485/ijst/2015/v8i35/79037
Sharma, A. (2019). A Comparative Analysis of Agile Methods for Core Banking Software,
XP Versus DSDM. International Journal Of Communication And Media Studies, 9(3), 85-90.
doi: 10.24247/ijcmsjun20199
Terblanche, J. (2014). Using HCI Principles to Design Interactive Learning Material.
Mediterranean Journal Of Social Sciences. doi: 10.5901/mjss.2014.v5n21p377
10

Australian Electric Supply
Appendix
To: The Senior Management
From: Project Manager
Date: 3rd June 2019
Subject: UCD and HCI Design techniques & principles for the project
The memo covers a brief introduction and details of the two design approaches and
frameworks that shall be used for the project. System design is one of the essential tasks
under the domain of development lifecycle and the design shall be tactfully done to
streamline the further development processes.
The design of the system provides its blueprint which is used in the development processes.
The design is also directly associated with the user experience and connection with the
system. Therefore, the design of the front-end shall be done as per the user expectations and
with a motive to gain increased user experience levels. There are some of the design
approaches that can be used for the purpose. One of such approach is User Centred Design
(UCD) in which the system design is done as per the end-user expectations. The expectations
of all the different end-user groups is gathered and used to carry on with the system design.
There are also some of the design principles defined under the domain of Human Computer
Interaction (HCI) principles that facilitate increased interaction between the machine and the
end-user for system development.
There is a lot of focus that shall be made on the system design. This is because such an
information system is being developed and implemented for OZES for the first time. The
employees and managers will like the system to have an enhanced design so that they may
understand the system functionalities with ease. Also, the visual appeal will play a great role
in ensuring that the users connect with the system and understand the specific workflows as
well. The use of adequate design methodologies will, therefore, be essential to meet the user
expectations.
There are numerous design principles defined and the user centred design shall be
implemented using the responsive design technique. There will be different users that will
access the system. The expectations of these users will vary from one another. There may be
11

Australian Electric Supply
users that may wish to have the high system resolution while some may prefer moderate
levels. There may also be some users that may access the system on their laptops and other
mobile devices in the landscape mode while some may access them in portrait mode. The
system shall be responsive and the UI elements shall be adjusted as per the mode or option
selected by the user (Natda, 2013). In this manner, the users will feel connected with the
system and will be able to explore the system functions. The system responsiveness will be
an essential element.
There are also a number of design principles that must be adhered with. The error resolution
is one of the primary principles for this case. It is because all of the system users will be new
and inexperienced with such a system. As a result, these users will carry out a number of
errors and will wish to roll back their actions at certain points. Thus, the users must be
provided with error resolution schemes so that the error handling is adequately done and the
user experience is enhanced. Navigation is one of the most significant UI aspects of such
systems and there shall be smooth navigation maintained in this case. The smoothness shall
be assured in terms of the single screen and in between the screens as well. The placement of
the UI elements shall be done such that there is no-overlapping of the contents at any times.
The whitespaces shall also be avoided so that the users have enhanced visual experience with
the system (Proctor and Wu, 2015). One of the most important design principles and elements
will be consistency of the elements. The consistency levels shall be maintained across all the
screens and levels. The system shall be consistent in terms of the layout, colors used,
placement of sections, and all the other UI elements. The color scheme, system language, font
face, font size, etc. are some of the elements that user shall be able to customize. The
personalisation of the system as per the desired look & feel for the customers shall be made
possible (Javaid, 2013).
We will be able to achieve enhanced levels of user experience with adherence to these
principles and design approach (Terblanche, 2014). Please take a look at these principles and
recommend any changes or improvements that can be done for the user experience of the
system.
Best Regards,
Project Manager
12