reminder meeting today, and more detailed deliverable outlines

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Reminder of the meeting exceptionally set this afternoon (4pm PT), see email 8/18.

 

Here is a more detailed evolution from the initial description of three of the deliverables in the charter complement (~1 year ago), for agenda item #1:

 

 

Deliverable #1: eMAM – event Model,  Access and Management.

A specification defining a event representation and metadata along with the event store management primitives for supporting event-centric testing and monitoring.  

 

Mostly includes the "Event Board" section of former eTSL draft.

(a)- includes the set of predefined Event Header attributes, and their XML representation.

(b)- includes the rest of the Event XML object ("event properties", and the event "body" including referencing of external payloads)

(c)- include security aspects.

(d)- includes the Access promitives (Post, Catch). The Mask primitive has more of a Test Case semantics

(masking events for the rest of the execution of a test case instance) so not sure if that can be supported by the Event Board, which is not supposed to have test case knowledge)

(e)- note that the Catch (formerly "Find") has an advanced selection/correlation semantics. Should be a section on its own?

(f)- includes an Event board Management interface (?) (event removal...)

(g)- profiling of the event model for common events, e.g. SOAP messages, metadata documents...(e.g. XML container for these)

(or should these be parts of the "Use Cases" document?)

 

                                                                                          

Deliverable #2: eTSM - event-centric Test Scripting and (execution) Model.

A specification defining a test case execution model that supports both the testing and monitoring of message and business data exchanges, and the scripting language for defining and executing these test cases.  

 

Mostly addresses what is covered today in the "Test Case Scripting and Semantics"section of eTSL.

(a)- includes the Test scripting overall model and constructs (triggers, test/monitor Case, monitors / wkflow threads or the like, adapters...) including the underlying requirements it addresses.

(b)- includes the Test scripting language markup reference (short of the primitives defined in eMAM deliverable?)

(c)- includes the Test scripting execution detailed model (flow control, scope of variables, concurrency, event visibility: masking, temp events) and modes of execution: deferred vs live execution. Time management.

(d)- includes the profiling of eMAM Events for specific events automatically posted by the test engine (end of Test Case, tracing events, Errors, etc.)

 

 

Deliverable #3: eTSM Use Cases Document - A set of examples and use cases illustrating the use of above specification for testing or monitoring business exchanges based on (1) some business content standards, (2) some choreography standards, and (3) some specifications in the domain of SOAP messaging or others. This document may serve to illustrate requirements that have been addressed.

 

- should it include the "profiling"" of events (g) in eMAM deliverable?

- should it cover the scripting and best practices for LTS , as a model for monitoring/verifying all workflows?

- should it include "bindings" (events, scripting best practices) for specific process markups (BPEL, ebBP...)