![]() ![]() By doing it together with my client, it is a good way to initiate communication and collaboration.The Actions that are more complex will be elaborated using a Business Process Flow Diagram. It helps me quickly understand the big picture of the requirements.I personally create a Use Case Diagram during my very first workshops or meetings together with key stakeholders of the current or future Dynamics 365 system.īelow the key benefits I get by creating a Use Case Diagram: Use cases are a powerful technique to help visualize high-level requirements very quickly. Or you can even use it to show the different areas covered in different releases. For example, you can create all the Use Cases and then use the system object to define the scope covered by each sub-system. This an optional element but useful when you’re visualizing large systems. A System (or Sub-System) : A system can be used to define the scope of the Use Case and drawn as a rectangle.The Use Case : A Use Case represents a function or an action done by an Actor within Dynamics 365.It can be a person, organization or another system. The Actor : An Actor is an object that has a role and performs an action in your Dynamics 365 system.To understand “what is the Use Case Diagram” it’s important to define each component of the Use Case Diagram: What is a Use Case Diagram?Ī Use Case diagram is a graphical representation of the interactions between an actor and a system. ![]() Knowing the answer to these questions can allow you to help the client to stay on the straight and narrow. What are the key success factors for the system?.What are the issues they are trying to solve to help them achieve that plan?. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |