OSLC Requirements Management 2.0
This text is derived from the OSLC Primer:
"Open Services for Lifecycle Collaboration (OSLC) is an open community creating specifications for integrating tools. These specifications allow conforming independent software and product lifecycle tools to integrate their data and workflows in support of end-to-end lifecycle processes."
"OSLC is based on the W3C Linked Data. One of the primary techniques for integrating tools using OSLC is Linking data via HTTP, which specifies creating, retrieving, updating and deleting (CRUD) lifecycle artifacts based on internet standards such as HTTP and RDF using Linked Data model. Each artifact in the lifecycle, such as a requirement, is an HTTP resource that is manipulated using the standard methods of the HTTP specification (like GET, POST)."
Enterprise Architect acts as an OSLC Provider and supports the Requirements Management 2.0 specification of OSLC, which allows for creating, retrieving and querying the Requirements in a model accessed via a Cloud connection. With OSLC support, Requirements in an Enterprise Architect model can be identified and accessed using a unique URL that can be linked to resources in other lifecycle products and tools.
Enterprise Architect complies with these Requirements Management 2.0 base requirements:
- Resource Operations
- Service Provider Resource
- Partial Resource Representations
- Creation Factory
- Query Capability
- Query Syntax
- Error Responses
- RDF/XML Representations
- OSLC Requirements Management was initially available through Pro Cloud Server (PCS) without needing a license; as of PCS version 4.1.44 this feature is available through the PCS only under license, so if you upgrade to the latest version of PCS you will not have access to the feature unless you have a valid license
- Also as of Pro Cloud Server version 4.1.44, OSLC Requirements Management will be superseded by the OSLC Architecture Management 2.0 feature if they are both implemented; whilst OSLC Requirements Management is still available for use (when OSLC Architect Management is not present), it is not expected that any further enhancements will be made to it