br relationships and their impact on the implementation of s1000d

©2014 Flatirons Solutions, Inc. All rights reserved.

BR* relationships and their impact on the

implementation of S1000D This presentation is made on behalf of Business Rules Working Group (BRWG)

{former Implementation Guide and Business Rules Task Team (IGBRTT)}

S1000D User Forum 2014

San Antonio, 2014-06-23/25

* BR = Business Rules


Agenda

2

IGBRTT to BRWG: our TT becomes a WG

Business rules: what we have today

BR components and how BRDP define BR relationships

BR use cases: a subset of BR decisions relationships

Understanding BRDP relationships

What S1000D provides for Issue 4.1 and beyond


Next topic

3








IGBRTT became BRWG in 2014

4

Reason:

• Starting with Issue 4.1 we are maintaining BRDP Index and other BR related information

• The future Implementation Guide will also be maintained by this group the group resumed work on it (IG will be maintained

outside of the S1000D)

BRWG meetings will primarily be web based*.

* Face-to-face meetings will

only take place if all

involved parties agree and

in conjunction with other

meetings (e.g. S1000D User

Forum, SC, etc.).


Next topic

5








Chapter 2.5.3 Business rules - Business rules decision points (BRDP) index

6

Special highlights: Structure, accessibility,

usability and clean-up!

BUT!

This list is flat! Only related chapters are listed.


Next topic

7








Business Rule Components

8

An example:

BRDP-S1-00003 - Issue of S1000D to be used

Description: Decide which issue or issues of S1000D

to be used.

Specification location: Chap 2.5.1 “Business rules –

Categories and layers” (Para 2.1.3)

BR Category: 1 General

Related XML Schema: appliccrossreftable, brex,

checklist, comment, comrep, condcrossreftable,

container, crew, ddn, descript, dml, fault,

frontmatter, ipd, learning, pm, prdcrossreftable,

proced, process, sb, schedule, scocontent,

scormcontentpackage, update, wrngdata,

wrngflds

BR Decision: S1000D Issue 4.1


Illustrating BRDP relationships (Continuing with BRDP-S1-00003 Example)

9

Relationship of BRDP-S1-00003 to Schema will

determine which Schema can be used.

For example, SB Schema can only be used from

Issue 4.1.

If using Issue 3.0, BRDP related to SB Schema are

not applicable.

Conclusion: For BRDP defined by S1000D

(identified as BRDP-S1-xxxxx), there is a certain

context and therefore relationships determined

by S1000D.


Next topic

10








BR use cases – subset of BR relationships (Continuing with SB Example)

11

Assumptions:

We chose Issue 4.1

We chose to use SB Schema and create SB data modules

We made decisions on BRDPs related to SB DM

The decisions made might have various Use Cases:

Some will be of interest for authors, other for managers, others for CSDB admins, others for all three etc.

Decisions can also apply to various customers, or various

types of organizations.

Conclusion: Business rules decisions relate to each other depending on their use. But they are also affected by the

BRDP relationships.


Next topic

12








First attempt to identify relationships between BRDP

13

FAILED!!!

Main reason:

the perception of

these relationships

can vary widely.


The clue is to consider a BRDP in various contexts: 4 major identified

14

Location in the document where it is defined (for

BRDP-S1-NNNNN, it is

S1000D Chap and Para)

BR categories

S1000D Schemas

All configurable attributes (the project ones and

@quantityUnitOfMeasure)


Next topic

15








S1000D BRDP relationships (in MS Excel and XML/HTML formats)

16

• Available for Issue 4.1 on www.s1000d.org and contains:

Mapping to Chaps and Paras

Mapping to BR Categories

Mapping to Schemas

Mapping to Configurable attributes

• Started and in full will be provided for Issue 4.2:

Allowable values for BRDPs defined by S1000D. This will considerably reduce misunderstandings in interpreting BRDPs and their meaning.

• Also from Issue 4.2:

This information will be available in XML-format using the S1000D brDoc data module.

• Why are we eager to provide this information?

The projects and organizations will be able to take the S1000D brDoc data module (or the same information as MS Excel file) and use it as a basis for their BR creation.

Reduction of ambiguity, better overview and understanding, less conflicts, saving time and money.

BRDP-relationships-Iss4-1_001-00.xlsx

DMC-S1000D-E-04-00-0000-00A-024A-D_000-02_EN-US.XML

DMC-S1000D-E-04-00-0000-00A-024A-D_000-02_EN-US.HTML

http://www.s1000d.org/


Vielen Dank!

Mulţumesc mult! Большое спасибо!

Mange tak!

Tack så mycket!

Merci beaucoup! Tusen tak!

¡Muchas gracias!

Thank you very much!

Mille grazie!

br relationships and their impact on the implementation of s1000d

Technology

brdp relationships

br relationships br

br components

br category

issue of s1000d

s1000d issue

flatirons solutions

relationship of brdp