logo

Australian Electric Supply Management System Model and Design

   

Added on  2022-11-14

17 Pages2733 Words394 Views
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.

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Agile System Development Methodologies for OZES Case Study
|17
|3121
|414

Implementing Management Information System in OZES
|16
|2390
|402

Implementing Management Information System in OZES
|12
|1968
|27

System Analysis and Design
|15
|2426
|115

Agile Methods and Memo
|13
|2347
|302

System Analysis and Design
|19
|2729
|159