Comprehensive System Analysis and Design Report for OZES Project

This report presents a detailed system analysis and design for the OZES organization, focusing on the implementation of a management information system for second-hand sales. It begins with a consultation on agile methodologies, comparing Lean Software Development, Agile Scrum, and XP methodologies, and recommends Agile Scrum. The report includes an analysis of the case, featuring an event table, use case diagram, use case descriptions, and domain model class diagrams for the system. It also provides a class diagram specifically for Associate Brokers and orders. A memo to the Executive Analyst summarizes the project, emphasizing the use of Human-Computer Interaction (HCI) and User-Centered Design (UCD) principles. The report concludes with a bibliography of relevant sources. This report is a valuable resource for understanding system analysis and design principles within the context of a real-world case study.

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.................................................................................................................................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
The software development agile methodology is an iterative methodology that includes
adaptive changes and include adaptive planning in the system. This methodology include
delivery of the system in short time period as well as includes the organization to organize its
business. The methodology of agile is a flexible method that allows to improve the business
process continuously and also improves the application quality. The case study of OZES
organization includes this methodology to make the working process systematic and work to be
done automatically. Three methodologies are explained below that can improve the working
process of the OZES system.
Methodology: Lean Software Development
Discussion: The lean software development methodology is an iterative method that
involves the team work to deliver value to all customer and increases the efficiency of working
(Schön, Thomaschewski and Escalona 2017). There are many principles that are include in the
lean methodology; the methodology eliminates the wastes, amplifies the learning, and takes
decision lately and delivering the software faster. The methodology also includes empowering
team, build the integrity and see the whole documents accurately.
Advantages:
 The lean methodology minimizes the waste along with the production facility.
 The lean methodology includes customer relationship.
 The methodology has lean structure; that is it does not include strict structure to follow.
Disadvantages:

4SYSTEM ANALYSIS AND DESIGN
 This methodology might include equipment failure.
 There are many inconsistencies in carrying out this methodology.
Methodology: Agile Scrum Methodology
Discussion: Scrim methodology of agile development includes scrum master that helps to
keep the team focused to achieve the goal. The scum methodology is divided in to many parts
that are stated as sprint backlog. The sprint backlog includes the priority of wish list of the
project owner and the team using scrum methodology plan to implement the sprint backlog first.
Each task in a sprint backlog is divided in to sprint usually of 2-4 weeks and after the sprint
being completed, the scrum master arranges meeting to discuss about the sprint.
Advantages:
 The methodology of scrum agile is very much flexible.
 Innovative ideas comes as a result of scrum technology.
 The methodology has very low cost.
 Quality of the software is improved with this methodology.
Disadvantages:
 Project team requires training to handle scrum prints.
 This methodology does not include scalability.
Methodology: XP Methodology
Discussion: The XP methodology is commonly used with the scrum methodology to
increase the customer satisfaction within the project. The XP methodology mainly concentrates

5SYSTEM ANALYSIS AND DESIGN
on the present need of the customer. The future enhancement of the application is not considered
while the project is under XP methodology.
Advantages:
 The XP methodology uses simple code to complete the project.
 The process are clearly visible and are accountable.
 Gives priority to feedback of the customer.
Disadvantages:
 This methodology focuses on the codes to complete the project.
 Code quality assurance is not measured.
Recommendation: The methodology that can be best used to develop the system of
OZES is scrum agile methodology. It will help the organization to increase their sell and make
their work automatic. The management system and the brokers will be associated with the
system and can do their work independently using the scrum agile methodology. This
methodology will be profitable for the organization as it will help the developer to complete the
project less cost and increase the capability of the business. The team members in a scrum
project has good communication among themselves and also have good communication with the
project client. This will help the OZES organization to develop a user centric application along
with the feedback of the customer.
2. Analysis of Case
Event Table
Event Event Trigger Source Use Case Output Destination

6SYSTEM ANALYSIS AND DESIGN
Type Actor actor
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 Temporal Item Associate Product The details Associate

7SYSTEM ANALYSIS AND DESIGN
Details Description Broker Details of the
product is
updated by
broker.
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

8SYSTEM 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.
Brief The details of the price is explained in this use case. The selling price is

9SYSTEM ANALYSIS AND DESIGN
Description detailed with the purchasing customer.
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
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.
Exception
Condition
If the item is not sold, the item is returned to the original owner of the
item who is selling the item.

10SYSTEM ANALYSIS AND DESIGN
Domain Model Class Diagram
Figure 2: Class Diagram
(Source: Created by author)
Class diagram for Associate Broker and order
Figure 3: Class Diagram for associated broker and order

11SYSTEM ANALYSIS AND DESIGN
(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.
The HCI includes a broad field that overlaps the areas including the user centred design (UCD)
and design related to user experience. With the HCI and the UX design, the practitioners mainly
focuses on the academic that include scientific research as well as develop understanding related
to users.
The UCD that is included for designing the software is an iterative process that helps the
designers to mainly focus on all the users and the needs of the users in each design phase. The
UCD mainly includes involving the users in designing the design process and includes different
research in the system. The design techniques in UCD are highly usable as well as includes
accessible product for the users. With the UCD, the developers or the designers include a mix
investigation process and a generative method and different tools for understanding the needs of
the user.

12SYSTEM ANALYSIS AND DESIGN
As the user of the information system will be management system of OZES, the associated
brokers, purchasing customers and the selling customer, interview and surveys are to be carried
out with the users of the system. The UCD includes four phases, understanding the context of
use, specifying the user requirements, designing the solutions and evaluating the requirements
that are included in the system.