SaaS Process Extension Verification Framework
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current SaaS enterprise systems lack the capability to effectively constrain and validate the behavior of process extensions, which is crucial for maintaining the integrity and stability of the platform, especially when multiple customers share the same SaaS platform.
Innovation Solution
A SaaS reference process extension verification framework is introduced, utilizing a process extension constraint definition language based on temporal logic and model-checking principles, which allows for the annotation of extension points with constraints and validation of user-customized behavior against these constraints, ensuring compliance with platform and domain-specific rules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If process extensions are allowed to be plugged into the core process model without constraints, then adaptability and versatility are improved, but reliability and stability deteriorate due to unauthorized modifications and data access issues
Solution Approach 1:
The patent applies preliminary action by pre-defining and annotating extension points with constraints before any extensions are plugged in. The constraint definition language and model-checking algorithms are prepared in advance to automatically verify extension compliance, preventing unauthorized modifications before they occur rather than detecting them after the fact.
Solution Approach 2:
The patent introduces an intermediary verification framework that acts as a mediator between the core process model and user-customized extensions. This framework includes constraint definition languages, model-checking algorithms, and verification engines that automatically check extension compliance, serving as a buffer that allows adaptability while maintaining reliability.
2Reliability
If formal verification methods based on temporal logic and model-checking are implemented, then reliability and stability are improved, but device complexity and ease of operation worsen due to the sophistication of the verification framework
Solution Approach 1:
The patent applies self-service by enabling the system to automatically verify extension compliance without requiring manual intervention from users. The model-checking algorithms and constraint verification engines autonomously check whether extensions satisfy the predefined constraints, eliminating the need for users to understand or manually verify complex temporal logic formulas.
Solution Approach 2:
The patent replaces manual verification processes with automated computational methods. Instead of requiring users to manually check extension compliance against complex constraints, the system uses model-checking algorithms and automated verification engines that computationally verify compliance, substituting mechanical human verification with automated computational verification.
3Manufacturing precision
If constraints are annotated at the type level of activities in extension fragments, then manufacturing precision and measurement precision are improved, but ease of manufacture and device complexity worsen
Solution Approach 1:
The patent applies self-service by automatically generating and verifying constraint compliance at the type level without requiring manual annotation by extension developers. The system automatically checks whether extension activities satisfy the predefined constraints based on their types, eliminating the need for developers to manually specify or verify complex constraint relationships.
Solution Approach 2:
The patent applies preliminary action by pre-defining constraints at the type level of activities before extensions are developed. This allows the verification framework to automatically check compliance based on activity types rather than requiring detailed manual specification during extension development, simplifying the extension creation process while maintaining precision.
Data Source
AI summary
The disclosure describes methods, software, and systems, including a method for providing extension points for core process models. Extension points are provided for a core process model associated with a core process. The extension points are pre-defined and annotated with constraints that specify restricted behavior of extensions plugged into the core process model at the extension points. The extension points are formulated in a process extension constraint definition language and allow a restriction of runtime behavior. The process extension constraint definition language is based on temporal logic and enhances existing property specification patterns with specific support to formulate constraints at an extension task type level for activities included in a process extension. Instructions are received from a user to plug selected extensions into an instance of the core process model. Each selected extension includes user-customized behavior for the extension. The instance of the core process model is validated.