ATMC ICT700: System Analysis and Design Report - Agile Methodologies

This report provides a comprehensive analysis of system design and agile methodologies. It begins with a consultation on various agile and iterative systems development methodologies, including Scrum, Kanban, Extreme Programming (XP), and Lean Development, evaluating their advantages and disadvantages. The report then delves into a case study, detailing use case diagrams, use case descriptions, domain model class diagrams, and design class diagrams related to a system for the Australian Electric Supply organization (OZES). Furthermore, the report includes a memo discussing User-Centered Design (UCD) and Human-Computer Interaction (HCI) and their implications for developing an automated system for OZES. The document showcases the application of these methodologies and concepts in a practical context, highlighting their importance in system development.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Consultation.................................................................................................................................2
2. Analysis of Case..........................................................................................................................6
Use Case Diagram.......................................................................................................................8
Use Case Description...................................................................................................................9
Domain Model Class Diagram..................................................................................................11
Design Class Diagram...............................................................................................................12
3. Memo.........................................................................................................................................12
Bibliography..................................................................................................................................15

2SYSTEM ANALYSIS AND DESIGN
1. Consultation
The agile and iterative systems development methodologies is a considered as a process that
can manage a project by diving the project in multiple stages as well as providing constant
collaboration with all stakeholders and includes continuous improvement within the project. This
iterative agile method includes iteration of process in each stage of the project (Anwer et al.
2017). This methodology basically begins with explanation of the customers about how the
product will be completed and the problem that the developing product or system will solve with
the completing of the project. This helps in clarifying the expectations of the project team. Four
types of agile and iterative systems development methodologies are explained below that can be
helpful for developing the management system of the OZES organization.
Methodology: Scrum Methodology
Discussions: The scrum methodology is the most efficient methodology that is used in
agile frameworks (Alqudah and Razali 2016). This methodology is defined by the cycles or the
states that are included in the system. These cycles or states are known as sprints. The scrum
methodology helps to maximize the time of developing a software product. This method is
mainly used for managing the projects that develop software products.
Advantages:
1. The scrum provides motivation among the team members in the team.
2. The project includes transparency for all the team members in a team.
3. The quality of the software is kept constant with the use of this methodology.
Disadvantages:

3SYSTEM ANALYSIS AND DESIGN
1. Sometimes this methodology might leads to project off-track because of project
segmentation.
2. The role of the team member might not be defined well that might create confusion in the
system.
Methodology: Kanban Methodology
Discussions: The meaning of the word Kanban indicates that the work is to be done just
in time. The Kanban practice is usually carried out in a board or in a table that are divided into
columns (Abrahamsson et al. 2017). The columns in the Kanban methodology shows the flow of
software production. Along with the development, the data in the table or the columns also
changes accordingly and new table is created with new activity or tasks performed.
Advantages:
1. This methodology has the ability to view all the tasks in a single project.
2. This methodology helps to limit the total number of tasks that are running in the project.
3. This methodology mainly focuses on the duration cycle of the project.
Disadvantages:
1. The team members involved in the system might misinterpret the data that are displayed
on the table or the columns of this methodology.
2. With this methodology, the project manager might face problems related to time as
because this project does not include timeframes.
Methodology: Extreme programming (XP)

4SYSTEM ANALYSIS AND DESIGN
Discussions: This is a framework that includes involvement of project in different
dimensions (Sandberg and Crnkovic 2017). This particular methodology mainly emphasises on
the values that includes Communication, respect for others, feedback for others, courage
included in the system, as well as simplicity in the project. This XP methodology provides trust
for the developers by providing them motivation in accepting the changes in the requirements of
the customer.
Advantages:
1. The codes that are written in this methodology are simple and this provides an advantage
in the system.
2. The cycle included in the XP development is clearly visible and helps to create goals for
the project (Rasnacis and Berzisa 2017).
3. This methodology include constant testing of the procedures in the system.
Disadvantages:
1. This methodology includes codes design and this might result to neglect the design of the
system that is being developed.
2. The errors that are included in the system might not be always included in the system
while developing the system with the XP methodology.
Methodology: Lean Development Methodology
Discussions: The lean development methodology mainly comes from the lean
manufacturing that was created by Toyota and is generally applied to the software development
methodologies (Tripp and Armstrong 2018). This particular methodology helps to include a

