MHonArc v2.4.5 -->
















emergency-msg message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Notifications, Messages and Methods Meeting Minutes




From: CSubatch@eteam.com
To: emergency-msg@lists.oasis-open.org
Date: Tue, 6 May 2003 16:11:39 -0700






EM TC
Notifications, Messages and Methods Subcommittee
May 6th, 2003
 
Attendees:
Art Botterell
Joyce Kern
Walid Ramadan
Nasseam Elkarra
Gary Ham
Eliot Christian
Rex Brooks
Cathy M Subatch
 
Meeting Notes:
 
CAP Requirements Documents
Art send out draft of CAP requirements document for comments.  Updated with Eliot's comments.  No other concerns or issues on document so motion was made to advance to the TC level.  Art will put on the TC website for comments and consideration of entire TC.
 
Use Cases
Next step is use cases - not sure how to document
Gary - use cases can go from detailed specs to simple set of steps that the user does. We should document existing user cases.
Art - current field cases probably not best use cases.  CAP has UML models but not use cases.  Three applications/general use cases:
  
Input side - such as data fusion application
  
Output side - push a button and warning devices are activated
  
Upstream - situational awareness
Eliot - Need to put human's judgement into the loops for input and output.
Gary  there are two types of use cases:
  
 Development Use Case is written with the purpose of how the   use interacts with system.  The developer should be able to match the   design to the requirements (traceability tool)
  
Business Use Case - broader/defines goals want to establish.  Written   around the architecture.
In summary:
  
Need use cases with input/output with human interaction and input/output   without human interaction.
  
Use cases should be short and terse - paragraph in length  
  
Use non-creative language (for same object use same language)
  
Use step-by-step description
  
Keep track of alternative flows
  
Should be directly traceable to requirements in requirements documents
Everyone in SC is encouraged to draft one use case and mail it to SC mailing list (emergency-msg@lists.oasis-open.org)
Next Meeting
The next meeting is Tuesday, May 13th at 1pm EDT/10am PDT 
 
Dial in Number = 1.800.453.7412     Access Code = 604776
 
 
Cathy M. Subatch
E Team Inc.
818.932.0660 x248
310.770.6885 (mobile)
csubatch@eteam.com





Follow-Ups:

Question for the group
From: Art Botterell <acb@incident.com>








[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]