Use Case Modelling

A business process is the combination of a set of activities within an enterprise with a structure describing their logical order and dependence, and whose objective is to produce a desired result. Business Process Modelling through use cases enables a common understanding and analysis of a business process.

This use case modelling workshop explores the subject of Business Process Modelling and creating the interaction between stakeholder and the system. The workshop commences with a definition of the Organisational and Business contexts, which enable the Business Analyst to understand the context within which they will operate (analyse). Both organisational and business contexts may be depicted graphically by way of models, the Business Process Model using use cases being a typical model utilised by the Business Analyst.

To assist the Business Analyst in constructing a model, or set of models, there are a number of tools, techniques and best practice approaches which have evolved globally within the IT industry. For our purposes, we will touch upon the Unified Modelling Language (UML) approach, and shall additionally introduce Business Process Modelling as two best practice approaches used within the analysis (and associated) domains, both in Australian and global organisations.

Workshop Objective

• Building upon fundamental business analysis concept with activities and workflows in line with the BABOK
• Introduction to Use Cases and their value to the organisation
• Understanding the key elements of use cases using endorsed tools and techniques
• Understand stakeholders, design scope using industry approved techniques
• UML overview and introduction to the commonly used symbols
• Developing a use case from Requirements documents and understanding associated risks

Who this course is for

• Business Analyst: Assist the BA in understanding the value of use case modelling and will enable them to construct a correct, concise and complete use case, which represents the current and future organisational (and business) environments, thereby enabling requirements elicitation to come alive, through use case process models.
• Solution Architect: Enable the Solution Architect to understand the business environment and future need, through a common use case ‘language’. The use case will additionally enable the Architect to map the process to physical system (and network) capabilities.
• Developers: Enable the technical team (including developers) to acquaint themselves with, and understand the ‘tools’ through which the business ‘need’ is established, and the use case are the requirements that have been elicited and analysed. Understanding this graphical ‘method’ will enable the technical team to recognise and speak the same ‘language’ as the BAs, and further assist them in reviewing BA documentation and working on the technical specifications.
• Project Manager: Enable the Project Manager to understand the documentation ‘standards’ adopted by Business Analysts, thereby enabling the PM to better review documentation, against the said  best practice documentation techniques.

In order to derive the greatest benefit from participation in this workshop, participants should be working in a business analysis environment or planning to do so in the near future. Students should have a general understanding of object-oriented analysis and design concepts. Students should have an understanding of the Business Analysis role and the responsibilities of a BA through the project lifecycle. Requirements understand and basic experience of the elicitation process.