| Description | This pattern implements an asset that can be inherited from other assets in order to provide these assets with an id, a name, a description and a primary key. |
|---|---|
| Default Namespace |
http://www.aoModeling.org/patterns/meta/generic/identifiedAsset
|
| Namespace Prefixes | {none} |
| Scope Definitions | {none} |
| Default Type System | {none} |
| Type System Prefixes | {none} |
| Default Subject Ontology | {none} |
| Subject Ontology Prefixes | {none} |
| Default Constraint Language | {none} |
| Constraint Language Prefixes | {none} |
| Default Operation Vocabulary | {none} |
| Operation Vocabulary Prefixes | {none} |
| Design Patterns | {none} |
| Included Models | {none} |
Pattern Info |
|
| Copyright | (c) Berthold Daum |
| Category | meta/generic |
| Keywords | identification asset identified named |
| Alias names | AssetWithId |
| Purpose | The purpose of this pattern is to propagate a uniform way to create identified assets. |
| Motivation | Especially in database applications, a primary key is required for a business object. Inheriting this property from a command abstract asset provides clients with a common interface for all business objects. |
| Applicability | This design pattern should be applied to most business object assets within a database application. |
| Consequences |
Advantages: Enforces a consist approach to the identification of business objects Disadvantages: In some cases a single object ID may not be sufficient. I some cases a name or a description may not be needed. |
| Known Applications | Database applications. |
| Related Patterns | {none} |
| Acknowledgements | {none} |
| Related Patterns | {none} |
| Level 2 Structures | {none} |
| Assets |
IdentifiedAsset
Asset |
| Annotations | {none} |
| Errors | {none} |
| Warnings | {none} |
| Infos | {none} |
| Status | Pattern contains 0 errors, 0 warnings, and 0 infos |
