Hendryx Hendryx
-
Upload
aamir97 -
Category
Technology
-
view
251 -
download
0
Transcript of Hendryx Hendryx
Hendryx Hendryx &
Associates
Progress report of theProgress report of theBusiness Rules Business Rules Working GroupWorking Group
Stan HendryxStan HendryxArlington, VirginiaArlington, VirginiaNovember 19, 2002November 19, 2002
2 © 2002 by Stan Hendryx 2
Hendryx Hendryx &
Associates
Since meeting in Orlando June 24, 2002the BRWG have …• Issued a RFI for Business Rules in Models
— ad/2002-09-13
• Met as a group at the Business Rules Forum in New Orleans, November 7- 8, 2002— Presentations of three Early Responses to the RFI
– Hendryx & Associates, North Face Learning, and ILOG
— Held a joint session with the Business Rules Group to discuss their Business Rule Motivation model and their joint response to the RFI– Included a Q&A session with John Zachman, author of the Zachman
Framework for Enterprise Architecture
— Developed a conceptual outline of business rules RFP’s– Group included end users, tool vendors, consultants, academia from the
US and Europe
• BRWG is an open group — OMG and non-OMG members alike are contributing
3 © 2002 by Stan Hendryx 3
Hendryx Hendryx &
Associates
The Business Rules in Models RFI
• Responses due January 10, 2002 — to be presented at the January TM in Burlingame, California
• Seeks input from industry, end users, tool vendors, consultants, academia— Practices, lessons learned, solution approaches to business rules in
models
• OMG member companies are invited to submit responses— Download from the OMG Web site, ad/2002-09-13
4 © 2002 by Stan Hendryx 4
Hendryx Hendryx &
Associates
The Early Responses to the RFI
• Hendryx & Associates
• North Face Learning
• ILOG
5 © 2002 by Stan Hendryx 5
Hendryx Hendryx &
Associates
RFI Response from Hendryx & Associates• Response focuses on a model framework to organize and
standardize models that collectively specify a business information system
• Frameworks provide a standard partitioning of a system specification and formalize the relationships of its parts— Especially the business part, which contains the business rules, and its
relationship to the technical parts of the system specification
— Allows viewpoint models to be standardized, substituted, reused
• The model framework structures the problem of transforming models – including business rules – to achieve correct correspondence, automation, and reuse
• We view the model framework as an essential part of business rules in models
6 © 2002 by Stan Hendryx 6
Hendryx Hendryx &
Associates
Frameworks and business rules
• The model framework provides a context for business rules and their derivative implementations
• Business terms, facts, and rules add business meaning to all framework models and to the system
• Business rules govern business processes
• Business rules originate with business people, in their own language, in the framework’s Enterprise viewpoint
• Technical system specifications contain manifestations of business rules, which must all be consistent
• The business rules provide the basis for validation of the system design specified in other framework models
7 © 2002 by Stan Hendryx 7
Hendryx Hendryx &
Associates
Model Frameworks are of Interest to Users• Tool vendors and OMG have not been particularly interested in
model frameworks— OMG modeling specifications and tools based on them are designed for
maximum flexibility in modeling
— Model frameworks are about separating concerns, restricting the content of models to an intended viewpoint, to achieve quality, automation, and reuse
— Users who have large, complex systems or a lot of models like to use model frameworks
• Teaching UML is teaching grammar
• Teaching model frameworks teaches writing
• Use of a standard framework will take modeling to the next level— With MDA, OMG is beginning to look at model frameworks
8 © 2002 by Stan Hendryx 8
Hendryx Hendryx &
Associates
There is a problem for MDA
• MDA will fall short of its goals unless the business model is formally connected to the technical models— Too many requirements errors without a formal link
— Business model must be in business language, not technical
— Models are not maintained unless they are connected to the code– This includes the business model
— MDA says the PIM must not violate the business model– But MDA neither defines the business model nor formally
relates it to the PIM or PSM
9 © 2002 by Stan Hendryx 9
Hendryx Hendryx &
Associates
What to do about it? – Use a Model Framework • An obvious solution to this problem is to formally
specify the business model and link it to the technical models— Business models in the language of business people
— Business models built on an underlying metamodel formalism
• Link business models to the technical models using a model framework— To validate the system design and provide test requirements
— To reduce system support and maintenance cost when rules change
• Realize the business model repository as a most valued asset of the enterprise— Linked to systems through the model framework
10 © 2002 by Stan Hendryx 10
Hendryx Hendryx &
Associates
The Framework has Models for Everyone…
Viewpoint Discipline Content
Enterprise Business Owners, Planners, Employees, Customers
Business modelSystem requirements
Information System Analysts Information modelInformation processing model
Computational Software Architects Object model Object interaction model
Engineering Systems ArchitectsSystem Administrators
Distribution model
Technology ProgrammersSystem Integrators
Program code API’s
11 © 2002 by Stan Hendryx 11
Hendryx Hendryx &
Associates
A Framework Primitive to aid Standardization
• Defining the metamodels in terms of the Viewpoints permits standardization of modeling languages for use with different architecture frameworks – existing or new
• Map concepts from the modified RM-ODP to use standard modeling languages and tools with other architecture frameworks
Viewpoint MDA Zachman DoD ?
Enterprise CIM Rows 1, 2 Operational …
Information PIM Row 3 Operational …
Computational PIM Row 3 Operational …
Engineering PIM or PSM Row 4 System …
Technology PSM Row 5 Technology …
12 © 2002 by Stan Hendryx 12
Hendryx Hendryx &
Associates
RFI Response from North Face Learning• Start-up university focused on training software
developers www.northfacelearning.com— Seeks to be a leading source of top-tier entry level developers
— Intensive, total immersion, model-based curriculum– Students can major in latest IBM or Microsoft technology– Will receive BS in Computer Science in 28 months
— To open fall 2003
• RFI response presented by Dr. Terry Halpin, VP— Using Object Role Modeling to Model Static Rules
— ORM has a thirty-year history
13 © 2002 by Stan Hendryx 13
Hendryx Hendryx &
Associates
Using ORM to Model Static Rules
• A conceptual approach to modeling any domain in terms of objects that play roles
• Attribute-free – all facts are expressed as relationships— Grouping facts into structures is an implementation issue
• Ideal for specifying static business rules— Constraints and derivation rules that apply to each state of the
information system
• Specify and define terms along with facts and rules
• Needs to be extended to include dynamic rules
• Use primarily for Enterprise viewpoint modeling
14 © 2002 by Stan Hendryx 14
Hendryx Hendryx &
Associates
Features of ORM
• Understandable— Express facts and rules in any natural language or intuitive graphics
• Reliable— Validate using natural language and sample populations
— Formal foundation of first order predicate logic, modal logic, and set theory
• Stable— Attribute-free semantics minimizes the impact of changes to models and
queries
• Executable— Map the formal model to relational schema, XML, …
• Learnable— Simplicity, uniformity, orthogonality
15 © 2002 by Stan Hendryx 15
Hendryx Hendryx &
Associates
Movie(Nr)
Person(Name)
ir
is based on
was reviewed by / reviewed
was directed by / directed
is banned
[director]
Sex(Code)
is of
{ 'M', 'F' }
Sample ORM Model
16 © 2002 by Stan Hendryx 16
Hendryx Hendryx &
Associates
Movie(Nr)
Person(Name)
ir
is based on
was reviewed by / reviewed
was directed by / directed
is banned
[director]
1 Ron Howard2 Ron Howard3 Peter Faiman
1 Peter Faiman1 Ann Green2 Ann Green
Sex(Code)
is of
{ 'M', 'F' }
4 14 23 2
45
Ann Green FPeter Faiman MRon Howard M
Sample ORM Model + Sample Fact Populations
17 © 2002 by Stan Hendryx 17
Hendryx Hendryx &
Associates
Reference schemes: Movie(Nr);Person(Name); Sex(code)
Base fact types: Movie is bannedMovie was directed by / directed PersonMovie was reviewed by / reviewed
PersonPerson is of Sex
Movie(Nr)
Person(Name)
ir
is based on
was reviewed by / reviewed
was directed by / directed
is banned
[director]
Sex(Code)
is of
{ 'M', 'F' }
Textual Version of ORM Model
Constraints:it is possible that the same Movie is based on more than one Movie and that more than one Movie is based on the same Movie no Movie is based on itself each Movie was directed by at most one Person it is possible that the same Movie was reviewed by more than one Person
and that the same Person reviewed more than one Movie
Movie(Nr)
Person(Name)
ir
is based on
was reviewed by / reviewed
was directed by / directed
is banned
[director]
Sex(Code)
is of
{ 'M', 'F' }
Textual Version of ORM Model, cont’d
Constraints (cont.):
each Movie that was reviewed by a Person also was directed by a Person
no Person directed and reviewed the same Movie
each Person directed a Movie or reviewed a Movie
each Person is of at most one Sex
each Person is of at least one Sex
SexCode has possible values: ‘M’, ‘F’
Movie(Nr)
Person(Name)
ir
is based on
was reviewed by / reviewed
was directed by / directed
is banned
[director]
Sex(Code)
is of
{ 'M', 'F' }
Textual Version of ORM Model, cont’d
20 © 2002 by Stan Hendryx 20
Hendryx Hendryx &
Associates
ORM Verbalization Features
• Allows free expression by the domain expert
• Caters for many kinds of constraints and derivation rules
• Caters naturally for fact instances, not just fact types
• Avoids any need for pluralization
• Mixfix notation caters for n-ary predicates
• Mixfix notation caters for foreign languages
Language Typical binary association pattern
English
Japanese
Tongan
…
Subject-Verb-Object (infix)
Subject-Object-Verb (postfix)
Verb-Subject-Object (prefix)
…
21 © 2002 by Stan Hendryx 21
Hendryx Hendryx &
Associates
Ref.: Jugyo in (jugyo in bango); Ka (namae)Fact: Jugyo in ‘37’ wa ‘Eigyo’ Ka ni shozoku suru
English EmpNr Dept
37 Sales
Jugyo in Ka
37 Eigyo
Ref. : Employee (empNr); Department (name)
Fact: Employee ‘37’ works for Department ‘Sales’
Mixfix allows Sentences in ANY Language
22 © 2002 by Stan Hendryx 22
Hendryx Hendryx &
Associates
Room(nr)
HourSlot(dh)
Activity(code)
... at ... is booked for ...
ActivityName
has / is of
20 Mon 9 am VSC20 Tue 2 pm VSC33 Mon 9 am AQD33 Fri 5 pm SP... ... ...
VSC Visual Studio classSP Staff Party
AQD Active Query demoC#-1 C# basics class
... ...
Ternary and longer associations require mixfix predicates for natural verbalization
23 © 2002 by Stan Hendryx 23
Hendryx Hendryx &
Associates
MOF model of ORM is underway
• Initial MOF model presented by David Cuyler of Sandia National Laboratories at the Orlando meeting
• Team of David, Terry and others are refining, completing the ORM metamodel— In ORM
— In MOF
24 © 2002 by Stan Hendryx 24
Hendryx Hendryx &
Associates
RFI Response of ILOG
• Describe Business Rules Management System
• Provide context for development of the RFP
• Put state-of-the-art requirements on record — Write business rules in a structured-English natural syntax
— Create business-user-friendly rule editors
— Use business terms in business rules
— Provide a business action language
— Store business rules and related data in a business rules repository
— Provide standard interchange format to implementation environment
25 © 2002 by Stan Hendryx 25
Hendryx Hendryx &
Associates
BRWG RFP’s to Focus on Business Modeling• The RFP’s should focus on the Enterprise viewpoint, i.e.,
the viewpoint of business owners, managers, employees, and customers — the modeling and communication needs of this group are considered
foremost
— Enterprise viewpoint models, including business rules, must be easy for this audience to use
26 © 2002 by Stan Hendryx 26
Hendryx Hendryx &
Associates
Why the emphasis on the business model?
• Because of inadequate consideration of the business requirements –
80% of software development projects fail or fall well short of their goals, or significantly overrun their budgets or schedules
$200 billion/year cost!
27 © 2002 by Stan Hendryx 27
Hendryx Hendryx &
Associates
BRWG Business Rules RFP Concepts
• There should be two RFP’s, one dealing with business rule expression, and another dealing with business rule management.
• Business rules must be expressible in natural language.
28 © 2002 by Stan Hendryx 28
Hendryx Hendryx &
Associates
Proposed Focus Business Rule Expression RFP • All aspects of the Enterprise viewpoint must be included in this RFP
— What? How? Where? Who? When? Why?
— Business model to including business terms, facts, rules, policies, processes, organization, locations, events
— The business process aspect should draw on selected emerging business process modeling standards, and link these to our rule expression models
— The Enterprise viewpoint may contain multiple levels of abstraction
— Enterprise requirements are to be stated in the form of contracts between the business and the system, including Quality of Service requirements.
• Both static and dynamic rules to be addressed— Static includes definition and interrelationships of terms, facts, and static
rules
— Dynamic includes policies affecting state changes in the business, and business processes
29 © 2002 by Stan Hendryx 29
Hendryx Hendryx &
Associates
Proposed Focus ofBusiness Rule Management RFP
• Address rule classification, interrelationships, ownership, change control, effectivity, and versioning
• Specify how this information about rules is to be formally linked to the rule expressions
• Specify how business rules are linked to the implementations – two way
30 © 2002 by Stan Hendryx 30
Hendryx Hendryx &
Associates
Other Proposed Requirements in theBusiness Rule RFPs
• Semantics should be specified separately from syntax, and alternative syntactical representations should be allowed
• The RFP’s should not specify pragmatics, including methodologies for capture, verification, or validation of rules — These are important, but are not an appropriate part of the specifications that
are the subject of these RFP’s
• The RFP’s should require an integrated MOF model of the semantics of rule expressions and rule management
• The RFP’s should require that a model interchange format be specified, suitable for use by downstream modeling, validation, and implementation tools to incorporate the enterprise viewpoint— Interchange formats should include separate interchange formats for
semantic information and for syntactic information, or diagrams
31 © 2002 by Stan Hendryx 31
Hendryx Hendryx &
Associates
Other Business
• BRWG BRSIG The BRWG will seek to become chartered as a Business Rules Platform Special Interest Group within OMG at the January 2003 meeting
• The next meeting of the BRWG will be at the OMG Technical Meeting in Burlingame, California, during the week of January 27-31— This will probably be two or three days, to review the RFI responses and
work on the initial RFP drafts, depending on the number of responses received
• Join the businessrules mailing list by sending your request to [email protected]
• Please send your comments, corrections, or suggestions to [email protected]