Building Business Solutions: Business Analysis with Business Rules (2nd Edition) … Just Out! http://www.brsolutions.com/b_building_business_solutions.php
Get it on Amazon: http://goo.gl/HXxN1fWhat It’s About: How to develop business solutions working directly with business leads, create blueprints of the solutions, and then use those blueprints for developing system requirements. Engineering business solutions, not just requirements.We have applied the techniques described in this book successfully in hundreds of companies worldwide.
Kind Words from a Practitioner: “We have based our whole business rules analysis practice on the methodology and techniques developed by the Business Rules Solution team. This book is an integral part of our practice. It’s an easy to read, useful guide with real life examples – we use it daily and couldn’t do without it!” – Michelle Murray, Inland Revenue Department NZ
New in this Edition: How Business Architecture corresponds with your projects and requirements work. Developing a Concept Model and how it will help you. How business rules align with the new terminology in the recently released IIBA® BABOK® Guide version 3.
When you show business people class diagrams or data models, you’re not really talking business. Class diagrams and data models are design artifacts that inevitably focus on how knowledge about real-world things is to be represented (and manipulated) as data in machines. If we want business people to talk business to us, we must talk business back. That means talking about their words, concepts and meanings. To do that you need to develop business vocabulary in a structured way – i.e., develop a concept model.Practitioners are slowly starting to ‘get’ this. Examples:
IIBA’s recently released Business Analysis Body of Knowledge (BABOK) version 3 devotes a new section to concept models.
A solid standard exists for concept models – OMG’s Semantics of Business Vocabulary and Business Rules (SBVR). Version 1.3 of the standard, comprehensively reorganized – but not changed – is due out this week.
Guest post by Cecilia Pearce~~~~~~~~~~~I have just completed the “Business Analysis with Business Rules: From Strategy to Requirements” on-line training session given by Ron Ross and Gladys Lam.This approach has additional benefits where requirements are concerned. During the session, it became evident that some of the requirements processes defined by BABOK® – Requirements Elicitation, Prioritization and Traceability – may be simplified when following the Business Motivation Model (BMM) approach.The BMM approach emphasizes starting with strategy for addressing the business problem. Being top-down and structured, it ensures that defined requirements are based on the business goals identified for the organisation. Since the source of the requirements is therefore known, their prioritization is simplified. Requirements linked directly to the goals will have a higher priority, whereas other requirements, depending how linked to the goals, may be allocated a lower priority. Traceability of requirements also benefits from the BMM approach. The requirements are already associated with the goals, possible business risks are identified, and relationships are traced to business processes, business milestones, and key performance indicators. The requirements elicitation process is just another benefit of the BMM approach. Requirements are defined with the goals in mind. The Policy Charter, a deliverable in the style of the BMM, illustrates the goals in more manageable segments and links the requirements directly to the identified goals. It allows the business stakeholders to ‘see’ their end result more clearly and understand what steps are required to get there.
“We actively use the BRS business-side techniques and train our business analysts in the approach. The techniques bring clarity between our BAs & customers, plus more robust requirements for our development teams. We’ve seen tremendous value.”