Business analysis practically

Everything starts with a joint analysis of the project assignment from the customer and clarification of requirements and needs. And then we will rush to propose a solution. We enter the basic set of requirements into the model, process the business domain, business processes, system use cases and the state diagram of the main business structure. We will create a component model and design the interaction of these components inside the system. Where appropriate, we will add validation rules and any communication elements (emails, letters, etc.). We connect everything correctly with sessions to maintain the necessary traceability. Each participant thus creates his own analytical model of a specific business case.

Be able to open Sparx Enterprise Architect, create a new project (.eap), create a new package and be able to create a diagram.
Know the concept of usecase, know the difference between a class and an activity.
We recommend taking the Business analysis of information systems course.

Everyone who:

• wants to do business analysis correctly
• wants to check if they are already doing it right
• is looking for good practical tips and tricks on how to do it
• hesitates how to go from drawing diagrams to modeling
• always wanted to know how business analysis is done and were afraid to ask

• Business domain modeling
• Business process modeling in the context of IS development
• Requirements modeling and description
• System modeling using Use Cases
• Screen modeling and screenflow
• Modeling of system components
• Modeling the interactions of system components

Create a system model independently in the CASE tool, including sessions for appropriate tracing and linking of elements. This training is intended for members of project teams who participate in the creation of IS and would like to finally try out how it is actually done :). Everything is modeled in UML and BPMN.