Video – ‘Basics of data modelling – Part 1’

Capiro

The notation used in the video is a simple form of UML. Many analysts consider that UML is too technical and complex to be used for business modelling. This is not correct if UML is used appropriately. In common with most modelling notations , UML comprises mainly rectangles and lines. UML refers to artefacts such as attributes and various graphic devices as ‘adornments’. Just because something is available in the UML, it doesn’t have to be used.

The complete guide to business process modeling (2021 edition)

Monday

UML diagram. UML diagram. Here’s where UML comes in handy. UML stands for Unified Modeling Language, and it’s a modeling technique that helps you describe the elements that make up a specific software system and how such elements interact with each other.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Business Analyst Interview Audio Book

The BAWorld

The Key aspects of this book are: These questions cover a wide range of topics like Agile, Core BA skills, UML, User stories etc. We have launched our Business Analyst Interview Audio Book after releasing the paperback edition on Amazon.

UML 83

A Fireside Chat: Martial Arts, Magic and Business Analysis

Adrian Reed's Blog

I think we need to avoid getting so caught up in arguments over UML vs BPMN, or User Stories vs Use Cases that we lose sight of our actual stakeholders and the context that they operate in.

5 Recommended Tools for Running Virtual Workshops

Business Bullet

This enables you to draw out BPMN process flows, Wireframes, UML, Mind maps, Flow charts etc. I am going to share some of the tools and techniques I have used for running workshops and meetings virtually.

UML 81

Do Product Owners Need Technical Skills?

Roman Pichler

For instance, if you were responsible for a physics engine, then you would probably have to be able to program in C++, use UML, and apply the right software architecture and design patterns. How can you tell if you would benefit from having technical skills as a product owner? To answer this question, I find it helpful to look at how the role is applied.

UML 85

Boost business agility with Three + One

Capiro

If using the Unified Modeling Language (UML) , for example, the models in the lower rows will feature additional icons and ‘adornments’. Business agility. Business agility is the ability to rapidly but safely change in response to or in anticipation of changes in the external environment.

UML 52

Analytical Thinking and Problem Solving – Underlying Competencies for a Business Analyst

MindsMapped

Whereas, in a project dealing with data flows, using an activity diagram comes handy (provided the Business Users are comfortable with UML concepts). Analytical Thinking and Problem Solving. Business Analysis Book of Knowledge (or BABOK as it is widely known) is a book authored and published by IIBA (International Institute of Business Analysis). BABOK serves as a guide for the Business Analysts across the world.

UML 60

The complete guide to managing your business processes in 2021

Monday

UML diagrams. The term “business” refers to the organized efforts of individuals looking to turn a profit in exchange for a product or service. Though the profitability of a business lies not in selling the product but in the processes used.

UML 52

Underlying Competencies for a BA as per BABOK – Behavioral Characteristics and Business Knowledge

MindsMapped

For example, some stakeholders prefer visual representation (flowcharts, UML diagrams…) over textual format (use cases, tabular charts). Business Analysis – Underlying Competencies. In this article we cover the 2 nd and 3 rd aspects of the underlying competencies for a Business Analyst as per BABOK namely Behavioral Characteristics and Business Knowledge. Behavioral Characteristics. These characteristics are not unique to the role of a Business Analyst.

UML 40

Where I Think “Agile” is Headed, Part 4: What Does “Agile” Mean?

Johanna Rothman

I'm pretty sure I learned about UML drawings in the 80s. I started this series asking where “Agile” was headed. (I I didn't like what I saw at the Agile 2019 conference.) Part 1 was about the 4 big problems I see. Part 2 was why we need managers. Part 3 was about how people want a recipe. This part is about what “Agile” or “agile” means. I understand that people want what they perceive as the value “Agile” will bring them.

UML 51