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




A general term for the things you can define in Design Studio, such as entities and data elements.


Oracle Communications ASAP equips telecommunications service providers with a single platform for automated service activation. ASAP receives service requests from any source and transmits the required service activation information to any destination network device.

ASAP's core architecture isolates business semantics (rules and behavior) from technology semantics (interface implementations and protocols). This architecture allows ASAP to handle multiple, heterogeneous network technologies and supports various interfaces.

base type element

A data element from which other data elements obtain attributes.

To increase modeling efficiency when modeling simple and structured data elements in Design Studio, you can create new data elements that derive from existing base types. Rather than referencing one of the primitive types (String, Boolean, Integer, and so forth), you reference another data element as their data type. In Design Studio, this is called deriving from a base type element, where the new element automatically obtains the information in the base element.

See data element for more information.


A process that updates existing resources and creates new resources. You run builds against projects to create or modify workspace resources. The type of project determines the type of build. For example, when you run a build for a Java project, the build converts each Java source file (.java files) into one or more executable class files (.class files).


A collection of entities and data defined in Design Studio and packaged in an archive file for deployment to a run-time environment. Cartridges are built in Design Studio in cartridge projects. They are compiled as archive files and then installed into a run-time server.

You can create your own custom cartridges to extend Oracle Communications applications. Additionally, you can obtain technology packs from Oracle that bundle cartridges containing data for particular technology domains, or obtain customized cartridges that support integration with other common applications.

cartridge project

A Design Studio project that contains a collection of application-specific entities and data. The collection of entities is packaged into an archive file, which you can deploy to a run-time environment.

Cartridge projects are the only Design Studio projects that are deployable to run-time environments.

cartridge designer

A person tasked with design of a deployable component spanning a single product domain. This person is considered an expert for a product in Oracle Communications and focuses on design in a single product domain. Some cartridge designers may be competent in this role for more than one product domain.

Cartridge Management Web Service (CMWS)

A Web service that enables lifecycle management of cartridge project (for example, deploy, undeploy, redeploy, and so forth).

clean build

A build that resolves any dependencies or similar errors from all previous build results. Clean builds update all resources within the scope of the build.

Data Dictionary

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.

data element

A structured or simple type data definition. When modeling data for a project, you create data elements that you can reuse throughout your model. There are two types of data elements: simple data elements and structured data elements.

See simple data element and structured data element for more information.

data modeler

A person responsible for designing the data types and structures necessary to support a cartridge or solution.

data schema

An XML schema that provides a formal description of a data model, expressed in terms of constraints and data types governing the content of elements and attributes.

All data elements are created and saved in data schemas, which can be accessible across all projects in a workspace. Design Studio automatically creates a project-specific data schema when you create a cartridge project. You can use this default schema to contain the data you require to model the project, you can create multiple schemas in the same project, or you can create schemas in common projects. You can model your cartridge project using data from any combination of these data schemas.

design pattern

A template containing a self-describing set of entities that can be applied to a Design Studio workspace. Solution designers use design patterns to deliver to end-users sets of pre-configured entities (and their relationships) that serve some domain-specific function. Design patterns enable you to create complex modeling patterns using a wizard. This approach reduces implementation time and effort.

Design Studio

An integrated design environment for the development of solutions based on the Oracle Communications OSS Applications. Design Studio enables solution designers to configure application-specific and multi-application solutions by leveraging application-specific concepts. Design Studio is built on an open architecture based on the Eclipse framework, and it uses a wide variety of innovative technologies.


An editor is a 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 open entities in editors at any time to modify existing projects and elements.


A functional unit created and edited in Design Studio; for example, tasks, processes, physical and logical resources, and projects. Entities are collected in a cartridge and deployed to run-time environments to support your business processes.


Values defined for data elements that are available for selection in a run-time environment. For example, you can define a set of values for data elements that appear as lists run-time environments.

environment project

A project that enables you to manage the attributes associated with your run-time environments, including connection attributes, projects ready to be deployed, projects previously deployed, and associated project attributes such as the version and build numbers.

extended entity

An entity with defined attributes that you leverage when creating new, similar entities. When you extend one entity from another, the target entity inherits all of the data elements defined for the extended entity. In Design Studio, you can extend orders and tasks.

Inherited data elements are read-only. If you extend an entity that includes structured data elements, you can add any number of additional simple and structured child elements.


