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

Previous
Previous
 
Next
Next
 

4 Solution Modeling and Design

This chapter describes the features and functionality you use in Oracle Communications Design Studio to model the configuration for service fulfillment and network and resource management business solutions.

About Data Schemas

A data schema is a description of a data model, expressed in terms of constraints and data types governing the content of elements and attributes.

You use data schemas when defining products, services, and resources, including the associated actions and the information necessary to perform the processes and tasks for those actions, as well as the interface definitions for integrating between applications.

See Design Studio Developer's Guide for information about data schemas.

About Data Elements

Simple data elements are reusable data types that contain no child dependencies. A simple data element has no structure, and is associated (directly or indirectly) to a primitive type (Integer, Boolean, String, and so forth).

Structured data elements are reusable data types that include embedded data types and are containers for simple data elements and structured data elements. For example, you might create a structured data element called building that contains the floor, room, aisle, rack, and shelf child structured data elements.

See Design Studio Developer's Guide for information about data elements and primitive types.

Working with Design Studio Data Modeling Tabs

Some Design Studio editors include tabs in which you can model information about data elements. These tabs are used by multiple Oracle Communications applications and enable you to configure entities by modeling a data tree to hierarchically represent all associated data elements. These tabs facilitate the reuse of data elements within a modeling solution and provide tools for locating and using existing data elements.

See Design Studio Developer's Guide for information about data modeling tabs.

Working with Predefined Data Models

Predefined data models that are provided by Oracle Communications applications include product definitions to support your solution development. You can use predefined data models as the foundation for your new solutions, and build your own data models to extend and augment the predefined models.

There are two types of predefined data models: productized models and common models.

Productized models are predefined cartridges that you can use as the foundation for your new solutions. For example, cartridges purchased from Oracle can be imported into Design Studio and reused to create your own cartridge projects. Productized cartridges include configuration that supports product definitions.

The following common models might also be required by your Design Studio solution:

You are required to obtain and import the following common models if you are working with Design Studio for Inventory or Design Studio for Network Integrity:

Sharing Data Across Application Projects

When you design your fulfillment solution, you need to develop a model comprised of data for use in multiple applications. For example, you may want to create order templates, atomic actions, and service specifications, and share the data defined for those entities across your OSM, ASAP, Network Integrity, and UIM applications. Design Studio enables you to design integrated solutions that reduce occurrences of design errors at the interface between the applications.

About The Data Dictionary

The Data Dictionary is a logical collection of all data elements and types in a workspace. The Data Dictionary enables you to leverage common definitions across an entire Oracle Communications solution.

Design Studio projects are containers of entities, one of which is a data schema. You save all of your solution data in data schemas (all Design Studio features include data schemas). All data schemas in a workspace at any given time contribute to the Data Dictionary. Some Oracle Communications features enable you to create entities and data elements in specific editors, which are also included in the logical collection. You can review the Data Dictionary logical collection in the Data Elements view.

The Data Dictionary enables you to:

  • Integrate and correlate the data models for multiple applications.

  • Reduce the size and complexity of a solution model.

  • Simplify the application integration by eliminating data translation among applications.

  • Validate data model integrity.

About Solution Modeling

When modeling entities for your solution, you can use configuration from any other entity. Data modeling is not limited to using data elements within data schema entities. Any data configuration that contributes to the Data Dictionary is available for use.

The following sections provide examples of solution modeling using the Data Dictionary.

Example: Activation Leveraging Inventory Data

Figure 4-1 illustrates how an atomic action (Add GSM Subscriber), created in an Activation project, can be defined using the Caller ID, Call Waiting, and Call Forwarding data elements from a service specification created in an Inventory project.

Figure 4-1 Example: Activation Leveraging Inventory Data


Example: OSM Leveraging Activation Data

Figure 4-2 illustrates how an order (Mobile GSM Delivery) created in an OSM project can use the TN (telephone number) and TN Type (telephone number type) data elements from a service action modeled in an Activation project.

Figure 4-2 Example: OSM Leveraging Activation Data


Example: OSM Leveraging Inventory Data

Figure 4-3 illustrates how an order (Mobile GSM Delivery) created in an OSM project can use the Caller ID, Call Waiting, and Call Forwarding data elements from a service specification modeled in an Inventory project.

Figure 4-3 Example: OSM Leveraging Inventory Data


Extending Reference Implementations

Oracle Communications reference implementations do not implement complete sets of features and actions for a domain, and they are not comprehensive solutions. For example, the Mobile GSM solution provisions a limited set of features and actions for GSM 3GPP. Reference implementations provide starting points for you and facilitate system integration and solution development.

When developing and extending OSS solutions, begin with the following:

  1. Gain an understanding of the service domains.

  2. Identify the types of customer-facing services.

  3. Identify the actions that a customer can request for services on an order.

  4. Identify the input parameters of each action by determining information elements.

  5. Describe the steps in the business process for how each action is realized in the network.

    For example, describe the work that is performed and network elements that are configured.

  6. Identify the types of resources and resource facing services that drive the business process and realize the actions in the network.

  7. Describe the administrative policies and behaviors that determine how each resource is managed.

    For example, administrative policies might include capacity management, and behaviors might include the lifecycle, searching, and selecting an instance of a resource for use by a service.

  8. Describe how the resources can be organized in the inventory with respect to readiness for provisioning.

  9. Identify the interfaces and protocols for integration for steps in the business process that involve application integration not supported by the reference implementation.

Working with Design Patterns

In Design Studio, a design pattern is a template containing a set of resources that can be applied to a Design Studio workspace. During solution design, designers often create and configure complex sets of related entities and the relationships among them. When these complex sets of tasks are predictable and repeatable, the tasks are often documented in a standard set of guidelines or in a best-practice guide. These sets of tasks are referred to as design patterns because designers can use a template or an established pattern for reproducing the configuration.

You can use design patterns to deliver sets of preconfigured artifacts that serve some domain specific function. Design patterns enable you to formalize modeling patterns into reusable components that can be applied to various solutions.

For information about design patterns, see Design Studio Developer's Guide.

Working with Guided Assistance

Design Studio guided assistance is 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.

When working with guided assistance, you can review the learning aids delivered with Design Studio, and you can create your own and map them to projects and entities by using design patterns or by defining values for attributes directly in the guided assistance extension point.

For more information about guided assistance, see Design Studio Developer's Guide.

About Cheat Sheets

Design Studio supports cheat sheets, which refers to the integration of documented procedures with wizards in the application. Cheat Sheets are XML documents that can be interpreted by the Eclipse Cheat Sheet framework, and developers can map cheat sheets to specific points in the Design Studio user interface (for example, in editors and views). You access the cheat sheets that are relevant to current tasks, and complete those tasks uses the included instructions. Cheat sheets enable you to find documentation for relevant solution design procedures, and facilitate the learning of those procedures.

For example, you can use cheat sheets with design patterns to describe the resources added to a workspace, and to assist users with any manual steps required after a design pattern is applied. Cheat sheets are not mandatory for design patterns, but recommended.

You can develop and edit cheat sheets using the Eclipse Cheat Sheet editor.

See Design Studio Developer's Guide for more information about cheat sheets.