Oracle® Communications Design Studio Concepts
Release 7.2.2
  Go To Table Of Contents


1 Design Studio Overview

This chapter provides an overview of Oracle Communications Design Studio, including an introduction to the Design Studio design environment.

About Design Studio

Design Studio is an integrated design environment (IDE) that shortens the development cycles for Operational Support Systems (OSS) solutions that are based on the Oracle Communications OSS applications. Design Studio enables you to deploy solutions quickly by providing a consistent design experience for both technical and non-technical users, and reduces costs by replacing coding with configuration.

The Cartridge Paradigm

Design Studio uses a cartridge paradigm to integrate with Oracle Communication OSS applications. The Design Studio cartridge paradigm is a design solution that decouples the service design model from the logic that is hard-coded in the core applications. The solution model is not coded or configured directly in any Oracle OSS core applications.

Instead, Design Studio solutions are comprised of one or more cartridges, which are application-specific modules that define service or solution logic and specifications. When creating new solutions, you can use productized cartridges, such as cartridges purchased from Oracle, as a starting point to your solution.

For example, consider a network activation core application that receives service activation requests from the ordering system and converts them into series of network vendor-specific commands. In this example, the core application includes features such as network connection pool management, session control, and support for the communication protocols. A network activation cartridge includes network element vendor-specific commands and the expected responses for the supported services. In the network activation cartridge, you can design inbound service data structures. For each network element vendor, you can design a cartridge that includes the network-specific request and response logic that realizes the service.

To enable solutions, you deploy cartridges from Design Studio to core applications that are integrated into a run-time environment. When deployed to a run-time environment, the cartridge is interpreted by the application server, which then activates the intended solution. Cartridges can be undeployed or replaced in the run-time environment to deactivate or to change the solution. Together, the core applications and the deployed cartridges comprise the solution operations environment.

To extend the network activation example, by deploying the network activation cartridge to the core application, you enable the run-time environment to activate the supported services on a specific type of network element (for which the cartridge has been designed). If you have multiple network element types deployed in the network, it's likely that you will deploy multiple cartridges to the run-time environment, one for each type of network element.

Figure 1-1 Design Studio Cartridge Paradigm

Design-Time Development

You create and configure cartridges in Design Studio, an integrated design environment that is optimized for solution design. Design Studio is a design-time environment in which you build and configure your Oracle service fulfillment and network and resource management solutions. A design-time data model represents the data configuration required by your solution design at run-time.

A Design Studio solution undergoes multiple iterations of design, test, and debug cycles, all completed in Design Studio. When you are satisfied with the solution, you build, package, and publish the cartridges so that they can be deployed to the run-time applications in the operational environment.

An integrated solution requires multiple Oracle applications. When you design these solutions, you can model and configure concepts that cross the boundaries of any one specific application. The Design Studio environment integrates the applications used in the solution for a consistent and efficient user experience.

With Design Studio, you can quickly change your solution based on ongoing responses from customers, changes in technology, and market analysis. You use Design Studio to configure solutions at all levels of solution maturity, and over the lifetime of a solution. As requirements change, and as your communications services evolve from incubation to early adoption, Design Studio enables you to evolve solutions during the growth phase (rather than reimplementing it). Also, Design Studio simplifies solution evolution through the growth phase into maturity, enabling you to refactor the solution design and to release updates that meet the evolving service requirements.

Figure 1-2 Design Studio: An Integrated Design Environment

The Design Studio Role in Business Solutions

Design Studio is an integral component in the lifecycle of the following business solutions:

About Design Studio Roles

Team members may play many roles during solution development. Table 1-1 lists the roles and the tasks each role typically performs in Design Studio.

Table 1-1 Design Studio Roles and Tasks

Role Tasks

Data Modeler

Designs the data types and structures necessary to support a cartridge or solution.

Cartridge Designer

Designs deployable components spanning a single product domain.

Solution Designer

Assembles collections of cartridges to deliver a multiproduct solution. Additionally, this role may design additional cartridges to achieve the desired solution functions.


