System Analysis and Design

This paper discusses the methodologies of agile and iterative development in the context of system analysis and design. It includes a memo and analysis of a case study. The paper also explores event tables, use case diagrams, use case descriptions, domain model class diagrams, and design class diagrams. It highlights the advantages and disadvantages of agile methodologies.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student:
Name of the University:
Author Note

1
SYSTEM ANALYSIS AND DESIGN
Executive summary:
The purpose of this paper is to prepare a report for the OZES management team. In
this report there will be a methodologies of agile and iterative development. There will be a
memo and a proper analysis about the case study in this paper.

2
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Executive summary:...................................................................................................................1
Methodology:.............................................................................................................................3
Event Table................................................................................................................................3
Use Case Diagram......................................................................................................................4
Use Case Description.................................................................................................................6
Domain Model Class Diagram...................................................................................................7
Design Class Diagram................................................................................................................8
Bibliography...............................................................................................................................9

3
SYSTEM ANALYSIS AND DESIGN
Methodology:
Australian Electric Supply (OZES) is a business that distributes and supplies electrical
equipment to all over the Australia. OZES is having some casual employees who are called as
the associate brokers that sell and buy electrical equipment’s that are electrical. The major
advantage that OZES is currently having is they are having few brokers, each of them store
their own sales record in their own way. In addition OZES have the ability to record the
broker details that including the bank details of them so that they can deposit money to their
bank accounts. On the other side, the major disadvantage that OZES is having that, it has
been becoming the concerned that the company is not gaining profit from the gathered data
from each of the sales for the record. The main idea behind the development of the agile
methodology is for countering various convoluted strategies to pervade the development of
the software. The methods are as follows:
Customer satisfaction:
The project development with various contributions that are inspired. Maintaining and
developing various software to carry out the projects that are complex. The most important
agile methodologies are as following:
Extreme programming:
This might be described as one of the foremost and important Agile methodology
which have the ability to explain the perception that is high degree among two parties that are
different. It is involved by the developers that for creation as well as upgradation of the
software for performing several researches on the technologies that are new for offering the
best service for the consumers who are associated. On the other side the consumers are
involved to inspire the procedure of the development through emphasizing and utilizing the
features that are the best for the products of the software. The feedback that has been shared

4
SYSTEM ANALYSIS AND DESIGN
from the consumers that can help the developers for understanding the need of the consumers
as well as inspiring them for the development that is the best. The methodology that has been
discussed carried five significant values which are simplicity, communication, respect,
feedback and courage.
Advantages:
 Without wasting the time that has been processed, comparatively this can provide a
working environment that is faster alongside the development that is continuous as
well integration.
 There is the advantages to carry out the visible and open communication procedure as
well as by eliminating the failures as well as the bugs.
 In the XP, the procedure of the feedback loop is so less as well as reducing the
investment cost.
Disadvantage:
 Sometimes this has been becoming so much difficult for handling the changes that are
constant, this can be resulting in the lack in the documentation as well as integration.
Scrum:
This methodology of the agile comprises alongside the complicated most principle s
for the development. Such as the extreme programming the admin of one particular product
must has to collaborate with the team of the information technology as well as the
development for the collectively isolate the functions of the systems. The advantages and the
disadvantages are, The major advantage that OZES is currently having is they are having few
brokers, each of them store their own sales record in their own way. In addition OZES have
the ability to record the broker details that including the bank details of them so that they can
deposit money to their bank accounts. On the other side, the major disadvantage that OZES

5
SYSTEM ANALYSIS AND DESIGN
is having that, it has been becoming the concerned that the company is not gaining profit
from the gathered data from each of the sales for the record.
Crystal methodology:
The concept of the crystal methodology is one of the parts of the crystal methodology
like crystal yellow, crystal clear and crystal red. It is involved by the developers that for
creation as well as upgradation of the software for performing several researches on the
technologies that are new for offering the best service for the consumers who are associated.
On the other side the consumers are involved to inspire the procedure of the development
through emphasizing and utilizing the features that are the best for the products of the
software. There is the advantages to carry out the visible and open communication procedure
as well as by eliminating the failures as well as the bugs.
Feature driven methodology:
The method of the FDD methodology that has been discussed, turns the models into several
builds at the fortnightly iteration. The methodology that has been discussed carried five
significant values which are simplicity, communication, respect, feedback and courage.
Without wasting the time that has been processed, comparatively this can provide a working
environment that is faster alongside the development that is continuous as well integration.
Event Table
The event table is basically a table which is gathered with the data and information,
also it is written typically to the log files that is for each of the scenarios and this is also
appearing the analysis windows. The events table have been contained the data as well as the
information that are about the timing of all of the events which can occur the entire scenario.
The only event which are considered as the stimulus with all of the codes that re related to the
events can be able to appear in the table of the events. The times that are given for that

6
SYSTEM ANALYSIS AND DESIGN
resolution is the difference of only 0.1 milliseconds. The table of the events are having
various columns, they are event type, trail, code, time, custom properties etc. For the
population of the table of the events, the triggers have to be created. The trigger is the major
construct of that particular database that may run the Script. The events table is given below.
Event Trigger Source Use Case Response Destinatio
n
Placement of
the
Advertisement
Upload the
Advertisement
Brokers Advertisement Contact Customers
Answer the
questions that
are given
Submitting
the answers
Customer Provide
Details
Request
reference
information
System
Connect with
Organisation
Placing call Customer Make Call Display
Questionnaire
System
Providing
reference
Reference ID Customer Provide
Reference
Store the
Details
System
Sell of the
items
Post
Advertisement
Brokers Sell-second
hand Items
Display to
customer
Customer
Buying Item Place a
purchase
request
Customer Purchase Process
Purchase
System
Items has Deposition by Staffs Item Pack Items System

7
SYSTEM ANALYSIS AND DESIGN
been received OZES Deposition
Send the
Items
Packing and
sending
Staffs Send Items Send to the
customer
Customer
Mail
Forwarding
Item sold System Send Mails Access
details
Broker
Payment
making
Receive Items Customer Receive
Payment
Process
broker
payment
System
Broker
Payment
Make
Payment
System Broker
Payment
Receive
payment
Broker
Use Case Diagram
The use case diagram is one of the depiction which is able to be present through the
graphical interface which is about that interactions that are existing with the elements of the
system. The use cases have been remaining the type of the strategies which can be used for
analysing the systems for the identification, clarification and lastly the organising the needs
and the requirements of all of the systems. The term that is considered as the systems has
been referred to something that is required for operating as well as for developing such as the
mail order items, sales and the services that are related to the websites. The unified model
language has employed the use cases diagrams. The goals of the objectives can have the
ability for including the needs and requirement plans, validity testing, normal testing and
lastly debugging of the product. The use case diagram is provided below.

8
SYSTEM ANALYSIS AND DESIGN

9
SYSTEM ANALYSIS AND DESIGN
Use Case Description
To write the contents that are related to the use cases, this might start by picking one
scenario as well as by assuming the taken scenario as the primary scenario. The beginning of
that description from that the use case will start, by writing the primary scenarios for the
success just of the sequential numbers of all of the steps. The other scenarios are able to be
written as well as taken as the extension. All of the extensions are having the ability for
achieving the success. The use cases have one of the primary actor which have the ability to
call the systems to deliver the services. All kinds of the steps which have the existence in the
use cases that is also for the interaction in between the client and the system. The most
complicate step within the use case is the use case only.
Name Sell-second hand item
ID 1
Description The brokers are able to sell items that are considered as the second
hand items for all of the customers. The clients may have a look at
the advertise as well as see all of the products that are available.
Actors The actors who are able to participate in the system that are
considered as the consumers.
Triggers The procedure that has been triggered after the advertise, is posted
through the broker.
Pre-condition Advertisement
Post-condition Make Purchase
Flow of process Actor System
1. Sending advertisement
2. Sell Second-hand item
1. Posting Advertisement
2. Displaying item to the

