ADPL - USE CASE MODEL (Kelompok 5)

Introduction

This tutorial will guide you through the process of creating a use case model, as presented by a group of students in their video. Understanding use case models is essential for effective system design and requirements gathering in software development. This guide will provide clear steps to help you create your own use case model effectively.

Step 1: Identify Actors

• Determine who will interact with the system.
• Actors can be users, other systems, or stakeholders.
• Create a list of all potential actors involved in the system.

Step 2: Define Use Cases

• Identify the key functionalities the system should provide.
• Each use case should represent a goal or task that an actor wishes to accomplish.
• Write a brief description for each use case, focusing on the purpose and outcomes.

Step 3: Develop Use Case Diagrams

• Use a diagramming tool (like Lucidchart or Draw.io) to visualize the interactions.
• Represent actors as stick figures and use cases as ovals.
• Connect actors to their corresponding use cases with lines to illustrate interactions.

Step 4: Detail Each Use Case

• For each use case, provide detailed descriptions including:
  • Title of the use case
  • Actor involved
  • Preconditions (what must be true before the use case can start)
  • Main flow (the typical sequence of actions)
  • Alternate flows (any variations from the main flow)
  • Postconditions (what will be true after the use case is completed)

Step 5: Review and Refine

• Examine your use case model for completeness and clarity.
• Ensure that all actors and use cases are accurately represented.
• Engage with stakeholders for feedback and make necessary adjustments.

Conclusion

Creating a use case model is a systematic process that requires identifying actors, defining use cases, and visualizing interactions. By following these steps, you can develop a comprehensive use case model that serves as a solid foundation for your software development project. Remember to refine your model based on feedback and keep it updated as project requirements evolve.