Advertisement

BT Technology Journal

, Volume 23, Issue 3, pp 111–120 | Cite as

OSS through Java — a standards-based approach to integration

  • J. Hardwicke
  • B. Naughton
  • P. E. Holmes
Article

Abstract

Designing application programming interfaces (APIs) for reuse is a balance between making an API easy to use while ensuring that it is generic enough to support a range of client requirements. This is easier to achieve in theory than practice, requiring in-depth knowledge of the business domain and implementation technology.

The OSS through Java™ (OSS/J™) Initiative comprises equipment vendors, independent software vendors (ISVs) and system integrators (SIs) that are producing a practical set of Java 2 Platform, Enterprise Edition (J2EE™) based APIs designed to support the business and technology goals of a telecommunications service provider.

This paper overviews the work of the OSS/J Initiative and evaluates the likelihood of it being adopted and reused as the standard practice for operational support systems interfaces.

Keywords

Human Computer Interaction Application Programming Interface System Interface Telecommunication Service Implementation Technology 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Java 2 Platform, Enterprise Edition (J2EE) — http://java.sun.com/j2ee/Google Scholar
  2. 2.
    Java community process — http://www.jcp.org/Google Scholar
  3. 3.
    OSS through Java Web Services Integration Profile (WSIP) — http://www.ossj.org/learning/docs/wp_ossj_wsip.pdfGoogle Scholar
  4. 4.
    Deployment strategies focusing on massive scalability — http://www.ossj.org/learning/docs/wp_massive_scalability.pdfGoogle Scholar
  5. 5.
    OSS/J common API — http://java.sun.com/products/oss/downloads/jsr144_downloads.htmlGoogle Scholar
  6. 6.
    OSS/J design guidelines — http://www.ossj.net/downloads/design_guidelines.shtmlGoogle Scholar
  7. 7.
    eTOM® — http://www.tmforum.org/browse.asp?catID=1647Google Scholar
  8. 8.
    OSS/J roadmap — http://www.ossj.net/downloads/docs/wp_ossj_api_roadmap_2.0.pdfGoogle Scholar
  9. 9.
    OSS/J core business entities — http://www.ossj.net/learning/docs/wp_cbe_concepts.pdfGoogle Scholar
  10. 10.
    NGOSS Shared Information/Data (SID) model — http://www.tmforum.org/browse.asp?catID=1684Google Scholar
  11. 11.
    OSS/J XML tooling — http://www.ossj.org/learning/docs/webseminar_xmltooling.pdfGoogle Scholar
  12. 12.
    Xdoclet — http://xdoclet.sourceforge.net/xdoclet/index.htmlGoogle Scholar
  13. 13.
    Multi-Technology Operations System Interface (MTOSI) — http://www.tmforum.org/browse.asp?catID=2319Google Scholar
  14. 14.
    OSS/J certified products — http://www.ossj.org/products/certified_products.shtmlGoogle Scholar

Copyright information

© British Telecommunications plc 2005

Authors and Affiliations

  • J. Hardwicke
  • B. Naughton
  • P. E. Holmes

There are no affiliations available

Personalised recommendations