Use Case diagrams can be used to show how the Use Case are related to other elements in the system, including up-stream elements such as Requirements and down-stream elements such as Components. The diagrams can be kept simple or they can be structured by the application of a number of additional connectors such as Include, Extend and Generalization relationships.Ī system Boundary can be included that is used to name the system, subsystem or entity under discussion the Actors lie outside the Boundary and the Use Cases inside. Use Cases will often act as the basis for the definition of Test Cases.Īny number of Use Case diagrams can be created to represent different parts of a system or Packages of Use Cases. They always describe the goal from the Actors' perspective, the details of the Use Case will describe the goal with more precision. The Use Case diagram is used to describe the goals that users or other systems want to achieve from interacting with the system. Ribbon: Design > Diagram > Add > UML Behavioral > Use Caseīrowser window Toolbar : New Diagram icon > UML Behavioral > Use Caseīrowser window context menu | Add Diagram. ![]() ![]() They are typically used in conjunction with higher level Business and Stakeholder Requirements and are often supplemented with a set of Non Functional Requirements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |