uml, owl and rea based enterprise business model 20110201a
TRANSCRIPT
UML, OWL and REA-based
Enterprise Business ModelEnterprise Business Model
Richard Kuo, Sr. Tech. Architect,
Architecture and Planning, IT Architecture & Common Services, AT&T
Services Inc.,
(925)823-9866 (Office), wiki
Why?Why?
22/1/2011
Who’s on first? http://www.youtube.com/watch?v=sShMA85pv8M
32/1/2011
What?What?
42/1/2011
Outlines
• Object-Process
• Events and Actions
• Similarity between UML and OWL
• REA Ontology
• Enterprise Ontology• Enterprise Ontology
• Backup Slides
• Model tools or specific domain.
52/1/2011
UML
(Unified Modeling Language)
62/1/2011
Triples and Graph
The base element of the
RDF model is the triple:
• a resource (the subject)
• inks (the predicate)
• another resource (the
object) object)
A resource <subject> has a
property <predicate>
valued by <object>.
<subject> <predicate> <object>
2/1/2011 7
OWL
(Ontology Web Language)
• OWL-Lite– Support simple classification, allows only cardinalities
(member count) of 1 and 0 and only minimal constraints.
• OWL-DL (Descriptive Language)• OWL-DL (Descriptive Language)– Supports more complex ontologies, but with
guarantees, such as processing finishing in finite time, restricting elements to be one type.
• OWL-Full– Full support for maximum freedom of RDF, with no
computational guarantees.
82/1/2011
OWL Classes and Properties partial list, see http://www.w3.org/TR/owl-guide/ for full list
• Class
– owl:class
– rdfs:subClassOf
• Property
– owl:ObjectProperty
– owl:DataProperty
• Property Restrictions
– owl:allValuesFrom
– owl:someValuesFrom
– owl:cardinality
– owl:someValue
• Equivalence
– rdfs:subPropertyOf
– rdfs:domain
– rdfs:range
• Property Characteristic
– owl:TransitiveProperty
– owl:FunctionalProperty
– owl:InverseProperty
– owl:InverseFunctionalProperty
– owl:EquivalenceClass
– owl:EquivalenceProperty
– owl:sameAs
• Complex Classes
– owl:IntersectionOf
– owl:UnionOf
– owl:CompoundOf
2/1/2011 9
UML & OWL Comparisonpage 196,The Semantic Web: ISWC 2006 :
5th International Semantic Web Conference, ISWC 2006, Athens, GA, USA, November 5-9, 2006
102/1/2011
Object-Process (1/2)
Object-Process Methodology, Prof. Don Dori, ISBN-13: 978-3540654711
• Process should be treated same as object
which has attributes and states.
• Process and Object should be able to show on
one diagram. It is not UML standard.one diagram. It is not UML standard.
• MIT summer short class: Systems Engineering, Architecture, and Life Cycle
Design: Principles, Models, Tools, and Applications.
112/1/2011
Object-Process (2/2)
122/1/2011
Events & ActionsActions and Events in Interval Temporal Logic, James F. Allen and Ferguson, University of Rochester.
• Events are the way by which agents classify certain useful and relevant patterns of change. (must involve at least one object and or involve at least one change of state).
• Actions and Events take time.
• The relationship between actions and events and their effects is complex.
• Actions and Events may interact in a complex ways when are overlaps or occur simultaneously.simultaneously.
• External changes in the world may occur no matter what action agent plans to do, may interact with planned actions.
• Knowledge of the world is necessarily incomplete and unpredictable, thus the predication can only be done on the basis of certain assumptions.
2/1/2011 13
REAAn ontology analysis of the economic primitives of the extended REA enterprise information
architecture, Guido Greets and William E. McCathy
• Resources – items with economic value. i.e.
goods, services or money.
• Events - business transactions or agreements
that affect resources. that affect resources.
• Agents – people (internal or other companies,
etc.) or systems.
142/1/2011
Modeling OWL with UML Tool
152/1/2011
REA Ontology
162/1/2011
Enterprise Ontology
2/1/2011 17
Basic Entities
182/1/2011
REA-based Enterprise Business Model 1/2
192/1/2011
REA-based Enterprise Business Model 1/2
202/1/2011
Thank you!Thank you!
212/1/2011
Backup SlidesBackup Slides
222/1/2011
UML Stereotype 1/4
232/1/2011
UML Stereotype 2/4
242/1/2011
UML Stereotype 3/4
252/1/2011
UML Stereotype 4/4
262/1/2011