Architecture Management Topics
This page outlines the currently active topics in the Architecture Management workgroup. Each topic should have an owner who is responsible for articulating the topic, its usage scenarios, and in general marshalling it through the workgroup.
Model management with change sets/requests
Owner: TBD
This scenario originated with a scenario that Tom Picolli originally presented to the workgroup that describes a workflow of someone making changes to a model (AM resource) in the context of change sets and requests that can provide a trail of activity and automatic associations to other types of resources.
Resource Type Discovery
Owner: Jim Conallen
As AM service providers offer customer defined resource types it would be useful for clients to be able to find out exactly what types of resources a provider manages, as well as allow the creation of. Presently a client must navigate all the service discovery documents looking at all creation and query services and the resource type and shapes associated with them. It is not clear how a client would know that a provider can manage a given type outside of creation/query.
Meaningful integrations
Owner: TBD
While simple linking to generic opaque resources provides some benefits, we need to be thinking a little deeper. How do we express meaningful relationships where the providers know about and make use of deeper semantic content through common ontologies and vocabularies.
Transactions and locking
Owner: John Crouchley
In the AM domain resources are often highly fragmented. When clients are creating or modifying a set of resources enmasse in a concurrent environment it is very difficult to maintain the integrity of the resources. Traditionally we've used transactions and locking to help manage this. Is it appropriate to use mechanisms like this to help control the integrity of the highly fragmented resources.
Control processing, generation and script execution
Owner: TBD
How do clients initiate processes that create and modify resources in a long running process (ie code generation from models, or simulations).
Automated Linking
Owner: Sandeep Kohli
Automated linking between artifacts that are generated (via transformation or other server side automation). Discuss ways to uniquely identify an artifact in the process.
Model Driven Development and Automation
Owner: TBD
Programmatic use of architecture resources. This includes search/discovery of resources, processing them off server. Creating other resources in file system, in SCM and in other OSLC service providers. What types of programmatic access is required to perform common tasks like code generation, model validation/simulation, and model transformations.
Topic revision: r2 - 15 Sep 2011 - 13:26:39 -
JimConallen