Dear Core Component Team Members,
Below is the BP Team's Project Plan (work-in-progress) for the Vienna PoC.
There are some dependencies on Core Components and, furthermore, the Core
Components team may want to drive the aspects of the PoC that deal with
business document specification, schema constructions, domain components,
core components, and Context.
Version 5.6 of the PoC specification can be found at:
http://lists.ebxml.org/archives/ebxml-poc/200104/msg00007.html
The BP team will be discussing the Viena PoC this Wednesday at the BP/CC
Analysis Team conference call. CC members interested in actively
participating in the PoC are welcome to attend. Remember the PoC mantra
that "ideas are fine; but, commited bodies are resources are listened too."
The agenda for this Wednesday's call:
8 AM PST - BP Document Status
9 AM PST - Vienna PoC.
Note that if the BP Document Status goes quicker than expected, we will get
started with the Vienna PoC. However, we will save the discussion of CC
related items until after 9 AM.
Call In Information:
Date: Wednesdays
Start Time: 8 AM PST
Duration : 2 hours
Toll Free Number: 877-939-5307 (18 lines)
USA Toll Number: +1-712-237-3264 (2 lines)
PASSCODES 266233#
-----Original Message-----
From: Hayes, Brian
Sent: Saturday, April 07, 2001 11:20 AM
To: ebXML-BP (E-mail)
Subject: BP Team PoC Project Plan
Here's my first cut at a project plan for the BP deliverables in the Vienna
PoC. This is based on version 0.56 of the PoC specification. Everything is
negotiable; but, lets get a general understanding ASAP. Also note that we
can phase in functionality -- but there's not much time.
Integration Availability Date is the date that the item must be available
for general integration. It does not need to have all functionality, it
just needs to be able to integrate with other components. Some dates may be
obvious based on the ebXML Timeline for documents and based on the PoC
team's face-to-face meetings.
Item: Business Process Editors
* Description:
There are two versions of the Business Process editors (small e).
The first is the primarily forms based editor that Nita demostrated in
Vancouver at the lunch-and-learn. We usually refer to this as the Business
Proces Editor or BP Editor. The second is the diagram based editor from
MEGA International as demonstrated by Antoine at X12 Seattle. Both types
are business process editors (small e).
* Basic Functionality:
A business process editor SHALL be able to connect to a business
library to retrieve and submit business process specifications (and business
collaboration specifications and business transaction specifications). A
business process editor MAY be configured with a local repository of
"out-of-the-box" specifications. A business process editor SHALL allow a
user to create new business process/collaboration/transaction specifications
and SHALL allow a user to modify an existing one.
* Lead(s): Nita Sharma (forms based BP Editor), Antoine Lonjon
(diagram based BP editor)
* Team members:
* Integration Availability Date: TBD (need to integrate with the
reg/rep implementation)
* General Availablity Date: TBD
* Dependent On:
* DO1: Registry/Repository implementation
* DO2: Business rocess specifications.
* Dependent To:
* DT1: CPP and CPP
* Issues:
* I1: Availability of reg/rep implementation
* I2: Development resources for the forms-based BP Editor
* I3: Reg/Rep metamodel for BP artificats
* I3: Availablity of business process specifications
* I4: What are the rules about the software? E.g. The Tokyo PoC was
distributed on CD in Vancouver.
* Assumptions: None
Item: Document Specification Editor
* Description:
A tool that allows for worksheet based creation/editing of business
document specifications.
* Basic Functionality:
A business document editor SHOULD be able to connect to a business
library to retrieve and submit business document, business object, and
domain components, and core component specifications. A business document
editor MAY be configured with a local repository of "out-of-the-box"
specifications. A business document editor SHALL allow a user to create new
business documents, business objects, and domain component specifications
and SHALL allow a user to modify an existing one. A business document
editor SHOULD take into account contextual context values obtained from
business process specifications.
* Lead(s): TBD
* Integration Availability Date: TBD (need to integrate with the
reg/rep implementation)
* General Availablity Date: TBD
* Dependent On:
* DO1: Registry/Repository implementation
* DO2: Business rocess specifications.
* DO3: Core Component specifications.
* Dependent To:
* DT1: TBD
* Issues:
* I1: Who is responsible for this? BP or CC team?
* I2: Do we want this type of editor, or a drag-n-drop diagram based
editor, or do we want a simple schema editor? or all three?
* Assumptions: TBD
Item: Drop-Ship Business Process Specification
* Description:
Assume that we can re-use what we have already created -- See
section 8.4 (?) in the Catalog document.
* Basic Functionality:
* Lead: David Welsh
* Team members: Bob Haugen, others interested in modeling
* Integration Availability Date: TBD (needed by Business Process
Editor)
* General Availability Date: TBD
* Dependent On:
* DO1: Analysis Worksheets
* DO2: Core Components
* Dependent To:
* DT1: Business Process Editor
* DT2: CPP and CPA
* DT3: Core Components
* Issues: None
* Assumptions: None
Item: ebXML Business Process Specification Schema
* Lead: Karsten Riemer
* Integration Availability Date: TBD (needed by Business Process
Editor)
* General Availability Date: April 23, 2001 (based on ebXML document
timeline)
* Dependent To:
* DT1: Business Process Editors
* DT1: CPP and CPA ?
* Issues:
* I1: Completetion of Schema
* Assumptions: None
Cheers,
Brian Hayes
Commerce One. +1 (925) 520-4498
------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-bp-request@lists.ebxml.org