Source-linked AI summary
Ontology-supported Design Parameter Management for Change Impact Analysis
Jan Novacek, Ali Ahari, Alessandro Cornaglia, Frederik Haxel, Alexander Viehl, Oliver Bringmann, Wolfgang Rosenstiel
TL;DR
Engineering requirements change in ways whose consequences are difficult to foresee, while operative relationships among design parameters are often unknown. The paper proposes an ontology-based, knowledge-supported approach integrating heterogeneous models, requirements traceability, and Mission Profile Aware Design. Two use cases demonstrate identifying affected parameters and deriving lower-level real-time requirements.
Problem
Requirement changes can have unforeseen consequences, while unknown operative relationships and heterogeneous models complicate Change Impact Analysis.
Method
The approach integrates heterogeneous data through ontology-based system models, OWL representations, trace links, expert knowledge, and Mission Profile Aware Design.
Results
Two use cases demonstrate the approach: detecting affected design parameters after a frequency change and deriving a memory write-latency requirement from real-time processing requirements.
Takeaways & Limitations
The approach supports decision-making by connecting requirements with design parameters and using formalized knowledge for system-model reasoning.
Abstract
from arXiv · showhide
This paper presents an ontology-supported approach to the management of design parameters in engineering. This approach aims specifically at enabling Change Impact Analysis through Requirements Traceability and acquainted expert knowledge of design parameters. The approach is suitable for both software and hardware designs. The activities and features are mainly obtained by (1) the application of an ontology-based universal system modeling procedure proposal for model integration, (2) the utilization of a knowledge base for capturing expert knowledge and (3) a semantic Mission Profile Aware Design platform. OWL is used to represent information and the underlying data model can improve knowledge transfer among heterogeneous systems which are common in complex engineering projects. At the same time, effort to perform reasoning on such models can be reduced. A demonstration and hands-on description of two illustrative use cases complements the paper.
I. INTRODUCTION
The paper addresses Change Impact Analysis for evolving requirements by linking requirements, design parameters, and expert knowledge across heterogeneous engineering models. Its ontology-based approach supports traceability, reasoning, and decision-making, with Mission Profile Aware Design included.
- Changing requirements can create unforeseen consequences, making monitoring, traceability, and Change Management mechanisms necessary, especially in safety-critical development.
- The approach formalizes design-parameter knowledge for reasoning on system models and incorporates Mission Profiles to enable Mission Profile Aware Design.Supported model operations include validation, transformation, and exchange.
- Because operative relationships are often unknown, requirement changes may cause undesired side effects or ripple effects and make Change Impact Analysis complex and effort-intensive.
- The system aims to identify which design parameters are affected when a requirement changes by integrating heterogeneous data sources.
- The claimed benefits include fewer errors, lower Change Impact Analysis costs, and improved understanding of designs and requirement–parameter relations.
- The approach integrates heterogeneous data sources through an ontology-based system model and represents links between design parameters, requirements, and traceability information.OWL and Linked Data principles support sharing and processing of system models.
II. BACKGROUND AND RELATED WORK
The background situates the approach within Mission Profile Aware Design, knowledge-based systems, and ontology-supported systems engineering. Prior work provides related modeling and integration ideas, but the cited approaches differ in their support for MPAD or Change Impact Analysis.
- Mission Profiles capture environmental conditions and stress factors across a component’s life cycle, including usage, environmental profiles, requirements, and stress-test scenarios.
- Mission Profile Aware Design remains largely manual in prior work, motivating tool support for easier adoption and automation.
- Prior research reduced Mission Profile stressors to effective stress level and effective stress time, with experiments fitting theoretical predictions within statistical variations.
- Knowledge-based systems explicitly represent domain knowledge and exploit it through reasoning mechanisms.
- Existing systems-engineering ontology work models processes or integrates disciplinary data, but cited approaches do not directly support MPAD or implement Change Impact Analysis.
D. Ontologies in Requirements Engineering
The paper situates its ontology-based approach within requirements engineering, where ontologies formalize requirements, domain knowledge, and relationships for traceability and reasoning. It addresses the limitation that many CIA approaches focus on functional changes, while this approach covers functional and non-functional changes.
- Ontologies have been used to represent requirements specifications, application-domain knowledge, and requirements consistency and completeness.
- Most ontology applications in requirements engineering focus on functional requirements, whereas this approach also handles non-functional requirements.
- The approach uses ontologies to represent relationships among requirements and machine-readable metadata that can support reasoning.
- Requirements represented in ReqIF may be formalized or non-formalized, but abstract descriptions must first be lifted into ontological representations for processing.
- The paper focuses on establishing a foundation for semantic enrichment rather than on the lifting process itself.
- Unlike many CIA approaches centered on functional changes, this approach analyzes overall system impact across functional and non-functional changes.
III. APPROACH
The approach integrates expert knowledge, requirements, and mission-profile data through ontological representations and links between design parameters and requirements. Once established, the system model supports graph-based identification of parameters affected by changes.
- III. APPROACH: The approach lifts expert knowledge and requirements documents into ontologies, then inserts links between design parameters and requirements semi-automatically.
- III. APPROACH: Standard graph analysis identifies affected parameters by collecting nodes on paths from a root node to leaf nodes after the system model and requirement links are established.
- III. APPROACH: The semantic MPAD platform is intended for use in other settings beyond the presented system.
- III. APPROACH: The approach uses a semantic Mission Profile Aware Design platform to support Change Impact Analysis across heterogeneous data sources.
1) Architecture and implementation:
The architecture combines a Mission Profile Framework, an extensible semantic platform, and an OWL-based system model. These components integrate mission profiles and requirements while representing relationships among systems, components, functions, design parameters, and requirements.
- Architecture and implementation: The Mission Profile Framework manages mission-profile documents, while the platform implements specialized Mission Profile Aware Design tasks.
- Architecture and implementation: Input documents are mapped into ontological representations that can define relationships between objects and support semantic processing.
- Architecture and implementation: The platform can recognize changes in ontological requirements specifications and automatically react or trigger actions based on change type.
- Architecture and implementation: A RESTful API and web-based interface provide access to platform features and allow custom client applications to perform additional tasks.
- Architecture and implementation: The OWL system model represents relationships between components, functions, design parameters, Mission Profiles, systems, and requirements.
- Architecture and implementation: The general approach lifts expert parameter relationships and requirements into ontologies, links them, determines affected parameters, and passes relevant mission-profile data to the analyst.
1) Supporting Change Impact Analysis:
Change Impact Analysis is enabled by representing relationships between requirements and design parameters as Trace Links in the system model. The approach proposes semi-automatic link collection in which users accept or decline suggested candidates.
- Supporting Change Impact Analysis: Trace Links connect requirements and design parameters in the system model, providing the primary mechanism for Change Impact Analysis.
- Supporting Change Impact Analysis: A semi-automatic procedure suggests candidate links to users, who can accept or decline them.
- Supporting Change Impact Analysis: The system model supports Requirements Traceability by inserting Trace Links between requirements and design parameters.
3) Integrating Mission Profiles:
Mission Profile data is integrated into the system model through links to component and document representations, enabling queries over specific mission-profile data portions.
- Mission Profile data is integrated by linking components with mission-profile document representations in the system model.
- Ontological mission-profile document representations can be queried for specific data portions.
- The link-suggestion procedure tokenizes requirements and parameters, applies part-of-speech tagging, and identifies token lemmas before comparing nouns.
- When noun lemmas have symmetric relationships, the procedure adds a link suggestion between the requirement and parameter.
D. Linking requirements to design parameters
The approach represents requirements, design parameters, and their links as ontology-based resources, choosing link individuals because they can carry additional information more easily.
- Design parameters are linked to corresponding requirements so gathered expert knowledge about operative relationships can be used.
- The system supports both manual link specification and semi-automatic link suggestions for users.
- Requirements and design parameters are represented as resources in an RDF data model, with links connecting them through predicates.
- Links can be represented indirectly through link individuals or directly through a relationship between requirement and parameter instances.
- The approach uses link individuals because adding information to a link is easier in that representation.
2) Suggestion of links:
The system suggests requirement–parameter links using natural-language processing and WordNet noun-synonym relationships, while the evaluation describes two illustrative use cases.
- 2) Suggestion of links:: Users can accept or decline link candidates suggested from natural-language requirement and design-parameter descriptions.
- 2) Suggestion of links:: The link-suggestion method uses Stanford CoreNLP for natural-language processing tasks.
- 2) Suggestion of links:: WordNet identifies related noun synonyms to generate candidate links between requirements and design parameters.
- 2) Suggestion of links:: The paper demonstrates the approach in two use cases: power-consumption analysis and transformation of real-time requirements into technology-level requirements.
A. Capturing expert knowledge
CTEF captures expert knowledge about parameter relationships, exports it for ontology-based integration and reasoning, and supports a power-consumption use case whose change analysis identifies affected parameters.
- A. Capturing expert knowledge: CTEF captures expert knowledge about operative relationships between design parameters in a centralized, loosely coupled server–client framework.
- A. Capturing expert knowledge: Its Dependency Matching Graph stores parameter specifications and dependencies, including relationships that can span providers in a supply chain.
- A. Capturing expert knowledge: CTEF exports captured information in RDF/XML, providing an interface to knowledge bases and supporting semantic enrichment and OWL-based reasoning.
- B. Use case: Power consumption: The TAMTAMS use case models power consumption through hierarchical low- and high-level parameters and explicitly specifies their dependencies using CTEF.
- B. Use case: Power consumption: After a system-frequency requirement changes, the system resolves affected requirements and identifies the affected design parameters through ontology-connected operative relationships.
- B. Use case: Power consumption: The reported affected parameters include frequency, ibtb, ion, mobility, vth, sce, qme, pde, dibl, capacitance, and resistance.
C. Use case: Real-time application
The real-time use case translates a frame-processing requirement into a memory write-latency constraint and links that requirement to corresponding design parameters. A learned performance model estimates that, at 600 MHz, write latency must not exceed 31 cycles.
- The traffic sign recognition application processes 24 frames per second, imposing a 42 ms processing requirement per frame.
- A machine-learning model maps performance counters and main-memory write latency to single-frame processing time.The model was trained using benchmarks measuring cache misses, predictable branches, and data read accesses on an ARM-based Zynq-7000 platform.
- 31 cycles is the maximum write latency at 600 MHz for meeting the 42 ms-per-frame processing requirement.
- The proposed system links the real-time requirement to corresponding design parameters and supports specifying dependencies between requirements.
- The approach remains limited by its expectation that inputs use natural-language representations, with ontology mapping or entity matching identified as an improvement for practical applicability.
- Further research could use reasoning to check consistency or identify links, while lifting natural-language requirements to formal specifications remains a prerequisite.