Introduction to reusable asset specification (RAS)

Reusable Software asset types

1. granularity Division

The granularity of an asset describes how many problems the asset can solve or how many solutions it provides. The simplest asset provides a single solution. As the granularity increases, problems that can be solved by assets also increase.

Generally, the increase in granularity will increase the capacity and complexity of assets.

2. Division of variability

Asset variability and visualization are important attributes of assets. An extreme asset may be immutable, that is, it cannot be changed in any way. For example, component binary files. Such components become black box assets because their internal implementations are invisible and cannot be modified.

It corresponds to a white box asset. Asset users can edit or replace its content implementation. White-box assets usually include development results, such as requirements, models, and source files.

The other two types are clear-box assets and gray-box assets. Clear-box assets provide implementation details (provide model code snippets, or other documents) but they cannot be changed. These details only help users better understand the internal mechanism of assets. A gray-box asset allows you to change a subset of an asset, usually a parameter of an asset.

3. Integrity Division

Integrity describes the completeness of solutions provided by assets. For example, the solution is provided, but the detailed implementation solution is not provided. Or the asset provides all solutions, including test documents.

Asset Packaging)

Each reusable asset must contain at least one inventory file, which is an XML document and complies with Ras XML schemas. An asset package is a collection of deliverables and inventory files. The format can be:

• Package it into an archive file
• It is not packaged. The result object can exist in a specified place or be moved to another place during packaging.

Core ras2.1

Core RASAndProfiles

Ras can be divided into two parts: Core ras and profiles. Core Ras contains the basic elements of the asset specification. Profiles describes the extension elements. A profile cannot replace the elements defined in core Ras.

 

Indicates the general relationship between core ras and profiles. More accurately represents the relationship between the two. Default profile is a core Ras implementation. Default component profile and default Web Service Profile inherit the default profile.

 

Displays some important parts and elements of core Ras. The four main parts of core Ras are:

Classification Section, solution section, usage section, and related assets section ).

The Classification Section lists the identifier of the asset category and the context of the asset.

The solution section describes the asset deliverables.

The usage section includes installation, configuration, and use of asset rules.

The related asset section describes the relationship between the asset and other assets.

 

 

RasDatabase Service

The standard. RAS file and rasset. xml file can be used to search and browse assets. Various services in the Asset Library can be implemented by Web Services. Each service includes servicename, request, and response. The request can be httprequest. Response is one of the two types of database data descriptors. The database data identifier is a database asset identifier or a library folder descriptor. The descriptor format is as follows: