Tigerstripe Workbench uses a revolutionary approach based on Service Artifacts to model the information and behavior of a Service Contract deployed in a Service Oriented Architecture. Service Artifacts introduce additional patterns and constraints compared to a typical modeling environment (for example, UML2). These enable architects, service designers and developers to automatically create consistent Service Contract metadata that helps to ensure a successful deployment in a product suite or enterprise architecture.
This Service Contract metadata is used to feed an ultraflexible generation engine to derive Service Contract implementation, runtime libraries, deployment information, test harnesses and documentation. The generation can be further extended and tailored to specific environments by editing and creating additional Tigerstripe Plug-ins.
The release of Tigerstripe Workbench versioin 2.2 includes the following:
- UML Instance Diagrams to graphically define an instance of your service contract at a given point of time.
- Custom Service Contract use case documentation, including diagram references.
- Optional Hibernate and Axis plug-ins allowing generation of Service Stubs for testing in a sandbox environment
- Linux support
The release of Tigerstripe Workbench version 2.1 includes the following:
- Service Contract Facets to define the scope within a service model and allowing you to define multiple facets of a Service Contract from a single service model.
- Improved UML Class Diagrams that includes (1) package visibility for attributes, methods, and association ends, (2) component visibility with usual UML notation on attributes, methods, and association ends and (3) abstract qualifiers are displayed properly in italic characters according to UML conventions for Artifact and Method names. For detailed information, refer to Entity Attributes.
- The ability to show or hide relationships in a Class Diagram.
- The ability to specify additional files referenced by a custom plug-in. These files are included in the plug-in and can be referenced from within templates, with the $pluginDir context entry.
- An enhancement has been introduced in Artifact-based rules to optionally loop over all artifacts visible in the context, i.e. including those defined in referenced projects or dependencies. This option is available from the Artifact Based rule definition editor.
- The velocity context has been extended with new entries corresponding to all artifacts visible in a project. The following have been added $allArtifacts, $allEntities, $allDatatypes, $allExceptions, $allQueries, $allUpdateProcedures, $allSessions, $allEnumerations, $allEvents, $allAssociations, $allAssociationClasses, $allDependencies.
The release of Tigerstripe Workbench version 2.0 includes a large number of new features for flexibility and ease of use. Some of these new features include:
- Graphical User Interface for Service Contract Design
- Fully customizable plugins based on Velocity Templates and Java code·
- UML2 support with additional UML2 elements such as Associations, Association Classes, or Dependencies, but also UML2 Import/Export.·
- Tigerstripe Workbench Java API, allowing you to write your own java code to interact with Tigerstripe Workbench
© copyright 2005, 2006, 2007 Cisco Systems, Inc. - All rights reserved