4 External Requirements

4.1 External Interfaces

REQ-EI-01-01: The API specification shall be compatible with the Javaä Platform v1.2 Core API Specification or later.

The added features of the new Javaä Platform v1.2 can be viewed at [http://java.sun.com/products/jdk/1.2/docs/relnotes/features.html]

 

4.2 Resource Requirements

 

REQ-RR-01-01: In order to execute the JAIN OAM Compatibility Test Suite, or a JAIN OAM application, the following shall be required:

  1. The JAIN OAM API specification is implemented over a JAIN compliant protocol stack or over the Reference Implementation.

  2. A Java Virtual Machine

 

4.3 Acceptance Test Issues

The acceptance test requirements are outlined in the Java Community Process (see [Reference 1]). The main Acceptance Test Requirements specified within the document include:

  • The API specification will be acceptable to the majority of participants of the JAIN OAM expert group and the Process Management Office (Sun Microsystems).
    •

  • All public comments as a result of a public review shall be read, considered, documented and if necessary incorporated into a new review of the API specification.
    •

  • API deficiencies shall be documented and made available to Sun Microsystems.

    •

 

 

4.4 Documentation Requirements

REQ-DC-01-01: The documentation shall be presented in HTML format.

The documentation supporting the API needs to be supplied with and in the same format as the API (HTML).

 

4.5 Portability Requirements

REQ-PO-01-01: A JAIN OAM implementation shall be considered compliant if a JAIN OAM application can run unchanged on both the JAIN OAM implementation and the JAIN OAM Reference Implementation.

The main aim of the JAIN OAM process is to provide portable JAIN OAM applications that will run over any SS7 stack, which is JAIN compliant.

 

4.6 Quality Requirements

REQ-QR-02-01: The JAIN OAM API specification development shall follow the Javaä Community Process.

The Javaä Community Process is Sun Microsystems’s process for developing API’s (see [Reference 1]).

 

4.7 Maintainability Issues

The maintainability requirements are outlined in the Java Community Process (see [Reference 1]). The main Maintainability Requirements within this document include:

  • The Interpretation Guru shall be responsible for ongoing maintenance in response to requests such as clarification, interpretation, enhancements and change requests by participants and the public.
    •

  • A change log should be made available via a public web site that lists all revisions made to the specification by the Interpretation Guru during maintenance.
    •

 

4.8 Compatibility Requirements

REQ-CR-01-01: A JAIN OAM Implementation shall be compatible after passing the CTS.

This will ensure that all JAIN OAM implementations can be tested to guarantee JAIN compliance. An implementation of the JAIN OAM specification will only be JAIN compliant if it passes the CTS. An acceptable standard will be set by the JAIN OAM Expert group, which will be used as a guideline with the CTS, of which JAIN OAM implementations must pass in order to be compliant.

 

4.9 Specification Deliverables

The specification deliverables are outlined in the Java Community Process (see [Reference 1]). The main Specification Deliverables Requirements within this document include:

  • A Javaä API specification shall be specified for JAIN OAM.

  • A Reference Implementation shall be developed to uncover areas of the API that are under-defined, incomplete or ambiguous.
    •

  • A Compatibility Test Suite shall be developed to ensure JAIN OAM specification compatibility.

  • A User Guide will be developed for the JAIN OAM specification. This will provide an overview of the JAIN OAM specification, a detailed description of the API and how its implementation can produce portable OAM applications.

    •

 

 

4.10 Constraints, Assumptions and Dependencies

 
  • The API specification will not restrict the Managed Objects (MOs) and Listeners to reside on the same Virtual Machine. This enables the JAIN OAM implementation to operate unrestricted in a distributed computing environment. There are many combinations of MOs and Listeners distributed over several Java Virtual Machines, however one possible configuration is shown in Figure 4.1.

Figure 4.1 - A possible solution of a distributed JAIN OAM Implementation

 
  • The API specification will provide the ability to reuse previously instantiated objects. This offers the capability of keeping object instantiation to a minimum, therefore maximizing performance.

  • As much as possible the focus of the JAIN OAM API Specification is on the management of the SS7 protocol, not the SS7 network.

  • The SS7 stack is already live and running, i.e. the start-up of the SS7 stack is outside the scope of this version of the JAIN OAM API specification. It will be handled in a later release of the JAIN OAM API specification.

  • The JAIN OAM API specification will support the other JAIN API’s from a developer point of view.

  • High Availability and Redundancy are outside the scope of this version of the JAIN OAM API specification. It will be considered in a later release.

 

If you have any comments on these webpages or content, please send them to:
JainOam@East.Sun.Com
Copyright - 1999 Sun Microsystems