ATMC Semester 1 ICT700 Systems Analysis and Design Report

This report provides a comprehensive analysis of system design, focusing on the application of various software development methodologies. It begins with a consultation section, exploring Scrum Agile, Waterfall, and Extreme Programming models, highlighting their advantages, disadvantages, and recommendations for implementation. The report then delves into a case study analysis, presenting an event table, use case diagram, and use case descriptions to illustrate system functionalities. A domain model class diagram and a class diagram for an associate broker and order are also provided to visually represent the system's structure. Finally, a memo is included, addressing the implementation of a management information system within Australian Electric Supply (OZES), discussing the importance of Human-Computer Interaction (HCI) and User-Centered Design (UCD) in the development process. The report concludes with a bibliography of relevant academic sources.

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

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

3SYSTEM ANALYSIS AND DESIGN
1. Consultation
SCRUM
Agile methodology is a very useful framework of software development life cycle
(SDLC) which uses the concept of iterative software development models for greater flexibility
and efficiency of the software. Scrum is an agile methodology to manage software development.
Scrum acts like a framework that helps in better teamwork. This framework is designed keeping
in mind that the team is unaware of the workings of the project and it helps them to adapt to
changes in the working condition and gain knowledge and improve during the development
cycle. The phases of scrum model are:
 Product backlog creation- This is a list or features that are required to be
implemented in the development process. This list is sorted by the priority of each
item.
 Sprint planning and backlog creation- In this phase the sprint or the release time is
determined and short sprit allows the release of the software in less time, which in
turn will help in the bug fixes.
 Working on sprint- The working structure of the sprint is developed in this phase.
 Testing the product- This phase tests the developed end product or the final
software.
 Next sprint planning- This phase is used to plan the future improvement of the
software.
Advantages

4SYSTEM ANALYSIS AND DESIGN
 This framework provides a good development process for the software which
amounts to a saleable product even in the development phase.
 The backlogs helps to fix the bugs and that results in greater revenue.
 The software is tested throughout the process because of the different sprint phases.
 The different sprint phases also enables the team to change the scope of the project.
Disadvantages
 Planning and structuring of the scrum can be difficult if there is no clear definition of
the project.
 The scrum is a very long process as it involves iteration.
 Scrum meetings and reviews require much resources.
Waterfall model
The basic idea of waterfall software development cycle is to complete one phase before
proceeding to the next phase so that there is no overlapping. It is also known as linear-sequential
life cycle model and is one of earliest approach of SDLC. This process follows liner sequential
flow which means that it is ensured that before starting a process the previous one is completed
and there is no overlapping in any process. The phases of waterfall model are:
 Requirement analysis- This step gathers all the information and requirement to develop
the software and a documentation is made accordingly.
 System design- The requirements are studied and a design of the system is prepared
according to the requirements. This step helps to specify the hardware and software
requirements.

5SYSTEM ANALYSIS AND DESIGN
 Implementation- In this step the implementation is done according to the system design
and the each unit is tested after their development and is commonly known as Unit
testing.
 Testing- This step is used to implement all the developed units into a single unit and the
whole unit is tested afterwards.
 Deployment- The software is deployed in the market and made available to the public.
 Maintenance- If some issues or bugs are detected after the release this step is used to fix
those issues. This phase also enhances the software.
Advantages
 This model is very simple and easy to use.
 Easily manageable as the model is very rigid in structure.
 The tasks are easily manageable as there is no overlapping in any process.
Disadvantages
 The development process is very tedious.
 This is a not a very good model for object-oriented projects and for long and ongoing
projects.
 Uncertainty and risks are high.
 Adjusting the scope of a project might result in end of the project.
Extreme programming
The aim of extreme programming or XP, is to develop or produce high quality software
and is an agile software development framework. It also aims to improve the quality of life of the
development team. XP is applicable when there is need to change the software requirements
dynamically, when risks are detected in fixed time projects by the use of new technology.

6SYSTEM ANALYSIS AND DESIGN
Advantages
 Programming related risks are reduced.
 Reduces cost and time to develop a software.
 Simple programs are created so that there is a scope for improvement at later stages.
 Regular testing of the software helps in bug fixes and helps to develop a faster and
efficient software.
 Promotes teamwork and increase satisfaction and retention of employees.
Disadvantages
 If programmers are separated geographically then surely extreme programming is not the