5SYSTEM ANALYSIS AND DESIGN
conceptual framework as well as follows values, good practice of development, and the
principles that are included in the system.
Advantages:
1. The advantages that are included in this methodology helps the team leaders to delete the
extra activities that are not important for completing the project (Campanelli and
Parreiras 2015).
2. The functionalities of the software project delivery are decreased using this agile and
iterative methodology.
3. This methodology is easily scalable methodology and project can adapt this methodology
easily.
Disadvantages:
1. This methodology is mainly dependent on developing the ability of the team as well as
follows the principle that are included in the lean methodology (Alqudah and Razali
2016).
2. This methodology can result in losing the focus on the project as there are many activities
involved in the project (Anwer et al. 2017).
3. This methodology needs documents for particular some characteristics in the business.
Recommendations: From the above discussion it can be stated that the methodology that
can be best used for developing the management system of the Australian Electric Supply
organization is the lean development methodology. This methodology is used for developing the
software and includes seven important principles that are needed for project development
(Zewairi et al. 2017). The principles that can be used for developing this project is excluding the

6SYSTEM ANALYSIS AND DESIGN
activities that are important for the project, includes quality development, create knowledge,
include differing commitments, include fast delivery, respects the team as well as optimize the
whole project.
2. Analysis of Case
Event Type
Event
Name
Type of
Event
Triggeri
ng
activity
Source
of Actor
Use
Case
Relate
d
Output description Actor
destination
Login of
Broker
External
event
Broker
Login
Broker Broker
Login
The brokers
associated with the
system .login in the
system as because
they need to provide
the item description
and the selling
customer description
in the system.
Administrator
Details
of the
seconds
hand
Internal Descripti
on of
product
Administ
rator
Selling
details
The selling details of
the second hand
items are stored in
the system.
Broker

7SYSTEM ANALYSIS AND DESIGN
product
sol
Buying
product
s
Tempora
l Event
After
customer
login in
the
system,
this event
might
take
place.
Custome
r
Buying
Product
s
The customer buys
product from the
system that are
uploaded by the
system.
Administrator

8SYSTEM ANALYSIS AND DESIGN
Use Case Diagram
Figure 1: Use Case Diagram
(Source: Created by Author)

9SYSTEM ANALYSIS AND DESIGN
Use Case Description
Use Case Name Uploading Product details
Scenario The details of the second hand product that to be sold by the OZES
organization are uploaded in the system from the description that is
provided by the Broker of the system. The system should store the details
of the second hand items that are to be sold by the system.
Triggering
Event
The triggering event associated with this use case is description of product
use case. The description of product use case provides the details that are
uploaded by the broker of the system.
Brief
Description
All second hand products that to be sold by the OZES organization are
uploaded in the system from the description that is provided by the Broker
of the system. The system should store the details of the second hand
items that are to be sold by the system.
Actors The actors associated with this use case is the broker, the customers and
the administrator in the system.
Related Use
Case
Description of Products, buying products, selling details.
Stakeholders The stakeholders responsible for this use case are the customers, the
associated brokers and owner of the company.
Pre-conditions The broker needs to provide the description of the items before carrying
out this use case.
Post-Conditions The post conditions that are included with this use case is that the
customer buys the product from the system after viewing the product

10SYSTEM ANALYSIS AND DESIGN
details of the seconds hand items.
Flow of
Activities
Actor System
The actor uploads the details of
the second hand products in the
system which can help the
customers to buy the products.
The system has an easy interface to
take the input that is to be given by
the user.
Exception
Condition
The details of the product can be taken only from the description that is
provided by the system, otherwise no new products will be added for sell.

11SYSTEM ANALYSIS AND DESIGN
Domain Model Class Diagram
Figure 2: Class Diagram
(Source: Created by author)

12SYSTEM ANALYSIS AND DESIGN
Design Class Diagram
Figure 3: Class Diagram for associated broker and order
(Source: Created by author)
3. Memo
Date: [Please Fill]
To: Executive Business People
From: Business Analyst
Subject: Discussion for UCD and HCI and Implication of adopting UCD approach
I want to discuss the concept of UCD and HCI that I have introduced for developing the
automated system for the Australian electric Supply. Before using the application software of the
organization, it is important to know the concept of UCD and HCI for developing an information

