4.1 It is recommended that SQA, HCD and associated activities are performed using a
quality management system such as ISO/IEC 90003 or relevant standards to ensure that
quality requirements are embedded in the development life cycle process in order to
achieve software quality, meet user needs and enhance safety of e-navigation systems.
4.2 This guideline can be applied to the design of systems with varying
levels of complexity, regardless of whether a new system is being developed or an
existing system is being modified.
Figure 2: Generic life cycle
4.3 Figure 2 shows a typical generic life cycle
footnote with the stages recommended as a minimum for
the application of this guideline to the development of e-navigation systems:
-
.1 Analysis of operational system feedback;
-
.2 Stage 1: Concept development;
-
.3 Stage 2: Planning and analysis;
-
.4 Stage 3: Design;
-
.5 Stage 4: Integration and testing;
-
.6 Stage 5: Operation; and
-
.7 Disposal.
4.4 The aim of SQA, HCD and associated UT activities is to ensure that for each
stakeholder, user and task requirements are considered in the development process. This
takes into account interactions between people, technology and the physical and
organizational environments within which they work. Outcomes can be maximized if SQA,
HCD and associated activities are applied by teams with relevant multidisciplinary
skills and experiences.
4.5 SQA and HCD are performance- and risk-based processes. Hazards are identified,
associated risks assessed and, if necessary, risk reduction and control measures are
implemented to ensure an acceptable level of quality, usability and safety. Because they
are performance-based processes, validation is based on how the outcomes are
achieved.