Category Archives: S1000D Business Rules

Contributing to Mekon’s Bitesize on Business Rules – 13: brDoc Schema: Why is there a brDecision Occurence outside of the brPara?

When you read an earlier issue of S1000D, you come upon a question disguised as an affirmative sentence, stating what a project has to do. But you still recognize it as a question, which you have to answer when defining a business rule. Since the Issue 4.0, these are even more distinguishable since they start with the words Business Rules Decision Point.

But when you look at the new business rules document (brDoc) Schema, defined in the S1000D Issue 4.2 you will see that there is a construct to markup a business rules decision without a decision point preceding it. What does that one stand for?

In this month’s contribution to the Mekon’s BR Bitesize series, I address this feature in the article brDoc Schema: Why is there a brDecision Occurrence outside of the brPara? Click on the title of the article or here to find out more.

(Credits: Photograph ©canva.com under the keyword decision)

Contributing to Mekon’s Bitesize on Business Rules – 12: brDoc Schema: What is a Business Rules Paragraph (brPara)?

One of the main purposes of the most of the S1000D Schemas is to standardize already available practices in the production processes of technical publications, and with that allow information’s reuse, interchangeability, and interoperability.

The business rules document (brDoc) Schema in S1000D Issue 4.2 is not an exception.

Many elements and attributes of this and other S1000D Schemas (for the latter starting with the Issue 4.0) have self-explanatory names. Take for example the elements dmCode, dmTitle, or attribute names securityClassification, brDecisionPointUniqueIdent and other.

However, some of the names of some of the core components of the S1000D Schemas need explanation.

That is also true for the major component of the brDoc Schema, the business rules paragraph (brPara).

In this month’s contribution to the Mekon’s BR Bitesize series, I have explained what a business rules paragraph is, and why the S10000D Business Rules Working Group (BRWG) has developed such a structure.

Click the title of the article to find out more: “brDoc Schema: What is a Business Rules Paragraph (brPara)?”

(Credits: Photograph ©canva.com under the keyword “paragraph”)

Contributing to Mekon’s Bitesize on Business Rules – 12: Understanding the Business Rules Document (brDoc) Schema

The new Business Rules Document (brDoc) Schema, introduced in the S1000D Issue 4.2, possesses excellent potential, and I believe it will help reduce the duration and costs of the business rules production and maintenance as well as increase their quality.

But like any new construct in a standard and specification, it raises the question, “What is it good for?”

And when it comes to the S1000D business rules, especially the specification’s seasoned users will naturally ask such questions as, “Doesn’t the Business Rules Exchange (BREX) Schema, which was introduced earlier, already cover the business rules aspects?”

I have given answers to these questions from my point of view in the latest article for the Mekon’s Bitesize series on business rules.

Click the title of the article to find out more: “Understanding the Business Rules Document (brDoc) Schema.”

(Credits: Photograph ©librestock.com under the keyword “document”)

Contributing to Mekon’s Bitesize on Business Rules – 11: Why Does It Make Sense to Generate a Business Rules Index First and a Guidance Document Second?

In the previous articles, I contribute to Mekon’s Bitesize articles on Business Rules, I mentioned about the importance of defining the business rules before signing contracts, and also about the sequence or order in business rules definition.

In the most recent article in this series, titled “Why Does It Make Sense to Generate a Business Rules Index First and a Guidance Document Second?”, I address the flow of business rules definition process in more detail, but especially the form of it.

In my opinion, it is much more sensible to have all business rules recorded as an index with all the necessary information and guidance attached to each entry, than to start with a flowing text, as it is usual for contracts and statements of work.

And above that, I think you should start with creating an index (before signing contracts) and keep it as a master knowledge base of all decisions, and then extract information out of it to create all the guides, the contracts, and statements of work.

You can find the reasons why I think so in this article here.

(Credits: Photograph ©canva.com under the keyword “format”)

Un-publishing “S1000D Issue 4.1 Untangled”

In a book I published earlier this year I wrote the following:

“Not many want to think about terminating the existence of their product or service, hoping it will be there forever.

But it won’t. At least not in its very first shape or version. Besides, the updates might be so crucial that at some point you will have something entirely new and different than merely an upgraded product or service.

I can guarantee that sooner or later you will need to discard one (and most probably more) of your products or services or various parts of them.”

“Take Control of Your Business: Learn what Business Rules are, discover that you are already using them, then update them to maximize your business success.”

I didn’t think I would need to terminate one of my books that soon after the start of my business (not yet two years), but I know it is a correct decision.

What happened is the following. Last year I published a resource for the S1000D community titled “S1000D Issue 4.1 Untangled.” It arranged 552 Business Rules Decisions Points (BRDP) defined by the specification and also added several new ones into a sequential chain for the S10000D implementation. The book was very well received by the community.

This year I have published a follow-up resource named “S1000D® Issue 4.1 and Issue 4.2 Navigation Map.” It could not serve as a new edition of the “S1000D Issue 4.1 Untangled” because this time the book covered two issues of the specification and also showed the relationship between them when it came to the Business Rules Decision Points.

The “S1000D Issue 4.1 Untangled” continued to sell after the publishing of the second book. I realized that it only sold because of its lower price and that situation didn’t feel good.

If we compare the “S1000D Issue 4.1 Untangled” and “S1000D® Issue 4.1 and Issue 4.2 Navigation Map,” it is clear that the former is of the lower quality than the latter. Therefore, I have unpublished it.

To compensate for the possible inconvenience, I have considerably reduced the price for the “S1000D® Issue 4.1 and Issue 4.2 Navigation Map.”

You can find the reasons of un-publishing “S1000D Issue 4.1 Untangled” and the new prices for the “S1000D® Issue 4.1 and Issue 4.2 Navigation Map” on the “S1000D Issue 4.1 Untangled” page here.