IMAT5209 - Interactive System Usability Evaluation Report at DMU

This report presents a comprehensive usability evaluation of an interactive system, focusing on human-computer interaction (HCI) principles and their application in system design. It covers interactive systems, their uses, and usability requirements, including ascertaining user needs, ensuring reliability, promoting standardization, and completing projects on schedule and within budget. The report also discusses cognitive and perceptual abilities, usability techniques, and specifications. Methodologies such as the naive developer’s approach and Cooper’s analysis are explored. The relationship between HCI and human dialogue is examined, and the results of the evaluation are presented, concluding with recommendations for enhancing technology acceptance, performance, and user satisfaction. This document is available on Desklib, a platform offering a range of study tools and resources for students.

Running Head:HUMAN INTERACTION IN SYSTEM DESIGN
HUMAN INTERACTION IN SYSTEM DESIGN
Name of the Student
Name of the University
Author Note

1HUMAN INTERACTION IN SYSTEM DESIGN
Executive Summary
Human Computer Interaction are becoming core aspects of the system development process
to improve and enhance system facilities and to satisfy users’ needs and necessities. HCI will
assist designers, analysts and users to identify the system needs from text style, fonts, layout,
graphics and colour, while usability will confirm if the system is efficient , effective, safe,
utility, easy to learn, easy to remember, easy to use and to evaluate, practical visible and
provide job satisfaction to the users. Adopting these aspects in the system development
process, including the sustainable design will measure and accomplish users’ goals and tasks
by using a specific technology. Finally, designers should include these aspects in their agenda
to enhance technology acceptance, performance and satisfy users’ necessaries.

2HUMAN INTERACTION IN SYSTEM DESIGN
Table of Contents
Introduction....................................................................................................................3
Discussion......................................................................................................................3
Interactive Systems....................................................................................................3
Uses of Interactive Systems...........................................................................................4
Direct Manipulation Systems.................................................................................4
Visualization, Virtualization, and Agents/Embedded Systems..............................4
Usability Requirements..................................................................................................5
Ascertain users’ needs............................................................................................5
Ensure proper reliability.........................................................................................6
Promote appropriate standardization......................................................................6
Complete projects on schedule and within budget.................................................6
Cognitive and perceptual abilities..........................................................................6
Usability techniques in interactive system.................................................................7
Conduct usability test on the user documents:.......................................................7
Benchmarking while testing the document’s usability:.........................................7
Clear and concise UI elements:..............................................................................8
Usability Specifications.........................................................................................8
Methodology used......................................................................................................9
The nave developer’s approach..................................................................................9
Cooper’s analysis.................................................................................................10
Relationship between the HCI and Human Dialogue..............................................11

3HUMAN INTERACTION IN SYSTEM DESIGN
Results of Evaluation...............................................................................................12
Conclusion................................................................................................................15
References....................................................................................................................17

4HUMAN INTERACTION IN SYSTEM DESIGN
Introduction
Interactive systems are computer systems characterized by significant amounts of
interaction between humans and the computer. Most users have grown up using Macintosh or
Windows computer operating systems, which are prime examples of graphical interactive
systems. Editors, CAD-CAM (Computer Aided Design-Computer Aided Manufacture)
systems, and data entry systems are all computer systems involving a high degree of human-
computer interaction. Games and simulations are interactive systems. Web browsers and
Integrated Development Environments (IDEs) are also examples of very complex interactive
systems. Some estimates suggest that as much as 90 percent of computer technology
development effort is now devoted to enhancements and innovations in interface and
interaction. To improve efficiency and effectiveness of computer software, programmers and
designers not only need a good knowledge of programming languages, but a better
understanding of human information processing capabilities as well. They need to know how
people perceive screen colours, why and how to construct unambiguous icons, what common
patterns or errors occur on the part of users, and how user effectiveness is related to the
various mental models of systems people possess.
Discussion
Interactive Systems

5HUMAN INTERACTION IN SYSTEM DESIGN
This module is about the design and evaluation of a class of systems that were not
even envisaged until relatively recently. Until the 1980s almost all commercial computer
systems were non-interactive. Computer operators would set-up the machines to read in large
volumes of data – say customers bank details and transactions – and the computer would then
process each input and generate appropriate output (Ali et al. 2018). The Present There are
still lots of these systems in place but the world is also now full of interactive computer
systems. These are systems that involve users in a direct way. In interactive systems the user
and computer exchange information frequently and dynamically. Norman’s
evaluation/execution model is a useful way of understanding the nature of interaction. User
has a goal (something to achieve) User looks at system and attempts to work out how he
would execute a series of tasks to achieve the goal. User carries out some actions (providing
input to the system by pressing buttons, touching a screen, speaking words etc) .System
responds to the actions and presents results to the user. System can use text, graphics, sounds,
speech etc. User looks at the results of his action and attempts to evaluate whether or not the
goals have been achieved. A good interactive system is one where: • User can easily work out
how to operate the system in an attempt to achieve his goals. • User can easily evaluate the
results of his action on the system. This course is about methods, tools and techniques that
can be used to ensure that the user and computer can interact effectively. We will be looking,
then, at the Human-Computer Interaction (or HCI) elements of systems design.

6HUMAN INTERACTION IN SYSTEM DESIGN
Uses of Interactive Systems
Direct Manipulation Systems
Direct manipulation system is one in which the user is able to select an object and
then specify which actions are to be taken. This is in opposition to command line systems
where the user would normally specify an action and then select an object upon which the
action was to be performed. This fundamental paradigm shift caused a number of changes in
how these systems were designed and implemented in code.
Visualization, Virtualization, and Agents/Embedded System
Throughout the 1980s and 1990s, there were numerous efforts to take advantage of
the human ability to process information visually. At the simplest level, consider that a
human looking at an image on a television screen has no problem in discerning a pattern that
consists of millions of individual pixels per second, changing in both time and space or
consider the example provided. The pattern is represented by the following set of numbers: a
set of X, Y pairs with the X value being the upper value in each column and the Y value
being the lower value? Even knowing they are pairs of X, Y coordinates, most people have
trouble seeing a pattern in this numerical example. If however, these points are plotted, or
visualized, a pattern emerges rather quickly as shown in Figure B. Visualization systems
manipulate information at high levels of aggregation, making the information more accessible
to users. The aggregates may be records, documents, or any other entity defined as an object.
Working with large numbers of objects that have multiple attributes, we can map these
attributes to the interface in such a way as to visualize the data or simulate some process. The
visualization of abstract data to sensory interfaces is central to software including geographic
information systems and data mining applications, among others. In these systems, every
effort was made to allow the user to explore a virtual world with little or no translation to
symbolic form. Thus, with visualization techniques and new forms of input devices, such as

7HUMAN INTERACTION IN SYSTEM DESIGN
data gloves, hand movements could be used to manipulate virtual objects represented
graphically in a virtual world. This virtual environment was presented to the user via two
display screens, each of which provided a slightly different perspective, giving the user a
stereoscopic view of a virtual space that appeared to have depth. Work on virtual and
artificial reality continues on a number of specialized fronts, including a field known
as telemedicine.
Usability Requirements
Ascertain users’ needs
Users’ needs the tasks and subtask that the user needs to carry out when using the
UI/product. Perform a task analysis: This will help to discover also infrequent and
exceptional tasks .Add appropriate extent of functionality (inadequate vs. clutter); possibly
hide infrequently used functions but make sure that advanced users can access them
effortlessly if required (e.g., calculator with different views for basic and scientific use).
Ensure proper reliability
All actions that the user takes must reflect appropriate results; presented information
must be accurate. If you do not provide this kind of reliability users will quickly loose trust in
your application and stop using it. It is important to use hardware, software, and/or
architectures that support this kind of reliability (e.g., high availability in networked
applications) finally, consider privacy, security, data integrity, and the possibility of
malicious tampering.
Promote appropriate standardization
Use of common UI features across multiple applications, especially important with
increasing number of available applications and users Standardization can be immensely
beneficial.

8HUMAN INTERACTION IN SYSTEM DESIGN
Complete projects on schedule and within budget
Certainly a general goal for all software projects. Sometimes UI designers forget
about this goal, however it is as crucial to UI design as it is to other parts of the software
development process. Every delay or increase in costs will affect your project in one way or
the other
Cognitive and perceptual abilities
You must understand the cognitive and perceptual abilities of your target group/user
community. A classification of human cognitive processes provides the UI designer with a
framework. Short-term and working memory, long-term and semantic memory problem
solving and reasoning, decision making and risk management .Language communication and
comprehension ,search, imagery, and sensory memory learning, skill development,
knowledge acquisition . Other factors that affect perceptual and motor performance are, for
instance, monotony and boredom, fear, anxiety, mood, and emotions .Naturally, background
experience and knowledge in the task domain influence the learning process and the user
performance.
Usability techniques in interactive system
Some of the basic usability techniques that can really help the technical
communicators to ensure a great user experience are:
Conduct usability test on the user documents:
The user documents, which you create, can be sometimes very tricky based on the
use-case scenarios you are documenting. Bearing in mind the length of user guide, testing the
entire document is not always feasible. You can choose some complicated procedures that are
significant from an end-user’s perspective and test them accordingly. As technical

9HUMAN INTERACTION IN SYSTEM DESIGN
communicators are mostly working from offshore, they can test their documents remotely or
one-on-one with the actual users.
Benchmarking while testing the document’s usability:
Now while testing the usability of the document, you need to have certain
benchmarks. Time taken to complete a procedure. Keeping track of the number of errors an
end-user encounters while referring to the document. The satisfaction level of the end-user
while referring to the document.
Clear and concise UI elements:
UI elements in the application/product/Website should be self-explanatory. Avoid
using a confusing terminology in the user documents. Error messages should be crisp and to
the point: As a technical communicator if you find the error messages not documented in a
simple and concise language, you can assist the development team in writing them so that the
end-user can perceive things easily. Thus, you need to be proactive in pointing out any
technical jargon, which is there in the error messages.
Usability Specifications
Once the designer has gathered and analysed information about the tasks, problems
and steps to work with the proposed system, the next step is to answer the question: How will
we know if the interface is usable? This is laid out in a usability specification. A usability
specification defines the measure of success of a computer system or website and serves as an
indicator about whether or not the development of the website is on the right track. A
usability specification should be developed during what Is USABILITY. The first stage of the
development process and monitored “at each iteration”, to determine whether the “interface,
is, indeed, converging toward an improved, more usable design. Usability specifications
should lay out explicitly how usability will be evaluated and can be divided into two sections:

10HUMAN INTERACTION IN SYSTEM DESIGN
• Performance Measures: are directly observable by watching a user complete a task within a
specific time. This includes monitoring the number of errors and time needed to accomplish
the task. These types are ‘quantifiable measures’ which means that they can be
communicated with numbers. For example “you can count the number of minutes it tasks a
user to complete a task or the number of negative comments that occur (Andrews 2015).
Preference Measures: give an indication of a “user’s opinion about the interface which is not
directly observable. Preference measures can be determined by using questionnaires or
interviews. Usability specifications are needed to determine when the iteration of prototypes
has produced a system with sufficient usability. Therefore, without usability specifications,
the key factors that “generally determine an end to the iterative refinement process are when
developers run out of time, patience, and/or money (Gerengi et al. 2018). Usability
specifications are very important to the development process since they define a quantifiable
end to the seemingly endless iterative refinement process confirm that usability is a core step
in the system development process as usability will allow users, analysts, and designers
(internal and external) to confirm that the website design is efficient, effective, safe, utility,
easy to learn, easy to remember, easy to use and to evaluate, practical, visible and provide job
satisfaction.
Methodology used
The nave developer’s approach
The main problem with nave developers is the total lack of any planning or structure
to their efforts. This results in any and all of the undesirable interactions taking place between
the submodels. In particular the developer’s model influences all of the rest of the system, as,
what is easy to do, is what gets done. Careless rapid prototyping may also suffer from this
malaise as eventually the system becomes the definition of the system. Warren and Viljoen

