| 4 External Requirements |
  |
4.1 External Interfaces
REQ-EI-01-01: The API specification shall be compatible with the Java Platform
v1.2.2 Core API Specification or later.
The added features of the new Java Platform v1.2.2 can be viewed at http://java.sun.com/products/jdk/1.2/
4.2 Resource Requirements
REQ-RR-01-01: In order to execute the JAIN SIP Technology Compatibilty
Kit, or a JAIN SIP application, the following shall be required:
-
The JAIN SIP API is implemented over a JAIN compliant protocol stack or
over the Reference Implementation.
-
A Java Virtual Machine
4.3 Acceptance Test Issues
The acceptance test requirements are outlined in the Java Community Process.
See http://java.sun.com/aboutJava/communityprocess/.
The main Acceptance Test Requirements specified within the document include:
-
The API specification will be acceptable to the majority of participants
of the JAIN SIP 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 SIP application shall be considered compliant if it
can run unchanged on any JAIN SIP implementation and the JAIN SIP Reference
Implementation.
The main aim of the JAIN SIP process is to provide portable JAIN SIP applications
that will run over any SIP stack that is JAIN-compliant.
4.6 Quality Requirements
REQ-QR-01-01: The JAIN SIP API development shall follow the Java Community
Process.
The Java Community Process is Sun Microsystems’s process for developing
API’s. Seehttp://java.sun.com/aboutJava/communityprocess/.
4.7 Maintainability Issues
The maintainability requirements are outlined in the Java Community Process,
see reference [0]. 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 stack vendor’s JAIN SIP Implementation shall be compatible
after passing the TCK.
This will ensure that all JAIN SIP implementations can be tested to guarantee
JAIN compliance. An implementation of the JAIN SIP specification will only
be JAIN compliant if it passes the TCK. An acceptable standard will be
set by the JAIN SIP Expert group, which will be used as a guideline with
the TCK and which JAIN SIP implementations must pass in order to be compliant.
4.9 Specification Deliverables
The specification deliverables are outlined in the Java Community Process.
See http://java.sun.com/aboutJava/communityprocess/.
The main Specification Deliverables Requirements within this document include:
-
A Java API specification shall be specified for JAIN SIP.
-
A Reference Implementation shall be developed to uncover areas of the API
that are under-defined, incomplete or ambiguous.
-
A Technology Compatibility Kit shall be developed to ensure JAIN SIP specification
compatibility.
-
A User Guide shall be developed for the JAIN SIP specification. This will
provide an overview of the JAIN SIP specification, a detailed description
of the API and how its implementation can produce portable SIP applications.
4.10 Constraints, Assumptions and Dependencies
This API specification will not be dependent on any other JAIN API specification,
however it will be compatible with the JAIN OAM API. The JAIN OAM API may
handle the provisioning and management of the JAIN SIP API depending on
the vendor’s implementation of the API. The JAIN OAM specification is the
interface for the service provider to provision the network. Transmissions
rates, hardware characteristics, routing configurations, etc. are all covered
by the JAIN OAM specification.The API specification shall provide the ability
to reuse previously instantiated objects. This offers the capability of
keeping object instantiation to a minimum, therefore maximizing performance.
Copyright - 2000 Sun Microsystems
If you have any comments or queries, please mail them to JAIN-SIP-interest@sun.com