BREX has nothing to do with Brexit and neither with a song, which only after one little change would sound like that: “Let’s talk about BREX, baby Let’s talk about you and me Let’s talk about all the good things And the bad things that may be Let’s talk about BREX Let’s talk about BREX… Read more Let’s Talk About BREX
As in prior three posts in this series, a note beforehand: for the simplicity and readability purposes I omitted the “<” and “>” brackets at the element names. Before we go any further, let’s recall the structure of the brPara (business rules paragraph) construct, which we need to markup a business rule decision point (BRDP)… Read more brDoc Schema: What is Business Rule Audit (brAudit) about?
As in prior two posts in this series, a note beforehand: for the simplicity and readability purposes I omitted the “<” and “>” brackets at the element names. Before we discuss today’s topic, let us recall what we need to record a business rules decision point (BRDP) and all the information related to it including… Read more brDoc Schema: What does brRelatedTo stand for?
A note beforehand: for the simplicity and readability purposes I omitted the “<” and “>” brackets at the element names. In the last post with the title “brDoc Schema: What is a Business Rules Paragraph (brPara)?”, we started looking a bit deeper into the business rules document (brDoc) XML Schema introduced in the S1000D Issue… Read more brDoc Schema: Why is there a brDecision Occurence outside of the brPara?
In this post, our Business Rules trainer Victoria Ichizli-Bartels will explain the brPara (business rules paragraph) and the reasons behind creating such a structure inside the new brDoc (business rules document) Schema in the S1000D Issue 4.2. A note beforehand: for the simplicity and readability purposes I omitted the “<” and “>” brackets at the… Read more brDoc Schema: What is a Business Rules Paragraph (brPara)?
Business Rules Document (brDoc) XML Schema is a new structure for capturing, managing and exchanging business rules. It has been added to the S1000D Issue 4.2 and represents the result of many years’ work by the Business Rules Working Group, which is a global S1000D working group with members coming from many different countries, industries,… Read more Understanding the Business Rules Document (brDoc) Schema
Most projects start their S1000D implementations with writing contracts and Statements of Work (SOW), sometimes even before even opening the specification. After that, they create plans for the technical publication based on those SOWs, which are then extended to define the project business rules. The specification is then consulted, and decision points are considered to… Read more Why Does It Make Sense to Generate a Business Rules Index First and a Guidance Document Second?
One would expect a standardization community to be large. So, you would not be surprised to hear that there are hundreds of S1000D protagonists around the world. But when it comes to a single S1000D project, many think that the people involved are not that many, especially if a given department assigned with the task… Read more The S1000D community is a big family – an S1000D project is a big family too
There are things in the S1000D that are self-explanatory, and others are understandable only on the second look. And then there are things you take for granted but don’t know why they are defined as they are. Only those who were present during the development of one or another Schema will know the reasons behind… Read more Why there is a dedicated element for a business rule decision and none for a business rule decision point
If you tell someone that you have to implement S1000D into your project or organization, one of the very first pieces of advice you will get will be: “Don’t forget to define business rules! They are one of the most important, if not the most important, steps while implementing the S1000D.” I thought so myself… Read more What is more important, or what comes first – business rules or implementation?