Dynamic Model Agenda June 21 2007

Thursday, June 21st

(Q1) 9:00-10:30 am EST

Inventory of where we are with the dynamic model

• We will try to compile a comprehensive list of needs and issues with the current behavrior modeling.
• UML Activity diagrams were deemed too complex when they were suggestes as a means for documenting system behavior

(Q2) 11:00-12:30 am EST

Services and Application roles

• In this session we will discuss how we relate operations (in interfaces) to interactions.
• Map our interaction concepts to operations and interfacesrespectively
• The common denominator between service specifications and application roles may be to represent both as interfaces

(Q3) 1:00-2:30 am EST

Identify artifacts that will affected by changes to dynamic modeling notation, style guide, or methodology.

• Documenting and specifying complex interaction patterns
• Look for consensus on the mapping developed in the previous session

(Q4) 3:30-5:00 am EST

Complex interaction patterns

In this session we will look at some concrete examples

• Service orchestration vs. choreography
• We will not go into the solution for run-time representation of system (e.g. WS-CDL, WS-BPEL).
  • We will focus on the design time representation of interfaces not at the runtime realization.

Friday, June 22nd

(Q1) 9:00-10:30 am EST

Develop approaches to "make it real"

• The methodology will be linked back to the product lifecycle management project in the HDT
• Select the notation

(Q2) 11:00-12:30 am EST

Open session