This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

OSLC Architecture Management Scenarios

DEPRECATED THIS DOCUMENT IS NO LONGER ACTIVE IN ARCHITECTURE MANAGEMENT DISCUSSIONS

This document outlines the scenarios discussed during the development of the AM specification. Not all scenarios ended up being fully supported in the 2.0 specification.

Resource Management

Scenarios focused on the creation, update and removal of AM resources like models and model elements.

OSLC simple client creates a new UML component

Update a property on an existing resource

Get quick (hover) information about an existing resource

Remove a resource from the server

Linking

Change Request Linking

Scenarios focused on the establishment and usage of links between resources, especially cross domain linkages. These include the functionality necessary to find the resources to link to in other servers.

Link a UML component to a requirement from the web UI of a service provider.

From the web UI of a service provider, link a business process model to a new work item task.

OSLC simple client update a link annotation on an existing link.

OSLC simple client removes a link from an existing resource.

Query

Scenarios supporting a client's ability to query for specific resources.

For all the resources of a certain type, get just the resource name, and its links of a certain type.

Get all the resources that have changed in the past week.

Run Processes

Execute long running MDD style transformations on resources

Topic revision: r4 - 30 Jan 2012 - 18:11:00 - JimConallen
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback