This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
AssetHome
>
AssetMgSpecificationV1
>
AssetMgScenarios
>
AssetMgScenariosEmphasys
(29 Jul 2009,
RandyLexvold
)
(raw view)
---+ Asset Management Scenarios - Architect These scenarios focus on ways that an Architect can specify & publish assets, and also how other users, Architects, Designers, or Developers, can consume those assets. *Roles* In these scenarios there are two major roles, asset submitter and asset consumer. * <a name="assetsubmitter" title="assetsubmitter"></a> *Asset Submitter*: performs asset preparation activities outlined in the publish scenario. For these scenarios, the submitter will be an Architect. * <a name="assetconsumer" title="assetconsumer"></a> *Asset Consumer*: performs asset searching and retrieval activities outlined in the search and retrieve scenarios. For these scenarios the consumer can be anyone consuming Architecture assets. *Security / Access Rights* In these scenarios it is assumed the asset submitter and the asset consumer have already provided user authentication. This means they are not providing user information as they publish an asset or as they search or retrieve assets. It is expected that the asset repository will determine that context from previous information provided by the respective user. ---++ Publish<a name="publishasset" title="publishasset"></a> *Publish Reference Architecture Scenario Example* An Architect has been developing a Reference Architecture that has reached a state where they are ready to share the Architecture with the development teams. They have been doing all of their work in a modeling environment, such as Rational Software Architect. The Architect selects that they are ready to publish the Reference Architecture to the asset repository. The modeling tool provides a way to select what items should be packaged together to form the asset. The Architect selects one or morel models and/or projects of other types that document the Reference Architecture and the points of variability. The Architect the provides necessary metadata, such as: * Name * Description * Depencencies on other assets * Context for using Reference Architecture * Whether the Architecture is recommended or required ---++ Search<a name="searchasset" title="searchasset"></a> *Search For Reference Architecture* *Scenario Example* <strong>Background <br /></strong> The asset information and workproducts provided in the [[#publishasset][Publish]] scenario provide the basis for searching and browsing. In the search scenario the [[#assetconsumer][Asset Consumer]] uses asset information to search for the asset. They are developing a new system and need to find a Reference Architecture that matches their type of system. They are in a modeling environment, such as Rational Software Architect, and select that they would like to find a Reference Architecture. The modeling tool collects the search parameters such as the context of the desired application, keywords, etc. The set of searchable assets are constrained by the access rights of the asset consumer; which means that another asset consumer with different access rights while using the same search parameters may have a different result set. The search returns the search result for the provided search parameters and user access rights. The Asset Consumer browses the asset information on the search result (i.e., browses the asset meta data). The service artifacts are NOT downloaded during this scenario; but are downloaded as part of the Retrieve scenario. ---++ Retrieve<a name="retrieveasset" title="retrieveasset"></a> *Retrieve* *Reference Architecture Scenario Example* *Background* In this scenario, the [[#assetconsumer][Asset Consumer]] is developing a new system and has found a Reference Architecture that they would like to retrieve into their modeling tool and start developing a new system, using the Reference Architecture as a starting point. They select the desired Reference Architecture and the modeling environment retrieves the Reference Architecture and makes a new instance of it. The Asset Consumer then uses the modeling tool to iterate through the variability points and select the correct options for the new system. The modeling environment creates a new asset in the repository for this instantiation of the Reference Architecture. It captures the variability and creates traceability to the Reference Architecture. The Asset Consumer the proceeds to develop the system. [[AssetMgEmphasysGenericScenarios][Generic Scenarios]]
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r4 - 29 Jul 2009 - 16:08:33 -
RandyLexvold
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback