EDOC 1.0 NO IDEA Avatar
  1. OMG Issue

EDOC — EDOC Issue: Document Structure

  • Key: EDOC-64
  • Legacy Issue Number: 5272
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Cory Casanave)
  • Summary:

    Issue: The EDOC Document is not well structured for the user. The document
    contains multiple sub-specifications that are of interest to different
    people at different parts of the development process and supply chain. In
    addition, the paragraph numbering is not unified across the document. The
    result of this is that someone interested in, say, events will have a very
    hard time finding it and will probably be confused by the other viewpoints.

    Suggested Resolution: Each section of the MDA document should be a separate
    document, the first document (Currently chapter 2) already talks about how
    these sections relate and could easily be altered to reference stand-alone
    documents using URL pointers. The formal response section (Chapter one) is
    not of interest to a user and should be excluded.

    The suggested document list is;

    EDOC Profile (Current Chapter 2 plus glossary and references)

    The Enterprise Collaboration Architecture overview (3.1)
    ECA Component Collaboration Architecture (3.2)
    ECA Entity Profile (3.3.)
    ECA Events Profile (3.4)
    ECA Business Process Profile (3.5)
    ECA Relationships Profile (3.6)
    ECA Patterns Profile (4)

    EDOC Technology Profile overview
    EJB and Java Metamodels (5.1)
    Flow Composition Model (5.2)

    UML Profile for MOF (This may be moved to MOF).

  • Reported: EDOC 1.0b1 — Wed, 8 May 2002 04:00 GMT
  • Disposition: Resolved — EDOC 1.0
  • Disposition Summary:

    see above

  • Updated: Fri, 6 Mar 2015 23:14 GMT