Free Feet Socks HCI Implementation Plan

This assignment details a plan for implementing Human Computer Interaction (HCI) principles into a new system for Free Feet Socks Limited. It outlines a multi-sprint development process involving requirement gathering, designing and prototyping, testing and feedback, and iteration. The plan emphasizes user needs, clear communication, and responsive application design.

System Analysis and Design for Free Feet Socks Limited
Contents
Part A....................................................................................................................................................2
Introduction...................................................................................................................................2
Adaptive methodologies................................................................................................................2
Recommendation...........................................................................................................................4
Part B: Modelling and Diagramming.....................................................................................................6
Question 3: Event Table....................................................................................................................6
Question 4: Domain Model Class Diagram.......................................................................................7
Question 5: Design class diagram..........................................................................................................7
Question 6: Use Case Diagram..........................................................................................................8
References...........................................................................................................................................10
Appendix.............................................................................................................................................11
Memo..............................................................................................................................................11
Human Computer Interaction (HCI)............................................................................................11
HCI Adoption plan......................................................................................................................11
Appendix: Memo.........................................................................................................................11
1

System Analysis and Design for Free Feet Socks Limited
Part A
Introduction
Adaptive methodologies
1: SCRUM
SCRUM is an Agile methodology that is most often used for software development projects.
This methodology is influenced by empirical investigations and adaptive feedback loops. In
this methodology, real world results are focused upon rather than the speculative measures.
SCRUM methodology divides the development project time into small time sprints that last
for a week or two. It provides a set of roles and responsibilities and rules for meetings. There
are three major roles in SCRUM including Product owner, Scrum master and the project
team. If this methodology would be used for the development project of Free Feet Socks
Limited then the people with these roles would have following responsibilities:
Role Responsibilities
Product Owner  Define and communicate project vision and priorities to the software
development team
 Answer all the questions that the software development team has
 Create a balance between the team members to get them involved in
the development process
Scrum Master  Facilitate the project team to achieve development goals
 Help project team to eliminate any issues that is faced in development
 Advise the product owner on taking steps to maximize ROI
Project Team  The team would have 7 members including two programmers, one
software engineer, one QA expert, two testers, and one User
Experience Designer
 Teams would have the freedom to decide how to achieve goals of
sprints.
Advantages
If the SCRUM methodology is used for the development of the software project for Free Feet
Socks Limited, then the project would have following advantages:
 The time utilized in development and the money used for development would be
saved
 The new developments of the project can be easily coded and tested in different
iterations
 The project progress is frequently updated which gives clear visibility
 As development is done in sprints that are small in duration and involves fast
feedback so coping with the changes done in the systems would be easier
 As methodology facilitates daily meetings, it would also be easier to assess the
productivity of individual team members
 A quality software would be developed within a short span of time
2

System Analysis and Design for Free Feet Socks Limited
 The overhead costs of management would be low with self-controlled approach of
team performance management
Disadvantages
There can also be some disadvantages for Free Feet Socks Limited’s software development
project if they use SCRUM methodology such as:
 The project would have definite end date and thus, if any of the decision makers of
FFSL including Alan Masters, Nils Lofgren or Steven Smith come up with new ideas
for feature development it would lead to scope creep.
 As this uses fasts processes, the team has to be experienced in SCRUM development
and as the company’s existing staff is new to digital or automated technologies or
such development projects, new staff may have to be hired or the existing team has to
be trained on SCRUM methodology to make the development effective. This would
add to the cost to the company.
 Because of tight deadlines and daily reporting structures, the work pressure on the
development team would be high which can frustrate them
Extreme Programming
Extreme programming is another Agile methodology that uses principles including customer
involvement, integrative development, and effective team communication that act as pillar for
the success of the methodology. XP utilizes iterative cycles of development that last for a
week each
Advantages
If the XP methodology is used for the development of the software project for Free Feet
Socks Limited, then the project would have following advantages:
 It would save the time needed for realization of the requirement of the development
project
 As there is less documentation required, the company would save on administrative
costs
 The methodology is simple and thus, it would be easier to develop codes such that the
company would have less challenges in development
 AS this methodology would lead all the people in the team to work from same
