HCI Adoption Plan for Free Feet Socks

The assignment details the development of a Human-Computer Interaction (HCI) adoption plan for Free Feet Socks Limited. It involves defining project phases using UPA methodology, building a SCRUM team, conducting requirement gathering and analysis, designing and prototyping interfaces, implementing and testing software, and incorporating user feedback. The plan emphasizes iterative development with regular feedback loops to ensure the software meets the needs of sales staff.

System Analysis and Design for Free Feet Socks Limited
Contents
Part A....................................................................................................................................................2
Question 1: Report.............................................................................................................................2
Introduction...................................................................................................................................2
Adaptive methodologies................................................................................................................2
Recommendation...........................................................................................................................4
Event table.............................................................................................................................................5
Domain class diagram...........................................................................................................................6
Design Class Diagram...........................................................................................................................7
Use case description..............................................................................................................................7
References.............................................................................................................................................9
Appendix.............................................................................................................................................11
Human Computer Interaction (HCI)............................................................................................11
HCI Adoption plan......................................................................................................................11
Appendix: Memo.........................................................................................................................12
1

System Analysis and Design for Free Feet Socks Limited
Part A
Question 1: Report
Introduction
This report covers the adoption process used by Free Feet Socks Limited for transformation
of its systems by developing new software that is expected to increase the productivity of the
sales staff. The report assesses different development methodologies and makes
recommendations for the most suitable methodology as well as presents a plan for the
adoption of Human Computer Interface (Chadli, Toval, Idri, & Nicolás, 2016).
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
(Chang, 2012).
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 (ADELL,
2013)
 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 (Craddock, 2012)
 A quality software would be developed within a short span of time
 The overhead costs of management would be low with self-controlled approach of
team performance management (Ghosh, Forrest, DiNetta, Wolfe, & Lambert, 2012)
Disadvantages
There can also be some disadvantages for Free Feet Socks Limited’s software development
project if they use SCRUM methodology such as:
2

System Analysis and Design for Free Feet Socks Limited
 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 (Hajjdiab & Taleb, 2011).
 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 (Craddock, 2012)
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 (Shelton, 2008)
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 (Farrell, 2007)
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,
3

System Analysis and Design for Free Feet Socks Limited
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 (Qi, 2013)
Constraints of the project and the company are:
 The purchasing model for managing supplies cannot be modelled as it would be
managed manually even after the new development
 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 (Ramsin,
2005)
 The company has only a limited budget in which the project has to be executed
 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 (Kaur & Sengupta, 2011)
4

System Analysis and Design for Free Feet Socks Limited
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 with self-control and fast speed of
development
 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).
Event table
Event Event
Type
Trigger Source Activity/Use
Case
System
Response/ Output
Destination
Addition of
a new
geographica
l area
Event
is
Internal
Scaling of
the business
Country’s
head
Add
geographical
area
Details are added in
the form of
geographical area
FFSL,
geographical
area
Addition of
a new store
Event
is
Internal
Setting up
of new store
Application
of the store
Add store Details are added in
the form of a new store
FFSL, store
Addition of
a new
customer
Event
is
Internal
Engagement
of new
customer
Customer Create
customer
Details are added in
the form of a new
customer
FFSL,
customer
Recording
of the sales
data and
records
Event
is
Internal
Checking of
the sales
FFSL Calculation of
the sales
Sharing of the sales
record
HBL
Addition of
a new
employee
Event
is
Internal
Engagement
of new
employee
Employee Create
employee
Details are added in
the form of a new
employee
FFSL,
employee
Submission
of the
application
Event
is
Internal
Engagement
of new store
in the form
of customer
Store Addition of a
store as
customer
Approved/Disapproved FFSL, store
5

System Analysis and Design for Free Feet Socks Limited
Domain class diagram
6

System Analysis and Design for Free Feet Socks Limited
Design Class Diagram
Use case description
Use Case Create a customer
Scenario Free Feet Socks wants to add a new retailer
Triggering Event New retailer has to be added in the system
Description Registered retailer can use the service as a customer
Actors Customer
Related Use Case N/A
Stakeholders 1. Customer
2. System
Pre-Condition System can be used over a browser by sales person
Post-Condition New retailer is added as a new registered customer
Flow of activities
Actor System
1) Sales person enters customer 2) The system would show a registration form with entry
7

System Analysis and Design for Free Feet Socks Limited
details
3) Customer submits details to
update customer database
5) Application is approved to
register customer
fields like customer name, email address, address, and
contact no.
4) System takes and forwards application to management
6) Management approves application in system
Alternate Course of Action 2.1 Incorrect data entry shows an error
4.1 Reports would be generated based on manager queries
8

