Compliance Checking for Architectural Software Models
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As software systems grow in complexity, maintaining the consistency and traceability between analysis and design models becomes challenging, leading to issues with risk analysis, requirement management, and project planning, especially in large projects with numerous tasks and fine-grained details.
Innovation Solution
A method and system for checking compliance between architectural analysis and design models, involving the creation of a directed graph for use cases, automatic tree formation, relationship deletion, cycle detection, and semiautomated conversion of analysis models to design models, with cross-model verification and hyperlinks for traceability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If analysis models become large with fine-grained details to capture real-world project complexity, then the model's ability to represent detailed requirements improves, but traceability and consistency between analysis and design models deteriorate
Solution Approach 1:
The patent segments the analysis model into hierarchical packages and groups, organizing fine-grained details into structured containers. This segmentation allows detailed requirements to be captured while maintaining overview control through the hierarchical structure, preventing traceability loss despite model complexity
Solution Approach 2:
The patent introduces an automated modeling rule engine as an intermediary between analysis and design models. This intermediary automatically checks compliance, enforces constraints, and maintains traceability relationships, preventing information loss while allowing detailed modeling
2Reliability
If the analysis model includes many fine-grained tasks and details for large projects, then the completeness of requirement coverage improves, but the complexity of maintaining consistency with design models increases
Solution Approach 1:
The patent implements self-service through automated compliance checking and constraint enforcement. The modeling rule engine automatically validates the analysis model against predefined rules, ensuring completeness and consistency without requiring manual intervention, thereby reducing management complexity while maintaining high reliability
Solution Approach 2:
The patent establishes feedback loops where the automated rule engine continuously monitors the analysis model for compliance with constraints and traceability requirements. This feedback mechanism automatically identifies and reports inconsistencies, enabling timely correction while maintaining requirement coverage completeness
3Adaptability or versatility
If manual methods are used to maintain analysis and design model consistency, then flexibility in model modification is preserved, but time consumption and cost increase
Solution Approach 1:
The patent applies preliminary action by pre-defining modeling rules, constraints, and compliance criteria before the analysis and design process begins. This preliminary setup enables automated enforcement during model development, maintaining flexibility while reducing time consumption through automation rather than manual synchronization
Data Source
AI summary
A method for extracting requirements of an architectural software model comprises providing a use case model as a directed graph of the architectural software model comprising nodes corresponding to use cases and relations between nodes, and creating, automatically, a tree comprising a root node corresponding to an abstract use case and at least one leaf node corresponding to one of an abstract use case and a concrete use case.