ATMC ICT700: Australian Electric Supply System Development Report

This report focuses on the development of the Australian Electric Supply (OZES) system, evaluating various agile methodologies. It begins with an executive summary and proceeds to explore the Scrum, Extreme Programming (XP), Kanban, and Lean software development methodologies, discussing their advantages and disadvantages. The report then recommends Scrum as the most efficient methodology for the project. It includes an analysis of the case, detailing an event table, a use case diagram, use case descriptions, domain model class diagrams, and design class diagrams, specifically for the order and associate broker classes. The assignment aims to provide a comprehensive understanding of system analysis and the selection of appropriate development methodologies for the OZES company, which deals with the selling of electronics through associate brokers and company employees.

1Australian Electric Supply Management System Model and Design
AUSTRALIAN ELECTRIC SUPPLY MANAGEMENT SYSTEM MODEL AND DESIGN
[Student name]
[University name]
[Professor Name]
[Date]

2Australian Electric Supply Management System Model and Design
Table of Contents
1 Executive summary..............................................................................................................................3
2 Consultation.........................................................................................................................................3
2.1 Scrum Methodology....................................................................................................................3
2.1.1 Discussions..........................................................................................................................3
2.1.2 Advantages..........................................................................................................................4
2.1.3 Disadvantages......................................................................................................................5
2.2 Extreme programming (xp) Methodology...................................................................................5
2.2.1 Discussions..........................................................................................................................5
2.2.2 Advantages..........................................................................................................................5
2.2.3 Disadvantages......................................................................................................................6
2.3 Kanban Methodology..................................................................................................................6
2.3.1 Discussions..........................................................................................................................6
2.3.2 Advantages..........................................................................................................................6
2.3.3 Disadvantages......................................................................................................................6
2.4 Lean software development Methodology...................................................................................7
2.4.1 Discussions..........................................................................................................................7
2.4.2 Advantages..........................................................................................................................7
2.4.3 Disadvantages......................................................................................................................7
2.5 Recommendation.........................................................................................................................8
3 Analysis of the case.............................................................................................................................8
3.1 An Event Table.............................................................................................................................8
3.2 A Use Case Diagram...................................................................................................................11
3.3 Use Case Description (intermediate).........................................................................................12
3.4 Domain Model Class Diagram....................................................................................................13
3.5 Design Class Diagrams...............................................................................................................14
3.5.1 Order class diagram...........................................................................................................14
3.5.2 Associate broker class diagram..........................................................................................14
Reference..................................................................................................................................................15
4 Appendix............................................................................................................................................16
Appendix A: Memo on pertinent issues.................................................................................................16

3Australian Electric Supply Management System Model and Design
1 Executive summary
This report is about the selection of the development methodology of the Australian Electric
Supply (OZES) company that deals with selling of the electronics to their clients.
This company uses the associate brokers to sell their send hand products and also had employed
the permanent employees who work in the company store.
These employees receive the items bought by clients and send them and later the associate
brokers are usually paid in commission of the products they had sold.
This report therefore covers various items like the various agile methodologies and the
recommendation of the best methodology, the identification of the various analysis cases.
The analysis cases includes the event table, the designing of the use case diagram, the description
of the system use case, the designing of the class diagram model, the drawing of the class
diagrams, and memo preparation.
Therefore the implementation of the proposed system will enable easy records management,
improve the information security.
Also the storage and retrieval of the information will be enhanced and also analysis of the items
sold will be eased and improve the customer service delivery.
2 Consultation
2.1 Scrum Methodology
2.1.1 Discussions
The scrum methodology is one of the methodologies in the agile system development
methodology and it is the most popular method that is used to implement the agile development.
This method is mainly in the case which require product owner, scrum master and the
development team members are required to participate in the development of the Australian
Electric Supply (OZES) system.

