Requirements Management and Definition 1.0 Specification

Introduction

This family of documents defines the Open Services for Lifecycle Collaboration Requirements Management and Definition specification, also known as OSLC RM. These documents collectively define the OSLC RM 1.0 specification, which is part of the OSLC group of specifications.

This specification supports key REST APIs for software Requirements Management systems. OSLC RM 1.0 takes an open, loosely coupled approach to specifc lifecycle integration scenarios. The scenarios and this V1.0 specification were created by the OSLC RM Working Group.

More information on the principles underlying OSLC and RM in particular can be found on the main OSLC site and the home page of the RM topic.

Specification Working Group

Authors of the OSLC RM 1.0 Specification:

• SteveAbrams (IBM)
• AndyBerner (IBM)
• ScottBosworth (IBM)
• JimConallen (IBM)
• GeorgeDeCandio (IBM)
• BrendaEllis (Northrop Grumman Corporation)
• RainerE (Siemens)
• IanGreen (IBM; OSLC RM Lead)
• AndreasKeis (EADS)
• TorgeKummerow (EADS)
• ChrisMcGraw (IBM)
• PaulMcMahan (IBM)
• DevangParikh (IBM)
• VishyRamaswamy (IBM)
• RenRenganathan (Citigroup)
• DavidRuiz (Ravenflow)
• MatthewStone (Stoneworks)
• DominicTulley (IBM)
• RandyVogel (Accenture)
• SimonWills (Integrate)

(Please address all enquires to the OSLC RM Lead, IanGreen.)

Specification

Document
RESTful Services
Requirement resources
Requirement collection resources
Delegated Resource Selection and Creation
Requirements Management Service Description
Requirements Management Service Description Vocabulary

In addition, the OSLC-RM 1.0 specification relies on the OSLC Service Provider Catalog specification, part of the OSLC Common Services family of specifications.

Supporting Documents

These non-normative documents do not form part of the specification, but document the use cases, design decisions, and over rationale that led to the OSLC RM 1.0 specification. In any discrepancy between what is described in these documents and the actual specifications, the specification prevails.

Document
Scenarios and Use Cases
Resource Design Guidelines

Intellectual Property Covenant

The members of the Working Group (or as appropriate, their employers) have documented a Patent Non-Assertion Covenant for implementations of the Requirements Management 1.0 Specification, as described in the open-services.net Terms of Use. Details of the Covenant may be found here.