Role Overview
There are several categories of roles for asset-based development. These include:
-
Managers
-
Practitioners
-
Administrators
Managers
The roles in this group are focused on determining the governance of asset-based development. This means that they
specify policies, determine investment direction, measure results, and adjust. The roles in this group may not directly
interact with the Repository, but certainly are not restricted from doing so. The reporting mechanisms or the results
of the reporting mechanism should be easily reached from this group.
There is one major scenario these roles perform using the Repository: Measure asset activity See the Concept: Major Repository Scenarios for more information on this scenario.
Practitioners
The Repository is heavily focused on supporting scenarios for the roles in this group. The roles are introduced below.
Asset Owner
The holder and keeper of the asset, who initially created and submitted the asset. This is generally a person, but may
also be an organizational unit as well as a Community.
Asset Producer
Someone who updates an asset, typically creating a new version, but is not the Asset Owner.
Asset Reviewer
Evaluates and submits asset reviews.
Asset Review Board
A collection of one or more individuals who evaluate submitted reviews and cast final votes on the asset's approval.
Asset Consumer
Searches, browses, evaluates, and reuses assets and provides feedback. Some of the major scenarios these roles perform
using the Repository are listed below.
-
Search or evaluate an asset
-
Retrieve and use an asset
-
Create and package an asset
-
Submit an asset
-
Review and approve an asset
-
Modify and create a new asset version
See the Concept: Major Repository Scenarios for more information on these scenarios.
Administrators
There are several administrative roles. The ones mentioned here relate to administrating the Repository.
Community Administrator
This role is responsible for specifying the asset types, review processes, roles and access control, and review
processes for a specific Community. A Community is an arbitrary collection of users and the assets that are relevant to
them.
Repository Administrator
This role is responsible for specifying server paths, application server paths, database configurations, web service
locations, background process settings, and overall performance.
Integration Administrator
This role is responsible for integrating the Repository with development lifecycle tools such as SCM tools, change
management tools, and service registries.
Some of the major scenarios these roles perform using the Repository are listed below.
-
Configure repository
-
Measure asset activity
See the Concept: Major Repository Scenarios for more information on these scenarios.
|