Model Landscape 1

1
2
3
Name
GoalML (Goal Modelling Language)
MEMO (Multi-perspective Enterprise Mod)
KAOS (Knowl. Acquisition in Automated Spec.)
Curator Year
-
-
-
2014
2011
1991
Scope
Enterprise*
Enterprise*
Enterprise
Keywords
goal, actor, structure
goal, process, organization
goal, structure
4 GRL (Goal Oriented Requirement Lang.) ITU-T 2003 Enterprise goal, structure, distribution
5 i* (Distributed Intentionality) - 1995 Enterprise goal, structure, distribution
6 UEML (Unified Enterprise Mod. Lang.) Interop-NoE 2002 (2006) Enterprise goal, structure, ontology
7 ODM (Ontology Definition Metamodel) OMG 2009 (2014) Enterprise* ontology, concept, rule
INTERACTION SoBM ENTERPRISE
SDBM s-BMC OMG E-BMM OpenGroup 8 ARIS (Architecture of Integrated Info. Syst.) AG Soft 1994 Enterprise* organization, process, product
Business (2014) (2017) (2014) BMM (2009)
BMM-IT+ Archimate 2 9 SoaML (Service oriented archit. Mod. Lang.) OMG 2009 (2012) Enterprise* service, architecture
e3 Value 10 SOMF (Service Oriented Modeling Framework) Meth. Corp. 2008 Enterprise* service, architecture
SoaML (2008) (2013) (2006)
(2001) 11 Archimate (Architecture of Integrated Info. Syst.) Open Group 2009 Enterprise* strategy, business, application
(2012) MODEL BMC 3 1 GOAL MEMO 2 12 E-BMM (Enterprise BMM) - 2009 Enterprise strategy, business, application
Value BMI (2010) (2011) AG Soft 13 BMM-IT+ (Business Motivation Model extension) - 2013 Enterprise strategy, structure, alignment
IBM GoalML UEML
Network Cube CBM (2014) KAOS ARIS 14 BMM (Business Motivation Model) OMG 2008 (2015) Business strategy, goal, influencer
(2002) 15 b-SOAML (Business SOAML) - 2012 Business architecture, service
ServML (2002) (2013) Capab (2005) (1993) (1994)
(2013) VALUE 16 BMI Cube (Business Model Cube) NEFFICS 2013 Business model, innovation
Map CAPABILITY i* 17 BMC (Business Model Canvas) - 2010 Business model, innovation
(2011) GRL OMG
SERVICE (1995) Ontology 18 S-BMC (Service Business Model Canvas) - 2014 Business model, innovation, service
PCN OMG POA (2003) ODM 3 19 SoBM (Service Oriented Business Modeling) - 2017 Business model, innovation, service
CJM VDML Languages
SJML (2012) 4 (2016) (2009) OWL, RDF,
20 SDBM (Service Dominant Business Model) - 2014 Business model, innovation, service
(1999) (2013) (2015) ONTO-
CL, TM
21 CBM (Component Business Model) IBM 2005 Business capability, structure
Value REA LOGY 22 CM (Capability Map) - 2011 Business capability, structure
SBP Stream OMG OMG 23 VDML (Value Definition Modeling Lang) OMG 2015 Business* value, capability
(2005)
Euler’s (1984) (1998) CMMN OMG 24 e3-value (Economic e-Commerce Value) 2001 Business value, exchange
Rummler- BPDM 25 Value net - 2002 Business value, flow
Graph Brache ARIS (2008) (2009)
RULE SBVR 26 ServiceML (Service Modelling Lang.) SINTEF 2013 Business* service, goals, interaction
(1736)
(1990) EPC PROCESS (2008) 28 SJML (Service Journey Modelling Lang.) SINTEF 2013 (2015) Business service, interaction, customer
(1992) OMG OMG 29 CJM (Customer Journey Map) IDEO 1999 (2014) Business service, interaction, customer
PetriNet OMG 4 PCN (Process Chain Network) - 2012 Business service, interaction, value
(1962)
BPMN v1 BPMN v2 DMN
30

