ICT700 System Analysis and Design: OZES Software Development

This report provides a comprehensive system analysis and design for OZES software development, focusing on the application of agile methodologies. It includes a consultation on various agile methods such as Lean, Scrum, Extreme Programming, and Kanban, recommending Scrum for its transparency and cost-saving benefits. The analysis of the case involves an event table, use case diagram, use case descriptions, and domain model class diagrams. The report also features a memo discussing the implementation of the information system, emphasizing User Centered Design (UCD) and Human-Computer Interaction (HCI) concepts. The document concludes with a bibliography, citing relevant sources used in the analysis and design process. Desklib provides a platform to access similar solved assignments and past papers for students.

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

2SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Consultation.................................................................................................................................3
2. Analysis of Case..........................................................................................................................6
Event Table..................................................................................................................................6
Use case diagram.........................................................................................................................9
Use Case description....................................................................................................................9
Domain Model Class Diagram..................................................................................................11
Class diagram for Associate Broker and Order.........................................................................12
3. Memo.........................................................................................................................................12
Bibliography..................................................................................................................................14

3SYSTEM ANALYSIS AND DESIGN
1. Consultation
Software development that is done by the agile methodology is considered as iterative
methodology that helps in adaptive changes as well as involves adaptive planning to design the
system. This particular agile iterative methodology helps to deliver the software in very less time
and helps in organizing the business in strategic way (Campanelli and Parreiras 2015). The
approach of agile method is a flexible method that improves the process of business in a
continuous way and also improves the quality of application. The Australian Electric Supply
company that is taken as the case study of this report is organizing a new business and wants to
implement the agile iterative method in its business process to automate the business and
planning the process systematically.
Methodology: Lean Agile Software Development
Discussion: This particular software development methodology comes under agile
iterative methodology and helps the team to deliver the work as per the customer demand and
thus increase the efficiency of the working in the system (Kotaiah and Khalil 2017). The lean
development includes principles that are included in the lean methodology and this methodology
helps to remove the waste and thus increases the learning in the system and takes prompt
decision in the working process of the business. The lean methodology also helps to deliver the
software soon compared to other methodology of software development. Lean methodology also
empower team building, increase integrity of the team and helps to verify documents in an
accurate way.
Advantages:

4SYSTEM ANALYSIS AND DESIGN
There are many advantages that lean methodology provides in software development.
This helps to minimize the wastes that are actually not needed in software development. This
also helps to increase the customer relationship in the development process (Serrador and Pinto
2015). This particular methodology is considered as to be lean structure that does not follow
strict methodology.
Disadvantages:
In lean methodology that disadvantages might result in failure of the equipment and in
this methodology, there are many inconsistencies.
Methodology: Scrum Methodology in Agile Iterative method
Discussion: The scrum methodology that can be used for software development helps in
keeping the straight focus to achieve aim of software development. The scrum methodology is
mainly divided in several parts that are defined as sprint backlog (Rasnacis and Berzisa 2017).
The sprint mainly includes the wish list that is to be followed in the project and team included in
the sprint backlog implements the sprint in the software development. The wish list is made
according to wish of project owner and scrum methodology is usually done in two to three weeks
of time. This methodology also includes scrum meeting that is discussed within the sprint.
Advantages:
The advantages that are used in scrum are that it is very much flexible, includes
innovative ideas, and the cost of the methodology is low (Tripp, Saltz and Turk 2018). This
methodology helps to improve the quality of the software.
Disadvantages:

5SYSTEM ANALYSIS AND DESIGN
The disadvantages includes project team training for handling sprints in scrum and this
includes scalability.
Methodology: Extreme Programming Methodology
Discussion: Extreme programing is known as XP that helps to increase the satisfaction of
the customer for developing the software. XP methodology concentrates on the requirement of
the customer. This methodology also includes future enhancement.
Advantages:
The advantages included in extreme programming involves simple coding and includes
visible and accountable resources in developing the system. Feedback of the customer is taken in
to account in this methodology.
Disadvantages:
The disadvantages focuses on codes for completing the project and includes code quality
assurance.
Methodology: Kanban Methodology
Discussion: Kanban Methodology includes managing the development of the software in
efficient way (Babar et al. 2017). This methodology is considered less structured methodology
compared to scrum and includes model to improve process by incremental improvements. This
methodology can be used in a running project that might help to complete the project faster.
Advantages:

