Implementing Management Information System in OZES

Running head: SYSTEM ANALYSIS AND DESIGN
ICT 700 System Analysis and Design Task 2
Name of Student-
Name of University-
Author’s Note-

2SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Consultation.................................................................................................................................2
2. Analysis of Case..........................................................................................................................5
Event Table..................................................................................................................................5
Use case diagram.........................................................................................................................6
Use Case description....................................................................................................................6
Domain Model Class Diagram....................................................................................................8
Class diagram for Associate Broker and order............................................................................9
3. Memo...........................................................................................................................................9
Bibliography..................................................................................................................................12

3SYSTEM ANALYSIS AND DESIGN
1. Consultation
This agile and iterative methodology allows rapid changes and include adaptive planning,
delivers the software in short time and includes elf-organization (Satzinger, Jackson and Burd
2011). This methodology is flexible, and allows continuous improvements regarding the quality
of the software. As the OZES management system deals with user requirements that needs to be
changed from time to time, the following three agile methodologies can be used for developing
the information of OZES.
Methodology: Scrum Agile Methodology
Discussion: The scrum methodology includes interlocking steps as well as components
where the owner of the OZES can make the priority of the activities listed in product backlog
(Schmitz, Mahapatra and Nerur 2018). The methodology includes sprint backlog which includes
a wish of the owner and tries to implement the plan. Each sprint using this methodology is
completed in between 2-4 week and meeting are organized after a sprint gets completed.
Advantages: The advantages are listed below:
 This methodology is flexible as well as adaptive.
 Scrum methodology is creative and includes innovation.
 This helps to lower the cost.
 Improves the quality of the software.
Disadvantages: The disadvantages are listed below:
 Training is required for the project team.
 With this methodology, scalability is difficult.

4SYSTEM ANALYSIS AND DESIGN
Methodology: Extreme Programming Methodology
Discussion: This methodology is mainly used to increase the customer satisfaction. The
XP methodology mainly concentrates on the present requirement of the user rather than thinking
of future requirement. This methodology is centred on small development cycles and include
short releases (Rasnacis and Berzisa 2017). This methodology uses unit testing and include
frequent communication with the client. The Extreme development methodology includes
involvement of the owner of the OZES and establish a good communication between the
development team and owner of the OZES. User stories are also stated in this developments and
the owner or the client of the application software can prioritize the functions that are important.
This can help the OZES to state the most important features that are to be included in the system.
This methodology delivers the software in very short interval of time which might help the
OZES to launch the management system in 1 to 3 weeks.
Advantages: The advantages are listed below:
 Helps to save cost of Australian Electric Supply.
 The codes are simple in this methodology.
 The process that is carried out is visible as well as accountable.
 Includes feedback from the client.
Disadvantages: The disadvantages are:
 Focuses mainly on the codes instead of design.
 Does not measures the assurance of code quality.
Methodology: Feature Driven Development (FDD)