<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://training-course-material.com/index.php?action=history&amp;feed=atom&amp;title=SoaML_and_UPDM</id>
	<title>SoaML and UPDM - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://training-course-material.com/index.php?action=history&amp;feed=atom&amp;title=SoaML_and_UPDM"/>
	<link rel="alternate" type="text/html" href="https://training-course-material.com/index.php?title=SoaML_and_UPDM&amp;action=history"/>
	<updated>2026-05-13T00:11:45Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>https://training-course-material.com/index.php?title=SoaML_and_UPDM&amp;diff=24002&amp;oldid=prev</id>
		<title>Cesar Chew at 19:13, 24 November 2014</title>
		<link rel="alternate" type="text/html" href="https://training-course-material.com/index.php?title=SoaML_and_UPDM&amp;diff=24002&amp;oldid=prev"/>
		<updated>2014-11-24T19:13:43Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Cat|SoaML}}&lt;br /&gt;
{{Cat|NAF}}&lt;br /&gt;
{{Cat|UPDM}}&lt;br /&gt;
&lt;br /&gt;
Sources:&lt;br /&gt;
http://www.ndia.org/Divisions/Divisions/SystemsEngineering/Documents/Committees/M_S%20Committee/2009/June%202009/08.%20%20UPDM%20for%20NDIA_v2_Dandashi.pdf&lt;br /&gt;
&lt;br /&gt;
[[File:SoaML UPDM UML SysML.png|400px]]&lt;br /&gt;
&lt;br /&gt;
== What SoaML can do what UPDM cannot ==&lt;br /&gt;
# Detail service modelling&lt;br /&gt;
# Contract is binding on ports typed by the interfaces of the contract&lt;br /&gt;
# Mapping to BPMN 2.0 (BPMN 2.0 mention service)&lt;br /&gt;
# UPDM planned reuse (mapping) of SoaML&lt;br /&gt;
# SoaML is universal (i.e. not focused on military vocabulary)&lt;br /&gt;
&lt;br /&gt;
== General Definition of a Service in UPDM ==&lt;br /&gt;
&amp;quot;The Service-Orientated View is a description of services needed to directly support the operational &lt;br /&gt;
domain as described in the Operational View. A service is described as a unit of work through &lt;br /&gt;
which a particular Resource provides a useful result to a consuming Resource. UPDM services &lt;br /&gt;
may include standard web-based services, but also define effects deployment, logistics support, &lt;br /&gt;
and even cooking meals for hungry soldiers.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
The resource provides the service, and the consuming  resource makes use of it. &lt;br /&gt;
&lt;br /&gt;
The Services Views are the following:&lt;br /&gt;
* SOV-1 Service Taxonomy (SoaML: Category)&lt;br /&gt;
* SOV-2 Service Interface Specification (SoaML: Simple Interface, ServiceInterface, ServiceContract)&lt;br /&gt;
* SOV-3 Capability to Service Mapping - shows how services support capabilities (SoaML: Integration with BMM) &lt;br /&gt;
* SOV-4a Service Constraints, SOV-4b Service State Model, and SOV-4c Service Interaction Specification (SoaML: Service Choreography)&lt;br /&gt;
* SOV-5 Service Functionality (SoaML: Operations in Services, more details mapping to methods)&lt;/div&gt;</summary>
		<author><name>Cesar Chew</name></author>
	</entry>
</feed>