Integrating Service, Process, Data & Rules Requirements. Mathew Cooper Graham Witt

Transcription

1 u Integrating Service, Process, Data & Rules Requirements Mathew Cooper Graham Witt

2 Topics Ø Some background l Why this project was a bit different l The techniques we used l Design component reuse l Managing change l Lessons and benefits l Further reading Graham Witt/Mathew Cooper 2012 Slide 2

3 Some background l The client: NSW Land & Property Information their examples reproduced with thanks l The overall requirement: a set of services, to support supply of information by industry to government (B2G) by government to industry (G2B) incoming information governed by numerous business rules l Implications: Business rules need to be: implemented in multiple platforms visible to multiple stakeholders (as far upstream as possible) Graham Witt/Mathew Cooper 2012 Slide 3

4 Business rule application across the process Client Subscriber Certifier Electronic Lodgement Network LR Financial institution documentation systems Industry case management & documentation systems Common data schemas and data standard Electronic Lodgement Network system Pre-lodgement acceptability checks Land Registry electronic lodgement and registration systems Land Registry Business Rule Book l Land Registry business rules are required to assure data compliance at first collection, to avoid re-work during the conveyancing and registration process l Industry s need to use Land Registry business rules justified NSW Land Registry adoption of the Business Rules Approach Mathew Cooper 2012 Slide 4

5 The challenge l How to convert from: information not in defined format and relying on accompanying supporting evidence documents, into discrete data necessary for automated compliance checking for registration l How to automate manual compliance assurance examination in industry and the Land Registry l How to enable industry to conduct compliance assurance (currently applied by expert examiners at the Land Registry under single expert supervision) Mathew Cooper 2012 Slide 5

6 Information rules ó practice rules l Electronic conveyancing uses tell-me principle instead of show me principle used for paper conveyancing Certifier: signs for a Subscriber ELN: Electronic Lodgement Network Subscriber: Industry participant Client: Transacting Party LR: Land Registry Client Client Identity Verification Client Authorisation Agreement Paper curtain Subscriber & Certifier roles and responsibilities Subscriber Certifier Transaction Supporting Evidence Supporting Evidence Control of Right to Deal Registry Instrument Instrument Registry Instrument Certification Registry Instrument Digital Signing Lodgement Case E L N Notice of Sale Lodgement Instruction Signing Compliance LR LR Transaction Services Subscriber Systems LR authorised Information Broker / LR website Mathew Cooper 2012 Slide 6

7 Topics l Some background Ø Why this project was a bit different l The techniques we used l Design component reuse l Managing change l Lessons and benefits l Further reading Graham Witt/Mathew Cooper 2012 Slide 7

8 A generic system Graham Witt Slide 8

9 A typical system Graham Witt Slide 9

10 This system Graham Witt Slide 10

11 Topics l Some background l Why this project was a bit different Ø The techniques we used l Design component reuse l Managing change l Lessons and benefits l Further reading Graham Witt/Mathew Cooper 2012 Slide 11

12 Techniques l Service Use Cases l Business-friendly message descriptions l BPMN process models l Natural language business rule statements l Standardised terminology (common agreed vocabulary) Graham Witt 2012 Slide 12

13 Service Use Cases 1 Graham Witt 2012 Slide 13

14 Service Use Cases 2 Graham Witt 2012 Slide 14

15 Service Use Cases 3 etc. Graham Witt 2012 Slide 15

16 Business-friendly message descriptions l Describe content of message types in terms of data items relationships between them cardinality and some content rules l Various textual and diagrammatic representations tried û Entity-Relationship diagrams ü Hierarchic block diagram with legal numbering û XMLSpy diagrams û Hand crafted structure diagrams (in Visio) ü High-level block diagram Graham Witt 2012 Slide 16

17 Hierarchic block diagram with legal numbering Graham Witt Slide 17

18 High-level block diagram Graham Witt Slide 18

19 BPMN process models Graham Witt Slide 19

20 Natural language business rule statements 1 l Constrained natural language Standardised terminology (terms and verb phrases) Standardised syntax l Allows for easier checking of duplicates, contradictions etc l Can be understood by business stakeholders and information providers as well as developers Graham Witt Slide 20

21 Natural language business rule statements 2 l Also full form of rule statement Stand-alone Can be used as error message expressing desired condition Graham Witt Slide 21

22 Standardised terminology l For all artefacts Services Message types Data items Data types Processes l Agreed Terms, compatible with current industry terminology, with: agreed definitions (intensional) synonyms (allowed and prohibited) exclusions ( as distinct from ) l Taxonomic relationships between Terms, e.g., Person is a category of Party l Fact types, linking Terms using verb phrases, e.g., Document specifies Transacting Party Graham Witt Slide 22

23 Topics l Some background l Why this project was a bit different l The techniques we used Ø Design component reuse l Managing change l Lessons and benefits l Further reading Graham Witt Slide 23

24 Data types 1 l A reusable data object (i.e., one that appears in multiple places in messages) l May be simple, e.g., l May be complex, e.g. Graham Witt Slide 24

25 Data types 2 l May be part of a taxonomy, e.g., Graham Witt Slide 25

26 Message types l Consist of data items that either: have a data type, or are composed of other data items Graham Witt Slide 26

27 Topics l Some background l Why this project was a bit different l The techniques we used l Design component reuse Ø Managing change l Lessons and benefits l Further reading Graham Witt/Mathew Cooper 2012 Slide 27

28 Managing change l No repository dealing with all this and change l Considered wiki approach: need relatively stable position for this to work l Many reviewers so needed accessible well-understood documentation and review platform l MSWord allowed: version deltas (revision marks) reviewers proposed changes (revision marks) reviewers comments (comments) hyperlinks for navigation within and between documents l PDF allowed: publication of final versions l Version number/folder discipline: Published\...vn.00 WIP\...vn.mmaa (e.g., v2.01gw, v2.02pn) Graham Witt 2012 Slide 28

29 Topics l Some background l Why this project was a bit different l The techniques we used l Design component reuse l Managing change Ø Lessons and benefits l Further reading Graham Witt/Mathew Cooper 2012 Slide 29

30 Lessons and benefits l identifying common business concepts and the relationships between them l agreeing, defining and using a common glossary l the need for precision in language used re-use of words with defined meanings l the need to define data, concepts and business rules concurrently and iteratively l how writing the rules helps get the concept model right or helps identify when it is wrong l how the Business Rules Approach identifies inconsistencies and problems in current or proposed practices l the benefit of using declarative rules l simplification of existing processes l the business can define, communicate and update its requirements Mathew Cooper 2012 Slide 30

31 A measure of success l The national body tasked with implementing electronic conveyancing needs: a single common data standard a set of message types incorporating the various state requirements l That body: determined the functional requirements for the national system used the NSW message and document schemas as the basis for the common data standard adopted the NSW documentation techniques collaboratively incorporated each jurisdiction s requirements l The resulting common data standard forms part of the electronic conveyancing system design to be implemented Graham Witt 2012 Slide 31

32 Topics l Some background l Why this project was a bit different l The techniques we used l Design component reuse l Managing change l A measure of success Ø Further reading Graham Witt/Mathew Cooper 2012 Slide 32

33 Further reading l Slide 33

34 Any questions? What? Why? How? Where? Who? When? Graham Witt/Mathew Cooper 2012 Slide 34