![]() ![]() A use case that is “mission critical” => must be processed within five seconds. (Much controversy on ‘extends’ and ‘includes’ and use cases invoking use cases.(Later) > and > … Use Cases may also be stereotyped “Stereotyped element” has ‘special’ criteria. ![]() (built-ins) Now, special kinds of associations between Use Cases (later) Can be used to ‘increase relevance’ of model elements, such as use cases in requirements gathering. Stereotyping makes these different model elements!!!Ĥ Stereotypes in Modeling: Built-ins and User-DefinedĪssociations in Use Case Diagrams may be stereotyped as includes or extends. Most common UML stereotyped element is the class. Extend UML? Built in feature! extend UML for new ‘types’ New types of model elements! allows customization of models for project Stereotypes allow ‘refine’ / ‘reclassify’ ‘re-specify’ all model elements into a more specialized form rather than create additional symbols! Example: might specify a Use Case as a > or class name with the stereotype: > or > etc. Use Case Book (Chapter 2) and Visual Modeling BookĢ Use Case Diagrams… actor use cases Withdraw Money Transfer Money 1 Use Case Diagrams Use Case Descriptions ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |