System Analysis and Design: OZES Electric Supply - ICT700 Task 2

This report provides a comprehensive analysis and design of an information system for Australian Electric Supply (OZES), a second-hand selling business. It begins with a consultation of different software development methodologies, including Scrum, Extreme Programming, and the Waterfall model, recommending Scrum as the most suitable approach. The analysis of the case includes an event table, use case diagram, use case descriptions, and domain model class diagrams. A memo is included, detailing the implementation of a management information system in OZES, focusing on Human-Computer Interaction (HCI) and User-Centered Design (UCD) to ensure user-friendliness and efficiency. The report concludes with a bibliography of cited sources.

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
1.1 SCRUM.....................................................................................................................3
1.2 Extreme Programming:..............................................................................................4
1.3 Waterfall Model:........................................................................................................5
2. Analysis of Case..............................................................................................................7
Event Table......................................................................................................................7
Use case diagram.............................................................................................................9
Use Case description......................................................................................................10
Domain Model Class Diagram......................................................................................11
Class diagram for Associate Broker and order..............................................................12
3. Memo.............................................................................................................................12
Bibliography......................................................................................................................15

3SYSTEM ANALYSIS AND DESIGN
1. Consultation
1.1 SCRUM
The Scrum is one of the extensively used agile SDLC model. The Scrum is famous for
supporting both the incremental and iterative software development structure. The Scrum has
successfully handled the drawbacks of the conventional SDLC model and provided a dynamic
approach toward software development. In order to introduce flexibility, productivity and
adoptability, the Scrum model was developed based on process control theory. The adaptation,
transparency and inspection are the main three features of the Scrum that makes it suitable for
big and complex projects. The Scrum methodology has three phases, such as pregame, game and
postgame. In the pregame phase, the project vision is defined. Along with the vision, the
functional and non-functional requirements are defined by the product owner. The product
backlogs are the required features of the product1. Based on the development plan of each feature
of the final products release plan is developed.
In the game phase, the actual development work is done. The game phase is completed
through executing small iterations called sprints sequentially. One sprint can be time period of
one week to four weeks, based on the complexity of the work. Each sprint has four parts like
develop, wrap, review and adjust.
The postgame is the closure phase of the project. The final release happens when the
intended works have been completed. The final integration testing is done in this project phase.
The training materials and user manuals are also created in the postgame phase.
1 Anwer, Faiza, Shabib Aftab, SS Muhammad Shah, and Usman Waheed. "Comparative Analysis of Two
Popular Agile Process Models: Extreme Programming and Scrum." International Journal of Computer Science and
Telecommunications 8, no. 2 (2017): 1-7.

4SYSTEM ANALYSIS AND DESIGN
The Scrum methodology is controlled by three roles mainly such as product owner,
scrum master and team. The product owner are generally the client representative who takes the
out of the scope decisions. The Scrum master monitor and control all the scrum related activities.
The team collect data, analyse data, create design, development software and test the software.
Advantages
i. The usage of time and capital is handled effectively and efficiently
ii. The coding and testing is done during the sprint review
iii. The short period of sprints allow adjustment in the development software quickly
iv. The fast-moving software development projects are best suited2
v. The scrum meetings are very assisting in sharing the clear picture of the project
Disadvantages
i. The scrum has a bad reputation of leading the projects to scope creep
ii. Can be done by only skilled and experienced experts who charge a lot of capital
iii. The daily meetings often hamper the workflow
iv. The quality of final product is often compromised as the new scopes are hard to
align with the project objective
1.2 Extreme Programming:
Extreme programming is also another agile software development model. The extreme
programming is very lightweight and it is more flexible than Scrum. The extreme programming
can easily capture the rapid changing requirements and integrate those changes into project. The
extreme programming focuses its time on the coding part and reduces the amount of planning
2 Edeki, Charles. "Agile Software Development Methodology." European Journal of Mathematics and
Computer Science Vol2, no. 1 (2015).

5SYSTEM ANALYSIS AND DESIGN
and requirement gathering. The extreme programming phases are exploration phase, planning
phase, release phase, iteration planning, iteration to release phase, productionizing phase,
maintenance phase and death phase.
Advantages
i. The extreme programming is very fast and it is quickly completed than other
methodologies
ii. The cost of the development is also very low than other methods
iii. The communication among the team is extremely good and it allows all members
to have proper idea of the project insights
iv. The methodology focuses on increasing teamwork
Disadvantages
i. There is a possibility that customer may not be happy with the final product as the
extreme programming does not focus on designing
ii. This methodology does not concentrate on documentation which increases the
possibility of unexpected failures
iii. As the deadline is tight, the team can be under immense pressure and may not
provide good quality work
1.3 Waterfall Model:
Waterfall model also known as the linear-sequential life cycle model is the very first
process model that was introduced and is known as the earliest SDLC (Software Development
Life Cycle) approach in the software development field. The process involves logical sequential

6SYSTEM ANALYSIS AND DESIGN
flow, this implies that without completing the previous development process the next phase
cannot be approached and thus, reducing the overlapping of the phases.
The Waterfall model comprises of mainly six stages which are, the requirement phase,
then comes the analysis of the requirement, the designing of the software comes after that,
coding and testing are the next two phases in this cycle and the last stage is the deployment of
the developed software.
In the requirements phase, a requirement document is created by the developers listing
every possible requirements. The functions of the system are defined in this document and is
used in the future development. The analysis stage is used by the developers to analyse the
requirements and draw the logical design for the system without any hardware and software
specifications. In the next phase, the logical design is altered according to the hardware and
software requirements for the system. The coding stage comes right after this, where the actual
coding for the required system is written3. The testing stage involves the quality checking of the
developed system, with the help of quality analyst, beta tester in order to report any bugs in the
system. The last stage, the deployment stage involves the release of the system in the market,
providing customer support, maintenance of the system and future up gradation to meet the
requirements of the customers.
Advantages
i. Better understanding of the errors and system.
ii. The process defines milestones which will help the developers to create definite
and concrete goals for the project
3 Chi, C. 2019. Everything You Need to Know About Using the Waterfall Methodology. [online]
Blog.hubspot.com. Available at: https://blog.hubspot.com/marketing/waterfall-methodology [Accessed 28 Jun.
2019].

7SYSTEM ANALYSIS AND DESIGN
Disadvantages
i. The developers cannot move to the next stage without completing the previous
one.
ii. The requirement cannot be changed later.
Recommendation: As per the requirements of Australian Electric Supply, the scrum
model is the most suitable methodology for developing the information system. The Scrum will
allow the organization to include staff, customer and other end users into the project. The final
product can be customer centric. As the system will be developed in pieces, Australian Electric
Supply will have working software from early stages of the development project.
2. Analysis of Case
Event Table
Event Event
Type
Trigger Source
Actor
Use Case Output Destination
actor
Generate
new
customer
detail
External New
Customer
Customer Sign up New
customer
details are
entered into
the system
Customer
Verify
customer
account
External Customer
verification
Customer Sign In System
allows
authentication
to use the
Customer

8SYSTEM ANALYSIS AND DESIGN
functions
Customer
make a
new
order
External Possible
product
sales
Customer Place
Order
Customer
order is
confirmed
and sent to
warehouse
Warehouse
Employee

9SYSTEM ANALYSIS AND DESIGN
Use case diagram
Figure 1: Use Case Diagram
(Source: Created by author)
Use Case description
Use Case Name Apply Coupon

10SYSTEM ANALYSIS AND DESIGN
Use Case ID Cust_UC_04
Actors Customer
Precondition There must be items in the cart before coupon can be applied
Activities Actor System
Customer add products to cart System checks item availability
Customer click on proceed System redirect to another page
Customer enter coupon code in
particular area
System check coupon validity and
reduce the coupon amount
Customer see updated cost
Post condition Customer can use coupon only once
Exception System does not approve code for specific items

11SYSTEM ANALYSIS AND DESIGN
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: June, 28, 2019
To: The Executive Analyst
From: The Business Analyst of Australian Electric Supply (OZES)
Subject: Implementation of Management Information System in OZES