Requirements Overlap & Gaps

[Mike Rawlins <rawlins@metronet.com>]

Folks,

To fix some of the overlaps and gaps in requirements,  I propose the
following changes and additions to the latest draft of the Requirements
Spec.  These will be incorporated in our next draft unless we receive
comment Monday.  If you want to make changes after the draft is
released, you may submit them during the two week comment period.

In the BP section, after the "Provide a Process..." bullets

NOTE:   This process will be developed in coordination with the process
for identifying ebXML Core Components

In the Architecture Section:

Strike the following:

o Support and represent business processes independent of the technical
solution
o Provide and support a library of common, standard intra-business
processes

Replace with:

o  Specify the roles, interactions, and interfaces among the various
ebXML specification components such as the business process meta-model,
core components, registry and repository, and message transport routing
and packaging

Add:

o  Design guidelines for ebXML compliant messages

[NOTE:  There seems to be some discussion about whether or not the
Architecture team has taken responsibility for this item, but I suggest
we put it here for now even if some other team does it later.  I think
it clearly is a deliverable].

Add the following in asterisks:

o *In coordination with BP process specification and core components
identification, * provide for naming conventions for technical and
business content in the technical architecture

-------------------------------------------------------
Mike Rawlins, ebXML Work Group, Requirements Project Team Leader
http://www.ebxml.org/working/project_teams/requirements/
Mirrored at: http://www.metronet.com/~rawlins/ebXML