Implementation of Management Information System (MIS) in OZES

Running head: AUSTRALIAN ELECTRIC SUPPLY
Australian Electric Supply
Name of the Student
Name of the University
Author note

1AUSTRALIAN ELECTRIC SUPPLY
Table of Contents
1. Consultation.................................................................................................................................2
2. Analysis of the case.....................................................................................................................7
2.1 Event Table............................................................................................................................7
2.2 Use Case Description.............................................................................................................9
3. Memo.........................................................................................................................................12
Bibliography..................................................................................................................................14

2AUSTRALIAN ELECTRIC SUPPLY
1. Consultation
Based on different kind of consultation within the OZES management team, it has been
discussed that the iterative and agile kind of methods of systems development would be useful
within the organisation. The discussion in this report focuses over the various kind of
methodologies. This include – Waterfall Methodology, Scrum Methodology, Unified
Programming and Extreme Programming. The OZES management system is primarily
concerned with the requirements of user. These kind of requirements would change in a
continuous manner. The discussion over the following methodologies could be helpful for
development of the information provided by OZES.
Methodology: Waterfall Methodology
Discussion: With this kind of methodology, the approach towards the project would be
based on completing each of the distinct stages. This would be put forward in a step by step
manner that would be ultimately released before the consumers1. Any task that would be
performed with the help of waterfall methodology would be subdivided into various kind of
activities.
Advantages – The advantages with the use of Waterfall Methodology are:
1. This kind of methodology would be helpful for being implemented in small projects in
which each of the requirements would be defined in a clear manner and thus would be well
understood2.
1 Salvador, Carolina, Arturo Nakasone, and Jose Antonio Pow-Sang. "A systematic review of usability techniques in
agile methodologies." In Proceedings of the 7th Euro American Conference on Telematics and Information Systems,
p. 17. ACM, 2014.
2 Serrador, Pedro, and Jeffrey K. Pinto. "Does Agile work?—A quantitative analysis of agile project
success." International Journal of Project Management 33, no. 5 (2015): 1040-1051.

3AUSTRALIAN ELECTRIC SUPPLY
2. There would be an easy way of monitoring over the rigidity of model as each of the
phase would have specific deliverables and a proper process of review.
Disadvantages – The disadvantages of the model could be listed as:
1. There is a huge rise in the number of uncertainties and risks associated with the use of
this methodology.
2. It would not be able to suit the ongoing and longer projects.
3. It would also not be suitable for implementing in projects where the requirements
would have a moderate nature of getting changed at different steps.
Methodology: Scrum Methodology
Discussion: This methodology can be defined as a form defined by agile ways in which a
project could be managed with the help of different forms of software development
methodologies3. This kind of framework would also help in the development of teams in a
grouped manner. This framework focuses over continuous form of improvement4. This
framework could also be discussed as heuristic and also help teams to adjust in fluctuating
situations.
Advantages – The advantages of using the Scrum methodology are:
1. This methodology would ensure an effective use of money and time within the
project5.
3 Glória Júnior, Irapuan, Rodrigo Oliveira, and Marcirio Chaves. "A Proposal for Using Web 2.0 Technologies in
Scrum." (2014).
4 Peroni, Silvio. "A simplified agile methodology for ontology development." In OWL: Experiences and Directions–
Reasoner Evaluation, pp. 55-69. Springer, Cham, 2016.
5 Qurashi, Saja Al, and M. Qureshi. "Scrum of scrums solution for large size teams using scrum
methodology." arXiv preprint arXiv:1408.6142 (2014).