11HUMAN INTERACTION IN SYSTEM DESIGN
studied a number of students attempting to design a user interface for a video store. What
they found was that these designers created an interface directly in terms of tasks that had to
be carried out. This in turn lead to the one screen per task syndrome, a malady that Cooper
calls dialog box pollution. A large number of dialog boxes is undesirable because at each
page switch the user loses context making exploratory learning difficult. In RM terms the
intermediate conceptual model is missing. A similar problem can be expected to occur when
the developer’s model directly influences the interaction model. This particularly manifests
itself in the one screen per relation approach which some database management systems tend
to encourage. But a relation does not necessarily map onto a concept in the user domain so
this technique may not be appropriate.
Cooper’s analysis
Cooper’s highly entertaining accounts of what is wrong with modern software can
largely be attributed in RM terms to the developer’s model influencing the rest of the system.
An example is that programmers tend to see each branch with equal importance because they
expend the same effort writing the code. The end user might prefer the most frequent branch
to be defaulted to avoid making the same choice each time. For instance, it is irksome to have
to choose printer parameters every time when they hardly ever change. Cooper also dwells on

12HUMAN INTERACTION IN SYSTEM DESIGN
the programmer’s zero, one, many view of the world which again does not match an end user
view where 10 items is a very different phenomenon from 1000 items. Cooper further claims
that once code starts to be written this code is cast in stone, resulting in the developer’s model
harmfully influencing the final product if the code has been designed without reference to
interface issues. His prescription is to ensure that the developers are only involved in the
developer’s model and nothing else, and only after the other submodels have been
constructed. Cooper also makes an important contribution (or claim) regarding the
development of the psychological model. Cooper is concerned about software that attempts to
be all things to all people with the inevitable consequence that it is nothing to anybody. In
turning Shneiderman’s structure to accommodate diversity around, Cooper introduces the
concept of a “persona” and the software is designed to cater for at most a few persona. The
persona are roughly worst case users of their type. He claims that interface designers can
visualise such a persona and draw accurate conclusions about their needs without the
requirement of abstract psychological models. While Cooper’s writings are worth reading for
their entertainment value alone, they also make many telling points. From the point of view
of the RM, however, they could not claim to be a complete description of how to design and
implement interactive computer systems.
Relationship between the HCI and Human Dialogue

13HUMAN INTERACTION IN SYSTEM DESIGN
HCI is the study and theory of the interaction between humans and complex
technology and is concerned with how current input and output technologies affect
interaction, and the situations in which these technologies and techniques might be put to best
use. Therefore, the relationship between HCI and human dialogue may be summarized as
follows. Human Computer interaction, like human dialogue, is a form of communication
where a degree of understanding can be achieved. Admittedly, this understanding may be
limited in some respects, but if designed properly, a computer system will do as its user
wishes, provided the user knows what is possible and how to give commands.
Communications requires agreement on the terms used in the dialogue. When humans
successfully communicate, they usually have a shared understanding of the words used and
the concepts to which they refer. This is also true of human computer communication. When
a user gives commands to a system, then the system must have an understanding of these
commands if the interaction is going to succeed. Communications requires agreement, not
only upon the terms and concepts used, but also upon the context of the communication. For
example, if two people are speaking to one another, then there needs to be an agreed
understanding of what they are speaking about. To illustrate this point further, let us consider
an example where two individuals do not agree on the context of their conversation. Two
people are sharing a car to travel to a conference. They stop at a garage for fuel and to check
the car tyres. Bill is putting air into the tyres when Fred asks, “How’s the pressure?” Bill
replies, “Not too good, the boss keeps getting on to me.” Fred explains, “Sorry I meant the
car tyre pressure, but how’s work anyway. In this example, we understand that Fred and Bill
do not share a common context for their brief exchange (Costa et al. 2018). In their separate
contexts, the necessary link of work and the context of car maintenance, some of the words
can have different meanings and the result is a failure in the dialogue between the two
individuals. Human Computer Interaction (HCI).This sort of dialogue failure can also occur

14HUMAN INTERACTION IN SYSTEM DESIGN
in human-computer communications (Campean, Yildirim and Henshall 2018). For example,
consider a user of a word processing system who issues a command to print the document
that is currently being edited. Following the printing process, the user issues a command for
the system to re-display the document on the screen, but instead nothing happen. The system,
upon receiving the first command changed to the printing mode, but did not adequately
inform the user who was unaware of the change in context and the subsequent legality of
some of the commands. The lesson to be learned is that those involved in communication
assign to symbols and terms depending upon the context in which they are communicated.
The previous two examples reveal that perspective is not only important in conversation
between humans, but is also a considerable factor in human-computer dialogue. To sum up,
HCI is similar to human dialogue, as it is a form of communication where a degree of
understanding is achieved. There must also be agreement between individuals involved in the
process of communication on the meaning of the symbols and terms used. The context of the
dialogue is also important, as it is the context that dictates the meanings of some of the
symbols and terms used.
Results of Evaluation
The goals of HCI are to produce usable and safe systems, as well as functional
systems. These goals can be summarized as safety, utility, effectiveness, efficiency, and
appeal. These goals focus on the services that the system provides, how quickly the tasks can
be achieved, and ensuring that users like the system. In general, usability is an essential
concept in HCI and is concerned with making systems easy to learn, easy to use, and with
limiting error frequency and severity. To establish a simple system with good usability, the
HCI specialists need to be aware of the following issues. Understand the factors such as
organizational, social, and psychological factors that determine how people operate and make

15HUMAN INTERACTION IN SYSTEM DESIGN
use of computer technology effectively (Arpaci-Dusseau and Arpaci-Dusseau 2018). Develop
tools and techniques to help designers ensure that computer systems are suitable for the
activities for which people will use them. Achieve efficient, effective, and safe interaction in
terms of both individual Human Computer Interaction and group interaction (Ching et al.
2016) These needs should be considered very carefully at the design stage, as most of the
users should not have to change radically to fit in with the system; rather, the system should
be designed to match their requirements (Jang et al. 2017). The purpose of HCI is to design a
computer system to match the needs and requirements of the users. The HCI specialists need
to think about the above factors in order to produce an outstanding system. To achieve the
goals of HCI, a number of approaches can be utilized. These approaches need to be studied
very carefully in order to develop a system, which provides the user with productivity and
efficiency. These approaches are involving the user integrating different kinds of knowledge
and expertise: (integrate knowledge and expertise from the different disciplines that
contribute to HCI design), making the design process iterative testing can be done to check
that the design does indeed meet users’ requirements). From the above, it was learned that
HCI design should be user-centred, integrate knowledge from different disciplines, and be
highly iterative (Li et al. 2017). In addition, it is important to undertake effective usability
evaluation (Welstead and Felder 2016). This will provide feedback regarding negative and
positive aspects of prototypes. It is important that the way in which people interact with
computers is intuitive and clear. However, designing appropriate HCI is not always
straightforward, as the many poorly designed computer systems testify. One of the challenges
of HCI design is to keep abreast of technological developments and to ensure that these are
harnessed for maximum human benefit. The goal of this research is to develop a framework
for rapid, integrated, incremental systems development that enables a group of designers and
users working together to produce a friendly, effective and efficient website. Two terms

16HUMAN INTERACTION IN SYSTEM DESIGN
interaction and interactivity need to be defined in order to understand how the user can
communicate with the system to accomplish his/her goals (Yang et al. 2018). Once the
designer has gathered and analysed information about the tasks, problems and steps to work
with the proposed system, the next step is to answer the question: How will we know if the
interface is usable? This is laid out in a usability specification. A usability specification
defines the measure of success of a computer system or website and serves as an indicator
about whether or not the development of the website is on the right track (Dones et al. 2017).
A usability specification should be developed during the first stage of the development
process and monitored “at each iteration”, to determine whether the “interface, is, indeed,
converging toward an improved, more usable design. Usability specifications should lay out
explicitly how usability will be evaluated and can be divided into two sections: • Performance
Measures: are directly observable by watching a user complete a task within a specific time.
This includes monitoring the number of errors and time needed to accomplish the task
(Freitas et al. 2018). These types are ‘quantifiable measures’ which means that they can be
communicated with numbers. For example “you can count the number of minutes it tasks a
user to complete a task or the number of negative comments that occur (de et al. 2017).
Preference Measures give an indication of a “user’s opinion about the interface which is not
directly observable. Preference measures can be determined by using questionnaires or
interviews. Usability specifications are needed to determine when the iteration of prototypes
has produced a system with sufficient usability. Therefore, without usability specifications,
the key factors that “generally determine an end to the iterative refinement process are when
developers run out of time, patience, and/or money. Usability specifications are very
important to the development process since they define “a quantifiable end to the seemingly
endless iterative refinement process confirm that usability is a core step in the system
development process as usability will allow users, analysts, and designers (internal and

17HUMAN INTERACTION IN SYSTEM DESIGN
external) to confirm that the website design is efficient, effective, safe, utility, easy to learn,
easy to remember, easy to use and to evaluate, practical, visible and provide job satisfaction
(Fan, Lin and Tan 2018).
Conclusion
This report outlined the basic concepts involved in Human Computer Interaction and
usability in the system development process. These considerations are very useful to the
business community in line to increase the efficiency of their staff, and thus, their profits.
Currently, HCI and usability are needed in any design, including sustainable design to
recognize the new smart technology and portable device needs from designers and users
perspective. Therefore, designers should integrate and combine HCI and usability in their
agenda design, including sustainable design, to enhance new smart technology and portable
devices performance and facilities, and to satisfy users’ needs. Once an interface has been set
up, it becomes clear that there is usually a better way of approaching it. With this in mind, a
number of hints and tips are on offer: KISS: Keep It Simple, Stupid. Low-tech is generally
more reliable than hi-tech (although less fun). The main objective of an interface is to be able
to trust it. Most of the time, it has been found that interfaces provided by application vendor
is specific to certain specific business scenario, which may not be applicable to customer. In
those cases, development of interfaces to be considered as a separate entity and it needs to be
developed by in-house team or third party. Treat each direction of an interface as a separate
problem. There is no rule that states that the same mechanisms need to be used for both the
incoming and outgoing messages. Interfacing system A to system B is much easier than most
people realize, and the benefits are enormous. These benefits are particularly important when
using a LIMS, as the majority of the organization’s QA/QC data is stored within it. Creating a

18HUMAN INTERACTION IN SYSTEM DESIGN
global village (rather than islands) of information will result in a truly enterprise LIMS
solution.
References
Ali, N.M., Admodisastro, N., Hassan, S. and Saeed, M.S.A., 2018. ID NO. UPM 008
TOPIC: UML DIAGRAM LEARNING TOOL. UNIVERSITY CARNIVAL on e-LEARNING
(IUCEL) 2018, p.408.
Andrews, D., 2015. The circular economy, design thinking and education for
sustainability. Local Economy, 30(3), pp.305-315.
Arpaci-Dusseau, R.H. and Arpaci-Dusseau, A.C., 2018. Operating systems: Three
easy pieces. Arpaci-Dusseau Books LLC.
Campean, F., Yildirim, U. and Henshall, E., 2018. Synthesis of functional models
from use cases using the system state flow diagram: A nested systems approach. In DS92:
Proceedings of the DESIGN 2018 15th International Design Conference(pp. 2833-2844).
Ching-Yu, C.H.A.I., Chen, C.S., Hu, W.Y. and Kuan, J.F., Taiwan Semiconductor
Manufacturing Co (TSMC) Ltd, 2016. Integrated circuit design system and method of
generating proposed device array layout. U.S. Patent 9,418,200.
Costa, C.H.N., Linhares, A.D.C., Borba, A.D.S., Henriques, D.F., Silva, E.V.P.D.,
Tavares, F.N., Batista, F.M.D.A., Guimarães, H.C.L., Martins, L.C., Monteiro, T.A.F. and
Cruz, A.C.R., 2018. Potential role of dengue virus, chikungunya virus and Zika virus in
neurological diseases. Memórias do Instituto Oswaldo Cruz, 113(11).
de Sousa, T.C., Kelvin, L., Neto, C.D. and de Carvalho, C.G.N., 2017. A Formal
Semantics for Use Case Diagram Via Event-B. JSW, 12(3), pp.189-200.

