Implementation of Management Information System (MIS) in OZES

This memo discusses the implementation of a Management Information System (MIS) in OZES for managing the different processes of business and second-hand selling.

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).

4AUSTRALIAN ELECTRIC SUPPLY
2. The entire list of developments would be entirely coded and tested based on the review
over sprints6.
3. The team would gain clear view and visibility through the use of scrum meetings7.
4. Shorter sprints would enable changes based on regular feedbacks in an easy manner.
Disadvantages – The disadvantages in relation to scrum methodology could be defined
as:
1. This methodology often leads to creep in scope due to a certain lack of a definite due
date.
2. Daily kind of meetings might lead to a factor of frustration for the team members.
3. The implementation of high quality within the system would incur an aggressive
process of testing.
Methodology: Unified Programming
Discussion: The Unified Programming process based on software development could be
defined as an incremental and iterative process of software development8. The framework of
Unified Programming could be defined as a modern form of software development process. This
kind of methodology divides the software development process into four unique phases known
6 Ungan, Erdir, Numan Çizmeli, and Onur Demirörs. "Comparison of functional size based estimation and story
points, based on effort estimation effectiveness in SCRUM projects." In 2014 40th EUROMICRO Conference on
Software Engineering and Advanced Applications, pp. 77-80. IEEE, 2014.
7 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.
8 Gilray, Thomas, Michael D. Adams, and Matthew Might. "Allocation characterizes polyvariance: a unified
methodology for polyvariant control-flow analysis." In ACM SIGPLAN Notices, vol. 51, no. 9, pp. 407-420. ACM,
2016.

5AUSTRALIAN ELECTRIC SUPPLY
as modeling of business, design and analysis, implementation of processes, testing of systems
and the final deployment of systems.
Advantages – The advantages of this methodology could be defined as:
1. The methodology focuses on implementing accurate kind of documentation9.
2. The methodology helps in resolving the risks over the project in a proactive manner.
Careful changes would be made and requests would be further managed.
3. There is a low need for integrating of process as the integration would move
throughout the process of development.
Disadvantages – The disadvantages associated with the methodology are:
1. The process of software development based on this process is highly complex in nature
and are not properly organized.
2. Each of the integrated processes are highly complex in nature, which makes it difficult
to understand10.
3. Many kind of integration within the process of software development would incur
confusion and thus raise issues during the testing process.
Methodology: Extreme Programming
Discussion: It can be defined as an agile based software engineering methodology. It
would also be known as XP methodology that could be used for the creation of software in an
9 Rasnacis, Arturs, and Solvita Berzisa. "Method for adaptation and implementation of agile project management
methodology." Procedia Computer Science 104 (2017): 43-50.
10 Špundak, M., 2014. Mixed agile/traditional project management methodology–reality or illusion?. Procedia-
Social and Behavioral Sciences, 119, pp.939-948.

6AUSTRALIAN ELECTRIC SUPPLY
unstable environment11. This methodology allows greater kind of flexibility and to lower the
various costs incurred within the requirements of software.
Advantages: The advantages of this kind of methodology could be described as:
1. The methodology is mainly consistent with the modern tools of software development.
This is mainly due to the reason that developers would be able to produce high quality software.
2. This methodology focuses on the involvement of customers12.
3. The methodology also helps in establishing rational kind of schedules and plans.
Disadvantages: The disadvantages of this methodology are:
1. With the involvement of people, the effectiveness would increase.
2. Too much of changes within the development processes would increase with this kind
of methodology.
3. Exact estimates of work effort would not be tracked. This is because the exact scope
and requirements would not be known at an early phase13.
Recommendation: Based on the discussion over the above methodologies, it could be
discussed that scrum methodology would be viable for the use of the OZES. This methodology
could be useful for the company to keep a track of their records and thus maintain a proper
update of their stocks.
11 D'Souza, Manoj Joseph, and Paul Rodrigues. "Extreme pedagogy: An agile teaching-learning methodology for
engineering education." Indian Journal of Science and Technology 8, no. 9 (2015): 828.
12 Puterman, Martin L., ed. Dynamic Programming and Its Applications: Proceedings of the International
Conference on Dynamic Programming and Its Applications, University of British Columbia, Vancouver, British
Columbia, Canada, April 14-16, 1977. Academic Press, 2014.
13 Li, J., Tang, L., Sun, X. and Wu, D., 2014. Oil-importing optimal decision considering country risk with extreme
events: A multi-objective programming approach. Computers & Operations Research, 42, pp.108-115.