4Australian Electric Supply Management System Model and Design
In this agile development method will require the development team to be meeting on daily basis
in order to update the development progress, delivering the build part to the team.
Then the development team will do system evaluation after every two or three weeks cycle and
this is referred as the development sprints.
2.1.2 Advantages
The following are the advantages of the scrum agile development methodology.
i. It is easy to remove the various mistakes.
ii. It is easy to view all the stages of the system development.
iii. It is easily copes with the changes that are required by the client since it consists of
several short sprints which have feedback from the system owners.
iv. It is easy to change the development of the system at any given stage since it is highly
flexible.
v. It is able to give best system results due to the client’s involvement in the system
development process.
vi. It is bale to allow success in the business which is hard to document.
vii. It supports fast results and simplified procedures of system testing to ensure best work
output and system quality.
viii. It is the best method of system development since it comprise of update of the system
development progress through the regularly held meetings.
ix. It is iterative by nature and receives the user’s feedback continuously to better the
development process.
x. It is easy to identify and solve problems and resolve them on time due to the development
daily meetings.
xi. The method is able to provide the clients with transparent system development process
and they are able to trace the system development procedures and also measure the
system development team individual efforts.
xii. The method easily motivates the development team.
xiii. The methodology is able to deliver system on time.

5Australian Electric Supply Management System Model and Design
xiv. The methodology is able to cope with the set budget, give desirable system and also
deliver system in a very short time.
2.1.3 Disadvantages
i. It is easy to fail the whole project due to the strict governance by the scrum master.
ii. The project will be affected in case a member of the team leave in the process of system
development.
iii. Due to lack of set deadline it allows project manager to keep on demanding new
functionalities which delay system delivery.
iv. The project expands to several sprints due to lack of predictable time limits and the cost.
v. System development requires committed development team members.
vi. It is the best method where a small development team for best cohesion.
vii. It requires experienced development team members to accomplish the tasks.
viii. The team members are subjected to great pressure and spend a lot of time on the project
developments.
2.2 Extreme programming (xp) Methodology
2.2.1 Discussions
The extreme programming is another agile system development methodology which incorporates
the frequent customer’s feedbacks and system changes to ensure that there is quality in the
system software developed.
In this case the software quality is highly maintained where the best coding practices are
followed which includes the pair programming like the code reviewing, and unit testing process
to the extreme level and therefore the method is referred to as extreme programming.
2.2.2 Advantages
Below are the advantages of the extreme programming agile development methodology.
i. It enables the development company to save on the development cost and time in the
realization of the project.
ii. The methodology supports the simplicity in the development process.

6Australian Electric Supply Management System Model and Design
iii. The XP processes are highly visible and accountable where the development team is able
to commit their deliverable and also shows the progress.
iv. The methodology however supports the client’s feedback which enables the making of
the relevant changes to the system.
v. The method enables the development of the system faster than other methods.
vi. The methodology increases the employees and customers satisfaction and retentions.
2.2.3 Disadvantages
Below are the various method disadvantages.
i. The methodology focuses mainly on the system coding rather than system design.
ii. There is no measure of the code quality.
iii. It is not best to use if the developers are in separate geographical areas.
2.3 Kanban Methodology
2.3.1 Discussions
This is the third methodology of the agile development methodology where the kanban
methodology is a method which the various tasks are organized on a kanban board.
The work progress is easily tracked from the boards and thus helps in the decisions making in the
development process.
2.3.2 Advantages
Below are the advantages of the kanban methodology.
i. It enables the efficient use of the resources which includes people, materials, and
products.
ii. It results to faster delivery of system than scrum method.
iii. It involves the experts in the development process.
iv. The development team does not depend on the employees.
2.3.3 Disadvantages
Below are the various disadvantages of kanban methodology.
i. The development engineers are less expert in some areas.

