Asset Management Specification

Version 1.0

Introduction

Asset Management Systems allow enterprises to catalog, govern, manage and maintain reusable software packages as a definitive software library. Using the constructs defined in the OMG Reusable Asset Specification we consider a reusable asset to be a collection of zero or more artifacts. Artifacts are workproducts from the software development lifecycle, such as requirements documents, models, source code files, deployment descriptors, test cases or scripts, and so on.

The intent of this specification is to define the set of HTTP-based RESTful interfaces (Asset Management REST Services API) in terms of HTTP methods: GET, POST, PUT and DELETE, HTTP response codes, mime type handling and resource formats for the use in Asset Management tools and use by ALM tools.

This specification also defines how Assets and Artifacts are represented in OSLC services. The Asset Resource is a set of properties for an Asset, and includes properties that describe an Asset's Artifacts.

The capabilities of the interfaces in this specification are driven by a use case scenarios and therefore don't represent a complete setup of operations on resources or resource types.

Refer to the definitions page for descriptions on asset management related terms used here.

Specification Working Group

Authors of the OSLC-Asset Mgmt 1.0 Specification:

• Grant Larsen (IBM)
• Gili Mendel (IBM)
• Kevin Bauer (IBM)
• Edwin Freekenhorst (Shell)
• Ren Renganathan (Citigroup)
• Jaimin Patel (WebLayers)
• John Favazza (WebLayers)
• Randy Lexvold (the Emphasys Group)
• Kaj Kandler (Black Duck)
• Richard Sherrard (Black Duck)
• Scott Bosworth (IBM)
• Steve Abrams (IBM)
• Hari Padmanabhan (IBM)
• Brad Sandler (IBM)
• Dave Johnson (IBM)

Specification Documents

Supporting Documents

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 Asset Management 1.0 Specification, as described in the open-services.net Terms of Use. Details of the Covenant may be found here.