10
SYSTEM ANALYSIS AND DESIGN
3. Making Purchase customer
3. Selling Item
Exceptions Exceptions would take the place whether the advertisement shall not
able to be reached out to the customer.
Domain Model Class Diagram
The domain model is an illustrating concepts which are within many of the domain.
The domain model class diagram was created at the time of the object oriented analysis. This
model is able to be identified through the conceptual class sets. It is on the basis of the design
of that particular software. The class diagrams are having much usage in several stages of the
system design. At the analysis part the class diagram can help the people to understand better
about the requirements and the need of the domain.

11
SYSTEM ANALYSIS AND DESIGN
Design Class Diagram
The UML diagram can be utilized for the manner that they are in a multiple number.
The term modelling might be considered as the modelling term that is common for the
purpose of the design class diagram.
On the above diagram, this can be seen that the date, purchase id, phone number and the
order detail is considered as integer and rest of the thing have been considered as the string.

12
SYSTEM ANALYSIS AND DESIGN
Memorandum
To: [Business People in the executive class]
From: [OZES Managing Department]
Date: [Please fill]
Subject: [Adoption of UCD approach for better HCI environment]
[Opening – User Centred Design (UCD) is one of the best way to develop or improve the
Human Computer Interaction (HCI) between the users and the company. UCD is widely used
in MNC companies for better understanding of the needs of the customers via an iterative
process of brainstorming and investigative (like by online surveys and interviews) approach.
Each of the iteration of the UCD that can pass from the four stages that can understand the
context as well as by specifying the requirements of the users and solution designing and
lastly the needs and requirements.]
[Summary – OZES is a young Australian brand of distributing electrical products throughout
the country and hence to survive in the competitive market it is very much required to
dynamically review and understand the needs of the customers. UCD via human computer
interaction very much helps to understand customers’ need and characteristics which helps to
segment customers based on their liked or needed products. The major advantage that OZES
is currently having is they are having few brokers, each of them store their own sales record
in their own way. In addition OZES have the ability to record the broker details that including
the bank details of them so that they can deposit money to their bank accounts. . It is involved
by the developers that for creation as well as upgradation of the software for performing
several researches on the technologies that are new for offering the best service for the

13
SYSTEM ANALYSIS AND DESIGN
consumers who are associated. Without wasting the time that has been processed,
comparatively this can provide a working environment that is faster alongside the
development that is continuous as well integration. On the other side, the major disadvantage
that OZES is having that, it has been becoming the concerned that the company is not gaining
profit from the gathered data from each of the sales for the record. Thus implementation of
new UCD based technology will definitely help the company to serve its customers in a
better way.]
[Conclusion – Thus it can be concluded that it is advisable to the executive business class of
customers to participate in UCD based design implementation in your companies along with
us and thus to efficiently serve your business needs.]

14
SYSTEM ANALYSIS AND DESIGN
Bibliography
Arora, P.K. and Bhatia, R., 2018. Agent-Based Regression Test Case Generation using Class
Diagram, Use cases and Activity Diagram. Procedia Computer Science, 125, pp.747-753.
Couckuyt, I., Dhaene, T. and Demeester, P., 2014. ooDACE toolbox: a flexible object-
oriented Kriging implementation. The Journal of Machine Learning Research, 15(1),
pp.3183-3186.
El Alami, A. and Bahaj, M., The Migration of a Conceptual Object Model COM (Conceptual
Data Model CDM, Unified Modeling Language UML class diagram...) to the Object
Relational Database ORDB. MAGNT Research Report (ISSN. 1444-8939), 2(4), pp.318-32.
Maier, A., Baltsen, N., Christoffersen, H. and Störrle, H., 2014. Towards diagram
understanding: A pilot study measuring cognitive workload through eye-tracking.
In International Conference on Human Behaviour in Design 2014.
Smid, W. and Rensink, A., 2013. Class diagram restructuring with GROOVE. arXiv preprint
arXiv:1312.0350.
Stellman, A. and Greene, J., 2014. Learning agile: Understanding scrum, XP, lean, and
kanban. " O'Reilly Media, Inc.".
Xu, H. and Musicant, O., 2016. Design and Implementation for Ontology Modeling of
Design Knowledge Based on UML Class Diagram. Telkomnika, 14(3A), p.326.