location, the communication would be easy and strong (Pierce, 2016).
Disadvantages
There can also be some disadvantages for Free Feet Socks Limited’s software development
project if they use XP methodology such as:
 The methodology focuses more on coding rather than on designing
 It would not provide measures for quality assurance such that bugs are efficiently
eliminated
3

System Analysis and Design for Free Feet Socks Limited
Unified Process Development
This software development methodology explores who does what, when it is done and how
project goals can be reached. It in an incremental and iterative methodology and utilizes use
cases, component based architecture, and unified language for modelling. Unified process
considers four aspects of software development as most important including product, people,
project, and process. Use cases define certain functionality and are the artefacts of
requirements. Using multiple use cases, a use case model is designed which gives the
foundation for the development process.
Advantages
If the UP methodology is used for the development of the software project for Free Feet
Socks Limited, then the project would have following advantages:
 Use cases would capture business value to the software development project
 As the development plan would reflect upon what people do, it would easier for the
team to understand it
Disadvantages
There can also be some disadvantages for Free Feet Socks Limited’s software development
project if they use UP methodology such as:
 The use cases my not define the complete requirement of Free Fee Stock
 End users would not be involved directly and thus, company may miss out of some
requirements.
Recommendation
A recommendation of the appropriate methodology can be given based on current project
requirements and constraints of the company. The requirements of the current project
include:
 Development of a software that allows sales people to record the orders in handheld
devices that are integrated with the back end systems of the company
 Dealers who are sold the bulk orders would be approved by management upon seeing
the order details
 The software interface must provide forms for recording customer details including
Name, Business number, Address, Telephone, Email, Application date, Discount
level, Sales area, and Date last visited
Constraints of the project and the company are:
 The purchasing model for managing supplies cannot be modelled
 Party planners would have separate responsibilities to manage parties and would not
be the part of the system
 The staff does not have the knowledge of IT systems and their development
 The company has only a limited budget in which the project has to be executed
4

System Analysis and Design for Free Feet Socks Limited
 The current systems are manual and hence data migration would be challenging and
time consuming
 As the company needs to hire people from outside for development project with
limited budget, the development needs to happen fast
Considering the requirements and constraints of the project, SCRUM methodology is
recommended for the following reasons:
 It would save on cost and time for the company
 Development team would be self-controlled and thus, effective development would
happen without the need of tight control
 Fast feedback would ensure that all stakeholder needs are sufficiently incorporated
(Qi, 2013).
5

System Analysis and Design for Free Feet Socks Limited
Part B: Modelling and Diagramming
Question 3: Event Table
Event Event
Type
Trigger Source Activity System
Response
or
Output
Destination
Customer
login
Login Customer
order
Custome
r
Data entry Data
storage
Customer
Database
Sales
Reports
Report
generation
Review by
manageme
nt
Sales
people
Running
report
generation
query
Sales
report
Manageme
nt user
screen
Potential
Customer
Login
Login Customer
visit
Custome
r
Data entry Data
Storage
Potential
customer
database
Order
manageme
nt
Order
processing
Customer
order
Custome
r
Take order
including
details of
products and
quantities
ordered
Data
storage
and
forwardin
g for
approval
Email to
senior
manageme
nt for
approval
Accounting
details
update
Accountin
g
Customer
and
supplier
payments
Custome
r
Supplier
Update
accounts
payable and
receivable
automatical
ly upon
entering the
payment
taken or
given
details
Updating
of
accountin
g
database
Accounting
system
update
The table above shows events that would happen in the human computer interaction and
would reciprocate into the features of the new developed system
6

System Analysis and Design for Free Feet Socks Limited
Question 4: Domain Model Class Diagram
Question 5: Design class diagram
7

System Analysis and Design for Free Feet Socks Limited
Question 6: Use Case Diagram
Question 7: Use Case Description (intermediate)
Use Case Create customer
Scenario Creation of new customer
Triggering Event Company wishes to add a new customer within the system
Description Allows customer to register through company portal
Actors Customer
Related Use Case Not applicable
Stakeholders Customer
Pre-Condition criterias Not applicable
Post-Condition criterias An entirely new customer account would be created
Activity Flow
Actor System
1) Customer would begin
by clicking on the
‘Register as a supplier’
link given on the portal.
2) The portal displays the form with different fields: Name,
address, phone number, email along with the payment terms.
5) System would display a unique order number for the
customer that has been created newly.
8

System Analysis and Design for Free Feet Socks Limited
3) Customer would then
fill in all the required
details on the form and
click on submit.
Alternative 5.1 If the customer fills in incorrect details or fails to enter the
mandatory fields then an error message would be shown with
respect to the error.
9

System Analysis and Design for Free Feet Socks Limited
References
Issa. (2015). Usability and Human Computer Interaction (HCI) . Springer.
Pierce, W. (2016). Disadvantages and Advantages of Extreme Programming. Atlaz .
Qi, X. (2013). Xiaojun QiThe Software Process. Dgital CS.
10

System Analysis and Design for Free Feet Socks Limited
Appendix
Memo
Human Computer Interaction (HCI)
HCI is about the development of a computer based system that would allow people to carry
out their activities productively. It uses interactional techniques through which users
communicate with the technology. HCI involves users at the earlier stage of development
such their needs are understood and considered while designing and developing graphics,
navigation, design, typography and multimedia (Issa, 2015).
HCI Adoption plan
Following steps would be followed for the adoption of HCI in the company:
Step 1: Team building - 1 sprint of 7 days
 Build a team of product owner, SCRUM master from developer agency and project
team of 4 people involving internal and agency people.
Step 2: requirement gathering - 1 sprint of 7 days
 Identify the needs of sales staff and establish clear requirements for the development
 Identify the goals of development and record them in documents
Step 3: Designing & Prototyping - 3 sprints of 7 days each
 Develop alternative designs for adoption
 Build prototypes of the interfaces and get them assessed by the users
Step 4: Testing and Feedback loop - 1 sprint of 7 days
 Evaluate the development process throughout involving users for feedback
 Create new iteration requirement based on user feedback.
Step 5: Next Iteration - 2 sprints of 7 days each
 Identify changes to be made in development
 Make changes in the development with new codes incorporated
The whole development would take 8 sprints involving 56 days
Appendix: Memo
To: Employees of Free Feet Socks Limited
From: Alan Masters
Date: 13th Oct 2017
Subject: HCI Adoption
11

System Analysis and Design for Free Feet Socks Limited
Our team had prepared a plan and User Interface (UI) analysis for the information analysis
that should be produced for your organization. The requirement for this investigation was to
think of the depictions, determinations and clarifications for the outline procedure and rule
that should be utilized. The clients of the present time have certain necessities and desires
from the frameworks and applications that are produced for them. Two of the essential
desires of the clients incorporate improved level of communication and expanded
responsiveness from the application. There are Human Computer Interaction (HCI) rule that
have been characterized and clarified for the framework.
The management has decided to make changes in the systems for improving productivity. A
new system allowing human computer interaction would be developed that would help you
take and manage orders as well as customer information and approvals through handheld
devices and computers. For this, we need to implement an organized plan and we need your
cooperation. We have hired a team of developers who would meet you to understand
processes and take requirements for development. Your active participation would be needed.
Another vital and huge HCI rule spins around the right utilization of route and the format in
the framework. The route alludes to the stream on a similar screen of the framework and in
the middle of the diverse screens. This stream might be smooth and there should dependably
be lucidity to the client as far as the stream of the application. The clients might have the
capacity to comprehend the route without anyone else. Format is another component that
should be set up effectively. The framework might incorporate and take after a
straightforward format. This should incorporate the utilization of compulsory components,
for example, title, header, body and footer areas. The format must be the same on the greater
part of the framework screens.
The users that will make utilization of the data framework that will be created for your
organization will be the inside workers of the association. Such a framework will be executed
without precedent for the organization. This may prompt the likelihood of the operational
missteps and mistakes. The clients should be given the capacity to move back their
procedures and operations with the goal that the effects of these blunders isn't gigantic. There
is a rule of mistake determination and rectification that must be followed in the framework
and the majority of the screens of the framework.
It would be ideal if you experience the greater part of the prescribed HCI standards for the
framework that will be produced for you organization and let us know your remarks and
proposals in regards to the same. The last outline that will be exhibited will incorporate the
greater part of the UI components and the HCI rule that will be finished.
12