A package of plug-ins that create a single, installable, and updatable unit. Features are delivered as JAR files, and each plug-in included in a feature is included as a separate JAR file.

Design Studio is a collection of features and plug-ins that you install with a single executable archive file. For example, the Design Studio Platform feature contains plug-ins for Oracle branding, online Help, and user interface functionality.


Operations that fulfill a customer's order, such as providing, modifying, resuming, or canceling a customer's requested products and services.

guided assistance

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.

incremental build

A build performed automatically in Design Studio when you save resources. You can disable incremental building and manually run builds if, for example, you want to finish implementing cartridge changes before building the project.


A file that can contain information about the files packaged in a JAR file. By editing information that the manifest contains, you enable the JAR file to serve a variety of purposes.

All Oracle Communications features have manifest file.


The data you model for order entities, specifications, or actions.

model project

A collection of data elements that can be referenced by other projects in a workspace. Model projects include business entities and schema entities that are not specific to any one Oracle Communications application and that enable you to leverage common definitions and share that data across a solution.

model variable

A variable that you create as a placeholder for environment-specific values that you will need at run time.

When you create cartridge projects, some of the information you provide may depend on a specific environment. If you have environment-specific values for variables that you will need at run time, you can create tokens for the variables and later define values for each environment in which you will use the variable. See token for more information.


An XML namespace is a method for uniquely naming elements and attributes in an XML document. Attributes and elements are identified by a fully qualified name that consists of a namespace name paired with the local attribute or element name.

Design Studio supports entity namespace as a method for uniquely naming entities across projects. Fully qualified entity names consist of a namespace name paired with the local entity name. Entity namespaces allow different work groups of Design Studio users to create different entities without concern for name contention. Services can be implemented independently by a different teams, then deployed into a single run-time environment.

Design Studio supports cartridge namespace as a method for uniquely naming Design Studio cartridge projects. This allows you to identify the cartridges deployed in an environment. For example, if you are diagnosing an order failure, it's useful to know the logic and configuration of the cartridge that processed that order. Fully qualified cartridge names consist of a namespace name paired with the cartridge name.

Network Integrity

Oracle Communications Network Integrity enables you to keep two data sources (such as an inventory system and a live network) synchronized. This improves data accuracy, which increases your service provisioning success rate. It enables better business planning, based on having an accurate view of your inventory, and supports scheduled or ad-hoc audits to ensure alignment of inventory with your network. Network Integrity can also be used as a convenient way to load initial network data into your inventory system.


A person responsible for managing a product run-time system, performing functions such as installing cartridges to production systems.

optimize deploy

Optimize deploy is a method of deployment that, when enabled, attempts to deploy only the changes you have made in your Design Studio cartridge project. For example, you can use optimize deploy when testing or debugging changes to your cartridge data.

Oracle Communications Design Studio for ASAP

A feature included in the Design Studio preconfigured installation that you use to define service actions, network actions, and scripts for service activation.

See feature for more information.

Oracle Communications Design Studio for Inventory

A feature included in the Design Studio preconfigured installation that you use to define service and resource definitions, rules, and domain-specific metadata.

See feature for more information.

Oracle Communications Design Studio for Order and Service Management

A feature included in the Design Studio preconfigured installation that you use to define solutions for OSS service order management and for BSS central order management, respectively.

See feature for more information.

Oracle Communications Design Studio for Order and Service Management Orchestration

A feature included in the Design Studio preconfigured installation that you use to define solutions for BSS central order management.

See feature for more information.

Oracle Communications Design Studio for Network Integrity

A feature included in the Design Studio preconfigured installation that you use to configure network discovery, assimilation, and reconciliation behavior.

See feature for more information.

Oracle WebLogic Server

Oracle's application server for building and deploying enterprise Java EE applications. The WebLogic server hosts the Design Studio application servers.


The process used to manage the fulfillment of a complex order. Order fulfillment often requires interaction with many fulfillment systems. Various dependencies may require that these interactions be run in a specific order to ensure that order items are sent to the proper systems, and that the required steps, in the proper sequence, are run.

Order and Service Management (OSM)

Oracle Communications Order and Service Management (OSM) coordinates the order fulfillment functions required to complete a customer order created in a customer relationship management (CRM) system, or other order-source system. As an order management system, OSM receives and recognizes customer orders and coordinates the actions to fulfill the order across provisioning, shipping, inventory, billing, and other fulfillment systems. OSM occupies a central place in order management solutions.


