Systems Analysis

This document provides an overview of Systems Analysis, focusing on Agile Methodology and Iterative System Development Methodology. It discusses the advantages and disadvantages of each methodology and when to use them. The document also includes event tables, use case diagrams, and design class diagrams. Additionally, it explores the User Centered Design (UCD) approach and Human Computer Interaction (HCI) principles in software development.

Systems Analysis
1 | P a g e

Table of Contents
Introduction:....................................................................................................................................3
Agile Methodology..........................................................................................................................3
Advantages:.................................................................................................................................4
Disadvantages:.............................................................................................................................4
When should Australian Fashion Designs (AFD) use the Agile methodology?.........................5
Iterative system development methodology....................................................................................5
Advantages:.................................................................................................................................5
Disadvantages:.............................................................................................................................5
When to use the iterative methodology?.....................................................................................6
Event table.......................................................................................................................................6
Use case diagram.............................................................................................................................8
Use case description – Takes Order.................................................................................................9
Domain model class diagram.........................................................................................................10
Design class diagram.....................................................................................................................11
Memo.............................................................................................................................................11
Reference:......................................................................................................................................14
2 | P a g e

Introduction:
In every organization, it is essential to have proper usage of technology so that the workings can
easily get analyzed and monitor. For effective working, it is crucial for the management to have
records regarding daily activities. Earlier in the past days, the manual systems of the stock
management and the customer relationship management help the organization in keeping
records, but now it is vital to have a proper information system that not only provides the
required information but also help in improving the process of working simultaneously.
There are several methodologies that the organizations can use to keep track of the activities
going on in the organization. The most common methodologies that the organization can use
include the iterative system development methodologies and agile methodologies. The iterative
system development methodology is a part of the software development life cycle. In this
methodology, a big software application tasks get breakdown into a manageable sub-task. The
main motive of this methodology is to simplify the implementation of the process and gaining a
broader feature.
On the other hand, there is an agile methodology. Agile methodology is a project management
process that helps in promoting the continuous iteration of development throughout the project
lifecycle. As compared to the traditional methods, the Agile methodology helps the organization
in working with more changes and flexibility. Before choosing any methodology, it is essential
to understand and analyze that which methodology will be best suited for the project scenario.
Agile Methodology
Agile methodology is a type of project management process. As compared to the traditional
methods, the Agile methodologies can help the Australian Fashion Designs(AFD) in adopting
more changes and flexibilities in the plans. With the help of such methodologies, clients can
easily alter small objectives without facing any High Budget issue or schedule. In this process,
Australian Fashion Designs (AFD) can easily break down the huge task into small tasks
according to the requirements (Papadopoulos, 2015). The main objective of agile methodology is
providing high priority to the customers. From the starting stage of the project development
cycle, customers get proper attention and priority.
3 | P a g e

According to the Agile methodologies, Australian Fashion Designs (AFD) should keep the
clients involved in every task. Agile methodologies also play an essential role in saving the time
and money of the client as well as the organization because, at each phase, the clients are
involved and the contest and approve the product simultaneously. In case any sort of risk or
challenges occurs than that can also be removed while the production cycle is going on. There
are several traditional methods that do not allow the Australian Fashion Designs (AFD) project
teams to test the projects while the task is going on, and that is why the defects chances are
enormous. This results in high prices and colossal customer dissatisfaction (Lei et al. 2017).
Advantages:
There are several advantages of agile methodologies that Australian Fashion Designs(AFD) can
avail:
 Customer satisfaction
 Continuous deliveries
 More emphasis laid on people as compared to process and tools
 Rapid delivery of working software
 The best form of communication that is face to face conversation
 Great corporation of developers
 Technical excellence
 Great design
 Changes get adapted regularly and can easily get modified
 Late changes can also be solved according to the requirements
Disadvantages:
Along with the advantages, there are several disadvantages of agile methodologies. It is crucial
for Australian Fashion Designs (AFD) to determine the disadvantages also:
 In crucial software deliverables, sometimes it becomes challenging to identify the efforts
in the beginning
 The lack of prominence towards the documentation and designing process
 In case the customer is not clear about the process then the whole project plan got
disturbed
4 | P a g e

 Only senior programmers can take ongoing decisions.
 No or less scope for the new programmers
When should Australian Fashion Designs (AFD) use the Agile methodology?
 The Agile methodologies should be used when any new change or alteration is required
to be implemented in the project
 For implementing some new features within less time
 When there is less or Limited planning for starting the project
Iterative system development methodology
The iterative methodology is a part of the software development life cycle. This methodology is
focused on simplifying the initial implementation so that the task can get completed accordingly
in a proper manner (Korpela et al. 2017). In the iterative methodology, there are five phases that
are followed. The phase involved is planning phase, analysis phase, designing face,
implementation phase, testing phase and the evaluation phase.
Advantages:
There are several advantages of iterative software methodology. The advantages of this
methodology to the Australian Fashion Designs(AFD) are:
 During the initial phase of the project cycle, the methodology can easily get implemented
 Helps the team members in identifying all the risks and defects as early as possible
 This methodology is easily adaptable with every type of modification of change required
in the project
 It is one of the best options available for Agile organisations (Balle et al. 2018)
 By using this methodology, The parallel development can efficiently get planned
 The process of documentation and designing does not take much time. It is easy to
manage and handle
Disadvantages:
Along with advantages, there are some disadvantages to the iterative software methodology. It is
essential to determine the disadvantages also. Hence the disadvantages are:
 To implement the iterative model; it is crucial for the organisation to have more resources
5 | P a g e

 This model is not suitable for organisations having small projects
 Risk analysis phase plays a vital role because the progress of the object depends upon it.
 Sometimes the increments reduce the whole objective and definition of the system
(Ahimbisibwe et al. 2015)
 The iterative methodology is not suitable for regular changes
 To handle this methodology; it is vital to provide more management attention.
Iterative methodology
 When the requirements of the project are defined clearly, this methodology can be used
 Whenever a new technology is being used in the project
 When there are high risks involved that may be required to change
 When there is no proper skillset available to handle the task (Chandra, 2015)
Event table
6 | P a g e

Event Event
Type
Trigger Source Activity/Use
Case
System
Response/
Output
Destination
AFD
management
wants to add
a new store
Internal New
private/individual
customer to be
added
Store Add new
store
Store data
will be
added
AFD
AFD wants to
add new
customer
Internal New customer to
be added
Customer Add new
customer
Customer
data will be
saved
AFD,
customer
AFD allocates
a sales area
to a
salesperson
Internal Allocation of sales
area
AFD Allocate
salesperson
A sales area
is to be
allocated
AFD,
salesperson
AFD and
customer
wants to
generate
reports
External Review by
management
Sales
people,
stores
Execute
report
generation
query
Sales report AFD
management
Store wishes
to register an
order of the
customer
Internal Customer’s new
order
Customer Takes order New order
has been
taken
successfully
AFD,
customer
7 | P a g e

Use case diagram
8 | P a g e

Use case description – Takes Order
9 | P a g e

10 | P a g e
Use Case Takes order
Scenario Create new order / sale record
Triggering Event Customer wants to place an order at a store.
Description Allows store staff to create a new order in the propose system
Actors Customer, Store staff
Related Use Case NA
Stakeholders 1. Customer
2. Store staff
Pre-Condition Store staff has login access in the system and is currently
logged int.
Post-Condition Store staff successfully added a new order of the customer in
the AFD system.
Flow of activities
Actor System
1) Store staff clicks on “New
order” link.
3) Staff enters the detail and
click submit button.
2) System displays a screen with the fields: customer ID,
product, date of sale and delivery date.
4) System displays an order ID of the newly added order.
5) System sends the data to salesperson of the area.
Alternate Course of Action 3.1 If store staff enters incorrect or mismatch data, system
displays an error message on the screen.

Domain model class diagram
11 | P a g e

Design class diagram
Memo
To: The Management Team, AFD
From: Project Leader
Subject: User Centered Design (UCD) Approach and Human Computer Interaction (HCI)
Principles
It is necessary for Australian Fashion Designs to implement Customer Relationship Management
(CRM) system to automate the associated business operations. There will be numerous
functional and non-functional requirements that will be incorporated in the system.
12 | P a g e

The system design and user interface are one area that will be of prime interest for the users. We
have decided to make use of User Centered Design (UCD) approach and adhere with the Human
Computer Interaction (HCI) design principles. UCD is a design approach in which the system
design is carried out on the basis of the needs and expectations of the end-users. In this case, the
primary end-users of the CRM system will be the employees of AFD and the management (Case,
2013). The design of the system as per the expectations of the end-users will make sure that the
overall usability is enhanced and the users get to know about the system functionalities to carry
out the business functions and operations.
HCI design principles support the idea of UCD and these have been developed so that the user
interaction is maximized. We will adhere with these design principles to ensure that the user
engagement and satisfaction levels are high at all times. For instance, consistency is one of these
principles that we will comply with. The screen layouts, color scheme, font size, font face, and
other UI elements will remain consistent across all the system screens. This will make it easier
for the users to connect with the system and understand the workflows included in the system.
Similarly, customization & personalization will be the two major principles that will be adhered
to. The users will be able to customize the look & feel of the system as per their liking (Javaid,
2013). For instance, they will be able to choose the preferred color scheme, background color,
font style, etc. They will also be able to change the default language of the system as per their
choice. Navigation is one of the HCI principles that will be incorporated and the system
navigation on one screen and in between the screens will be kept smooth. The over-scrolling on
any of the CRM system screens will also be avoided. Error resolution will be included in the
system to allow the users to roll back their actions without causing any permanent damage. This
is because we understand that CRM system is first of its kinds that are being implemented in the
organization.
The adherence towards the UCD approach and HCI principles will enhance the user connectivity
with the system and will lead to the increase in the user engagement levels. The system features
will also be designed as per the user specifications and expectations.
Please review the UCD approach discussed and the HCI principles included and let us know
your take on the same.
13 | P a g e

Best Regards,
Project Leader
Australian Fashion Designs (AFD)
14 | P a g e

Reference:
Ahimbisibwe, A., Cavana, R.Y. and Daellenbach, U., 2015. A contingency fit model of critical
success factors for software development projects: A comparison of agile and traditional plan-
based methodologies. Journal of Enterprise Information Management, 28(1), pp.7-33.
Balle, A.R., Oliveira, M., Curado, C. and Nodari, F., 2018. How do knowledge cycles happen in
software development methodologies?. Industrial and Commercial Training, 50(7/8), pp.380-
392.
Case, K. (2013). Tools for User-Centred Design. Advanced Engineering Forum, 10, pp.28-33.
Chandra, V., 2015. Comparison between various software development
methodologies. International Journal of Computer Applications, 131(9), pp.7-10.
Javaid, M. (2013). Review and Analysis of Human Computer Interaction (HCI) Principles. SSRN
Electronic Journal.
Korpela, M., Soriyan, H.A., Olufokunbi, K.C. and Mursu, A., 2017. Made-in-Nigeria systems
development methodologies: An action research project in the health sector. In Information
Technology in Context: Studies from the perspective of developing countries (pp. 134-152).
Routledge.
Lei, H., Ganjeizadeh, F., Jayachandran, P.K. and Ozcan, P., 2017. A statistical analysis of the
effects of Scrum and Kanban on software development projects. Robotics and Computer-
Integrated Manufacturing, 43, pp.59-67.
Papadopoulos, G., 2015. Moving from traditional to agile software development methodologies
also on large, distributed projects. Procedia-Social and Behavioral Sciences, 175, pp.455-463.
15 | P a g e