[Bug 223] New: Consistency of specification approach

[bugzilla-daemon@arjuna.com]

http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=223

           Summary: Consistency of specification approach
           Product: WS-Context
           Version: 1.0
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Text and diagrams
        AssignedTo: ws-caf@lists.oasis-open.org
        ReportedBy: tony.fletcher@choreology.com
         QAContact: mark.little@arjuna.com


Section 4 ‘Context Manager’ has a ‘message direction’ diagram (Figure 8) but no
specification of the allowed message sequencing.  In contrast Section 5 ‘Context
Service’ has no ‘message direction’ diagram but does have an overall ‘state
flow’ (Figure 10) and an incomplete specification of the allowed message
sequencing in the form of a state chart (Figure 12).

Suggestion:  For each service / interface provide a full state chart or table
which specifies the allowed sequencing of all the messages.  If the sequencing
is very simple (such as any request message may be sent in order independent of
previous history) then this should be stated, together with the allowed
response(s) to each request message.

More generally, I suggest that all of the CAF family of specifications are
consistent in the approach and each has the same outline, set of diagrams, state
tables, state charts and so forth.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.