ATMC - ICT700 System Analysis and Design Report: Agile Methodology

This report provides a comprehensive analysis of system analysis and design, focusing on the development of an information system for managing second-hand items within a company. It begins with a consultation section, exploring various agile methodologies such as Extreme Programming (XP), Kanban, Feature Driven Development (FDD), and Dynamic System Development Model (DSDM), evaluating their advantages and disadvantages, and recommending the Kanban methodology for the project. The report then delves into a detailed analysis of a case study, including an event table, use case diagram, use case descriptions, and class diagrams for both the general system and specifically for the broker and order components. Finally, a memo is included, addressing the need for Human Computer Interaction (HCI) and user-centered design in the development of the application. The report covers various aspects of system design, from identifying actors and use cases to designing class diagrams and discussing the importance of user interface design. The report also explores pre-conditions, post-conditions, and exception conditions for the use cases. Overall, the report provides a well-structured and in-depth examination of the system analysis and design process.

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

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Consultation.................................................................................................................................2
2. Analysis of Case..........................................................................................................................6
Event Table..................................................................................................................................6
Use Case Diagram.......................................................................................................................7
Use Case Description...................................................................................................................8
Class Diagram............................................................................................................................10
Class diagram for Broker and order...........................................................................................10
3. Memo.........................................................................................................................................11
References......................................................................................................................................13

2SYSTEM ANALYSIS AND DESIGN
1. Consultation
Agile methodology is considered to be a flexible methodology that includes a process of
developing the project and is divided in to different processes for creating a practical project. The
agile methodology requirements for all the projects are quickly decided and there is an
interaction between the specialists that are carried out in framework of organizing a project team
(Serrador and Pinto 2015). The agile project management helps to release a product more
quickly that is needed by a customer and the target audience. The agile iterative methods that can
be used by OZES management team are explained below.
Methodology: Extreme Programming
Discussions: This is the foremost agile methodologies that are used in agile
methodologies. The XP methodology involves very high degree participation between the parties
in software exchange that is the customers and the developers. This methodology includes
further development with emphasizing all the useful features of the given software products with
the testimonials (Rigby, Sutherland and Takeuchi 2016). All the developers included in XP
methodology includes successive software upgrades on the feedback that continues to include
new innovation in every week.
Advantages:
1. The XP methodology is a fast software development methodology that lasts only several
months. This includes an environment that is very fast (Lechler and Yang 2017).
2. This XP methodology also helps to reduce the cost carrying out the project. The feedback
loop in XP methodology is reduced thus decreasing the cost of carrying out the project.

3SYSTEM ANALYSIS AND DESIGN
3. The XP methodology includes team work where the team members work hard to achieve
the goals of the project.
Disadvantages:
1. The code in a project overcomes the design that uses the XP methodology (Hoda and
Murugesan 2016).
2. If customers are away from the development team, the project development is difficult to
be built up with the XP methodology.
3. This particular methodology includes a very high working pressure.
Methodology: Kanban Methodology
Discussions: The Kanban methodology is a method that is similar to lean agile
methodology (Vijayasarathy and Butler 2015). This methodology is a scheduling method that
designs a system to schedule, introduces the Kanban facilities as well as the inventory control
that are included in a project. The Kanban methodology is one of the best methodologies that
that works best as a team for accomplishing the production in time.
Advantages:
1. Kanban includes inbox iterations (Rasnacis and Berzisa 2017).
2. The scrum team mainly consists of many specific iteration work.
3. Scrum team is better known as cross functional work and prescribes estimation in the
scrum methodology.
4. This increases the flexibility process in the project.
Disadvantages:

4SYSTEM ANALYSIS AND DESIGN
1. The Kanban methodology mainly leads issue in development process (Hobbs and Petit,
2017).
2. The team handling the project with Kanban makes the process complicated.
3. There is a lack of timing as this methodology includes no timeframes.
Methodology: Feature Driven Development (FDD)
Discussions: The FDD approach of agile project management that includes turning the
models to build with a fortnight iterations (Vijayasarathy and Butler 2015). With comparison to
the Extreme programming as well as the scrum agile methodology, the FDD methodology shows
strict operations that includes walkthrough of the domains and also includes design, inspection as
well as code of carrying out the project (Serrador and Pinto 2015). The model with FDD can be
built up with many features. Development as well as design plan are implemented in the FDD
methodology. Unite test is performed in this FDD methodology.
Advantages:
1. The FDD methodology is very high adoptive development that involves stress for
designing as well as modelling the aspects of the project.
2. The team of FDD mainly focuses on the quality of project along with development phase
(Schmitz, Mahapatra and Nerur 2018).
Disadvantages:
1. This methodology does not have guidance regarding the gathering phase, the requirement
analysis, and regarding the risk management.

5SYSTEM ANALYSIS AND DESIGN
2. To carry out this methodology, the team handling the project should be highly skilled
(Rigby, Sutherland and Takeuchi 2016).
3. Project criticality is not provided by this project.
Methodology: Dynamic System development model (DSDM)
Discussions: The DSDM methodology is a framework that involves rapid development
of the application (Rasnacis and Berzisa 2017). This methodology provides proper assistance to
complete the project successfully in the project life cycle. This an also an iterative model that
uses incremental approach for delivering a project successfully (Permana 2015). This
methodology generally has three development phase for carrying out the project in the project
life cycle. The advantages and the disadvantages are explained in the section below.
Advantages:
1. The methodology of DSDM provides application development in a rapid way along with
integration of the agile principle (Hoda and Murugesan 2016).
2. This methodology is an adoptable framework that incorporates all best practices from
different approaches.
Disadvantages:
1. This methodology creates administration issue in the development process in the project
life cycle (Hobbs and Petit 2017).
2. The criticality of the project is not included in the project using DSDM methodology.
3. Specific guidance does not involve specific guidance that are related to the issue of team
size and the iteration length.

6SYSTEM ANALYSIS AND DESIGN
Recommendations: From the above discussion, it can be stated that the best
methodology for developing the information system of OZES is the Kanban methodology
(Crowder and Friess 2015). This is a methodology that helps to manage product creation that will
emphasis on continuous delivery without overburdening the team development. The Kanban
methodology includes process that helps to manage the application building.
2. Analysis of Case
Event Table
Event
Name
Type of
Event
Triggering
activity
Source
of
Actor
Use Case
Related
Output
description
Actor
destination
Ordering
Products
External
event
Customer
login
Custom
er
Order the
products
The customer
orders the
product from
the
application
when they
are agreed
with the
price.
Admin
Sign Up Internal Customer
login
Custom
er
Login There should
be proper
credentials
given by the
Customer

7SYSTEM ANALYSIS AND DESIGN
user while
processing
sign up
process.
Descriptio
n of the
item
Tempora
l event
Broker has to
login in the
system
Broker Item
Description
The
description of
the item is to
uploaded in
this use case.
Administrat
ion
Details of
selling
customer
State
event
The
associated
broker needs
to login in
the system
Broker View
selling
Details
The details of
the customer
selling the
products are
to be detailed
in this use
case
Administrat
ion
Getting
sell details
State
event
The
administratio
n should
upload the
details of
selling
products
Broker Views
selling
details
The details of
the sell is to
be uploaded
in this use
case so that
the broker
can get the
Broker

8SYSTEM ANALYSIS AND DESIGN
details.
Selling
Offers
Tempora
l event
The
administratio
n needs to
provide the
selling
offers.
Admini
stration
Selling
Details
Administratio
n gets selling
offers and the
selling offers
are to be
given by the
admin.
Customer
Login of
customers
External
event
Customer
needs to first
sign up with
the system
before
logging in.
Custom
er
Login The database
management
system has
stores the
details of the
login details
in the system.
Database
managemen
t
Broker
login
External
event
The broker
should have
a username
and
password.
Broker Login The broker
has to login
the system
for getting
service
Managemen
t system
Viewing
Offers
State
event
The
customer
needs to
Custom
er
View offers The customer
views the
offers that are
Administrat
or

9SYSTEM ANALYSIS AND DESIGN
login for
viewing the
offers.
given by the
administrator.
Uploading
Product
Details
State
event
The
management
has to upload
the details of
the product
Admini
strator
Upload
product
Details
The details of
the product is
upload by the
admin so that
the customer
can view
them.
Customer.

10SYSTEM ANALYSIS AND DESIGN
Use Case Diagram
Figure 1: Use Case Diagram
(Source: Created by Author)

11SYSTEM ANALYSIS AND DESIGN
Use Case Description
Use Case Name Sell product
Scenario This use case details the selling of the second hand items in the system.
The organization sells second hand items and the customer buys the
products from the application. This use includes all the possible activities
that are needed to fulfil the work.
Triggering
Event
The second hand selling of the product is initiated when the staff
management collects the item from the customer and the admin updates
the details of the item on the system.
Brief
Description
The use case provides the details of the products along with the price of
the product and detailed description of the product. The customer gets the
product details from this particular use case and buys the product.
Actors The actors who are associated with this particular use case are customer
and the administrator who manages the system.
Related Use
Case
Upload details of product, buy products, description of item.
Stakeholders The stakeholders who are associated with this use case are customers, the
brokers, the administrator, and the owner of the company.
Pre-conditions Before carrying out this use case, the system should have the details of all
the items that are to be sold in the system.
Post-Conditions The details of selling the product is to be updated on the application so
that the broker can view them and negotiate price with the selling
customer.