Implementing Human-Computer Interaction and Agile Strategies at FFSL

The memo addresses the need for integrating effective methodologies like Human-Computer Interaction (HCI) and Agile practices within FFSL. It highlights the importance of developing user-friendly systems by analyzing how employees interact with computers to ensure successful integration. The strategy involves adopting a specific agile methodology, providing training on newly adopted software applications, and ensuring these tools are accessible and easy for sales associates across various stores. By evaluating and refining these processes online, FFSL aims to enhance customer relationship management through improved application usability. Additionally, the memo recommends employing the Technology Acceptance Model (TAM) to further understand employee motivations towards system adoption, aiming to increase organizational output.

Running head: THE SYSTEM ANALYSIS AND DESIGN
The System Analysis and Design
Name of the Student
Name of the University

1THE SYSTEM ANALYSIS AND DESIGN
Table of Contents
Part A:..............................................................................................................................................2
Scrum:..........................................................................................................................................2
XP:...............................................................................................................................................3
UP:...............................................................................................................................................5
Part B:..............................................................................................................................................7
Event table:..................................................................................................................................7
Use Case:.....................................................................................................................................9
Use Case Description:..................................................................................................................9
Class Diagram:...........................................................................................................................11
Domain Model Class Diagram:.................................................................................................12
Bibliography:.................................................................................................................................13
Appendix:......................................................................................................................................15
Memo:........................................................................................................................................15

2THE SYSTEM ANALYSIS AND DESIGN
Part A:
Scrum:
Description: Scrum depends in possessing a cross-functional team. A team members of
scrum is self-organizing about the foundation, which there's not an additional complete team
leader who are able to determine the complete shebang of team members related to be able to the
project or requires initiation inside trouble dealing with among staff and project in-scope issues.
All these motives could be because circumstances, which have been complete inside team
members, jointly, to be able to commonly be complete. Through the agile Scrum approach, as an
alternative to furnishing total, precise information of methods all of things are all usually as done
on the quest, your the majority of it might be eventually left about the Scrum application
enactment team. The main reason staying the team will find out greatest methods to fix the
specific they are generally presented.
Advantages: The advantages are as following.
1) Scrum makes positive right entry to funds in addition to time frame is carried
out
2) The coding and testing is accomplished over the race evaluation step
3) The project can become split into little components then it may be possible
quickly
4) Them allows the project manager for getting feedback on the customers in
addition to client
5) If perhaps the project is action-packed then Scrum is excellent for the project

3THE SYSTEM ANALYSIS AND DESIGN
6) A daily scrum meetings are an easy way regarding must personal work of the
associates
7) A short sprints are valuable about joining fresh modifications in the project
Disadvantages: The disadvantages are as following
1) That Scrum system can be at risk of breadth crawling trouble, this kind of is
really because involving indefinite process description and also anonymous
deliver the results movement
2) If job party can be considerable with quantity, and then Scrum is often a
responsibility for the purpose of job office manager
3) That job level of quality should not be retained within the job, sole exit can
be violent testing process
4) That associates could certainly be frustrated with regular party group
meetings
5) The degree of pessimistic have an impact on crumbles with typically the job
with relinquish from the party associate can be massive
6) If associates typically are not professional then this assembly can be
unsuitable
XP:
Description: Extreme Programming or XP can be known as the software engineering
technique this is the majority of obvious a number of agile software improvement practices. Just
like the additional agile treatments, Excessive Development contrasts coming from traditional
methodologies principally in interesting larger diagnosis with freedom than on liability. Clients
involving XP dilemma continuous modifications in order to specifications simply just united

4THE SYSTEM ANALYSIS AND DESIGN
regularly usual and predictable element of software implementation projects. In most cases to be
thought this variation in order to specifications modifications from any cycle in the challenge our
life is the persuading and superior procedure as compared to not enough to outline many
specifications within the beginning involving a project and taking in toughness to operate
alterations to the requirements. Software implementation activities in just 1990s had been shaped
through a couple of chief has an effect on such as inside the camera, object-oriented
programming replaced procedural programming because programming structure utilized
Advantages: The advantages are as following.
1) The software development club might have necessary time and money making
sure that assignment are generally realized place, enough time and charge
protecting showcase on the mythology permits it all
2) The most important target on the scheme remains to be for the supply in
finished merchandise promptly of which this conserve considerable time for
the purpose of club
3) Using less documented files is without a doubt the true reason for charge
reducing
4) The posts said to be the customers is without a doubt the way of eliminating
the issues
5) The scheme is quite simple
Disadvantages: The disadvantages are as following.
1) Placing more give attention to codes rather than model of the system can
possibly be harmful element

