System Analysis and Design Report - ICT700 Agile & Iterative Methods

This report provides a detailed analysis of system analysis and design, focusing on agile and iterative methodologies. It includes discussions on Extreme Programming (XP), Scrum, Feature Driven Development (FDD), and Crystal methodology, highlighting their advantages and disadvantages. The report also features an event table, a use case diagram and description, a domain model class diagram, and a design class diagram to illustrate the concepts. Furthermore, a memo is included, addressing the adoption of the User-Centered Design (UCD) approach for creating an effective Human-Computer Interaction (HCI) environment. This document aims to provide OZES management team insights into improving their software development processes and overall system design. Desklib provides access to similar past papers and solved assignments for students.

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 main goal of this paper is to prepare a report for the OZES management team. There will
be a memo, and methodology on agile and iterative development in this paper.

2
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Methodology..............................................................................................................................3
Extreme programming (XP):..................................................................................................3
Scrum.....................................................................................................................................4
Feature driven development (FDD).......................................................................................5
Crystal methodology:.............................................................................................................5
Event Table................................................................................................................................6
Use Case Diagram......................................................................................................................8
Use Case Description.................................................................................................................9
Domain Model Class Diagram.................................................................................................11
Design Class Diagram..............................................................................................................12
MEMO:....................................................................................................................................13
Bibliography.............................................................................................................................15

3
SYSTEM ANALYSIS AND DESIGN
Methodology:
The vital idea behind developing the agile methodology is to counter several convoluted
methods for pervading the software development (Moniruzzaman and Hossain 2013)Its
methods generally keep an eye to the followings;
Customer satisfaction
Developing the projects with several inspired contributions
Developing maintaining several software for carrying out complex projects.
The four important Agile methodologies are as follows.
Extreme programming (XP):
It can be described as one of the important as well as foremost Agile technology, that
explains an effective high degree participation among two different parties; that is developers
and the customers, involved in the software exchange (Dalalah 2014). The developer involves
in creating as well as upgrading the software along with performs several research on the new
innovations in order to provide best service to the associated customers. On the other hand,
the customers involve inspiring the process of devolvement by emphasizing as well as using
the best features provided in the software product. Moreover, the feedbacks shared by the
customer helps the developers to understand the customers need and inspires them for better
development. The discussed methodology carries five important values that is,
communication, simplicity, respect, courage and feedback. These values will definitely help
the OZES to counter the issues occurring in their current business. However, the concept has
some advantages and disadvantages as follows;
Advantages

4
SYSTEM ANALYSIS AND DESIGN
 Without wasting the process time, it provides comparatively faster working
environment along with continuous deployment and integration.
 It is advantageous in carrying out open and visible communication process,
eliminating the bugs and failures.
 In XP, the process of feedback loop is less, reducing the costs.
Disadvantages
 It sometimes become difficult to handle the constant changes, resulting in lack of
documentation along with difficulties in tracking the failure`
 When the customer is away from the development team or vice versa, the XP
programs are difficult to locate.
Scrum
This particular methodology of agile comprises with the most complicated development
principles. Unlike the extreme programing; here, the owner of a particular product has to
collaborate with the development or information technology team in order to collectively
harness as well as isolate the system functions; which is known as product backlog
(Rodriguez, Soria and Campo 2015). Moreover, the development team also involved in
distributing the software program in increments, known as the sprint. The time duration of
each sprint is decided by the developing team itself. The advantages and disadvantages
related to it are as follows,
Advantages:
 Effective use of cost as well as the time is ensured here.
 Complicated projects are divided into several manageable sprints in order to perform
simplified operations (Stellman and Greene 2014).
 Effectively address the adopted feedbacks of the customers
Disadvantages:
 Lack of a perfect end date sometimes create scope creep.
 Daily meetings can become hectic for the team members.

5
SYSTEM ANALYSIS AND DESIGN
Feature driven development (FDD)
The discussed method FDD methodology turns the models into several builds at the
fortnightly iteration. Unlike the above discussed methodology the strict operations in the
FDD, effectively involve in the walkthrough of designs as well as domains, inspections and
codes. After that, the model is build including a series of features (Firdaus, Ghani and Jeong
2014). Moreover, individual design as well as d3evelopment plan is prepared for every single
feature. The pros and cons of FDD are as follows,
Advantages:
 It successively carried out the process of parallel working of multiple teams.
 A well-defined reporting capabilities along with progress tracking is ensure here.
 The projects development consumes comparatively less time.
Disadvantages:
 In case of smaller project and individual developers, it cannot turn as one ideal
methodology.
 Unlike other Agile methodology, the project interrelation is less visible here.
Crystal methodology:
The concept of crystal methodology is a part of different crystal agile methodology such as,
crystal yellow, crystal clear and crystal red. It mainly relies on three vital factors that is the
system criticality, priority of the project and the team size for carrying out successive
projects. Keeping an eye to the system criticality, the project are categorized (Hamed and
Abushama 2013). The system criticality can be broadly divided into four types, such as, life,
essential money, discretional money and comfort. In addition to that, it emphasizes on
interaction, community, people, skills, communication and talent. The vital concern of this
methodology is to promote high customer satisfaction and adopt every customer feedback for

6
SYSTEM ANALYSIS AND DESIGN
developing more successful software. The advantages and disadvantages of crystal
methodology are as follows;
Advantages:
 Easy management of projects using minimal rules.
 The risk factor related to the deliverables are comparatively less here.
Disadvantages:
 In case of less customer understanding regarding the process and product, it is
difficult to handle the problem
 In case of complicated projects it is difficult to estimate the resource requirement.
Event Table
The event table is a table that is fulfilled with data, written typically to the log file for
every scenario as well as it also appears in the window of analysis. The table of the event is
containing the information about the timing that is also about the events that are specific
which are occurring with the scenario. Only the events that are stimulus with the codes of the
events may appear in the events table. The times that is provided for the resolution is 0.1
milliseconds. The event table is having several columns that are trail, event type, code,
custom properties, time, req time etc. For populating the table of the event, the triggers must
have to be created. The trigger is the construct of the database which is able to run the script
of the SQL at the time of occurring of the actions that were defined previously. The example
of the event table is as per following.
Event Trigger Source Use Case Response Destinatio
n
Placement of
Advertisement
Upload
Advertisement
Brokers Advertisement Contact Customers
Answer the Submit the Customer Provide Request System

7
SYSTEM ANALYSIS AND DESIGN
given
questions
answers Details reference
information
Contacting
with the
Organisation
Placing call Customer Make Call Display
Questionnaire
System
Giving
reference
Reference ID Customer Provide
Reference
Store the
Details
System
Selling of the
items
Post
Advertisement
Brokers Sell-second
hand Items
Display to
customer
Customer
Buy Item Place a
purchase
request
Customer Purchase Process
Purchase
System
Items is
received
Deposition by
OZES
Staffs Item
Deposition
Pack Items System
Sending the
Items
Packing and
sending
Staffs Send Items Send to the
customer
Customer
Forwarding
the emails
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

8
SYSTEM ANALYSIS AND DESIGN
Use Case Diagram
The use case diagram is a depiction that can be presented graphically that is about the
interactions which is within the system elements. The use case is the kind of methodology
that is utilized for the analysis of a system for identifying, clarifying as well as organizing the
requirements of the systems. The term “system” is referring to the things that need to
operated and developed like the mail order product services and sales of the web sites. The
use case diagrams has been employed in the unified modelling language (UML). The
objectives of the systems are able to include the plan of the requirements, testing, validating
as well as debugging of a product of the software that is under the development. The use case
diagram is given below.

9
SYSTEM ANALYSIS AND DESIGN
Use Case Description
For writing the contents of the use cases, it should begin through picking a scenario,
and assuming that scenario as the main scenario. The starting of the body of that use cases
will be begin with the writing the major scenario of the success as the sequential number of

10
SYSTEM ANALYSIS AND DESIGN
the steps. However the other scenarios can also be taken and can also be written as the
extension. The extensions are able to achieve success, as all of the use cases are having one
major actor that is able to call the systems for delivering services. All of the steps that are
existing in the use case for the interaction that is between the system and the user. A step that
is complicated in the use case may be another use case only.
Name Sell-second hand item
ID 1
Description The broker may sell the products which are the second hand for the
consumers. The consumers could look at the advertise and the see all
of the items of the system.
Actors The actors who can take part in the system are considered as the
consumers.
Triggers The procedure which is triggered after the ad, is posted from the
broker.
Pre-condition Advertisement
Post-condition Make Purchase
Flow of process Actor System
1. Sending advertisement
2. Sell Second-hand item
3. Making Purchase
1. Posting Advertisement
2. Displaying item to the
customer
3. Selling Item
Exceptions Exceptions may take place whether the advertisement will not able to
be reached out to the client.

11
SYSTEM ANALYSIS AND DESIGN
Domain Model Class Diagram
The domain model has been illustrating the concepts that are noteworthy within the
domain. The domain model has been created during the analysis that is object oriented. For
decomposing the domain within the concepts that are connected with the real world. The
model can be identified by the set of the classes that are conceptual. This is based on the
design of the software. The classes that are conceptual are the things, ideas or the objects
within the domain. The class diagrams have so much use in many of the stages of the design
of the systems. In the stages of the analysis the model class diagram is able to help the user
for understanding all of the needs as well as the requirements of the domain of the problems
as well as for identifying the components of this.
Design Class Diagram
The UML diagram is able to be used in the prospective that are multiple in number.
At one perspective that is conceptual is able to be utilized for visualizing the model of the

12
SYSTEM ANALYSIS AND DESIGN
domain. A modelling term that can be considered as the common modelling term for the aim
of this is the design class diagram. The other parts of the design model class diagram is
including package diagrams as well as the UML interaction.
On the above diagram it can be seen that the purchase id, date, order detail and the phone
number has been taken as the integer and the other parts have been take as string.
MEMO:
To: [Business People in the executive class]

13
SYSTEM ANALYSIS AND DESIGN
From: [OZES Managing Department]
Date: [Please fill]
Subject: [Adopting the UCD approach for effective HCI environment]
[Opening- One of the suitable method for developing the human computer interaction (HCI)
can be named as user centred design (UCD) User centred design is the effective as well as
iterative design method, where the user needs is emphasized in every single stage of the
development. Every iteration of a UCD passes through four stages, which is understanding
the context, specifying the user requirements, designing the solution and evaluating the
requirements.]
[Summery- OZES is one of the young Australian brand actively participate in distributing
numerous electrical products within the geographical region of Australia. However, the
organization is successfully stay ahead of the competition as it serves the customer according
to their needs. The organization always aims to understand customer needs, and design the
products accordingly. Furthermore, for improving the design in order to provide more
customer satisfaction, 6the designing and development team always look forward to the
customer reviews and feedbacks. UCD via the human computer interaction is one of the best
way to understand the customer criteria. As discussed, the UCD involves the best iterative
approach in every phase. In the initial phase, the designer intended to understand the context
of the project. After that, identification as well as specification of the user requirements are
carried out followed by the evaluation of the entire project. Moreover, with the help of close
user participation or involvement the products are more expected to meet the user
requirement, resulting in increasing the sales as well as the revenue. The System designers
tailors the products in accordance to specific contexts with specific tasks, nullifying the

14
SYSTEM ANALYSIS AND DESIGN
chances of human error. Furthermore, the UCD provides the designers the flexibility of
creating their projects based upon the explicit customer understanding, therefore, the whole
team of designer must include experts in several fields such as, hardware as well as software
engineer, ethnographers and many more. Apart from that, stakeholders, domain experts must
be included in the development team for the better evaluation as well as understanding of the
project. Moreover, in order to expand the entire user experience, users also need to be
involved for other user evaluation. UCD is very much advantageous in keeping close contact
with the end users helping the organization to move in the right direction for creating
successful, profitable as well as sustainable business. ]
[Conclusion- Therefore, it can be recommended to the executive business customers to
involve in the UCD based development or design as well as implementations in the
organization. Apart from that, the customer feedbacks need to be considered carefully for
improving the project designing. ]

15
SYSTEM ANALYSIS AND DESIGN
Bibliography
Dalalah, A., 2014. Extreme Programming: Strengths and Weaknesses. Computer Technology
and Application, 5(1).
Firdaus, A., Ghani, I. and Jeong, S.R., 2014. Secure feature driven development (SFDD)
model for secure software development. Procedia-Social and Behavioral Sciences, 129,
pp.546-553.
Hamed, A.M.M. and Abushama, H., 2013, August. Popular agile approaches in software
development: Review and analysis. In 2013 International Conference on Computing,
Electrical and Electronic Engineering (Icceee) (pp. 160-166). IEEE.
Moniruzzaman, A.B.M. and Hossain, D.S.A., 2013. Comparative study on agile software
development methodologies. arXiv preprint arXiv:1307.3356.
Nikiforova, O., Ahilcenoka, D., Ungurs, D., Gusarovs, K. and Kozacenko, L., 2014. Several
issues on the layout of the UML sequence and class diagram. In Proc. of the 9th Int. Conf. on
Software Engineering Advances (pp. 12-16).
Py, D., Auxepaules, L. and Alonso, M., 2013. Diagram, a learning environment for initiation
to object-oriented modeling with uml class diagrams. Journal of Interactive Learning
Research, 24(4), pp.425-446.
Rodriguez, G., Soria, Á. and Campo, M., 2015. Virtual Scrum: A teaching aid to introduce
undergraduate software engineering students to scrum. Computer Applications in
Engineering Education, 23(1), pp.147-156.
Smid, W. and Rensink, A., 2013. Class diagram restructuring with GROOVE. arXiv preprint
arXiv:1312.0350.

16
SYSTEM ANALYSIS AND DESIGN
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.