Tigerstripe Artifacts are intended to capture common design practices for Service Contracts. By using artifacts, an architect can capture business requirements for the design of Service Contracts and separate them for implementation choices.
The Tigerstripe meta-model extends the core meta-model to capture the specifics of Service Contract modeling. These artifacts provide the appropriate level of granularity to model business requirements in a Service Contract and to identify how a Service Contract can support a business process (For example, in the context of an automated business process). The following Tigerstripe Artifacts have been defined:
- Managed Entity Artifacts, to model a thing of physical or logical existence that can be uniquely identified (For example, a circuit, a switch, or a customer). These artifacts will typically be managed by Session Facade Artifacts.
- Datatype Artifacts, to model a commonly used representation of multiple primitive values. (For example, an Address). Datatype Artifacts are used to defined complex types to be used as fields for other artifacts.
- Notification Artifacts, to model a non-solicited notification to be emitted by a Service Contract. The OSS/BSS environment being mostly event-driven, this type of artifact allows you to model and specify the details of each notification. Examples of such notifications are NetworkFaults or CustomerRegistration.
- Exception Artifacts, to model exceptions as they may occur while invoking operations on a Service Contract. For example, in the context of a customer management service contract, a customer creation operation may throw an IncompleteCustomerInformation exception.
- Enumeration Artifacts, to model a series of values that can be taken by artifact fields or artifact method arguments. A typical example of an enumeration artifact can be probable causes to be reported on network alarms, eg.
- Query Artifacts, to model the ability to run pre-specified queries on a Service Contract. The result of a Query artifact being run on a Service Contract is a set of managed entity artifacts corresponding to the result of the query. For example, an AllOutstandingAlarmsQuery can be defined as returning a set of NetworkAlarm managed entities that are all outstanding.
- Update Procedure Artifacts, to model the ability of a Service Contract to take in long running procedures (or batches) that perform multiple internal tasks. For example, an ActivateVPNProcedure.
- Session Facade Artifacts, to model the actual facade of a Service Contract. The session facade groups:
- The Managed Entities, as managed by the Service Contract including all operations as defined on the managed entities,
- The Notifications as emitted by the Service Contract,
- The Queries as exposed by the Service Contract,
- The Update Procedures as exposed by the Service Contract
Each of these artifacts may be used in a Tigerstripe model to generate implementation-specific Service Contracts. Refer to each section for detailed definitions.
A set of artifacts used to refine the modeling of relationships between Service Contract artifacts are also available with Tigerstripe Workbench. The following Artifacts are available for modeling purpose:
For more details about References between artifacts, refer to References within Tigerstripe models.
- Association Artifacts: Used to model UML2-type associations.
- Association Class Artifacts: Used to model UML2-type association classes.
- Dependency Artifacts: Used to model UML2-type dependencies.
Core Tigerstripe Artifacts
© copyright 2005, 2006, 2007 Cisco Systems, Inc. - All rights reserved