Information Technology Reference
In-Depth Information
t:Business
ObjectNode
f:Action
f:Item
t:Representational_Model
f:Query
t:Interface
Pattern
f:Manage
t:Business
Object
f:SalesOrder
t:Access
Pattern
t:Pattern
t:DataModel
t:Operation
Pattern
f:Change
t:Process
Component
f:SalesOrder
Processing
t:Direction
Pattern
f:Find
t:Communication
Pattern
f:Approve
t:Deployment
Unit
f:SalesOrder
Processing w/o HCM
f:In
f:Out
Relationship
Concepts
t:Terminology
Concept
f:RequestConfirmation
f:Information
r
df:ty
pe
p
:belo
ngsTo
t:Software
Component
f:Factual
Concepts
f:ERP
f:Notification
f:QueryResponse
Fig. 2.
RDF Schema of the knowledge base showing terminological and factual concepts
(S1)
SalesOrderItemScheduleLineChangeRequestConfirmation In
Signature (S1) defines an incoming request operation (invoked by a seller) to
change the schedule line of an item contained in an existing sales order of a spe-
cific customer. From this signature, we can recognize factual concepts that have
been modeled as part of our schema. On the one hand, the terms ”Sales Order”,
”Item” and ”Schedule Line” refer to factual concepts belonging to terminologi-
cal concepts listed under data model (cf. Fig. 2). On the other hand, the terms
”Change”, ”Request” and ”In” represent factual concepts of a particular service
development pattern, also a terminological concept. In a final step, these terms
are arranged according to a specific order that is defined by a set of naming
conventions. Next, we explain terminological concepts of the data model and
pattern and show how they are utilized to create Enterprise Service signatures
using naming conventions.
A domain-specific data model.
Typically, Enterprise Services are built on
key entities of a domain-specific data model. For instance, signature (S1) is
specified according to the factual concept ”Sales Order”, ”Item” and ”Schedule
Line” as inferred from the data model defined as part of the knowledge base
(cf. Fig. 2). This model represents an abstract and trimmed-down version of
an existing information model used by SAP. Such an information model de-
scribes, in more detail, the relationship of business-related entities used by an
organization to realize internal operations. Each terminological concepts has fac-
tual concepts associated with it. Applying this to our example, the terminolog-
ical concept ”Business Object Node” (BO Node) belongs to ”Business Object”
(BO), which implies that the factual concept ”Item” belongs to ”Sales Order”:
SalesOrderItemScheduleLineChangeRequestConfirmation In
Service development patterns.
Apart from the data model, the service
knowledge base also describes development patterns recurrently used by de-
velopers to uniformly define Enterprise Services. These patterns can further be