5THE SYSTEM ANALYSIS AND DESIGN
2) The actual substandard involving design typically is a downside
3) The software can constitute sub standard
UP:
Description: The Unified Process (UP), or just Unified Software Development Therapy,
is mainly a iterative as well as incremental software development program where a personalized
activity is typically defined. That program consist of many things and functions really been
changed numerous minutes for building a good portion of variations. The most effective well-
liked distinctions add some Realistic Unified Course of action (RUP) along with Clear Unified
Course of action (OpenUP) (Fuggetta and Di Nitto 2014). That program has a good portion of
important functions what seemingly cause fundamentally all variations. Automobile an iterative
as well as slow development system. It may be architecture-centric with huge purpose being
carried out to confirm you identify as well as validate a system design and beauty for lots of
cryptography is surely done. It may be risk-focused as well as brings interest that highest-risk
causes land up being answered found in the initial deliverables possible.It could be use-case as
well as UML design enticed usually problems keeping identified present in a form of forms.
Following are the phases of the method.
Inception: The principal target about the Inception phase might be to cultivate the reality
for the viability from the planned system. That four styles are often discussed this big an
essential section of it collection, That All five Workflows. The important landmark regarding the
Inception phase is named Life-Cycle Objectives.
Elaboration: The principal target about the Elaboration phase might be to cultivate the
capability to construct the new method provided these income constraints, routine constraints, or

6THE SYSTEM ANALYSIS AND DESIGN
other kinds constraints that the increase undertaking faces. That initiates if this portion are often
catching a normal functioning taste the rest of the practical situations, growing these pick
construction right into an entire process fundamental, which really is a inner alleviate the system
advised toward meals these construction, spanning important hazards all through an on-going
time period and also finalizing the corporation case for the undertaking and also making some
type of undertaking program which includes enough details to steer another thing from the
project.
Construction: The main target about the Construction phase is regarded as being to create
a mind system skillful at working productively found in doll with customer's surroundings.
During Construction, these undertaking team operates projects that require generating the system
iteratively and also incrementally, ensuring that these viability from the process is consistently
established found in practicable form.
Transition: The main target about the Transition phase might be to list out completely
practical method to successfully customers. During Transition, these undertaking team is
targeted on correcting issues and also modifying the system to mend earlier in the day
unidentified problems. The important landmark regarding the Transition phase is named Unit
Release.

7THE SYSTEM ANALYSIS AND DESIGN
Part B:
Event table:
Event
Event
Type
Trigger Source
Activity/
Use Case
System
Response/
Output
Destinatio
n
Purchase
from
supplier
External
Product
stock of
FFSL is to
be in
creased
Management
and
Warehouse
Purchase
Update
Stock,
Product
Availability
FFSL
Filling
applicatio
n
External
The
management
will review
and register
retail store
FFSL
Potential
Customer
Creates
Customer
Update
Customer
base, read
application
data,
verification
Retail store
Tracking
Sales
Person
Area
Internal The areas of
sales
personnel
will be
divided and
activity of
individuals
Sales
Personnel of
FFSL
Input Sales
Details,
Sales Area
Coverage
Read sales
personnel
related
data,
Update
area
Sales
Person

8THE SYSTEM ANALYSIS AND DESIGN
monitored
Sales
Tracking
Internal
Creating
report on
sales
Steven
Smith
Sales
Report
Create
report
based on
sales data
Sales
Person
Visit Data
View
Internal
Generating
information
based on
sales person
visit to
customer
Steven
Smith
Visit
Customer,
Failed
Visit, Make
Order
Create a list
of visited
customer
along with
date and
sales
person who
visited him
and amount
of order
made
Sales
Person

9THE SYSTEM ANALYSIS AND DESIGN
Use Case:
Use Case Description:
Name Creates Customer
ID UC-1
Brief
Description
Registration of retails store into the system
Trigger New update entry is available to customer

10THE SYSTEM ANALYSIS AND DESIGN
Pre-
Condition
The application form must be valid
Post
Condition
Retail store must be eligible
Activity Retail Store System
application form fill up Collect application form data
Evaluate data
Send extra details required Evaluate the information
Receives and validate application
form
Customer registration process initiate
Exception The stores are not within geographical boundary

11THE SYSTEM ANALYSIS AND DESIGN
Class Diagram:

12THE SYSTEM ANALYSIS AND DESIGN
Domain Model Class Diagram:

13THE SYSTEM ANALYSIS AND DESIGN
Bibliography:
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Estler, H.C., Nordio, M., Furia, C.A., Meyer, B. and Schneider, J., 2014. Agile vs. structured
distributed software development: A case study. Empirical Software Engineering, 19(5),
pp.1197-1224.
Fuggetta, A. and Di Nitto, E., 2014. Software process. In Proceedings of the on Future of
Software Engineering (pp. 1-12). ACM.
Kaur, R. and Sengupta, J., 2013. Software process models and analysis on failure of software
development projects. arXiv preprint arXiv:1306.1068.
Krahn, H., Rumpe, B. and Volkel, S., 2014. Roles in software development using domain
specific modeling languages. arXiv preprint arXiv:1409.6618.
Perkusich, M., Soares, G., Almeida, H. and Perkusich, A., 2015. A procedure to detect problems
of processes in software development projects using Bayesian networks. Expert Systems with
Applications, 42(1), pp.437-450.
Sharma, C., Sabharwal, S. and Sibal, R., 2014. Applying genetic algorithm for prioritization of
test case scenarios derived from UML diagrams. arXiv preprint arXiv:1410.4838.
Störrle, H., 2014. On the impact of layout quality to understanding UML diagrams: size matters.
In International Conference on Model Driven Engineering Languages and Systems (pp. 518-
534). Springer, Cham.

14THE SYSTEM ANALYSIS AND DESIGN
Storrle, H., 2016. On the impact of size to the understanding of UML diagrams. Software &
Systems Modeling, pp.1-20.
Turk, D., France, R. and Rumpe, B., 2014. Assumptions underlying agile software development
processes. arXiv preprint arXiv:1409.6610.
Turk, D., France, R. and Rumpe, B., 2014. Limitations of agile software processes. arXiv
preprint arXiv:1409.6600.

15THE SYSTEM ANALYSIS AND DESIGN
Appendix:
Memo:
To: Customer manager
From: Manager
Date: XXXX
Re: A strategy for implementing the Human -Computer Interaction (HCI) in FFSL
Dear XXX,
I want to tell you regarding the improvements in the FFSL Organization by introducing
some new effective methodologies. At provide, number employees in the FFSL have a solid
command on the pcs and its use to get their work done external to the conventional applications.
Ergo, I'm proposing the acceptance of the new system which is my principal concern. So here I
could be describing the brief setting of an agenda to build up the Human-Computer Interaction
(HCI).
Description:
HCI which is generally accepted as the human-computer interaction may be identified as
the analysis of how people is going to be getting together with the pcs and from what level the
pcs have already been developed or not for having a successful interaction with the human
beings. You will find substantially several variety of important corporations and the academic
institutions which are trying out the analysis of HCI. With a lot of the conditions historically, the
developers of computer system did not pay much attention for easy life time with the computer.
Today lots of the customers computer is going to be fighting that the designers of the computer

16THE SYSTEM ANALYSIS AND DESIGN
are not spending enough attention still to make their products and services user-friendly. But, the
developers of the computer system might improve the risk for discussion that pcs are the
products that are extremely complicated in designing and making. The demand for the
companies that are given by the computer has generally discovered to be outdriven the ease of
use demand.
Plan for HCI for FFSL
The plan for human-computer interaction for FFSL organization has been revealed in
these figure. It provides several phases by attaining that your computer system can be developed
depending on certain requirements of the company associated with software. Maybe it's made
user-friendly by providing training on the software's which have been adopted by the company.
This may make using the system by human beings very simple.
The business enterprise technique of FFSL is it has determined to concentrate primarily
on building and implementation of the application of the client relationship administration and it
wants to perform a project separately for the purchasing project. For this, a specific agile
methodology may be adopted by the organization and then all of the employees may be qualified
on the same. Monitoring and confirming of the application can be created by allowing the
revenue individuals to complete the application in every keep they visit. The phase jobs come in
to the picture where in fact the programs is going to be reviewed by the management team and
the programs with mistakes won't be approved. Then your required action is taken by preparing
were the files of the FFSL is going to be having everything of the clients such as for instance
name, number, handle, last visited, etc. so that the usage of the system by the revenue associates
in the organization is going to be easy. In the whole populace, each region is identified some
particular sales members finding out the breaks in the revenue could be easy through the info that