2.1 The scope of this guideline is to provide an overarching document to
ensure that e-navigation quality design attributes are included in the development of
e-navigation systems. Figure 1 provides an overview of the quality design attributes
that should be considered and includes "product and data quality", "meet user needs",
"security" and "functional safety". This guideline mainly addresses software quality,
which incorporates "product and data quality" and "meet user needs". Consideration of
all the design attributes will help ensure that software and human-based risks are
addressed. Figure 1 also provides information on relevant standards that developers and
designers of e-navigation systems should consider in ensuring all quality attributes are
addressed ensuring overall system quality.
Figure 1: Concepts and standards for e-navigation quality design
attributes
2.2 This guideline is intended to be used by all stakeholders involved in the design and
development of e-navigation systems, with its primary users being those who develop and
test e-navigation systems. Stakeholders include equipment designers and manufacturers,
system integrators, maritime authorities and regulators, shipbuilders, shipowners, ship
operators, Vessel Traffic Service authorities and Rescue Coordination Centres, and other
relevant international organizations such as the International Association of Marine
Aids to Navigation and Lighthouse Authorities (IALA) and the International Hydrographic
Organization (IHO).
2.3 Table 1 provides a summary of stakeholder involvement in the application of this
guideline at each stage of the e-navigation system's life cycle.
Table 1: Stakeholder involvement
| Life cycle Stage
|
Stakeholder
|
| Analysis Operational System Feedback
|
Manufacturers/system designers, users,
shipowners, ship operators, regulatory authority
|
| Stage 1: Concept development
|
Manufacturers/system designers, users
|
| Stage 2: Planning and Analysis
|
Manufacturers/system designers, users
|
| Stage 3: Design
|
Manufacturers/system designers, users
|
| Stage 4: Integration and Testing
|
Manufacturers/system designers, users, approval
authority (regulator), shipowners, ship operators
|
| Stage 5: Operational
|
Users, shipowners, ship operators and
manufacturers/system designers
|
| Disposal
|
Shipowners, ship operators and
manufacturers/system designers
|
2.4 The provisions in this guideline are goal-based and are not intended to specify or
discourage the use of any particular quality assurance, management process, or testing
method. Hence, detailed and prescriptive design requirements, which specify design
solutions, are not covered.
2.5 It is recommended that users of this guideline be generally familiar with
contemporary quality management processes, software quality assurance and human
factors.
2.6 This guideline does not address training requirements.