YAWL (2004) (2011) 31 SBP (Service Blueprint) - 1984 (2008) Business service, process, interaction
Flow- (2002)
ADF WORK- (2015) 32 POA (Possesion-Ownership-Availability) - 2015 Business process, value, exchange
chart (2000s) FLOW KPI
5 33 Value stream - 1998 Business process, value
(1947) DECISION 34 SBVR (Semantics of Business Vocab. & Rules) OMG 2008 (2017) Business ontology, rule
TDM 35 TDM (The Decision Model) KPI 2009 Business decision, rule
(2009) 36 DMN (Decision Model and Notation) OMG 2015 (2016) Business decision, rule
DFD State- OMG OMG
37 CMMN (Case Management Model and Notation) OMG 2009 (2014) Business case, structure, state
OMT Booch 38 BPDM (Business Process Def. Metamodel) OMG 2008 Business process, collaboration
(1974) charts UML v1 UML v2 5 40 BPMN (Business Process Modeling Notation) OMG, ISO 2004 (2011) Business process, flow
(1997) (1991) (1994) (1997) (2005) 41 EPC (Event Process Chain) AG Soft 1992 Business process, flow, structure
PHYSICAL
42 REA (Resource-Event-Agent) - 1982 Business process, structure, ontology
Structure OOSE 43 UML (Unified Modeling Lang) OMG, ISO 1997 (2015) Software* object, function, behavior
ERD
Chart (1976) (1992) OMG OMG 6 44 YAWL (Yet Another Workflow Lang.) YAWL Found . 2002 (2013) Software process, flow
OMG
(1974) WebML 45 DFD (Data Flow Diagram) - 1974 Software process, flow, data
IFML 6 SoaML SysML
SOFTWARE (1998)
46 IFML (Interaction Flow Modeling Lang.) OMG 2015 Software interface, flow,user
(2009) (2006)
(2015) 47 SC (Structured Chart) - 1988 Software flow, structure
48 ERD (Entity Relationship Diagr) - 1976 Software data, structure, ontology
49 SysML (Systems Modelling Lang) OMG, ISO 2006 (2017) System* block, functional
50 IDEF (Integration Definition) KBSI 1995 System* function, data, process
51 Flowchart ASME 1947 System process, flow
7 52 Statechart - 1987 System state, transition
53 Petri net - 1962 General flow, queue

- Service engineering can be viewed as an alternative abstraction of

1
Enterprise engineering in containing business model,
capability, value, interaction, process and software
concepts.
 UML Definition
►The Unified Modeling Language (UML) is a
graphical language for visualizing,
specifying, constructing, and documenting
the artifacts of a software-intensive system.

►The UML offers a standard way to write a

system's blueprints, including conceptual
things such as business processes and
system functions as well as concrete things
such as programming language statements,
database schemas, and reusable software
components
(OMG)
 Kategori Diagram UML
►Structure diagram
►Behavior diagram
►Interaction diagram
Overview diagram
 UML diagrams: use cases
► A use case encodes a typical user interaction with
the system. In particular, it:
– captures some user-visible function.
– achieves some concrete goal for the user.
► A complete set of use cases largely defines the
requirements for your system: everything the user
can see, and would like to do.
► The granularity of your use cases determines the
number of them (for you system). A clear design
depends on showing the right level of detail.
► A use case maps actors to functions. The actors
need not be people.
5
Use case examples, 1
(High-level use case for powerpoint.)

6
 Use case examples, 2
(Finer-grained use cases for powerpoint.)

7
Use case examples, 3
(Relationships in a news web site.)

8
Use Case Relationships

9
 Structure diagram
►Class Diagram
►Object Diagram
►Component Diagram
►Composite Structure Diagram
►Package Diagram
►Deployment Diagram
 Behavior diagram
►Activity diagram
►State Machine diagram
►Use case diagram
 Interaction diagram
