UML Stereotype Automation for Requirements Traceability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
When modeling requirements management tool elements in a UML-based modeler, the characteristics such as nesting and traceability relationships, along with stereotype designations, are not preserved, leading to inefficiencies and quality issues like inconsistent stereotype usage and loss of traceability.
Innovation Solution
A method that involves obtaining the requirement type and associated stereotype of a requirements management tool element, and automatically applying the stereotype to the UML element during instantiation, ensuring that the nested structure and traceability relationships are preserved in the UML model.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If requirements management tool elements are modeled in a UML-based modeler using standard UML metamodel, then the modeling can be performed in a standardized environment, but the model element characteristics such as nesting and traceability relationships are lost
Solution Approach 1:
The patent applies preliminary action by pre-defining stereotypes in the UML profile that encode nesting and traceability relationship characteristics before the modeling process begins. When requirements management tool elements are instantiated in the UML-based modeler, these pre-configured stereotypes automatically preserve the relationship characteristics without requiring manual recreation, thus preventing information loss while maintaining UML standard compatibility.
Solution Approach 2:
The patent uses stereotypes as an intermediary mechanism between the requirements management tool elements and the UML metamodel. The stereotypes act as a bridge that translates and preserves the specific characteristics (nesting and traceability relationships) of requirements management elements while fitting them into the standard UML framework, thereby maintaining both adaptability and information integrity.
2Manufacturing precision
If stereotypes are manually applied to UML elements to represent requirements management tool elements, then the proper extension can be achieved, but significant effort is required and productivity decreases
Solution Approach 1:
The patent implements self-service by enabling automatic stereotype application through the imported UML profile. When requirements management tool elements are instantiated in the UML-based modeler, the system automatically determines and applies the appropriate stereotypes based on the element type, eliminating the need for manual stereotype assignment. This automation maintains manufacturing precision while significantly improving productivity.
Solution Approach 2:
The patent applies preliminary action by pre-configuring the mapping between requirements management tool element types and corresponding stereotypes in the UML profile before the modeling process begins. This pre-configuration enables the system to automatically apply the correct stereotypes during instantiation without requiring manual intervention, thus achieving both accuracy and high productivity.
3Ease of manufacture
If requirements management tool elements are instantiated without preserving characteristics, then the instantiation process is simple, but inconsistent stereotype usage and traceability loss occur
Solution Approach 1:
The patent uses stereotypes as an intermediary that automatically preserves relationship characteristics during instantiation. The stereotype mechanism acts as a mediator that maintains consistency in stereotype usage and traceability relationships while keeping the instantiation process simple, as the preservation happens automatically through the stereotype application rather than requiring complex manual processes.
Solution Approach 2:
The patent applies preliminary action by pre-defining the stereotype characteristics and relationship rules in the UML profile before instantiation. This pre-configuration ensures that when elements are instantiated, the correct stereotypes and relationships are automatically applied, maintaining reliability without complicating the instantiation process itself.
Data Source
AI summary
Model element characteristic preservation is provided when instantiating unified modeling language elements of a unified modeling language model. Requirements management tool elements become associated with a stereotype via, for instance, user assignment of the stereotype to a requirements type of the requirements management project. A stereotype assignment is obtained for a requirements management tool element, and the stereotype is automatically applied when instantiating a UML element representative of the requirements management tool element. Nesting and traceability relationships between the requirements management tool element and other requirements management tool elements are additionally preserved.