19SafQB

8.1 Introduction 281
will in the tables below present a summary of the challenges for technical and
semantic interoperability.
IoT Technical Interoperability Challenges/Requirements
Requirement(s)
Rationale & Remarks
Best practices awareness
• Avoid spreading effort in
• Coordinate worldwide interoperability initiatives
on market support specifications or protocols
addressing interoperability • Develop market acceptance roadmap
for worldwide protocols • Use clear specifications development and testing
methodologies leading to improve quality while
reducing time and costs in a full chain optimized
development cycle
• Define if needed profiles to improve interoperability
Validation of specifications
• Reduce ambiguities in specifications
and development
time
Tests specifications
• Provide market accepted test
specifications ensuring minimum
accepted level of interoperability
Tools and validation programmes
• Develop market accepted
and affordable test tools used
in market accepted validation
programmes
• Specifications development time could be too
long
• Ambiguities in specifications could lead to major
non interoperability issues
• Quality, time and cost factors lead to the needs
of models and automation
• No test specifications lead inevitably to different
specifications implementation and interoperability
issues
• Development test specifications is often too
expensive for limited set of stake holders and
effort should be collectively shared
• Tools processing and automation are only way to
reduce time and market (e.g. use of MBT)
• Development of test tools are expensive
• Available test tools developed spontaneously by
market forces can have test scopes overlapping
and even not answering to all tests needs.
• Full chain of specifications to tool development
not considered
• Providing final confidence to end users with consistent
tests not always considered
The following table/ lists summarize the main requirements associated
with the development of the IoT service(s)/application(s) in reference to