Tigerstripe Workbench provides support for OSS/BSS Architects and Engineers throughout the process of designing and implementing a Service Oriented Architecture (SOA) based solution.
The tasks associated with the following steps are detailed in the corresponding sections:
- Creating a new Tigerstripe Project: A Tigerstripe Project is the placeholder for a Tigerstripe model. It holds all the details of a Service Contract from which you can generate technology specific specifications and documentation.
- Modeling the Information and capabilities of a Service Contract: The first part in modeling a Service Contract is to identify the information that will go through your contract. Once the information model has been identified, the capabilities offered by the contract must be modeled. For example, how information is going to be accessed and whether the Service Contract should emit unsolicited notifications.
- Creating and using Tigerstripe Profiles: Using a Tigerstripe Profile allows you to create your own Primitive types and to annotate your model with Stereotypes.
- Generating the Technology Specific Specifications: Once your model is complete, you will Generate technology specific specification to produce the target integration profiles, whether using built-in profiles such as J2EE, XML, Web Services, or user defined outputs.
- Creating a User Defined Plug-in: If you need to generate your output according to a specific user or company guidelines, you can capture those rules in a plug-in to be used when you Generate your project.
- Publishing a Service Contract: Once your Service Contract design is complete, you will release it to your implementation teams. You can use Tigerstripe to generate web-based documentation of your Service Contract along with the selected integration profiles directly available for download.
Beyond the core tasks associated with creating and releasing a Service Contract, Tigerstripe provides a complete design environment allowing integration with other modeling environments, in addition to providing the appropriate tools for team collaboration. The following topics are covered in the corresponding sections:
- Tigerstripe Models and Versioning: Service Contracts often evolve over time due to additional business requirements or updates of underlying applications therefore, it is extremely important to place Tigerstripe models under version control.
- Sharing information between Tigerstripe Projects: By nature Service Contracts are meant to be interactive, therefore your information models could be shared. Tigerstripe allows you to define modules that can be shared between Tigerstripe projects. For example, information libraries.
© copyright 2005, 2006, 2007 Cisco Systems, Inc. - All rights reserved