13SYSTEM ANALYSIS AND DESIGN
system. Before in the early days, only the personnel who are highly trained was able to use
computer system and the computer systems were considered to be very high expensive machines.
But today the concepts are changed totally. Computer has become the basic requirement for
managing the working process in an organization. The importance of HCI is extremely needed in
an organization to make clear intuitive system that will be used by the people having different
expertise and abilities. HCI includes the knowledge of that are needed to handle the systems that
are used in the organizations. Implementing proper HCI techniques while developing a system
will allow the user to use the system with ease.
The system that is being proposed in the system will help to meet the business goals of the
organization. This business goals are managed through many technological capabilities, as well
as the hardware tools that are needed in the system. The UCI interface of designing helps to fulfil
the business goals that are associated with the system. This is a process to develop a tools to
meet the business goals and fulfil the objective of the organization. The UCI tool helps to
develop a website that will fulfil the business processes. The system that will be built for
developing the system should support the beliefs of the existing users, the attitudes of the users
and the behaviours of the users in the system. UCI measure the usability of the system to
measure the ability of a product that a user can achieve and set the gaols efficiently as well as
effectively.
There are many implications that UCD has on developing the system of OZES. The implications
are listed below:
The UCD in developing the system will help to specify the use of the system that are
given by the users.
This will help to specify the requirements of the business.

14SYSTEM ANALYSIS AND DESIGN
This will help to create unique solution design for system.
This will help to evaluate the system designs.
This will help to implement the designs in the system.
This UCD helps to deploy business operations design in the system.

15SYSTEM ANALYSIS AND DESIGN
Bibliography
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Rasnacis, A. and Berzisa, S., 2017. Method for adaptation and implementation of agile project
management methodology. Procedia Computer Science, 104, pp.43-50.
F. Tripp, J. and Armstrong, D.J., 2018. Agile methodologies: organizational adoption motives,
tailoring, and performance. Journal of Computer Information Systems, 58(2), pp.170-179.
Campanelli, A.S. and Parreiras, F.S., 2015. Agile methods tailoring–A systematic literature
review. Journal of Systems and Software, 110, pp.85-100.
Alqudah, M. and Razali, R., 2016. A review of scaling agile methods in large software
development. International Journal on Advanced Science, Engineering and Information
Technology, 6(6), pp.828-837.
Anwer, F., Aftab, S., Waheed, U. and Muhammad, S.S., 2017. Agile Software Development
Models TDD, FDD, DSDM, and Crystal Methods: A Survey. International journal of
multidisciplinary sciences and engineering, 8(2), pp.1-10.
Al-Zewairi, M., Biltawi, M., Etaiwi, W. and Shaout, A., 2017. Agile software development
methodologies: survey of surveys. Journal of Computer and Communications, 5(05), pp.74-97.
Bhamra, T. and Lofthouse, V., 2016. Design for sustainability: a practical approach. Routledge.
Burns, C.M. and Hajdukiewicz, J., 2017. Ecological interface design. CRC Press.

16SYSTEM ANALYSIS AND DESIGN
Afanasyev, A.N., Voit, N.N., Voevodin, E.Y. and Gainullin, R.F., 2015, October. Control of
UML diagrams in designing automated systems software. In 2015 9th International Conference
on Application of Information and Communication Technologies (AICT) (pp. 285-288). IEEE.
Gomaa, H., 2015. Designing Real-Time applications with the COMET/UML method. URL:
http://citeseerx. ist. psu. edu/viewdoc/download.
Tlili, A., Essalmi, F., Ayed, L.J.B. and Jemni, M., 2016, July. Towards a generic UML model to
support designing educational role playing games. In 2016 IEEE 16th International Conference
on Advanced Learning Technologies (ICALT) (pp. 153-157). IEEE.
Sandberg, A.B. and Crnkovic, I., 2017, May. Meeting industry: academia research collaboration
challenges with agile methodologies. In Proceedings of the 39th International Conference on
Software Engineering: Software Engineering in Practice Track (pp. 73-82). IEEE Press.