We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byDana Brummett
Modified about 1 year ago
Designing Services, Messages & Business Rules for eBusiness Graham Witt
Topics Some background Why this project was a bit different The techniques we used Managing change Lessons and benefits Further reading Slide 2© Graham Witt 2012
Some background The client: NSW Land & Property Information their examples reproduced with thanks 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 Implications: Business rules need to be: implemented in multiple platforms visible to multiple stakeholders (as far upstream as possible) Slide 3© Graham Witt 2012
Business rule visibility across the end-to-end process To avoid rework data compliance should be checked as early as possible Industry therefore needs access to Land Registry business rules © Mathew Cooper / Graham Witt 2012Slide 4 Client Subscriber Certifier Electronic Lodgement Network LR Land Registry Business Rule Book Industry case management systems Electronic lodgement & registration systems Common data standard Pre- lodgement acceptability checks Financial institution systems
The challenge To convert from unstructured information with accompanying supporting evidence, to structured data for automated compliance checking To convert from manual compliance checking by expert examiners at the Land Registry, to compliance checking by industry To automate manual compliance checking in industry and the Land Registry Slide 5© Mathew Cooper / Graham Witt 2012
LR Information flow Paper conveyancing: “show me” Electronic conveyancing: “tell me” Slide 6 Lodgement Case ELNELN Client Identity Verification Client Authorisation Agreement Control of Right to Deal Registry Instrument Supporting Evidence Notice of Sale Lodgement Instruction ‘Paper curtain’ Land Registry Transaction Services Digital Signing Instrument Certification Registry Instrument Client Subscriber Certifier © Mathew Cooper / Graham Witt 2012 Subscriber System
Topics Some background Why this project was a bit different The techniques we used Managing change Lessons and benefits Further reading Slide 7© Graham Witt 2012
A generic system © Graham Witt Slide 8
A typical system © Graham Witt Slide 9
This system © Graham Witt Slide 10
Topics Some background Why this project was a bit different The techniques we used Managing change Lessons and benefits Further reading Slide 11© Graham Witt 2012
Techniques Standardised terminology (common agreed vocabulary) Business-friendly service definitions Service Use Cases aka Message Use Cases BPMN process models where service logic complex Business-friendly message descriptions Business-friendly notations Design component re-use Natural language business rule statements Catalogued against data items © Graham Witt 2012Slide 12
Standardised terminology For all artefacts Services Message types Data items Data types Processes Agreed Terms, compatible with current industry terminology, with: agreed definitions (intensional) synonyms (allowed and prohibited) exclusions (“as distinct from”) Taxonomic relationships between Terms, e.g., Person is a category of Party Fact types, linking Terms using verb phrases, e.g., Document specifies Transacting Party © Graham Witt Slide 13
Service Use Cases – 1 Slide 14© Graham Witt 2012
Service Use Cases – 2 Slide 15© Graham Witt 2012
Service Use Cases – 3 etc. © Graham Witt 2012Slide 16
BPMN process models © Graham Witt Slide 17
Business-friendly message descriptions Describe content of message types in terms of data items relationships between them cardinality and some content rules Various textual and diagrammatic representations tried Entity-Relationship diagrams XMLSpy diagrams “Hand crafted” structure diagrams (in Visio) “High-level” block diagrams Hierarchic block diagrams with legal numbering Slide 18© Graham Witt 2012
“High-level” block diagram © Graham Witt Slide 19
Hierarchic block diagram with legal numbering © Graham Witt Slide 20
Data types – 1 Reusable data objects, i.e., that appear in multiple places in messages May be simple, e.g., May be complex, e.g. © Graham Witt Slide 21
Data types – 2 May be part of a taxonomy, e.g., © Graham Witt Slide 22
Message types Consist of data items that either: have a data type, or are composed of other data items © Graham Witt Slide 23
Natural language business rule statements – 1 Constrained natural language Standardised terminology (terms and verb phrases) Standardised syntax Allows for easier checking of duplicates, contradictions etc Can be understood by business stakeholders and information providers as well as developers Each catalogued against relevant data item © Graham Witt Slide 24
Natural language business rule statements – 2 Also full form of rule statement Stand-alone (requires complete context) Can be used as error message expressing desired condition © Graham Witt Slide 25
Topics Some background Why this project was a bit different The techniques we used Managing change Lessons and benefits Further reading Slide 26© Graham Witt 2012
Managing change No repository dealing with all this and change Considered wiki approach: need relatively stable position for this to work Many reviewers so needed accessible well-understood documentation and review platform MSWord allowed: version deltas (revision marks) reviewers’ proposed changes (revision marks) reviewers’ comments (comments) hyperlinks for navigation within and between documents PDF allowed: publication of final versions Version number/folder discipline: Published\...vn.00 WIP\...vn.mmaa (e.g., v2.01GW, v2.02PN) Slide 27© Graham Witt 2012
Topics Some background Why this project was a bit different The techniques we used Managing change Lessons and benefits Further reading Slide 28© Graham Witt 2012
Lessons and benefits Lessons: the importance of agreeing, defining and using a common glossary the need for precision in language used the need to define concepts, messages (data), services/processes and business rules concurrently and iteratively, e.g. errors in message design identified during rule writing Benefits: simplification of existing processes the business has been able to define, communicate, review and update its requirements Slide 29© Mathew Cooper / Graham Witt 2012
A measure of success NECDL, the national body tasked with implementing electronic conveyancing, needed: a single common data standard a set of message types incorporating the various state requirements 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 then incorporated each jurisdiction’s additional or different requirements to produce a common data standard for the National Electronic Conveyancing System Slide 30© Graham Witt 2012
Topics Some background Why this project was a bit different The techniques we used Managing change A measure of success Further reading Slide 31© Graham Witt 2012
Further reading – 2 Slide 32 © Graham Witt 2012
Further reading Slide 33
Any questions? Slide 34 What?How?Who?When?Where?Why? © Graham Witt 2012
ELECTRONIC CONVEYANCING WORKSHOPS 2009 Simon Libbis Executive Director Ann Kinnear Operations Manager.
UPDATE ON THE NATIONAL ELECTRONIC CONVEYANCING SYSTEM Simon Libbis Executive Director.
National Electronic Conveyancing Legal Framework First Stakeholder Meeting SYDNEY 16 May 2011.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4e Basic Health Data Standards Component 9/Unit.
A New Computing Paradigm. Overview of Web Services Over 66 percent of respondents to a 2001 InfoWorld magazine poll agreed that "Web services are likely.
3 rd Annual European DDI Users Group Meeting, 5-6 December 2011 The Ongoing Work for a Technical Vocabulary of DDI and SDMX Terms Marco Pellegrino Eurostat.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 8/e (McGraw-Hill, 2014). Slides copyright 2014 by Roger Pressman.1.
Chapter 9 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall & Kendall Sixth Edition.
UPDATE ON THE NATIONAL ELECTRONIC CONVEYANCING SYSTEM LIXI Industry Forum 10 September 2008 Simon Libbis Executive Director.
NATIONAL ELECTRONIC CONVEYANCING Australia’s joint government and industry initiative to create an efficient and convenient way of completing property.
Categories of Vocabulary Compatibility Dmitry Lenkov Oracle.
This chapter is extracted from Sommerville’s slides. Text book chapter
CIW Lesson 6MBSH Mr. Schmidt1. Define databases and database components Explain relational database concepts Define Web search engines and explain.
Chapter 9 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall & Kendall Sixth Edition © 2005 Pearson Prentice.
8/28/97Information Organization and Retrieval Files and Databases University of California, Berkeley School of Information Management and Systems SIMS.
OECD Expert Group on Statistical Data and Metadata Exchange (Geneva, May 2007) Update on technical standards, guidelines and tools Metadata Common.
Sharif University of Technology Session # 6. Contents Systems Analysis and Design Planning the approach Asking questions and collecting data
Chapter 11 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall and Kendall Fifth Edition.
Confidential 111 Financial Industry Business Ontology (FIBO) [FIBO– Business Entities] Understanding the Business Conceptual Ontology For FIBO-Business.
Database Design: ER Modelling (Continued) Reading: C&B, Chaps 11,12&16.
Tool support for Enterprise Architecture in System Architect Architecture Practitioners Conference, Brussels David Harrison Senior Consultant, Popkin.
Requirements Engineering Overview Senior Design Don Evans.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.
EDM Council / Object Management Group Semantic Standards Workstream Definitions and Detailed Objectives May 04, 2011.
Copyright © 2011 Pearson Education Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall & Kendall Global Edition 9.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall.
Semantic Web Thanks to folks at LAIT lab Sources include : Tim Berners-Lee Presentation W3C Semantic Web Activity Presentation of W3C and Semantic Web.
1 Lecture 9: Chapter 9 Architectural Design Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides copyright.
Harmonization Project FAS Meeting Harmonization project and ISSAI 200 Purpose and scope of the project The purpose is to provide a conceptual basis.
© 2003 McGraw-Hill Australia Pty Ltd, PPTs t/a Accounting Information & Reporting Systems by A. Aseervatham and D. Anandarajah. Slides prepared by Kaye.
Configuration & Build Management. Why Software Configuration Management ? The problem: Multiple people have to work on software that is changing More.
10 December, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: DPM Meta model CWA1Page 1.
Reading literacy. Definition of reading literacy: “Reading literacy is understanding, using and reflecting on written texts, in order to achieve one’s.
CA. Saju Sreedhar.K, FCA. Preface Audit evidence forms the bedrock of the auditor’s report on financial statements. Auditor expresses his opinion of.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Slide 1 OMG, Montreal, August 2004 OMG_SWIFTMDA_200408_v2.ppt SWIFTStandards (UNIFI – ISO 20022) “MDA-like” approach Frank Vandamme Tools, Products & Methodology.
Chapter 2 Accountants as Business Analysts Copyright © 2014 McGraw-Hill Education. All rights reserved. No reproduction or distribution without the prior.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
DDI 3.0 Conceptual Model Chris Nelson. Why Have a Model Non syntactic representation of the business domain Useful for identifying common constructs –Identification,
Research Introduction to the concept of incorporating sources into your own work.
WP.5 - DDI-SDMX Integration E.S.S. cross-cutting project on Information Models and Standards Marco Pellegrino, Denis Grofils Eurostat METIS Work Session6-8.
9.1 CSC 123 Systems Analysis & Design Part III: Systems Analysis Chapter 9 Describing Process Specifications and Structured Decisions.
ADA Langage Report Ligia Nitu. Introduction Ada is the most extensive and expensive computer language ever developed. Ada is the most extensive and expensive.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
© 2017 SlidePlayer.com Inc. All rights reserved.