Software Requirements Analysis and Design ACS2913 PDF

ACS2913 Software Requirements Analysis and Design Instructor: David Tenjo USE CASE DOCUMENTATION AND MODELING THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 1  Use Brief Use...

ACS2913 Software Requirements Analysis and Design Instructor: David Tenjo USE CASE DOCUMENTATION AND MODELING THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 1  Use Brief Use case descriptions Documenting Use Cases We will learn to create detailed (Fully developed) use case descriptions later in the course THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 2 Use Cases and Brief Use Case Descriptions Brief use case description is often a one sentence description showing the main steps in a use case Typically the Use case description should include what action the user is intending to perform, and how data is affected internally in the system THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2024 3 ©2016. Cengage Learning. All rights reserved.  RMO CSMS Project Use Cases Try to come up with Brief use case descriptions for these!! THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 4 ©2016. Cengage Learning. All rights reserved.  RMO CSMS Project Use Cases THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 5 ©2016. Cengage Learning. All rights reserved. Use Case Diagrams Use case diagram— a UML model used to graphically show uses cases and their relationships to actors UML: Unified Modelling Language, the standard for diagrams and terminology for developing information systems Actor is the UML name for an end user Automation boundary— the boundary between the computerized portion of the application and the users who operate the application THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 6 ©2016. Cengage Learning. All rights reserved.  Use Case Diagrams Symbols THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 7 ©2016. Cengage Learning. All rights reserved. Use Case Diagrams Draw for each subsystem THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 8 ©2016. Cengage Learning. All rights reserved. Use Case Diagrams Draw for a single actor, such as customer THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 9 ©2016. Cengage Learning. All rights reserved. Use Case Diagrams Draw for internal RMO actors THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 10 ©2016. Cengage Learning. All rights reserved. Include Relationship In a system, there are typically main use cases that represent primary functionalities. For example, in an online shopping system, "Make a Purchase" and "View Shopping Cart" could be main use cases. The include relationship could be used: to simplify large use case by splitting it into several use cases, to extract common parts of the behaviors of two or more use cases. THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 11  The "includes" relationship is a way to modularize and reuse common functionalities across different use cases. Example: Main Use Case 1: "Make a Purchase" Main Use Case 2: "View Shopping Cart" relationship Both these main use cases require the functionality of "Calculate Total Price." Instead of duplicating the same steps in both use cases, you can create a separate use case called "Calculate Total Price" and include it within the main use cases using the "include" relationship. THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 12  Use Case Diagrams— The relationship A relationship between use cases where one use case is stereotypically included within the other use case— like a called subroutine. Arrow points to subroutine Include relationship between use cases is shown by a dashed arrow with an open arrowhead from the including (base) use case to the included (common part) use case. The arrow is labeled with the keyword «include». THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 13 ©2016. Cengage Learning. All rights reserved. More examples Checkout use case includes several use cases - Deposit Funds and Withdraw Cash use cases Scan Item, Calculate Total and Tax, and include Customer Authentication use case. Payment THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 14  Use Case Diagrams: Steps 1. Identify all the stakeholders and users who would benefit by seeing a use case diagram 2. Determine what each stakeholder or user needs to review in a use case diagram: each subsystem, for each type of user, for use cases that are of interest 3. For each potential communication need, select the use cases and actors to show and draw the use case diagram. 4. Carefully name each use case diagram and then note how and when the diagram should be used to review use cases with stakeholders and users THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 15 ©2016. Cengage Learning. All rights reserved.  Summary Brief use case descriptions are written for use cases The use case diagram is the UML diagram used to show the use cases and the actors The use case diagram shows the actors, the automation boundary, the uses cases that involve each actor, and the relationship. A variety of use case diagrams are drawn depending on the presentation needs of the analysis THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 16 ©2016. Cengage Learning. All rights reserved.