Builds the code to support the metadata-driven components of a cartridge. This role may be an expert in development languages such as Java, XPath, XQuery, or SQL.

Release Engineer

Manages the solution development and test environment. This role configures and automates the solution build and the solution testing.

Cartridge and Solution Tester

Deploys cartridge archives to a test environment to certify that the cartridge or solution is working as intended.

System Administrator

Manages the design environment software. This role acquires, configures, and distributes Design Studio to cartridge designers.

Working with Design Studio for Oracle Communications Applications

In addition to configuring common design-time models that apply across an entire solution, you can also use Design Studio to configure specific design artifacts for one or more Oracle Communications applications:

About Design Studio for OSM

You use Design Studio for OSM to configure and deploy OSM solutions for order orchestration and for order provisioning. Design Studio for OSM enables you to design process flows to meet requests for orders, such as customer, service, and technical orders.

More specifically, order orchestration functionality enables you to configure and deploy OSM cartridges that support customer, service, or technical orders. Design Studio enables you to configure all order details necessary to fulfill the orchestration functions, such as data fields containing XML documents and XQuery automation.

Order provisioning functionality enables you to configure and deploy service provisioning cartridges that include integrations with UIM, ASAP, and IPSA, as well as with third-party applications. Solution integration with UIM and ASAP is facilitated by Design Studio through design-time integration capabilities.

About Design Studio for Inventory

You use Design Studio for Inventory to define the configuration of services and to assign resources to them. Service configuration includes specifications, characteristics, rules, equipment models, capacity models, and component packaging. You define the metadata needed to configure services and map the services to logical and physical resources.

About Design Studio for Activation

You use Design Studio for Activation to model services such as voice services (including wireless, voice over IP), data services (including digital subscriber line, IPTV), and other services that require controlled and coordinated activation in the network.

As part of the service fulfilment process, Design Studio for Activation provides a set of technical actions that you can implement against network and IT resources. You assemble the technical actions into order handling process flows (using OSM), and map the attributes and data from orders (at the service level) to specific resources.

The Design Studio Activation task supports IP Service Activator. For IP Service Activator, OSM data is transformed to a Web service order that is sent to IP Service Activator to activate the specified services. You can create workflows that integrate IP Service Activator data and activation actions with other tools and systems.

About Design Studio for Network Integrity

You use Design Studio for Network Integrity to maintain the data integrity of telecommunications data sources. Using Design Studio for Network Integrity, you can connect to devices in the network (such as EMS, NMS, and other systems) to retrieve data; make changes to that discovered data; import inventory data back into the model; create rules to compare data and identify discrepancies; and integrate with external systems to update data and resolve any discrepancies.

About Design Studio Product Architecture

Design Studio builds on an extensible Eclipse platform to facilitate the creation of service fulfillment and network and resource management solutions. Eclipse provides a vendor-neutral open development platform comprised of extensible frameworks and tools for building and deploying software. See the Eclipse Web site for more information about the Eclipse platform.

Design Studio is supported by design tools for product, service, and resource definition.

Figure 1-3 Design Studio Product Architecture

Working with Design Studio User Interface Components

The Design Studio interface includes a number of components to assist you with configuration. Interface components include workspaces, a workbench, perspectives, views, editors, menus, and toolbars.

Figure 1-4 is an overview of Design Studio components and their relationships to each other as they appear in the Design perspective, and Figure 1-5 is an overview of Design Studio components and their relationships to each other as they appear in the Environment perspective. The Workbench, perspectives, views, and editors are further described in subsequent sections of this chapter.

Figure 1-4 Overview of Design Studio Components in the Design Perspective

Figure 1-5 Overview of Design Studio Components in the Environment Perspective

Figure 1-6 and Figure 1-7 illustrate component relationships in the Design perspective and the Environment perspective, respectively.

Figure 1-6 Design Studio Components in the Design Perspective

Figure 1-7 Design Studio Components in the Environment Perspective

About Workspaces

