requirementsmodelingandusecasediagrams

requirementsmodelingandusecasediagrams内容摘要：

name below the stick man – The UML standard allows for the option of using a class rectangle with the stereotype 171。 actor187。 C o m m a n d E n dIt e m H a r d w a r eU s e r171。 actor187。 Sensor Stereotype Use Case Diagram Rules  The only valid relationship between an actor and another actor is generalization U s e r S u p e r U s e rR u n A p p l i c a t i o n s I n s t a l l A p p l i c a t i o n sA U s er c an R un A p pl i c at i on s .A S up e r U s e r c a n I n s tal lA pp l i c a ti on s an d R unA pp l i c a ti on s , s i nc e a S u pe rU s e r i s a s pe c i al i z ati o n o fU s e r.Use Case Diagram Rules  Use only the following relationships between use cases – Use the include relationship to show that the behavior of one use case is wholly and unconditionally used in another use case – Use the generalization relationship to show that a use case is a specialization of another use case Use Case Diagram Rules  the include relationship P e r f o r m T r a n s a c t i o nS e n d C o m m a n d R e c e i v e R e s p o n s eA p p l i c a t i o n玦 n c l u d e ? 玦 n c l u d e ?T h e P e r f o r m T r a n s a c t i o nu s e c a s e i n c l u d e s t h ep r o c e s s i n g s p e c i f i e d b yb o t h t h e S e n d C o m m a n da n d R e c e i v e R e s p o n s eu s e c a s e s .Use Case Diagram Rules  the generalization relationship V a l i d a t e I d e n t i t y I d e n t i f y b y f i n g e r p r i n t s c a nI d e n t i f y b y r e t i n a l s c a nI d e n t i f y b y b a d g e s c a nC u s t o m e rUse Case Diagram Rules  Use the extend relationship to show that one use case conditionally augment (or extend) the behavior of another use case. Example of Extends relationship Use Case Diagram Rules  Extension points for a base use case are identified within the specification of that base use case  These are the locations where another use case may extend the base use case. These extension points are optionally shown in a diagram by listing them in a partment of the base use case bubble under the heading “extension points  The extending relationship identifies, within parenthesis, the extension point(s) in the use case being extended L o g I ne x t e n s i o n p t : :S e t P r i v i l e g e sU s e rG r a n t A d m i n i s t r a t o r P r i v l e d g e s e x t e n d s ( S e t P r i v i l e g e s )[ A d m i n i s t r a t o r L o g i n e v e n t ] ]Identify, within brackets, the condition under which the extension is executed Example of Extends, includes, and generalization relationships Use Case Diagram Rules  There must be one extension point listed for each segment identified in the extension use case  Although considered optional, it is remended that the extending relationship also identify, within brackets, the condition under which the extension is executed Use Case Diagram Rules Use Case Packages  Use cases are often written and anized in layers of abstractions using Use Case Packages  A use case package contains a number of actors, use cases, their relationships, and perhaps other packages A Use Case Package Use Case Diagrams and Packages L o g I ne x t e n s i o n p t : :S e t P r i v i l e g e sU s e rG r a n t A d m i n i s t r a t o r P r i v l e d g e s e x t e n d s ( S e t P r i v i l e g e s )[ A d m i n i s t r a t o r L o g i n e v e n t ] ]Use the system Use case package outline  Review of development phases and UML Development – Overview  Requirements Engineering and the Requirements model  Introduction and importance of Use Case Diagrams  Use Case Diagram Rules  Examples of Use Case diagrams  Requirements Elicitation Process 1. Identify Actors 2. Identify Scenarios 3. Identify Use Cases 4. Refine Use Cases 5. Identify Relationships between actors and Use Cases 6. Identify Initial Analysis Objects 7. Identify Nonfunctional requirements Examples of Use Case Diagrams Example 1: Medical Clinic Software, could be missing use case relations Each usecase is described further by textual document and by Scenarios developed using UML sequence diagrams Example 2: ECommerce Application (Inplete) Missing a link between “Place Requisition” and “Supplier” and missing use case relationships C u s t o m e r Su p p l i e rB a n kB r o w s e C a t a l o gC o n f i r m Sh i p m e n tP r o c e s s D e l i v e r y O r d e rSe n d I n v o i c eP l a c e Re q u i s i t i o nC o n f i r m D e l i v e r y Example 3: Coffee Maker, “waiting state” Not a good name for a usecase (bad example) Example 4: Anesthesia System (Inplete) Example 5: Automated Air Traffic Control System (AATCS) Example 6: Use case diagram of the Internal Thermal Control subsystem (NASAISS project) Showing probabilities of use cases S e t t i n g _ 1 S e t t i n g _ 2 S e t t i n g _ 4。