19HUMAN INTERACTION IN SYSTEM DESIGN
Dones, H.C.L., Womack, M., Alvarellos, J., Bierhaus, E.B., Bottke, W., Hamill, P.,
Nesvorny, D., Robbins, S.J. and Zahnle, K., 2017, June. Ways of Changing the Number and
Size Distribution of Ecliptic Comets. In AAS/Division of Dynamical Astronomy Meeting#
48 (Vol. 48).
Fan, Y., Lin, G. and Tan, H., 2018, April. PDF report automatic generation system
based on JAVA. In Proceedings of the International Conference on Geoinformatics and
Data Analysis(pp. 18-21). ACM.
Fourgeau, E., Gomez, E., Adli, H., Fernandes, C. and Hagege, M., 2016. System
engineering workbench for multi-views systems methodology with 3DEXPERIENCE
Platform. the aircraft radar use case. In Complex Systems Design & Management Asia (pp.
269-270). Springer, Cham.
Freitas, T.K.F.S., Almeida, C.A., Manholer, D.D., Geraldino, H.C.L., de Souza,
M.T.F. and Garcia, J.C., 2018. Review of utilization plant-based coagulants as alternatives to
textile wastewater treatment. In Detox Fashion (pp. 27-79). Springer, Singapore.
Gerengi, H., Mielniczek, M., Gece, G. and Solomon, M.M., 2016. Experimental and
quantum chemical evaluation of 8-hydroxyquinoline as a corrosion inhibitor for copper in 0.1
M HCl. Industrial & Engineering Chemistry Research, 55(36), pp.9614-9624.
Ibrahim, R., Aman, H., Nayak, R. and Jamel, S., 2018. Consistency Check between
XML Schema and Class Diagram for Document Versioning. International Journal on
Advanced Science, Engineering and Information Technology, 8(6), pp.2590-2597.
Jang, W.S., Park, B.K., Son, H.S., Jeon, B.K. and Kim, R.Y.C., 2017, March.
Extracting Test Cases with Message-Sequence Diagram for Validating the Photovoltaic
Energy Integrated Monitoring System. In International Conference on Information Science
and Applications (pp. 603-608). Springer, Singapore.

20HUMAN INTERACTION IN SYSTEM DESIGN
Kini, A., Hegde, G. and Vittal, A.J., 2017. Mapping of use cases to activity diagram
for online grocery management system.
Krainer, D., Ströckl, D.E. and Oberzaucher, J., 2017, June. Use Case Focused User-
Interaction Diagram: A Communication Tool within AAL Projects. In Proceedings of the
10th International Conference on PErvasive Technologies Related to Assistive
Environments (pp. 193-196). ACM.
Li, C., Sun, Y., Djerdj, I., Voepel, P., Sack, C.C., Weller, T., Ellinghaus, R., Sann, J.,
Guo, Y., Smarsly, B.M. and Over, H., 2017. Shape-controlled CeO2 nanoparticles: stability
and activity in the catalyzed HCl oxidation reaction. ACS Catalysis, 7(10), pp.6453-6463.
McKenney, S. and Reeves, T.C., 2018. Conducting educational design research.
Routledge.
Mithun, M. and Jayaraman, S., 2017, September. Comparison of sequence diagram
from execution against design-time state specification. In 2017 International Conference on
Advances in Computing, Communications and Informatics (ICACCI) (pp. 1387-1392). IEEE.
O'Neil, H.C.L., Prowse, T.D., Bonsal, B.R. and Dibike, Y.B., 2017. Spatial and
temporal characteristics in streamflow-related hydroclimatic variables over western Canada.
Part 2: future projections. Hydrology Research, 48(4), pp.932-944.
Sabharwal, S., Kaur, P. and Sibal, R., 2017. Empirical and Theoretical Validation of a
Use Case Diagram Complexity Metric. Int. Assoc. of, pp.35-47.
Saha, S.K., Dutta, A., Ghosh, P., Sukul, D. and Banerjee, P., 2016. Novel Schiff-base
molecules as efficient corrosion inhibitors for mild steel surface in 1 M HCl medium:
experimental and theoretical approach. Physical Chemistry Chemical Physics, 18(27),
pp.17898-17911.

21HUMAN INTERACTION IN SYSTEM DESIGN
Salman, Y.D. and Hashim, N.L., 2016. Automatic test case generation from UML
state chart diagram: a survey. In Advanced Computer and Communication Engineering
Technology (pp. 123-134). Springer, Cham.
Schäper, S., Yau, H.C., Krol, E., Skotnicka, D., Heimerl, T., Gray, J., Kaever, V.,
Søgaard-Andersen, L., Vollmer, W. and Becker, A., 2018. Seven-transmembrane receptor
protein RgsP and cell wall-binding protein RgsM promote unipolar growth in
Rhizobiales. PLoS genetics, 14(8), p.e1007594.
Sharifabadi, K., Harnefors, L., Nee, H.P., Norrga, S. and Teodorescu, R.,
2016. Design, control, and application of modular multilevel converters for HVDC
transmission systems. John Wiley & Sons.
Singh, M., Sharma, A.K. and Saxena, R., 2016. Formal Transformation of UML
Diagram: Use Case, Class, Sequence Diagram with Z Notation for Representing the Static
and Dynamic Perspectives of System. In Proceedings of International Conference on ICT for
Sustainable Development(pp. 25-38). Springer, Singapore.
Tan, J.H., Tan, H.C.L., Ng, Z.Q. and Ramli, N., 2018. A Rare Association of Small
Bowel Atresia and In-Utero Midgut Volvulus Presenting as Fetal Meconium
Pseudocyst. Journal of Neonatal Surgery, 7(4), p.48.
Torre, D., Labiche, Y., Genero, M., Baldassarre, M.T. and Elaasar, M., 2018, May.
UML diagram synthesis techniques: a systematic mapping study. In 2018 IEEE/ACM 10th
International Workshop on Modelling in Software Engineering (MiSE) (pp. 33-40). IEEE.
Vemuri, S., Chala, S. and Fathi, M., 2017, April. Automated use case diagram
generation from textual user requirement documents. In 2017 IEEE 30th Canadian
Conference on Electrical and Computer Engineering (CCECE) (pp. 1-4). IEEE.

22HUMAN INTERACTION IN SYSTEM DESIGN
Venturini, P.R., Thomazini, B.F., Oliveira, C.A., Alves, A.A., Camargo, T.F.,
Domingues, C.E., Barbosa-Sampaio, H.C. and do Amaral, M.E.C., 2018. Vitamin E
supplementation and caloric restriction promotes regulation of insulin secretion and glycemic
homeostasis by different mechanisms in rats. Biochemistry and Cell Biology, 96(6), pp.777-
785.
Vezzoli, C., Kohtala, C., Srinivasan, A., Xin, L., Fusakul, M., Sateesh, D. and Diehl,
J.C., 2017. Product-service system design for sustainability. Routledge.
Welstead, J. and Felder, J.L., 2016. Conceptual design of a single-aisle turboelectric
commercial transport with fuselage boundary layer ingestion. In 54th AIAA Aerospace
Sciences Meeting (p. 1027).
Yang, Y., Wang, H., Sangwongwanich, A. and Blaabjerg, F., 2018. Design for
reliability of power electronic systems. In Power Electronics Handbook (pp. 1423-1440).
Butterworth-Heinemann.

23HUMAN INTERACTION IN SYSTEM DESIGN