best option.
 These is no assurance of the quality of the code.
 Software development does not depend on coding alone so, there is need for a good
design of the software also.
 There is no proper documentation of the changes and this may lead to unexpected failures
or retention of previous bugs.
Recommendation: The extreme programming has been chosen for the implementation of
the information system at Ozes. The extreme programming will allow the organization to handle
change in the most efficient and effective way. The functionality and coding quality of the
system will be extremely high. The system will be almost free of bugs. As the other aspects of
the system rather than coding is not considered as important, the system will be developed very
quickly.
2. Analysis of Case

7SYSTEM ANALYSIS AND DESIGN
Event Table
Event Event
Type
Trigger Source
Actor
Use Case Output Destination
actor
Register External New Client Client Create an
Account
The customer
database is
updated with
a new row
Client
Sign in External Access
request
from client
Customer Access
System
System
allows
authentication
to use the
functions
Client
Order External Potential
sales of
product
Client Make
Order
The customer
order is
transferred to
the
warehouse
Warehouse
Pack
Order
Internal Initiate
Delivery
Warehouse Ready
Order
The
warehouse
staff will
check the
order details
and pack
Delivery
Personnel

8SYSTEM ANALYSIS AND DESIGN
orders as per
order list
Deliver
Order
Internal Order
ready to be
delivered
Delivery
Personnel
Deliver
order
The products
are delivered
to the client
Management
Use case diagram
Figure 1: Use Case Diagram
(Source: Created by author)

9SYSTEM ANALYSIS AND DESIGN
Use Case description
Use Case Name Make Order
Use Case ID Client_UC_03
Actors Client
Precondition The customer must be logged in
Activities Actor System
The customer open the system The system shows the options in
home page
Customer add products to cart System updates cart
Customer place order System ask for confirmation
Client confirm
Post condition A new order is assigned to the warehouse staff
Exception The product is out of stovk

10SYSTEM ANALYSIS AND DESIGN
Domain Model Class Diagram
Figure 2: Class Diagram
(Source: Created by author)

11SYSTEM ANALYSIS AND DESIGN
Class diagram for Associate Broker and order
Figure 3: Class Diagram for associated broker and order
(Source: Created by author)
3. Memo
Date: May, 30, 2019
To: The Executive Analyst
From: The Business Analyst of Australian Electric Supply (OZES)
Subject: Implementation of Management Information System in OZES
I am writing this to inform you that OZES is planning to implement an information
system that manages their business process of second hand selling in the business. The

12SYSTEM ANALYSIS AND DESIGN
information system is already under process and I am expecting to finish the same within 6 to 9
more months.
The HCI (Human-Computer Interaction) has a wide scope and includes the field that overlaps the
areas with the user central design (UCD) and other related user experience designs. With the use
of HCI and UX design, the main focus of the professional is on the academics which includes
scientific research and also to develop an understanding related to the user.
The UCD used to design the software uses iterative process to make sure it helps the
designers to focus mainly on the needs of the users, what are their requirements and this is
implemented in each design phase. The user central design as the name suggests, primarily
involves the user in the design process and several other research techniques in the system
design. UCD design techniques offers a high usability for the users and also includes a high
accessibility of products. The UCD help developers or the designers to understand the users or
their needs by including a mix investigation process along with a generative method and several
other tools.
The UCD consists of mainly four phases which are understanding the context of use of
the system, identifying the requirements of the users, design of the solution or the proposed
design and evaluation of requirements for the proposed system. The main users of this
information system will be the management system of the OZES, the associated brokers of the
organization and the second hand product purchasing customers and the selling customer of the
respective product. There should be interviews and surveys with the users of the information
system to collect data to improve the system.

13SYSTEM ANALYSIS AND DESIGN
Bibliography
Arnott, D., & Pervan, G. (2016). A critical analysis of decision support systems research
revisited: the rise of design science. In Enacting Research Methods in Information Systems (pp.
43-103). Palgrave Macmillan, Cham.
Balanis, C.A., 2016. Antenna theory: analysis and design. John wiley & sons.
Dennis, A. and Wixom, B.H., 2018. Systems analysis and design. Wiley.
Zhang, T. C., Wen, C. K., Jin, S., & Jiang, T. (2016). Mixed-ADC massive MIMO detectors:
Performance analysis and design optimization. IEEE Transactions on Wireless
Communications, 15(11), 7738-7752.