►Communication diagram
►Interaction overview diagram (UML 2.0)
►Sequence diagram
►UML Timing Diagram (UML 2.0)
01 Class diagram
 01 Class definition
►A class represents a group of things
that have common state and behavior.
►A class is a blueprint for an object in
an object-oriented system.
►In UML, a class is a kind of classifier.
►Volkswagen, Toyota, and Ford are all
cars, we can represent them using a
class named Car.
02 Object diagram
 02 Object definition
►An object is an instance of a class.
►Several instances of a class named
Car:
– one two-door red car,
– one four-door blue car, and
– one pickup green car.
03 Componenet diagram

UML 2.0 UML 1.4

03 Component diagram (uml 2)
 03 Component diagram
►A component is a replaceable,
executable piece of a larger system
whose implementation details are
hidden

UML 2.0 UML 1.4

04 Composite structure diagram
 04 Composite Structure
►A structure is a set of interconnected
elements that exist at runtime to
collectively provide some piece of
functionality.
– Connector
– Ports
– Structured Classes and Properties
05 Package diagram
 05 Package
►Packages provide a way to group related
UML elements and scope their names.
– Several classes contained inside the Utilities
package
– Easier to build and test
– Better tracking and project transparency
– Working at a stable overview without the noise of
low-level churn
– Less conflict between distributed teams
– Easy refactoring and extension
06 Deployment Diagram
 06 Deployment diagram
►Deployment diagrams model the mapping of
software pieces of a system to the hardware
that is going to execute it.
►Software elements (components, classes,
etc.) are typically manifested using artifacts
and are mapped to the hardware or software
environment that will host them, called
nodes.
►Communication between nodes can be
modeled using communication paths.
07 Activity diagram
 07 Activity diagram
►Activity modeling focuses on the
execution and flow of the behavior of a
system, rather than how it is
assembled.
►Possibly more than any other UML
diagram, activity diagrams apply to
much more than just software
modeling.
08 State machine diagram
 08 State diagram
►State machine diagrams capture the
behavior of a software system.
►Two types of state machines:
– Behavioral state machines
• Show the behavior of model elements such as objects. A
behavioral state machine represents a specific
implementation of an element.
– Protocol state machines
• Show the behavior of a protocol. Protocol state
machines show how participants may trigger changes in
a protocol's state and the corresponding changes in the
system (i.e., the new state of the protocol). Protocol state
machines aren't typically tied to a particular
implementation, and they show the required protocol
behavior.
09 Use case diagram
 09 Use Case
►Use cases are a way to capture system
functionality and requirements in UML.
►Use case diagrams consist of named
pieces of functionality (use cases), the
persons or things invoking the
functionality (actors), and possibly the
elements responsible for implementing
the use cases (subjects).
10 Communication diagram
 10 Communication diagram
►A communication diagram focuses on
the interaction between lifelines, where
the architecture of the internal
structure and how this corresponds
with the message passing is central.
The messages are usually notated with
sequence numbers, which indicate the
relative execution order of the
associated messages.
 11
Interaction
overview
diagram
11 Interaction overview diagram
►An interaction overview diagram focuses on
the overview of the flow of control within a
given interaction.
►This type of diagram resembles an activity
diagram in that interactions and/or
interaction occurrences serve as the activity
nodes.
►All other symbols that appear on sequence
diagrams and activity diagrams can appear
on interaction overview diagrams.
12 Sequence diagram
 12 Sequence diagram
►A sequence diagram focuses on the
time-ordering of messages between
objects.
13 Timing diagram
 13 Timing diagram
►Timing diagrams (UML 2.0) are a specific
type of interaction diagram, where the focus
is on timing constraints.
►Timing diagrams are used to explore the
behaviors of objects throughout a given
period of time. A timing diagram is a special
form of a sequence diagram. The differences
between timing diagram and sequence
diagram are the axes are reversed so that the
time are increase from left to right and the
lifelines are shown in separate
compartments arranged vertically.
UML untuk website
Hatur nuhun