UML modelling is used to provide visual representations of business analysis information from different viewpoints. BAs use these representations to communicate requirements by depicting boundaries for business domains, business processes decomposed into activities, user interactions with systems, data relationships among objects, etc.Models are essential to communicate complexity to business and technical stakeholders and following the UML standard notation enables BAs to collaborate in the same project and reutilize models efficiently.
Leverforce SAAS supports two features to import information directly from the Modelio and Enterprise Architect UML tools:
Import Use Cases: Use Cases constructed in the modelio UML tool can be imported as use cases in Leverforce and linked automatically to a model record in the CRM. The feature imports all descriptions, exceptions, conditions and constraints from the UML model.
Import Use Cases, Classes and Actors: Besides importing all use cases,the classes and actors constructed in the Modelio UML tool are also imported to Leverforce as model elements. These can be used by the BA to maintain glossaries that can be shared across projects.
BA Video Tip: Importing Models from Modelio
Producing a visual representation of a business process is an effective technique to provide context to the concerns or needs business owners express during requirements workshops.
The video clip below demonstrates how business analysts can save time and effort in documenting elicitation results by importing model elements to Leverforce from Modelio. The technique shown is the use of SIPOC in conjunction with UML activity diagrams to structure requirements in a business process context.
Below is a list of Business Analysis activities when we use UML modelling during Project Initiation:
PROJECT INITIATION SERVICE
Below is a list of Business Analysis activities and how we use Modelio software to carry them out during the Project Initiation:
Prepare for Elicitation (BABOK® 4.1)
UML Model: Prepare use case, activity, class and other UML diagrams to gather insights from stakeholders during elicitation activities
Conduct Elicitation (BABOK® 4.2)
UML Model: Use modelling to walk stakeholders through a representation of the business problem being analyzed
Define Future State (BABOK® 6.2)
Activity Diagram: Share activity diagrams of decomposed business processes in order to identify opportunities for improvements or risk mitigation
Use Case Diagram: Share use case diagrams that model the scope of the required changes
Specify and Model Requirements (BABOK® 7.1)
Activity Diagram: Prepare a visual representation of the activities carried out by users when interacting with systems
State Diagram: Prepare a visual representation of how data objects will transition states in a sequence of system events
UML Model: Analyze, synthesize, and refine elicitation results into UML models that express different view points of requirements
Class Diagram: Prepare a visual representation of how data objects are associated in systems
Sequence Diagram: Prepare a visual representation of the sequence of interactions between users and systems
Use Case Diagram: Prepare a visual representation of users interacting with systems
Define Design Options (BABOK® 7.5)
UML Model: Use UML Models to collaborate with solution architects and implementation experts in the definition of a HL design of the technical components of the solution