System Analysis and Design for Free Feet Socks Limited
References
ADELL, L. (2013, April 11). BENEFITS & PITFALLS OF USING SCRUM SOFTWARE
DEVELOPMENT METHODOLOGY. Retrieved from Belatrix Software Blog:
http://blog.belatrixsf.com/benefits-pitfalls-of-using-scrum-software-development-
methodology/
Awad, M. A. (2005). A Comparison between Agile and Traditional Software Development
Methodologies . The University of Western Australia.
Chadli, S. Y., Toval, A., Idri, A., & Nicolás, J. (2016). Software project management tools in
global software development: a systematic mapping study. Research Gate.
Chang, C. (2012). Selecting an Appropriate Software Development Lifecycle (SDL) Model in
an Agency Environment. Retrieved November 12, 2015, from
http://www.metia.com/seattle/chong-chang/2012/08/sdl-model-in-an-agency-
environment/
Craddock, A. (2012). The DSDM Agile Project Framework for Scrum. Nlighten.
Farrell, A. (2007). Selecting a Software Development Methodology based on Organizational
Characteristics . ATHABASCA UNIVERSITY .
Ghosh, S., Forrest, D., DiNetta, T., Wolfe, B., & Lambert, D. C. (2012). Enhance PMBOK®
by Comparing it with P2M, ICB, PRINCE2, APM and Scrum Project Management
Standards. PM World Today , XIV ( I), 1-77.
Hajjdiab, H., & Taleb, A. S. (2011). Adopting Agile Software Development: Issues and
Challenges. International Journal of Managing Value and Supply Chains (IJMVSC) ,
1-10.
Issa. (2015). Usability and Human Computer Interaction (HCI) . Springer.
Kaur, R., & Sengupta, J. (2011). Software Process Models and Analysis on Failure of
Software Development Projects . International Journal of Scientific & Engineering
Research , 2 (2), 1-4.
Mishra, A., & Dubey, D. (2013). A Comparative Study of Different Software Development
Life Cycle Models in Different Scenarios. International Journal of Advance Research
in Computer Science and Management Studies , 1 (5), 64-69.
Models, Collections and Toolkits for Human Computer Interaction:What Can We Learn?
(2010). The 24th BCS Conference on Human Computer Interaction (pp. 1-9).
Netherlands: Delft University of Technology.
9

System Analysis and Design for Free Feet Socks Limited
Pierce, W. (2016). Disadvantages and Advantages of Extreme Programming. Atlaz .
Qi, X. (2013). Xiaojun QiThe Software Process. Dgital CS.
Ramsin, R. (2005). Software Development Methodologies. Sharif University of Technology.
Shelton, C. (2008, July 9). Agile and CMMI: Better Together. Retrieved from Scrum
Alliance: https://www.scrumalliance.org/community/articles/2008/july/agile-and-
cmmi-better-together
Sofia. (2010). Software Development Process – activities and steps. UACG.
Vukovi}, Z. (2004). PROJECT MANAGEMENT - SOFTWARE DEVELOPMEN
TMETHODOLOGY. Siemens.
10

System Analysis and Design for Free Feet Socks Limited
Appendix
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 in a software application (Issa, 2015). HCI
development can be done using several tools and with the progress of practitioner’s
exploration and learning, these tools are updated. Different tools are used by different types
of projects in different phases. For instance, UPA defines methodology in four phases
including analysis, design, implementation and deployment while IDEOs human centred
design kit defines three phases including hearing, creation and delivery. In this project, UPA
phases would be used (Models, Collections and Toolkits for Human Computer
Interaction:What Can We Learn?, 2010).
HCI Adoption plan
Following steps would be followed for the adoption of HCI in the company:
Step 1: SCRUM 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.
 There would be 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 (Awad, 2005):
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 (Craddock, 2012)
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 (ADELL,
2013)
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 (ADELL, 2013).
11

System Analysis and Design for Free Feet Socks Limited
Step 2: Requirement gathering and Analysis phase of HCI - 1 sprint of 7 days
 Identify the needs of sales staff and establish clear requirements for the development
of the software
 Identify the goals of development and record them in official documents that would
be shared with the project team for guidance
Step 3: Designing & Prototyping - 3 sprints of 7 days each (Kaur & Sengupta, 2011)
 Develop alternative designs for adoption would be explored and assessed to find the
most suitable design as per users
 Build prototypes of the interfaces and get them assessed by the users
Step 4: HCI Implementation, Testing and Feedback loop - 1 sprint of 7 days
 Evaluate the software development process throughout the project involving users
who would provide feedback
 Create new iteration requirement based on user feedback to improve the functionality
of the software (Sofia, 2010).
Step 5: HCI Delivery and Next Iteration - 2 sprints of 7 days each
 Identify changes to be made in development and accordingly update the development
requirement
 Make changes in the development with new codes incorporated in the software
The whole development would take 8 sprints involving 56 days. Each sprint have defined
goals that have to be achieved by the time it finishes and the progress would be monitored to
ensure that objectives are met sufficiently at the end of the sprint.
Appendix: Memo
To: Employees of Free Feet Socks Limited
From: Alan Masters
Date: 13th Oct 2017
Subject: HCI Adoption
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
(Vukovi}, 2004). The software would help you keep records of new customers, get them
12

System Analysis and Design for Free Feet Socks Limited
approved as registered retailers online. Only the approved retailers would be given ordered
goods for sales.
13