Governance Functional Profile
Governance.
Workflow models.
A workflow capability is deemed required to manage curation workflows and governance workflows.
This Functional Profile includes, but is not limited to, the following capability elaborations:
Derived From Requirements
- Gap Analysis::Workflow::000 - Provide support for Curation Workflow Activities Provide support for Curation Workflow Activities
- Gap Analysis::Workflow::015 - Authoring tools should automate the construction of workflows Provide a means to visualize the models that have been loaded into the KR. The UML Model Browser displays the granular details of a model in list format, but there isn't away to visualize and navigate the whole model. The grid portal provides this feature from the metadata, there should be a way to do this when viewing models in the KR. This would enhance a potential new user’s ability to determine if they can use all or part of a model.
- Gap Analysis::Workflow::016 - Semantics describing workflows will be needed Provide a means to visualize the models that have been loaded into the KR. The UML Model Browser displays the granular details of a model in list format, but there isn't away to visualize and navigate the whole model. The grid portal provides this feature from the metadata, there should be a way to do this when viewing models in the KR. This would enhance a potential new user’s ability to determine if they can use all or part of a model.
- Gap Analysis::Workflow::041 - Automate model submission process Use business process workflow tool to automate the process of model submissions( and other related data) to the KR.
- Gap Analysis::Workflow::135.3 - Modularization and Customization Provide workflow component modularization and customization
- Gap Analysis::Workflow::155 - Create workflows Application developers need to be able to easily use the infrastructure to create workflows without having to figure out how to integrate the data or services, the infrastructure should step them through it and just ask for things that are not already available
- Semantic Infrastructure Requirements::Artifact Management::Behavioral Models Behavioral dynamic models capture the behavior of services. Behavior of services provides an unambiguous definition of the service constraints, capabilities, dependencies and interactions. The metadata and grammar required to realize service behavior is called behavioral semantics. Behavioral semantics provide a mechanism for better service discovery and enforcing the constraints at design and runtime.
- Semantic Infrastructure Requirements::Service Discovery and Governance::Service Governance and workflows This includes predefined templates, workflows, and governance policies for governing the service lifecycle as well as an approval and review process for service specifications and the ability to promote services through the stages of the service lifecycle.
- Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::Service Orchestration and Choreography Service orchestration and choreography allows both application developers and non-developers to discover service "building blocks" that can be composed dynamically to provide business capabilities. Special cases include the orchestration of multiple services for a distributed query, or for a transactional workflow. Service orchestration and choreography will leverage static and behavioral semantics from the Semantic Infrastructure 2.0. The Semantic Infrastructure provides the behavioral semantics required for dynamic composibility of services or generation of distributed queries. This includes runtime contract discovery and negotiation to determine composibility of services based on service capabilities and constraints. Another use case is dynamic retrieval and enforcement of the policies that are in effect for a service interaction in the areas of logging, validations, data transformation, or routing. This information can be used either during the design of the orchestration or during the execution of the defined flow. Link to use case satisfied from caGRID 2.0 Roadmap: Federated query over the TCGA data and other data sets is performed using a service orchestration.
workflowModel
Workflow Model maintenance
Application developers need to be able to easily use the infrastructure to create workflows without having to figure out how to integrate the data or services, the infrastructure should step them through it and just ask for things that are not already available
Authoring tools should automate the construction of workflows.
Provide workflow component modularization and customization
Use business process workflow tool to automate the process of model submissions( and other related data) to the KR.
Provide support for Curation Workflow Activities
Semantics describing workflows will be needed.
This includes predefined templates, workflows, and governance policies for governing the service lifecycle as well as an approval and review process for service specifications and the ability to promote services through the stages of the service lifecycle.
Service orchestration and choreography allows both application developers and non-developers to discover service "building blocks" that can be composed dynamically to provide business capabilities. Special cases include the orchestration of multiple services for a distributed query, or for a transactional workflow. Service orchestration and choreography will leverage static and behavioral semantics from the Semantic Infrastructure 2.0.
The Semantic Infrastructure provides the behavioral semantics required for dynamic composibility of services or generation of distributed queries. This includes runtime contract discovery and negotiation to determine composibility of services based on service capabilities and constraints.
Another use case is dynamic retrieval and enforcement of the policies that are in effect for a service interaction in the areas of logging, validations, data transformation, or routing. This information can be used either during the design of the orchestration or during the execution of the defined flow.
