ICT700 System Analysis: Software Development Methodologies Report ATMC

This document presents a system analysis report focusing on various software development methodologies, including Dynamic Software Development Method, Lean Thinking, Plan Driven Development, and Extreme Programming. It offers a comparative analysis of these methodologies, highlighting their advantages and disadvantages. The report also includes a recommendation for the Australian Fashion Designs case study, suggesting the Dynamic Software Development Method for implementing an accounting information system. Additionally, the document features a memo on adopting a User Centered Design (UCD) approach, an event table, a domain model class diagram, a design class diagram, a use case diagram, and a use case description. The analysis aims to provide a comprehensive understanding of different software development approaches and their practical applications.

Running head: SYSTEM ANALYSIS
System Analysis
Name of the Student:
Name of the University:
Author Note

1
SYSTEM ANALYSIS
Table of Contents
Part A...............................................................................................................................................2
Task 1: Report..................................................................................................................................2
Methodology 2: Lean Thinking...................................................................................................3
Recommendation.........................................................................................................................5
Task 2: Memo..................................................................................................................................7
Appendix......................................................................................................................................7
Part B: Modelling and Diagraming..................................................................................................8
Task 3: Event Table.....................................................................................................................8
Task 4: Domain Model Class Diagram.....................................................................................12
Task 5: Design Class Diagram..................................................................................................13
Task 6: Use Case Diagram........................................................................................................14
Task 7: Use Case Description (intermediate)............................................................................14
Bibliography..................................................................................................................................16

2
SYSTEM ANALYSIS
Part A
Task 1: Report
Methodology 1: Dynamic Software Development Method
Description: The methodology is basically a software methodology that is used for the
development which are based largely on the Rapid Application Development process. The
method is a four phase framework that is used for the development of the software for the
organizations that involves the feasibility study of the project and analysis of the case study for
the organization. In addition to this the prototype iteration process is involved during the
development that is succeeded by the design and build iterations. The implementation is the final
step of development in the methodology. The evolution of the project happens with the co-
located collaborations in between the project team the higher officials of the organization. The
development is followed by regular iterative feedback which are then again followed by iterative
developments.
Advantages: The main advantages of the methodology are:
 The involvement if the end users are very prominent in this type of software
development.
 The basic functions are developed very easily and the complex functions are added to the
skeletal of the system and hence, it becomes easier to include the advanced parts in the
system.
 This methodology helps in checking the cash flow of the company.
Disadvantages: The main disadvantages of the methodology are:

3
SYSTEM ANALYSIS
 The implementation of software using this methodology becomes very expensive for the
organization.
 It not suitable for small business organizations.
 As this is a new model it becomes very difficult for the organization to implement.
Methodology 2: Lean Thinking
Description: This methodology is developed on the base of the agile software development and
the methodology involves the procedures that can incorporate with the changes in idea in the
middle of development. the main idea behind this type of development is to develop an
application in 1/3rd of its time and help the organization in the development of the software with
a very low budget. This methodology involves the process of reducing the additional procedures
for the and only involving the procedures that are very essential for the development of the
application.
Advantages: The main advantages of the methodology are:
 All the unnecessary procedures involved with the development of the software are
eliminated.
 The methodology helps in building up the team work and co-operations for the project.
 The software can be developed in a very short time and budget for the development is
also very low.
 The methodology also involves reducing the errors in the project in the earlier stages.
Disadvantages: The main disadvantages of the methodology are:
 The success of the project depends on the team work of the project team and needs an
excellent collaboration in between the team members for the completion of the project.

4
SYSTEM ANALYSIS
 In case the decisions for the development of the software are not taken promptly the
project can be disrupted.
 The project also doesn’t provide flexibility to the developers. Any analysis that is done
incorrectly would be hampering the procedures in the project.
Methodology 3: Plan Driven Development
Description: The Plan driven development involves the planning extensively in the earlier stages
as the name suggests. The development is less costly than the planning stages and costlier during
the implementation steps. Hence, in this methodology the planning phase is extensive so that all
the required changes can be made during the planning phase of the project, as changes in the
implementation phase would mean that the project cost would be very high.
Advantages: The main advantages of the methodology are:
 The planning methodology provides the developers of the system with fool proof
planning and the development are generally faultless.
 The development of the software in the methodology helps in the organization to reduce
the extra cash flows for the system.
Disadvantages: The main disadvantages of the methodology are:
 The planning phase of the methodology has to be optimum and any fault in the planning
the software can create huge disruptions in the system development.
 Without stable requirements the development of the software would become very
difficult for the developers of the organization.
Methodology 4: Extreme Programming

5
SYSTEM ANALYSIS
Description: in extreme programming method the development of the system is very flexible and
this method allows the changes to be made in the software. The four main stages and processes
of the system are Coding, Testing, Listening and Designing. These procedures are incorporated
within a software and the procedures are very helpful in concentrating on the different aspects of
the software so that designing of the software is complete.
Advantages: The main advantages of the methodology are:
 The methodology helps the organization in lowering the cost of development of the
software for the organization.
 The involvement of the customers is made a priority in this methodology.
 Emphasis is put on the practical plans and the schedule.
Disadvantages: The main disadvantages of the methodology are:
 The cost of changing the requirements in for the development of the software can be very
high.
 The success of the project is mainly dependent on the people that are involved with the
project and their responsibilities.
 Development in the project regularly and updating the project can be very difficult for the
developer following this methodology.
 Assumption of realistic quotes can be very difficult when using this methodology.
Recommendation
For the development of software for any type of organization it has to be known that the software
that the organization is looking to develop. All the above mentioned methodologies have their
ups and downs and hence, a suitable methodology is to be selected for the development of the

6
SYSTEM ANALYSIS
software for the organization. The case study of the Australian Fashion Designs has been
provided and the organization is a retail business that provides the customers with the clothes.
The organization is looking to implement an accounting information system and hence the
Dynamic Software Development Method is being recommended for the development of the
system for the organization.

7
SYSTEM ANALYSIS
Task 2: Memo
Appendix
Memo
To: Business Executives
From: Please Fill
CC: Please Fill
Date: August 29, 2024
Re: Adopting a User Centered Design (UCD) approach and setting a plan for the
development of the Human Computer Interaction (HCI)
---------------------------------------------------------------------------------------------------------------------
It has been noticed that there is a need of development of the human computer interaction and
hence the it is advisable for the company to adopt a user centered approach for the development
of the human interaction system in the organization has been identified as the main solution for
the manual system present in the organization. The main problems are that the manual procedure
is very slow and involves various complex procedures.
The solution is the automated system that can be used by the organization for automating
their procedures and hence, the system would be very effective for the business of organization.
It is also recommended that the information system is implemented locally and this would help
the organization in improving the overall business procedures.

8
SYSTEM ANALYSIS
Part B: Modelling and Diagraming
Task 3: Event Table
Event Event
Type
Trigger Source Activity/
Use Case
System
Response/Outp
ut
Destination
Fill
application
form
Extern
al
Event
enter
details in
the
applicatio
n form
customers application Accept the
form
submission
system
Review of
the
application
Interna
l Event
The
admin
views the
form
Managemen
t
Applicatio
n review
Provide the
application for
analysis
Customers
Record the
customer
details
Interna
l Event
The
details of
the
customer
s are
entered in
to the
system.
Sales
representati
ve
Record
customer
details
Store the
details of the
customers
Customers

9
SYSTEM ANALYSIS
Record
ABN
Interna
l Event
The ABN
number
of the
customer
id entered
into the
system.
Sales
representati
ve
Record
ABN
details
Store the
details of the
customers
Customers
Place the
order online
Select the
items
customers Order
products
online
The items are
placed into the
account of the
customers
System
Review
order
Interna
l Event
View the
orders
placed by
the
customer
s.
Managemen
t
Review
order
The items are
produced to the
management
for review
System
Confirmati
on of
Order
Interna
l Event
The
confirm
order
option is
selected.
system Confirm
order
The system
stores the order
of the customer
customer
Check the Interna The customer Track The system System

10
SYSTEM ANALYSIS
progress of
the order
l Event progress
of the
orders is
tracked.
orders displays the
progress of the
order
Delivery Of
the Order
Interna
l Event
The
product is
delivered
Delivery
staff
Deliver
order
The order
delivery in
stored in the
system
Customers
Check
Monthly
sales report
Interna
l Event
The
monthly
sales
report is
generated
system Check
Monthly
sales report
The monthly
sales report is
displayed
Manageme
nt
Run sales
report
Interna
l Event
The sales
report is
analyzed
Managemen
t
Run sales
report
The sales
report analysis
is displayed
System
Maintain
record
Extern
al
Event
The
record of
the report
is
maintaine
d
Managemen
t
Maintain
record
The record is
stored in the
system
System
Identify Interna The Managemen Identify The customers System

11
SYSTEM ANALYSIS
potential
customers
l Event customer
s actions
are
viewed.
t potential
customers
of the system
are stored
Track the
customer’s
visits
Interna
l Event
The
orders of
the
customer
s online
are
tracked
Managemen
t
Track the
customer’s
visits
The details of
the orders of
the customers
are displayed
System
Task 4: Domain Model Class Diagram