A portion of a user interface that you can collapse to hide or expand to display.


A defined set and layout of views and editors in the workbench window.

Perspectives determine how information appears in the workbench, in menus, and in toolbars. Each perspective contains a default set of views and editors, which you can customize. The Design Studio perspectives work together with other perspectives that are used for implementation, debugging, builds, and version control.


Modular, extendable, and sharable units of code that enable integration of tools within Eclipse. Each plug-in specifies its own dependencies and specifies the set of Java packages it provides. Additionally, plug-ins integrate with other plug-ins.

Plug-ins can be exported as directories or JAR files, shared among different applications, and grouped into features.


Persistent Object Modeling Service. POMS provides the modeling language, tooling, and framework for modeling entities, the relationship between entities and capabilities that entities have. POMS then generates the plain old Java objects (POJOs) that represent the entities and the relationships between the entities and persists them in a relational database schema.

POMS generates a Java interface as well as a Java implementation with the annotations required by JPA, specifically the EclipseLink JPA implementation, which is required for managing the persistence of the objects. The service also provides framework that provides methods for performing CRUD operations on the entities within a transaction.

The metadata that represent the modeling language is called Entity Relationship Model Language (ERML).


An entity that represents something that your business sells. Because Design Studio is primarily used for service fulfillment rather than sales, products are often identifiers associated with information from other systems.

project dependency

A state in which entities in one project reference entities in another project, creating a dependent relationship between the projects. For example, an application project might reference data elements defined in a common model project.


A set of processes that provide the data necessary for enabling a service, with the actual enabling done by activation.


The process of changing data elements without modifying the external functional behavior of a solution.

Refactoring in Design Studio enables you to propagate data model changes across the entire solution without sacrificing model integrity. You can rename, change the location of, copy, and move data elements. Additionally, refactoring enables you to copy data elements to create similar data entities, and to create modular and reusable data structures.

root data element

A data element found at the root of a schema entity. A root has no parent data element.

schema entity

An independent resource containing a set of data elements.


An entity that represents the way that a product is realized and delivered to a customer. For example, if you sell DSL Gold as a product, it is delivered as a DSL Gold service, enabled by appropriate resources.

service fulfillment

A business process in which a customer order is accepted and a new service is provisioned to meet it.

simple data element

A non-structured, reusable data type. A simple data element has no structure, and is associated to a primitive type (String, Boolean, Integer, and so forth). Simple data elements can be defined at the root of a schema entity or in a structured data element. A simple data element cannot contain any child elements.


A blueprint that defines the composition of an entity. There are different types of specifications for different types of entities, such as telephone numbers, networks, physical devices, and inventory groups. Specifications are defined in Design Studio and deployed into run-time environments, where entities can be created based on them.

solution designer

A person responsible for pulling a collection of cartridges together to deliver a multi-product solution; an activity that may involve the design of additional cartridges to perform the desired solution functions. The solution designer focuses on cross-product interactions, rather than on the details of a single product.

solution tester

A person who validates that a cartridge or solution is functioning correctly. The solution tester deploys cartridge archives, produced by Design Studio, to a test environment to certify that the cartridge or solution is functioning as intended.

structured data element

Complex data types that include embedded data types. For example, you might create a structured data element called building that contains the floor, room, aisle, rack, and shelf child elements.

Structured data elements can also contain other structured data elements. For example, a structured data element called person might contain the child elements firstName, lastName, and the child structured data element address.

technology pack

A bundle of cartridges created in Design Studio that collectively address a particular business need or technology. Oracle offers technology packs as products to cover particular technology domains.


A placeholder for environment-specific values that can be defined at the time of deployment.

Unified Inventory Management (UIM)

Oracle Communications Unified Inventory Management gives service providers a single, comprehensive, accurate view of customer services and maps these services to logical and physical resources, ensuring that trusted, actionable, real-time information is available to any business process for both current and next-generation services and technologies.


A presentation of information in the workbench. Views enable you to customize the manner in which information is presented, and provide 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.


A set of tools you can use to navigate within and manipulate the workspace, access functionality, and edit content and properties of resources.


A representation of your data. Workspaces are directories on your local machine that contain resources, including projects at the top of a tree structure and folders and files underneath. A workspace root directory is created internally when you create a Design Studio workspace. You can create more than one workspace, but you can have only one workspace open at a time.