Getting Started with Tigerstripe Workbench

Introduction

In the context of Enterprise Architecture, the choice of Service Oriented Architecture (SOA) has emerged over the past few years as a flexible solution to align business needs with IT decisions. At the core of SOA, the IT infrastructure is presented through a set of services that are often composed to fulfill business processes. Each of these services are specified through Service Contracts that capture the capabilities offered by these services from a business perspective.

One of the challenges of deploying a successful Enterprise Architecture, is to properly identify and design the services that will be deployed on top of IT applications and systems. The telecommunication industry has developed a set of standards through bodies such as the TeleManagement Forum or the OSS through Java™ initiative that provides design guidelines, best practices, and patterns to ensure that the final solution is successful.

Tigerstripe Workbench encapsulates these design guidelines and best practices in a Workbench integrated with Eclipse, where an OSS/BSS Architect can model, design, and release standard compliant Service Contracts.

This first section is intended to guide you through your first Tigerstripe project, where you will design a simple Service Contract. The basic concepts behind Tigerstripe Workbench are introduced so you can easily navigate the Workbench Perspective.

The following concepts will be covered:

Tigerstripe Workbench Architecture

Tigerstripe Workbench is composed of three major components:

Eclipse Integration

Tigerstripe Workbench is fully integrated with Eclipse and adheres to the Eclipse guidelines. As a result, an Eclipse user will quickly become acquainted with Tigerstripe.


© copyright 2005, 2006, 2007 Cisco Systems, Inc. - All rights reserved