This post extends a previous post that introduced viewing a business architecture capability/outcome graph as a finite state machine – FSM, and
The Business Architecture Core Metamodel – BACM uses the term “outcome” to label and name a concept in business architecture. Our purpose
In the previous posts, we illustrated how business architects can model dynamic value streams using outcomes as entry and exit criteria for
Unpacking Value Stream Stages and Adding Capabilities In the previous post, we saw how outcomes can be used to link together the
Turn your business architecture into a behavioral model and unlock its potential for analysis projects.
Value streams represent delivery of value to a customer or stakeholder in stages. Value stream stages represent dynamic business behaviors; stages may be skipped or repeated.
Analyzing and improving business processes is a fundamental practice of business analysts, but until recently, the role of business process modeling and
A business of any size will have invested in creating models of business structure (e.g. organization charts, application portfolios) and behavior (e.g.
