3.1 Data quality: The degree to which quality characteristics of data have the
intrinsic potential to satisfy stated and implied needs.
3.2 Data Quality Assurance (DQA): A set of processes, that ensures
that shore and shipboard based data used by e-navigation systems meets and complies with
required quality specifications.
3.3 Effectiveness: Measure of accuracy and completeness with which
users achieve specified goals.
3.4 Efficiency: Resources expended in relation to the accuracy and
completeness with which users achieve goals.
3.5 E-navigation: The harmonized collection, integration, exchange,
presentation and analysis of marine information on board and ashore by electronic means
to enhance berth-to-berth navigation and related services for safety and security at sea
and protection of the marine environment.
3.6 Human factors: The scientific discipline concerned with the
application of validated scientific research about people, their abilities,
characteristics and limitations to the design of systems they use, environments in which
they function and interact, and jobs they perform to optimize human well-being and
overall system performance.
3.7 Human-Centred Design (HCD)footnote: An approach to system design and
development that aims to make interactive systems more usable by focussing on the use of
the system; applying human factors, ergonomics and usability knowledge and techniques.
3.8 Product quality: The degree to which a product or system meets
functional suitability, performance efficiency, compatibility, usability, reliability,
security, maintainability and portability as defined by ISO/IEC 25010 or relevant
standards. The overall product quality is a result of quality of hardware, software and
data.
3.9 Satisfaction: Freedom from discomfort along with positive
attitudes towards the use of the system.
3.10 Socio-technical system: A system that includes interaction
between people, technology (i.e. equipment and systems) and their physical and
organizational environments.
3.11 Software quality: The degree to which a software product (system,
component or process) meets specified requirements with the aim of also meeting
stakeholder expectations.
3.12 Software Quality Assurance (SQA): A set of processes that ensures
software meets and complies with required quality specifications. Designated SQA
processes align with a system design life cycle.
3.13 Software quality evaluation: A systematic examination of the
extent to which a software product is capable of satisfying stated and implied needs.
3.14 Software quality in use: Capability of a software product to
enable specific users to achieve specific goals with effectiveness, productivity, safety
and satisfaction in specific contexts of use.
3.15 Stakeholder: An individual or organization having a right, share,
claim or interest in a system.
3.16 System: Combination of interacting elements organized to achieve
one or more stated purposes. A system can consist of products (tools used to achieve a
specific task), equipment, services and/or people.
3.17 System life cycle (Life cycle): The stages containing the
processes activities and tasks spanning the life of the system and/or product from the
definition of its requirements to the termination of its use; life cycle covers its
conception, design, operation, maintenance, support and disposal.
3.18 Usability: The extent to which systems can be used by users to
achieve specified goals with effectiveness, efficiency and satisfaction, in a specified
context of use.
3.19 Usability Testing (UT): Evaluation methods and techniques used to
support Human-Centred Design (HCD) and used for the purpose of increasing the usability
of a system.
3.20 User: Anyone interacting with the system, including its operators
and maintainers.