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.

AM Use Case Scenario - Basic Linking

This set of scenarios outlines the basic functionality for creating and navigating basic linking across AM and other domain resources (or across AM resources managed in different servers or domains).

In these scenarios we continue to assume that the details (raw resource formats) of individual AM resources are a black box as concerned by the specification, however implementing service can and should know how to manage them.

All scenarios assume that the user has proper permissions and has already been authenticated by all required systems/services. It also assumes that all services have been configured propertly (i.e. link types have been defined, and servers have been configured with references to the other servers implementing the expected OSLC interfaces (CM, RM, QM, ...). The OSLC AM specification does not attempt to define how this happens.

Create link from AM resource to requirement

Goal: A deisgner wants to indicate that a AM resource implements a specific requirement

  1. The designer navigates to a AM resource (UML diagram).
  2. The designer invokes the action to create a new link from this resource to a requirement type resource.
  3. If the system is configured with more than one requirements project associated with the context that the AM resource is in, then the user is prompted to select which requirements 'project' to find the requirement in.
  4. The system delegates resource selection to the requirements service. The requirements service provides a resource picker to the designer.
  5. The designer uses the resource picker to select a requirement to link to.
  6. The designer selects the link type 'implements' from the list of available types, and confirms the link creation. The list contains the labels for each link type (not the internal id/uri). Systems may optionally display hover help or a short description for each.
  7. The system creates a new link resource that has the AM resource as the subject, the requirement resource URI as the object, and the link type as the predicate. This link will appear in the links view for AM resources, and can be queried for.

View and navigate to a linked resource from a AM resource

Delete a link from a AM resource

-- JimConallen - 21 Oct 2009

Edit | Attach | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 21 Oct 2009 - 15:07:35 - 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