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


2 Solution Development Methodology

This chapter describes solution development methodologies.

Working with Project Phases and Tasks

This section describes project phases and associated tasks that you can use during operations support systems (OSS) solution development. These example phases and tasks focus on service fulfillment scenarios.

This list is not intended to be prescriptive; it is provided as one part of a best practice approach to solution methodology.

  1. Inception

  2. Requirements Analysis

  3. Functional Design

  4. Construction

  5. System Test

  6. Deployment

  7. Maintenance

Inception Phase

During the inception phase, you Define the goals of the project.

Requirements Analysis Phase

During requirements analysis phase, you:

Functional Design Phase

During the functional design phase, you:


Proving at-risk aspects of the solution architecture can require that you perform some tasks in the functional design phase and construction phase concurrently, enabling the team to clarify requirements and evaluate design alternatives.

Construction Phase

During the construction phase you:

System Test Phase

During the system test phase you:


Complete test development in conjunction with the construction phase. Test development includes the development of tools or scripts for generating data, including installed base of subscribers, services, and resources, for example.

Deployment Phase

During deployment phase you:

Working with Document Artifacts

Table 2-1 lists an example set of document artifacts that your team can create and share among stakeholders during solution development. This list is not intended to be prescriptive; it is provided as one part of a best practice approach to solution methodology.

Table 2-1 Example Document Artifacts

Document Use


  • Defines the functional or business requirements the OSS system should meet.

  • Documents the requirements analysis phase conclusions.

Functional Specifications

  • Documents the services and actions to be supported.

  • Documents the use case for each service action and the flow through each application component (for example, through OSM, UIM, Network Integrity, and ASAP).

  • Documents the function that each application component should perform internally for each service action.

  • Documents any application extensions and business logic to be implemented.

Integration Specifications

  • Documents the integration architecture.

  • Documents each interface (for example, UIM to OSM and OSM to ASAP), the integration technology used, and the interface protocols.

Technical Design

  • Documents the list of cartridges to be developed or extended, and all the cartridge dependencies.

  • Identifies all major Design Studio entities, including UIM rulesets, OSM XQueries, ASAP CSDLs and ASDLs, and so forth.

  • Identifies all major Java classes and methods to be implemented to extend the solution.

Note: You can create one technical design document for each application component.

Test Strategy

  • Describes the testing methods to be used during solution development, such as unit testing, integration testing, and performance testing.

  • Describes the methods for testing environments, tools, and hardware.

  • Documents test metrics and measures to be used.

Test Cases

  • Describes the test cases for each test type (for example, for unit testing and integration testing).

Technical Architecture

  • Documents the technical architecture of the system implemented.

  • Documents the implemented integration architecture, including JMS resources.

  • Documents the environment specifications, such as hardware, operating system, and database specifications.

  • Lists all application components that require backup, such as WebLogic domains, database schemas, and application home directories.

User Guides, Administration Guides, and Online Help

  • Describe the documentation to support the solution.