Table 1 Comparison of current methodologies and IAM-ICT methodology, and impact on its effectiveness in the implementation of innovative ICTs

ESA standard

◦ General methodology that includes practices and guidelines for the phases of software development including transfer, operations and maintenance and prototyping concept.

[28]

◦ IAM-ICT specifies the tools to be used in each of these development phases except for transfer, operations and maintenance phases.

◦ It includes the prioritisation of the acceptance barriers. Co-creation is used to resolve implementation barriers.

Agile methodology

◦ Flexible method allowing frequent and regular software releases.

◦ Includes agile methods giving general ideas of what to be done.

[29]

◦ IAM-ICT defines the methods to be used in the requirements gathering phase.

◦ Prioritisation of barriers in the design phase.

◦ Co-creation is used to resolve implementation barriers.

Vienna development method (VDM)

◦ Used for the detection of errors and improvement of requirements. Allows the analysis of designs and identification of defects at an early stage of system development.

[30]

◦ IAM-ICT addresses market needs within a specific scope and prioritises barriers in the design phase.

◦ Co-creation is used to resolve implementation barriers.

Fuzzy clustering

◦ Method to hierarchize a set of objects and identify modules .

[8]

◦ IAM-ICT includes the prioritisation of the acceptance barriers and how they can be overcome using co-creation methods.

Voice of the customer (VOC)

◦ Method to gather customer needs as to how they use the product, through interviews, surveys, etc.

[8]

◦ IAM-ICT includes: the selection of the most appropriate elicitation technique, the consideration of cost benefit analysis, prototyping, and the prioritisation of implementation barriers.

Design structure matrix (DSM)

◦ Used to represent activity dependencies.

◦ Allows the formation of clusters that indicate possible modules.

[8]

◦ IAM-ICT includes the design of the modules and the development of a prototype, the selection of the most appropriate elicitation technique, UDI techniques to gather requirements and implementation barriers, the consideration of cost benefit analysis, and the prioritisation of implementation barriers.

Modular function deployment (MFD)

◦ Manages data efficiently and performs numerical or statistical analyses (with qualitative and quantitative data).

◦ Allows the formation and definition of clusters.

[8]

◦ IAM-ICT methodology includes an additional phase for the analysis and prioritisation of implementation barriers; using co-creation to resolve them.