Special:Recentchanges
Special:Categories
Special:Titles
Special:Files
index
Predefined Query Example: Commented Resources with Keyword
Predefined Query Example: Locked Resources
V3 Scenario: Change Request Linking
Open UP Development Scenario
Some simple AM scenarios
Business Scenario: Implement Requirement Set
Scenario: Update a link type description
Scenario: Obtain the Architect Management Service URIs
Scenario: Find AM Resources with Properties
Scenario: Create a Link from an AM Resource to Requirement
Scenario: Update Link Properties
Scenario: Remove Existing Link from AM Resource
Scenario: Add Custom Property
Scenario: Create a new Architecture Resource
Scenario: Change the title of an AM resource
Scenario: Find Resources Specific Relationship External Resource
Scenario: Find All Resources with any relationship to a given URI
Scenario: Obtain the AM Resource URI via Picker
Scenario: Register new link type
Model driven Development Scenario
Implement Change Request
Use Case Scenario: Link Types and Query
Use Case Scenario: Basic Linking
Diagram Resource Usage Scenarios
Common Architecture Resource Types
Some thoughts on Impact Analysis
Common Architecture Resource Properties
Use case scenarios
Deprecation of Link Type Resource
Managing Links in the OSLC AM Specification
Alignment with Core 3.0
Scenario: Long Running MDD Transformations
Predefined Queries
Diagram Resource
OSLC Architecture Management Specification Version 2.0 Appendix B: Resource Shapes
OSLC Architecture Management 2.0 Appendix A: Samples
OSLC Architecture Management v3.0 Specification Issues
Version 3.0 Use Case Scenarios
OSLC Architecture Management v2.0 Specification Issues
OSLC Architecture Management Vocabulary
Architecture Management Meetings
OSLC Architecture Management Specification Version 2.0
OSLC Architecture Management Specification Version 3.0
m20120913
Meeting 13 Sep 2012
Meeting 27 Sep 2012
Meeting 11 Oct 2012
Rational Design Management example DM Parts
DM Parts Example
AM specification backlog
Architectural Direction 3.0
Meeting 8 Nov 2012
AM Link Type Predicates
Diagram Resource Example
Meeting 06 Dec 2012
Meeting 20 Dec 2012
Examination of use of rdf:Seq instead of oslc_am:next
Meeting 03 Jan 2013
CRUD
Partial Update
UI Preview
OSLC Simple Query
Alternate Query
Pre defined queries
Meeting 17 Jan 2013
Meeting 25 Apr 2013
Meeting 09 May 2013
Meeting 23 May 2013
Meeting 06 Jun 2013
Meeting 20 Jun 2013
Meeting 18 Jul 2013
Meeting 01 Aug 2013
Meeting 29 Aug 2013
Structured Views
Simple containers and views
Meeting 12 Sep 2013
Meeting 26 Sep 2013
Meeting 24 Oct 2013
Meeting 21 Nov 2013
under development
The following link type predicates may be used in any Architecture Management Resource, provided the specific service provider permits it.
Prefixed Name
Occurs
Read-only
Value-type
Representation
Range
Description
Dublin Core: Common relationships
dcterms:relation
zero-or-many
unspecified
Resource
Reference
any
A related resource. This property is the most generic type of relationship and can be used when there is no better defined property.
OSLC AM: SysML relationships
oslc_am:refines
zero-or-many
unspecified
Resource
Reference
any
This resource is a refinement of the referenced resource. For example, a Use Case scenario might be a refinement of a textual requirement that describes the interaction.
oslc_am:satisfies
zero-or-many
unspecified
Resource
Reference
any
This resource satisfies a requirement (the referenced resource). For example a UML Component satisfies a requirement to provide some type of functionality.
oslc_am:verifies
zero-or-many
unspecified
Resource
Reference
any
A dependency from a model element to a requirement that determines whether a system fulfills the requirement. For example a Sequence diagram verifies a requirement that describes a protocol.
Rational Design Management: Pre-defined relationships
dm:derives
zero-or-many
unspecified
Resource
Reference
any
The model element derives from a requirement.
dm:elaborates
zero-or-many
unspecified
Resource
Reference
any
The model element elaborates a change request.