The working of the device through the interface
The devices for which the interface is made are drone jamming, man-portable systems
named “Chimera 200” and “Dexter 20”. These systems are capable of detecting a drone
and also jamming it, within a range of 1.5 km in all directions.
The speci cations of the buttons of the device are given below, along with the interface
designs attached as reference. Since the platform itself are not available, an evaluation on
graphical equivalent of the interface has to be done. The interfaces are known as D20UI
and C200UI for Dexter 20 and Chimera 200 interfaces, respectively.
The device features several buttons, each with a distinct function, arranged in a speci c
sequence, as shown in the gure below. Here’s a detailed overview of their roles:
1. Power Button:
The device is powered on by pressing the power button. This is the rst step to start any
operation of the device.
2. Antenna Selection (ANT Button):
The antenna used by the device is chosen using the ANT button. Users can select
between two antenna options:
ANT 1,ANT 2 for D20UI and A1,A2 for C200UI.
3. Mode Selection (MODE Button):
fi
fi
fi
fi
The MODE button controls the operating mode of the device. There are four available
modes:
i). Detection ii). Auto Jam
iii). Custom iv). Forced Jam
4. Con guration Con rmation (CONFIRM/VALID Buttons):
After selecting the desired antenna and mode, the con guration must be con rmed. This
is done using:
CONFIRM button for D20UI and VALID button for C200UI.
Pressing either button nalizes the current settings and prepares the device for operation.
5. Device Lights Control:
The device’s lighting can be toggled using:
The light icon button on D20UI and the LIGHT OFF button on C200UI.
This feature allows the user to turn the device lights on or off as needed, which can be
useful in various operational environments.
Besides the buttons, there are STATUS, BATTERY and JAMMING indicators, showing the
overall status of the device, battery level and the jamming status.
Operational Sequence:
The standard order for operating the device is:
Select the antenna (ANT) ———> Choose the mode (MODE) ———> Con rm the
con guration (CONFIRM/VALID)
This sequence may be repeated as many times as necessary, depending on the user’s
preferences or operational requirements (for example, we again want to change the ANT,
then we have to press ANT, then if we don’t want to change MODE, go directly to
CONFIRM/VALID).
fi
fi
fi
fi
fi
fi
fi
Based on the above operation sequence, please answer each of the questions that follow
in a simple YES/NO —— (Y/N). Write NA for cases where a Y/N answer cannot be given.
H1 - Visibility and system state
• Does the application include a visible title page, section or site?
• Does the user always know where it is located?
• Does the user always know what the system or application is doing?
• Are the links clearly de ned?
• Can all actions be visualised directly? (No other actions are required)
H2 - Connection between system and real world, metaphor usage, human objects
• Does information appear in a logical order for the user?
• Does the design of the icons correspond to everyday objects?
• Does every icon do the action that you expect?
• Does the system use phrases and concepts familiar to the user?
H3 - User control and freedom
• Is there a link to come back to initial state or homepage?
• Are the functions “undo” and “re-do” implemented?
• Is it easy to come back to an earlier state of the application?
H4 - Consistency and standards
• Do link labels have the same names as their destinations?
• Do the same actions always have the same results?
• Do the icons have the same meaning everywhere?
• Is the information displayed consistently on every page?
• Are the colours of the links standard? If not, are they suitable for its use?
• Do navigation elements follow the standards? (Buttons, check box,…)
H5 - Recognition rather than memory, learning and anticipation
• Is it easy to use the system for the rst time?
• Is it easy to locate information that has already been searched for before?
• Can you use the system at all times without remembering previous screens?
• Is all content needed for navigation or task found in the “current screen”?
• Is the information organised according to logic familiar to the end user?
fi
fi
H6 - Flexibility and ef ciency of use
• Are there keyboard shortcuts for common actions?
• If there are, is it clear how to use them?
• Is it possible to easily perform an action done earlier?
• Does the design adapt to the changes of screen resolution?
• Is the use of accelerators visible to the normal user?
• Does it always keep the user busy? (without unnecessary delays)
H7 - Help users recognise, diagnose and recover from errors
• Does it display a message before taking irreversible actions?
• Are errors shown in real time?
• Is the error message that appears easily interpretable?
• Is some code also used to reference the error?
H8 - Error prevention
• Does a con rmation message appear before taking the action?
• Is it clear what information needs to be entered in each box on a form?
• Does the search engine tolerate typos and spelling errors?
H9 - Aesthetic and minimalist design
• Is used a design without redundancy of information?
• Is the information short, concise and accurate?
• Is each item of information different from the rest and not confused?
• Is the text well organised, with short sentences and quick to interpret?
H10 - Help and documentation
• Is there the “help” option?
• If so, is it visible and easy to access?
• Is the help section aimed at solving problems?
• Is there a section of frequently asked questions (FAQ)?
• Is the help documentation clear, with examples?
H11 - Save the state and protect the work
• Can users continue from a previous state (where they had previously been or from
another device)?
• Is “Autosave” implemented?
fi
fi
• Does the system have a good response to external failures? (Power cut, internet not
working, etc)
H12 - Colour and readability
• Do the fonts have an adequate size?
• Do the fonts use colours with suf cient contrast with the background?
• Do background images or patterns allow the content to be read?
• Does it consider people with reduced vision?
H13 - Autonomy
• Does it keep the user informed of system status?
• Moreover, is the system status visible and updated?
• Can the user take their own decisions? (Personalisation)
H14 - Defaults
• Does the system or device give the option to return to factory settings?
• If so, does it clearly indicate the consequences of the action?
• Is the term “Default” used?
H15 - Latency reduction
• Is the execution of heavy work transparent to the user?
• While running heavy tasks, is remaining time or some animation shown?
fi