7AUSTRALIAN ELECTRIC SUPPLY
2. Analysis of the case
2.1 Event Table
Event Event
Type
Trigger Source Use Case Output Destination
Signing up Internal Sign up by
Customer
Customer Sign up Account created Customer
Logging Internal Login by
customer
Customer Login Account setup Customer
Ordering
of
Products
External Purchase Customer Purchase Ordering of
products
Customer
Selling
details
State Products
ordered
Management Products
ordered
Product details
provided
Customer
Seller
details
External Login
credentials
Seller Login
credentials
Seller details
provided
Management
Product
Details
Temporal Description
of product
Seller Descriptio
n of
product
Supported Product
details
Management
Selling
Offers
Internal Uploading
offers
Management Selling of
Offers
Items sold Customer
Viewing
Offers
External Message
generated
Customer Viewing
all offers
Items sold Management
Purchase
Products
External Search for
items
Seller Purchase
of Products
Items sold Customer
Receiving
Items
Temporal Item List
generated
Seller Receiving
of items
Items stacked Warehouse
Storing
Items
Temporal Item list
maintained
Seller Storing
items
Items arranged Warehouse
Warehouse
Storage
Temporal Items
matched
with list
Warehouse Warehouse
Storage
Storing of items in
a proper order
Customer
Customer
Details
Internal Asking for
customer
details
Customer Customer
details
Entering of
customer details
Management
View of
Sold Items
Internal Stock
update
Management View of
Items sold
Listing of sold
items
Warehouse

8AUSTRALIAN ELECTRIC SUPPLY

9AUSTRALIAN ELECTRIC SUPPLY
Use Case Diagram
(Figure 1: The Use Case Diagram for the OZES Information System)
(Source: Created by author)

10AUSTRALIAN ELECTRIC SUPPLY
2.2 Use Case Description
Name of Use Case Description
Scenario
described
Selling of hand items would be stored in this particular use case.
Triggered event Purchase of products by customers after negotiating of prices and details
of products
Description Price description of products are put in proper place. After any kind of
purchase, the seeling details are updated on the records of OZES.
Supported Actors The management, associate brokers and purchasing customer
Stakeholders The management, associate brokers and purchasing customer, OZES
Owner, purchasing and selling customer
Pre and Post
Conditions
Pre-conditions are that management would update product details. Post-
conditions include the negotiation of prices after they are viewed.

11AUSTRALIAN ELECTRIC SUPPLY
Domain Model Class Diagram
(Figure 2: Domain Model Class Diagram for the OZES Information System)
(Source: Created by author)

12AUSTRALIAN ELECTRIC SUPPLY
Class Diagram for Order Details and Associate Broker
(Figure 3: Class Diagram for the Order and Associated Broker)
(Source: Created by author)

13AUSTRALIAN ELECTRIC SUPPLY
3. Memo
Date: May 04, 2019
To: Executive Analyst
From: Business Analyst of QZES
Subject: Implementation of Management Information System (MIS) in OZES
This is to inform you that we are in the process of implementing an Information System
for managing the different processes of business and incurring the process of second hand
selling. The implementation is currently under process and is likely to end within the next 9
months.
Based on the prospects of second hand selling, it could be discussed that the Human
Computer Interaction (HCI) system would be implemented based on the user centric design.
Each and every kind of detailed information would be fed within the system for the
supportability of the users. The design of this kind of system would also help in high level design
of the entire system. Latest and updated technologies would also be used within the process of
development. However, another major point that would need to be in high discussion is that the
entire HCI system would be based on desktop version. This would also include different kind of
tablets and mobile phones. I would also like to present before you about the detailed kind of
discussion on the UCD and HCI, which are the prime fundamentals based on implication of
UCD within the system.
The HCI is defined to be covered under a broader area that would also overlap the
various areas based on implicating the User Centred Design (UCD) and the interior of design

14AUSTRALIAN ELECTRIC SUPPLY
based for the experience of users. Based on the implication of such kind of designs, it would be
highly helpful for maintaining the UX and HCI design. Hence the different practitioners mainly
focus over the ways in different scientific methods could be researched and an understanding
could be gained at an advanced level.
The development of the UCD could be defined as a certain iterative process based on
helping the designers for focusing over the needs of users in each of the phases of design. It
would mainly involves the users within the design process. Various kind of research have also
been made in the current process that would be helpful for implementation of the HCI. Based on
the impacts made by UCD, the designers and developers would be able to implement a certain
process of mix investigation. It could thus be defined as a generative method. Such kind of
different tools could be used based on understanding of the user needs.
The user who would manage the Information System would be responsible for managing
the various kind of systems within OZES. It would include the management for the associated
brokers, conducting of surveys and interviews, making a list of the purchases done and the sale
by the sellers. There are four kind of phases that would be included. These are: specification of
the requirements of user, designing particular solutions and thus evaluating the necessary
requirements that would be included within the system.
Hence, due to the above supported reasons, it could be recommended that the company
should implement the HCI and UCD systems based on bringing better impacts.

15AUSTRALIAN ELECTRIC SUPPLY
Bibliography
D'Souza, Manoj Joseph, and Paul Rodrigues. "Extreme pedagogy: An agile teaching-learning
methodology for engineering education." Indian Journal of Science and Technology 8, no. 9
(2015): 828.
Gilray, Thomas, Michael D. Adams, and Matthew Might. "Allocation characterizes
polyvariance: a unified methodology for polyvariant control-flow analysis." In ACM SIGPLAN
Notices, vol. 51, no. 9, pp. 407-420. ACM, 2016.
Glória Júnior, Irapuan, Rodrigo Oliveira, and Marcirio Chaves. "A Proposal for Using Web 2.0
Technologies in Scrum." (2014).
Li, Jianping, Ling Tang, Xiaolei Sun, and Dengsheng Wu. "Oil-importing optimal decision
considering country risk with extreme events: A multi-objective programming
approach." Computers & Operations Research 42 (2014): 108-115.
Peroni, Silvio. "A simplified agile methodology for ontology development." In OWL:
Experiences and Directions–Reasoner Evaluation, pp. 55-69. Springer, Cham, 2016.
Puterman, Martin L., ed. Dynamic Programming and Its Applications: Proceedings of the
International Conference on Dynamic Programming and Its Applications, University of British
Columbia, Vancouver, British Columbia, Canada, April 14-16, 1977. Academic Press, 2014.
Qurashi, Saja Al, and M. Qureshi. "Scrum of scrums solution for large size teams using scrum
methodology." arXiv preprint arXiv:1408.6142 (2014).
Rasnacis, Arturs, and Solvita Berzisa. "Method for adaptation and implementation of agile
project management methodology." Procedia Computer Science 104 (2017): 43-50.

16AUSTRALIAN ELECTRIC SUPPLY
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.
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.
Špundak, M., 2014. Mixed agile/traditional project management methodology–reality or
illusion?. Procedia-Social and Behavioral Sciences, 119, pp.939-948.
Ungan, Erdir, Numan Çizmeli, and Onur Demirörs. "Comparison of functional size based
estimation and story points, based on effort estimation effectiveness in SCRUM projects."
In 2014 40th EUROMICRO Conference on Software Engineering and Advanced Applications,
pp. 77-80. IEEE, 2014.