The workspace contains a logical collection of your projects. Your projects exist independent of a workspace, but can only be used in a workspace. The workspace directory root is created on your local machine when you create a Design Studio workspace. The root exists as long as the workspace exists. You can create more than one workspace, but the only one workspace can be open at a time. A workspace is persisted as a directory on your local machine where Design Studio saves your resources.

When you start Design Studio, you identify a workspace in which you want to work. You can switch to a different workspace, when necessary. Design Studio will automatically close down and restart using the new workspace. See the Design Studio Help for information about switching workspaces.

About the Workbench

The Design Studio workbench is a set of tools you can use to navigate within and manipulate the workspace, access functionality, and edit content and properties of resources.

Figure 1-8 Design Studio Workbench

About Perspectives

Perspectives are collections of views, menus, and toolbars that appear in a specific layout, and they determine how information appears in the workbench. The Design Studio provides two predefined perspectives that work together with Eclipse and third-party perspectives that are used for implementation, debugging, builds, and version control.

Perspectives are task oriented. For example, you use the Design perspective to model the entities in your cartridges. You use the Environment perspective to create and manage the attributes associated with your environment, and to deploy and undeploy cartridges to run-time environments.

Each perspective contains a default set of views and editors, which you can customize. The views automatically included in the Design perspective assist you with cartridge modeling. You can also create your own perspective.

Figure 1-9 Design Studio Perspectives

About Views

A view provides access to a specific set of functions, available through the view's toolbars and context menus. For example, the Problem view displays errors that exist in the model entities, so you use the Problem view to locate and resolve entity errors. You use the Data Element view to model and review data in your workspace. The Data Element view and Problem view each provide access to a different set of Design Studio functions.

A view can appear by itself, or it can be stacked with other views. You can change the layout of a perspective by opening and closing views and by docking them in different positions in the workbench window.

Figure 1-10 Design Studio Views

About Editors

An editor is a special type of view that enables you to edit data, define parameters, and configure settings. Editors contain menus and toolbars specific to that editor and can remain open across different perspectives.

You can double-click entities in the Cartridge view to open the entities in an editor, where you can edit existing model data. All Design Studio entities have associated editors in which you configure data for the entity. Design Studio supports drag-and-drop functionality, enabling you to drag files or entities from the Cartridge view to editors. Additionally, you can open an editor associated with an entity by dragging the entity from a view into the editor area.An asterisk in the editor title bar indicates that the changes you made in an editor are unsaved.

Design Studio editors are associated with entities. Many Design Studio views enable you to double-click on entities to open the entity in the associated editor. You can double-click an entity in the Cartridge, Resource, Problems, Relation, and Relation Graph views to open the associated editor. Additionally, you can double-click on table entries that reference entities to open the entity in the associated editor.

For example, if you double-click a Process entity in the Cartridge view, the Process editor opens. You can create diagrams in the Process editor to illuminate patterns and identify inefficiencies in tasks and processes. Process editor shapes, colors, and presentation can communicate information about the flows and processes.

If you double-click a Specification entity in the Cartridge view, the Specification editor opens. You can use the Specification editor to define properties of business entities. The Process editor, and the Specification editor are just two of the many editors available to you in Design Studio.

About the Design Studio Help

Design Studio includes multiple methods for obtaining Help when working in the user interface, including:

  • Some Design Studio editors include an editor help button that you can use to open the Help view. The view contains a list of topics relevant to the corresponding entity. You can use the Help view to review the Design Studio Help without leaving the workbench. The help button is located on editors and dialog boxes and is represented by a question mark.

  • Design Studio guided assistance provides a range of context-sensitive learning aides mapped to specific editors and views in the user interface. For example, when working in editors, you can open the Guided Assistance dialog box for Help topics, cheat sheets, and recorded presentations that are applicable to that editor. The Guided Assistance button is represented by a question mark and play button combination.

  • The Studio menu includes options for accessing the Help in a separate window, and for accessing the Guided Assistance dialog box.