7Australian Electric Supply Management System Model and Design
ii. The system does not have assurance of adhering to the coding rules.
2.4 Lean software development Methodology
2.4.1 Discussions
The Lean software development methodology is the other method of agile methodology and it is
based on various principles that help in the system development.
The methodology principles include waste elimination unnecessary codes, amplified learning,
late decision, faster delivery, team empowerment, and integrity building.
2.4.2 Advantages
Below are the various advantages of the lean software development methodology.
i. There is overall efficiency in the system development process due to elimination of the
wastes and a result it speeds the development process.
ii. The methodology is able to deliver the product quite early compared to the other
methods.
iii. The empowering of the development team enables good decision making.
2.4.3 Disadvantages
Below are some disadvantages of lean system development methodology.
i. The project depends of the team cohesiveness and the individuals commitments.
ii. The project success is determined by the discipline of the development team members.
iii. The project sponsor and the client require knowing things they require and make the
decisions which the developers stick to.
iv. The process requires the business analyst to enable the clear understanding of the
proposed business requirements.
v. The lean method allows the evolving of the initial system requirements which cause to
delay in system delivery.

8Australian Electric Supply Management System Model and Design
2.5 Recommendation
In the implementation of the proposed system I would recommend the use of the scram agile
development method since it will more efficient, include all clients’ requirements and also stick
on the proposed system budget.
Below are the various major reasons of selecting the scrum methodology.
i. The development mistakes are removed with ease.
ii. The development process involves all stake holders (Stephen, 2014).
iii. The system users, clients and the development manager are allowed to give feedback on
the system after every meeting.
iv. It enables quick development of the system.
v. The system can be easily changed as the team meets daily.
vi. The system delivered is according to clients requirements.
vii. The system proposed is delivered on time to the clients.
viii. The methodology will cope with the clients set budget.
ix. The problems are easily identified and resolved during system development.
3 Analysis of the case
3.1 An Event Table
Event Event
Type
Trigger Source Activity/Use
Case
System
Response or
Output
Destination
1. Temp Broker wants to
sale item
Associate
broker
Advertise
items and List
their prices
Items
advertised
successfully.
Customer
2. Ex Want to store
broker details.
Sales
officer
Record
brokers
Broker’s
details saved
successfully.
Associate
broker
3. Temp Want to store
items details.
Store
officer
Record items Items details
saved
Sales
officer

9Australian Electric Supply Management System Model and Design
successfully.
4. Temp Want to buy
item.
Customers Respond to
items adverts
Viewed the
advertised
items
Customer
5. Temp Want to store
customer details.
Sales
officer
Record
customer
details
Customer
details saved
successfully.
customer
6. Ex Want to issue the
item to sell to
customer.
Associate
broker
Deposit item
to sell to
OZES
Items delivered
to OZES store.
Associate
broker
7. Temp Want to keep
record of sold
items.
Sales
officer
Record item
sold
Sold items
details saved
successfully.
Customer
8. Temp Want to check
quality of the
items
Quality
officer
Check, log
and store the
item
Items quality
checked
successfully.
Associate
broker
9. Temp Want to link
items to the
respective
customers.
Full time
brokers
Associate item
to customer
Items
associated to
the buyers
successfully.
Customer
10. Temp Want to have
commission
increment.
Associate
broker
Negotiate for
commission
Broker agrees
on the sales
commission.
Sales
officer
11. Temp Want to store
original owner
details.
Sales
officer
Record the
original item
owner details
Original item
owner recorded
successfully.
System
12. Ex Customer wants
to buy an item ,
item is available
and customer
agrees on price
Sales
officer
Sell second
hand item
Items are sold
to customers.
Customer

10Australian Electric Supply Management System Model and Design
13. Temp Want to pay for
the item.
Customer Pay purchase
price
Customer
deposited
payment to
trust account.
Finance
officer
14. Ex Want to pay
commission to
associate brokers.
Finance
officer
Pay broker Broker
received
commission
payments.
Associate
broker
(Thomas, 2013).

11Australian Electric Supply Management System Model and Design
3.2 A Use Case Diagram
(Shamkant, 2015).

12Australian Electric Supply Management System Model and Design
3.3 Use Case Description (intermediate)
Name Sell second hand item
ID UC12
Description This is the case where the item brought by the associate broker to the
company is sold to the respective buyer customer.
Actors i. Sales officer.
ii. Associate broker
iii. Customer
Organizational
benefits
This is where the organization gains profit and also the brokers some salary
through the sales commissions.
Frequency of use At least ten times per day.
Triggers i. Customer wants to buy an item
ii. Item is available
iii. Customer agrees on price
Pre-conditions i. Associate broker advertise item.
ii. Customer responds to broker adverts.
iii. Customer wants to buy the item.
Post conditions i. Customer pay purchase price.
ii. Customer receives the item.
Main course Below are the steps of the sell second hand item.
i. Associate broker advertise item.
ii. Customer responds to broker adverts.
iii. Customer wants to buy the item.
iv. Associate broker deposit the item to the company.
v. The quality officer checks the item for quality.
vi. The full time broker stores the item.
vii. The customer pays for the item.
viii. Customer receives the item.
ix. Finance officer pay the associate broker.
Exceptions Below are the exception conditions
EX1:Buyer want to buy item
Below are steps for first exception condition
i. Customer responds to broker adverts.
ii. Customer wants to buy the item.
iii. Customer pay for the item
EX2:Seller want to sell item
Below are steps for second exception condition
i. Customer responds to broker adverts.
ii. Customer wants to buy the item.
iii. Customer pay for the item.
iv. Sales person issue item to customer.
(Ramez, 2015).

13Australian Electric Supply Management System Model and Design
3.4 Domain Model Class Diagram
(Elmasri, 2013).

14Australian Electric Supply Management System Model and Design
3.5 Design Class Diagrams
3.5.1 Order class diagram
3.5.2 Associate broker class diagram
(Dick, 2018)

15Australian Electric Supply Management System Model and Design
Reference
Dick,B.(2018) IT Project Management Essentials: Information Systems Project Methodology
Kindle Edition.1st edn.New York:Amazon Digital Services LLC.
Elmasri,E.(2013) Database Systems: Models, Languages, Design and Application Programming.
2nd edn India: PEARSON EDUCATION.
Ramez,E.(2015) Database Systems: Models, Languages, Design and Application Programming
- International Edition Paperback.2nd edn. India:PEARSON EDUCATION.
Shamkant, B.(2015) Fundamentals of Database Systems (7th Edition).India:pearson.
Thomas,C.(2013) Database Systems: A Practical Approach to Design, Implementation and
Management: WITH Success in Your Project.1st edn. USA:Addison Wesley.
Stephen,H.(2014) Management Information Systems with student CD and MISource.3rd edn.
New York:McGraw-Hill.

16Australian Electric Supply Management System Model and Design
4 Appendix
Appendix A: Memo on pertinent issues
Memorandum
TO: Executive Business People
FROM: [Student Name]
CC:[Proffessor]
SUBJECT: Implementing proposed system
This is a memo concerning the implementation of the new proposed system in your organization and the
proposed system will be installed in your computers for use and to make the operations easy.
In the implementation process there are two major aspects that will be put into consideration which
include adopting a User Centered Design (UCD) approach and Human Computer Interaction (HCI) which
mainly make use of the content relation management (CRM) application.
The User Centered Design is the method that will be adopted in the implementation which is an iterative
design process where the development team will involve the members as the system users and the
implementation will focus on the user’s needs and this will be done in phases.
The Human Computer Interaction plan will be included in the system design, this will entail various
aspects as the way the system user will be able to interact with the computer system.
However the plan that will be used for the users to interact with the system includes the use of the system
keyboard to key in data, the system login forms and the system data capture forms.
Moreover the system implemented will have interaction methods which include the use of menus, buttons
and links.
Therefore the implementation of the system will be involving all users in the various phases and the
delivered system will meet all requirements and ease the service delivery and record management.
Yours faithfully
System development manager

17Australian Electric Supply Management System Model and Design