6SYSTEM ANALYSIS AND DESIGN
The advantages included in Kanban methodology is that it is an event driven rather than
time boxed. The commitment in Kanban agile methodology is optional and include default
metric planning. This helps to include new items when the capacity is available.
Disadvantages:
The disadvantages of Kanban states that if the Kanban board is outdated, it might lead in
issue for developing the software (Schmitz, Mahapatra and Nerur 2018). Sometimes the process
becomes over complicated. This also includes lack of time.
Recommendation: Scrum methodology is recommended for development of OZES
software development as this includes more transparency as well as visibility compared to other
methodology and increase the team accountability (Haines, Idemudia and Raisinghani 2017).
Changes are also easily possible in scrum methodology and includes cost saving development.
2. Analysis of Case
Event Table
Event Event
Type
Trigger Source
Actor
Use Case Output Destination
actor
Sign Up
event
External
event
Signing
Up the
customer
Customer Sign up
Use Case
The
customer
in the
system
sign up
with the
system in
Customer

7SYSTEM ANALYSIS AND DESIGN
this use
case.
Login
event
External
event
After
customer
sign up,
login is
triggered
Customer Login use
case
The
customer
login with
the system
after
getting the
username
and
password
in sign up
process.
Customer
Order
Products
event
External
event
Buying of
products
Customer Order
Products
Use case
The
products
are
ordered
from the
system.
Management
system.
Sold
details
event
State
event
Order
Products
Management Selling
details
Details
related to
the
product
Associate
Broker

8SYSTEM ANALYSIS AND DESIGN
are
detailed in
the
system.
Product
Details
Use case
Temporal
event
When
description
of the item
is given in
the system.
Associate
Broker
Product
Description
use case
Details of
the
product is
given by
the broker
in the
system.
Associate
Broker
Seller
Details
event
Temporal
event
Triggered
when
associate
broker log
ins in the
system.
Associate
Broker
Seller
Details
This
provides
details of
the item
description
from
where the
item is to
be picked
up.
Management
system.

9SYSTEM ANALYSIS AND DESIGN
Use case diagram
Figure 1: Use Case Diagram
(Source: Created by author)
Use Case description
Use Case Name Selling Description
Scenario Details of all the items that are to be sold are provided in this use case.
Triggering
Event
This event is triggered when there is customer buys the products from the
company. Detailed price of the product is updated in this system so that
the associate broker knows the selling details.

10SYSTEM ANALYSIS AND DESIGN
Brief
Description
Details of the product is described in this system that will help the
associate brokers to get the details of the product and negotiate price with
the selling customer accordingly.
Actors Purchasing customer, management system
Related Use
Case
Buying products, product details and get selling details
Stakeholders Associate brokers, management system of OZES and the purchasing
customer.
Pre-conditions The customer needs to buy the product so that the details of the product is
updated in the selling description use case.
Post-Conditions Associate broker needs to get the price from the selling customer only
after view the selling description details.
Flow of
Activities
Actor System
Details of the product is updated
in the system.
The interface of the system takes the
details about the product.

11SYSTEM ANALYSIS AND DESIGN
Domain Model Class Diagram
Figure 2: Class Diagram
(Source: Created by author)
Class diagram for Associate Broker and Order

12SYSTEM ANALYSIS AND DESIGN
Figure 3: Class Diagram for associated broker and order
(Source: Created by author)
3. Memo
Date: [Please Fill]
To: Business Executive Analyst
From: Business Analyst
Subject: To implement the information system in OZES
I would like to inform you that our company is implementing an information system to
automate the business process in the system. The information system is to be implemented in the
process of selling second hand items in the company. As the information system is new concept
among you, I would like to explain the concept of UCD as well as HCI so that the information is
easy to use.
HCI concept mainly includes overlapping the areas that are included in UCD. UCD is the
User Centred Design as well as the design that is related with the user experience. The HCI
includes practitioner who focuses on academic design of the UX design and also includes
scientific design.
UCD includes designing software in an iterative way which helps designers to emphasis
on all the users related with the information system and then includes users in all the design
phase. UCD includes the user designing and includes different research in the system. Design
techniques used in designing process are highly usable and includes accessible use of products in
the system.