While many organizations have adopted The Decision Model, others are actively exploring how it may improve or totally replace their current business rules approaches. The latter are asking the critical question:
How is The Decision is Model different from what we are doing and why are these differences important?
(How to Recognize, Classify, and Validate Common Logic Structures)
It is not by accident that all decision models look similar. The similarities reflect the rigor of The Decision Model principles, the most important being mandatory adherence to Decision Model First Normal Form. These similarities are useful because they make it easy for people to understand and validate decision models, as there is only one way to interpret one. This is a major advantage of The Decision Model over other approaches for representing business logic.
However, this month we focus, not so much on the similarities among decision models, but on their differences. More than that, we explore the idea of classifying decision model structures based on differences in their logic.
Below, Part 1 summarizes the similarities among decision models. Part 2 does the same for their differences. Part 3 introduces three fundamental Rule Family classifications so you can recognize them and use them for validating business logic.
The number of successes with The Decision Model is escalating. Organizations are using The Decision Model to solve a range of business challenges and opportunities including some we did not expect. Therefore, this month we summarize three real world projects to illustrate how organizations are using decision models and how quickly project teams are delivering them.
This article assumes knowledge of the Decision Model.
This article assumes knowledge of the Decision Model.
This article assumes knowledge of the Decision Model.
(This article assumes knowledge of The Decision Model.
The purpose of this article is to provide project managers and business analysts an example of a hybrid system development life cycle (i.e., combination of agile and waterfall). Much discussion has transpired on the virtues of agile and waterfall approaches. Successes and failures can be claimed on both sides. Depending on the conditions of the project, advantages of one approach can be cited over the other. So enters the Hybrid SDLC that considers both approaches for all or portions of the project.
Software engineering is a much younger discipline than are other branches of engineering. We see this in the continuing evolution of attitudes and approaches to requirements. In early days, there were no requirements. In later days, there were volumes of approved textual statements. Eventually, there were formal models. Today, sometimes models and statements are merely interim deliverables because code becomes the requirements.
This article assumes knowledge of the Decision Model. If you are not already familiar with the theory of the Decision Model you can download a brief primer from www.TheDecisionModel.com.)
Everyone starts here.
You're looking for a way to improve your process improvement skills, but you're not sure where to start.
Earning your Business Process Management Specialist (BPMS) Certificate will give you the competitive advantage you need in today's world. Our courses help you deliver faster and makes projects easier.
Your skills will include building hierarchical process models, using tools to analyze and assess process performance, defining critical process metrics, using best practice principles to redesign processes, developing process improvement project plans, building a center of excellence, and establishing process governance.
The BPMS Certificate is the perfect way to show employers that you are serious about business process management. With in-depth knowledge of process improvement and management, you'll be able to take your business career to the next level.
|
Courses
|
|
|
|
Courses
|
|
|
|
Courses |
|
|
Business Architecture
|
|
|
|
Courses |
Certificate
|
|
Courses
|
|
|
|
Courses |
Certificate
|
