ICT700 System Analysis and Design: OZES Management System Design ATMC

This report presents a system analysis and design for the OZES (Australian Electric Supply) management system, focusing on second-hand selling business processes. It explores agile methodologies, recommending Scrum for its flexibility, adaptability, and focus on iterative development. The report includes an event table, use case diagram, use case descriptions, and domain model class diagrams to illustrate the system's functionality and data relationships. A memo to the Executive Analyst outlines the implementation of the management information system and emphasizes the importance of user-centric design (UCD) and human-computer interaction (HCI) to ensure the system meets user needs and is accessible across various devices. The analysis aims to provide a clear understanding of the system's architecture and its alignment with OZES's business objectives.

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

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

3SYSTEM ANALYSIS AND DESIGN
1. Consultation
This agile and iterative methodology allows rapid changes and include adaptive planning,
delivers the software in short time and includes elf-organization (Satzinger, Jackson and Burd
2011). This methodology is flexible, and allows continuous improvements regarding the quality
of the software. As the OZES management system deals with user requirements that needs to be
changed from time to time, the following three agile methodologies can be used for developing
the information of OZES.
Methodology: Scrum Agile Methodology
Discussion: The scrum methodology includes interlocking steps as well as components
where the owner of the OZES can make the priority of the activities listed in product backlog
(Schmitz, Mahapatra and Nerur 2018). The methodology includes sprint backlog which includes
a wish of the owner and tries to implement the plan. Each sprint using this methodology is
completed in between 2-4 week and meeting are organized after a sprint gets completed.
Advantages: The advantages are listed below:
 This methodology is flexible as well as adaptive.
 Scrum methodology is creative and includes innovation.
 This helps to lower the cost.
 Improves the quality of the software.
Disadvantages: The disadvantages are listed below:
 Training is required for the project team.
 With this methodology, scalability is difficult.

4SYSTEM ANALYSIS AND DESIGN
Methodology: Extreme Programming Methodology
Discussion: This methodology is mainly used to increase the customer satisfaction. The
XP methodology mainly concentrates on the present requirement of the user rather than thinking
of future requirement. This methodology is centred on small development cycles and include
short releases (Rasnacis and Berzisa 2017). This methodology uses unit testing and include
frequent communication with the client. The Extreme development methodology includes
involvement of the owner of the OZES and establish a good communication between the
development team and owner of the OZES. User stories are also stated in this developments and
the owner or the client of the application software can prioritize the functions that are important.
This can help the OZES to state the most important features that are to be included in the system.
This methodology delivers the software in very short interval of time which might help the
OZES to launch the management system in 1 to 3 weeks.
Advantages: The advantages are listed below:
 Helps to save cost of Australian Electric Supply.
 The codes are simple in this methodology.
 The process that is carried out is visible as well as accountable.
 Includes feedback from the client.
Disadvantages: The disadvantages are:
 Focuses mainly on the codes instead of design.
 Does not measures the assurance of code quality.
Methodology: Feature Driven Development (FDD)

5SYSTEM ANALYSIS AND DESIGN
Discussion: The FDD methodology is considered as a model driven methodology having
short process of iteration. This methodology mainly starts by establishing the overall shape of the
software or the model (Schön, Thomaschewski and Escalona 2017). As the management system
of OZES needs to have requirement of developing the system, the development process includes
object modelling, FDD methodology includes this particular practice. The FDD methodology has
tight control on the development process that result in developing a tangible software.
Advantages: The advantages are listed below:
 This supports working of many teams in parallel.
 All the aspects of the project can be tracked by this feature.
 This system includes large team
 Provides progress tracking of development and includes reporting capabilities.
 Have excellent documentation
 Includes designing and code inspecting that results in providing high quality of
application.
Disadvantages: The disadvantages are:
 This methodology promotes code ownership.
 The iterations are not well defined in this methodology.
Recommendation: The best methodology that can be used for developing the
management system of OZES is the agile scrum methodology. This methodology will help the
company to improve the productivity that are in teams as well as will help to deliver the
information system in every 2 to 4 weeks (Rajagopalan and Mathew 2016). This method

6SYSTEM ANALYSIS AND DESIGN
includes team formation along with diversity, will includes a good communication in between
the team members, and includes frequent feedback from the owner of the company.
For developing the management system of OZES, the scum methodology will help to
control the scope of the project and will encourage the team associated with the project (Zewairi
et al. 2017). This methodology increases the transparency of team and includes good visibility to
manage the drawbacks of the system that is to be developed for the system. This particular
methodology is adaptive. The agile scrum methodology will help the developer of OZES to
interlock the steps and the components that are given by the OZES owner and also has the ability
to make priority to all the activities that are to be included in the system. The main methodology
that agile scrum method follows are using the sprint backlog system that also includes the wish
of owner about how the owner wants to implement it in the system. All the sprints that are used
in the agile scrum methodology are to be done in two to three weeks and after each sprint being
completed, meeting is organized for the system. This methodology has many advantages of
completing the project in a flexible manner and in an adaptive way. The scrum methodology is
very much creative in nature and also involves innovation. This methodology can help the
developer to complete the work with low cost and improves quality of software.
2. Analysis of Case
Event Table
Event Event
Type
Trigger Source
Actor
Use Case Output Destination
actor

7SYSTEM ANALYSIS AND DESIGN
Sign Up External Customer
sign Up
Customer Sign up The
customer
sign up with
details
Customer
Login External Customer
login
Customer Login The
customer
login with
username as
password.
Customer
Order
Products
External Buy
products
Customer Order
Products
The
customer
orders the
product that
they want to
buy.
Management
Sold
details
State Order
Products
Management Sold
details
The details
of selling is
update on
the system
by
management.
Associate
Broker
Product
Details
Temporal Item
Description
Associate
Broker
Product
Details
The details
of the
Associate
Broker

8SYSTEM ANALYSIS AND DESIGN
product is
updated by
broker.
Seller
Details
Temporal Login of
associate
broker
Associate
Broker
Seller
Details
The details
of the seller
from where
the item is to
be picked up
by the staff
of OZES
Management

9SYSTEM ANALYSIS AND DESIGN
Use case diagram
Figure 1: Use Case Diagram
(Source: Created by author)
Use Case description
Use Case Name Selling Details
Scenario The Details of selling of the second hand item is stored in this use case.
Triggering
Event
The triggering event associated with this use case is the customer buying
the second hand items from the OZES after price negotiating and the
details the item is uploaded in the system so that the broker can negotiate

10SYSTEM ANALYSIS AND DESIGN
the price with the selling customer.
Brief
Description
The details of the price is explained in this use case. The selling price is
detailed with the purchasing customer. After the customer buys the item
from the OZES, the selling price details of the item is uploaded in this
use case so that the associated broker can negotiate the price with the
selling customer and make profit out of that.
Actors The purchasing customer, the associate brokers and the management are
the actors associated with this use case.
Related Use
Case
Buy products, upload product details and item description are the three
use cases related with selling details use case.
Stakeholders The associate brokers, the management system of the OZES, the owner of
OZES, the selling customer and the purchasing customers are the
stakeholders associated with this use case.
Pre-conditions Pre-conditions for this use case are that the management has to upload the
details of the items along with the product which the purchasing customer
can buy. After the payment process is done, the details is stored in this use
case.
Post-Conditions The broker after viewing this use case negotiate price with the selling
customer.
Flow of
Activities
Actor System
The management uploads the
details of selling item to the
customer.
The system takes input of the price
of the item, the quantity of item and
the description of the item.

11SYSTEM ANALYSIS AND DESIGN
Exception
Condition
If the item is not sold, the item is returned to the original owner of the
item who is selling the item.
Domain Model Class Diagram
Figure 2: Class Diagram
(Source: Created by author)

12SYSTEM ANALYSIS AND DESIGN
Class diagram for Associate Broker and order
Figure 3: Class Diagram for associated broker and order
(Source: Created by author)
3. Memo
Date: May, 30, 2019
To: Executive Analyst
From: Business Analyst of Australian Electric Supply (OZES)
Subject: Implementing Management Information System in OZES
I am writing this to inform you that OZES is implementing an information system to manage the
business process of second hand selling in the business. The information system is already under
process and I am expecting to finish the project within 6 to 9 months.
As our company wants to extend its business process to second hand selling, I want to design the
human computer interaction system (HCI) by implementing the user centric design. As the