Extending Status Models in Computer Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As software systems become larger and more complex, managing the state of objects to ensure that actions are performed only when allowed by the object's state becomes increasingly burdensome for programmers, as they need to understand and account for multiple constraints across various objects.
Innovation Solution
A status schema model is defined at design-time and stored in a computer-readable medium, comprising a core status schema group and an extended status schema group, which includes preconditions that determine whether actions can be performed by a data object node instance based on its status, allowing for coherent and efficient state management by separating the core and extended status schema groups.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If programmers directly code state requirements into objects themselves, then state management is self-contained and reliable, but programming complexity and burden increase significantly as software projects become larger
Solution Approach 1:
The patent segments state management into two distinct parts: core status schema (defined by object programmers) and extended status schema (defined by other programmers). This segmentation allows each programmer to focus on their own object's state requirements without being burdened by understanding all state constraints across the entire system, thereby reducing programming complexity while maintaining reliability through structured separation of concerns.
Solution Approach 2:
The patent introduces an intermediary mechanism (the status schema system) that mediates between objects and their state constraints. Instead of objects directly encoding all state requirements, the status schema acts as an intermediary layer that manages and enforces state constraints, reducing the burden on individual programmers while ensuring state management reliability.
2Ease of operation
If programmers rely on other objects to enforce state requirements, then programming burden is reduced, but state determination becomes independent of the actual object state
Solution Approach 1:
The patent merges the state determination logic into the status schema instance that is created for each data object node instance. The status management runtime component uses the status schema instance to determine whether actions are allowed based on the actual status of the specific object instance, ensuring that state determination remains accurate and tied to the actual object state while still reducing programming burden through the predefined schema structure.
3Stability of the object's composition
If a unified status schema is used for all objects, then consistency is maintained, but flexibility to customize for specific user requirements is reduced
Solution Approach 1:
The patent segments the status schema into core status schema (providing consistency and stability) and extended status schema (providing customization flexibility). The core status schema ensures uniform state management across all objects, while the extended status schema allows customization for specific user requirements and particular companies or departments, thereby resolving the contradiction between consistency and flexibility.
Solution Approach 2:
The patent creates a universal status schema framework that can serve multiple purposes: the core status schema provides a standardized foundation for all objects, while the extended status schema allows the same framework to be customized for different users, companies, or departments. This multi-functionality enables both consistency and adaptability within a single unified system.
Data Source
AI summary
A design-time status schema model is defined at design-time and includes a core status schema group and an. a status schema model. The status schema model includes a core status schema group and an extended status schema group. The status schema model also includes a precondition included in one of the status schema groups. The precondition identifies how a status affects whether an action included in the other of the status schema groups is to be allowed to be performed at runtime by a data object node instance having the status. Based on a status schema instance, the status of a data object node instance is monitored to determine whether the action is allowed to be performed by the data object node instance. In response to a determination that the action is allowed, enabling the action to be executed.