[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [ubl-ndrsc] more input
Use cases are almost always written as plain text documents. Nothing elaborate. A use case diagram is only used to show the relationship among several use cases, and we don't need that at this point. I'd suggest a simple template for each use case: 1. Name of the use case (short and descriptive) 2. Assumptions or preconditions (before use case is invoked) 3. Sequence of actions Write the use case from the perspective of the person/system who is performing the actions (referred to as an Actor in use case jargon). ----- Original Message ----- From: "Eve L. Maler" <eve.maler@sun.com> > > >Re: Use cases. FWIW - If we do these as brief, informal, and text based, > >I can > >probably submit three or four different profiles. However, if we decide on > >semi-formal using UML notations and diagrams, I'll be stretched to get one > >done > >for next week. > > In that case, definitely submit away using text! > > Eve > --
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC