UMM and Business process specification schema ebXML

1
UMM and Business process specification schema
ebXML

• Enn Õunapuu
• Tallinn Technical University
• enn_at_cc.ttu.ee
• 372 050 97720

2
Infosüsteemi elutsükkel

• Veelange meetod
• Spiraal meetod
• Iteratiivne (RUP)

3
(No Transcript)
4

• The Rational Unified Process captures many of
  modern software development's best practices in a
  form suitable for a wide range of projects and
  organizations
• Develop software iteratively.
• Manage requirements.
• Use component-based architectures.
• Visually model software.
• Continuously verify software quality.
• Control changes to software.

5
The core process workflows are divided into six
core engineering workflows 1. Business
modeling workflow 2. Requirements workflow 3.
Analysis Design workflow 4. Implementation
workflow 5. Test workflow 6. Deployment
workflow And three core supporting
workflows 1. Project Management workflow 2.
Configuration and Change Management workflow 3.
Environment workflow
6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14
(No Transcript)
15
(No Transcript)
16
ebXML business process specification schema
Business process models describe interoperable
business processes that allow business partners
to collaborate. Business process models for
e-business must be turned into software
components that collaborate on behalf of the
business partners. The goal of the ebXML
Specification Schema is to provide the bridge
between e-business process modeling and
specification of e-business software components
17
UMM Metamodel and ebXML Business Process
Specification Schema
18
Basic Semantics of a business collaboration
19
1.      Business Collaborations A business
collaboration is a set of Business Transactions
between business partners. Each partner plays one
or more roles in the collaboration. The ebXML
Business Process Specification Schema supports
two levels of business collaborations, Binary
Collaborations and Multiparty Collaborations. Bina
ry Collaborations are between two roles only.
20
A Business Transaction is the atomic unit of work
in a trading arrangement between two business
partners. A Business Transaction is conducted
between two parties playing opposite roles in the
transaction. The roles are always a requesting
role and a responding role. Like a Binary
Collaboration, a Business Transaction is a
re-useable protocol between two roles. The way it
is re-used is by referencing it from a Binary
Collaboration through the use of a Business
Transaction Activity as per above. In a Business
Transaction Activity the roles of the Binary
Collaboration are assigned to the execution of
the Business Transaction. Unlike a Binary
Collaboration, however, the Business Transaction
is atomic, it cannot be decomposed into lower
level Business Transactions.
21
1.      Choreography The Business Transaction
Choreography describes the ordering and
transitions between business transactions or sub
collaborations within a binary collaboration. In
a UML tool this can be done using a UML activity
diagram. The choreography is described in the
ebXML Business Process Specification Schema using
activity diagram concepts such as start state,
completion state, activities, synchronizations,
transitions between activities, and guards on the
transitions.
22
Business Transaction
A Business Transaction is the atomic unit of work
in a trading arrangement between two business
partners. A business transaction consists of a
Requesting Business Activity, a Responding
Business Activity, and one or two document flows
between them. A Business Transaction may be
additionally supported by one or more Business
Signals that govern the use and meaning of
acknowledgements and related matters in the
transaction.
23
(No Transcript)
24

• Thank You!!!