11 September DM2 TWG Agenda - Silver Bullet Solutions, Inc.

18 December DM2 TWG Agenda
• News –
– DoDAF CM
– Others SoAML Monday
• New References – M3 1.2 in M3 folder
• Continue review planned 2.01 Action Items in
preparation for technical cutoff
• DM2 PES XML Examples Work Update
• Others
– measures and rules example – Dryer example from
NCEM project – next TWG
Capability States or Model
Metadata
• Capability temporal parts
– Current
– Next year
– 10 years from now
• ArchitecturalDescriptions
– Capability model (CV’s)
that are
ArchitecturalDescriptions
named “Current”
– Capability model that is
“next year”
– Capability model that is “10
years from now”
Dave to take to Mike (#326)
• Where to put DM2 PES Examples
– Journal – pro-easy to change; con-buried
– MDR – pro-like CoT;
– PES document (former Vol III) – part of alt 2 but not in
.doc form
– All of the above – pro-hits everybody; con-need
sync’d
– Others?
• What is the release plan schedule detail for
2.01?
Events (#330)
•
•
•
•
•
•
•
Declaration of completion
Causes reaction
Typically unsolicited or unexpected
Natural events
Recognition of the effect of the activity
Sufficiency to proceed
Use – OV-3 (trigger), OV-6bc, SV-6 (trigger), SV10bc
– Activity1 causes activity2
342
WORKING DRAFT
Desired
Effect in SoA
Property
Capability
Measure
+
numericValue: string
measureOfType
measureOfTypeActivityChangesResource
MeasureOfEffect
supertype
howMuchDesired
measureOfType
Activity
subtype
measureOfTypeCondition
IndividualType
MeasureOfDesire
measureOfType
effectMeasure
overlapType
desiredEffect
BeforeAfterType
IndividualType
activityChangesResource
desiredFutureResourceState
Resource
measureOfType
measureOfTypeActivityPerformableUnderCondition
desiredFutureResourceState
IndividualType
overlapType
Condition
activityPerformableUnderCondition
WholePartType
Type
measureOfType
desiredEffectOfCapability
CapabilityType
whole
measureOfTypeActivityPartOfCapability
WholePartType
IndividualType
activityPartOfCapability
Capability
supertype
measureOfType
measureOfTypeActivityPerformedByPerformer
propertyOfType
capabilityOfPerformer
subtype
overlapType
activityPerformedByPerformer
Performer
desirer
Example XML docs
• Initial Source Material
– UPDM SAR example
– TISP/ISP examples
– NCES, other examples
• Tutorial
• Guidance
• Validation
326 Issue: include whole-parts,
super-subs, overlaps, …
Info A is-a-type of some higher-level category
Org a
Info A
Act 3
Act 4
Part-of Org a
Org b
Part-of info A
Part-of Org a
Part-of info A
Act 1
Act 2
11 December DM2 TWG Agenda
• News –
– OMG Technical Meeting – UPDM – DM2 work
– Others
• New References – M3 1.2 in M3 folder (Dave & Greg)
• How to create a calculation/measure using the Rules
and/or Measures data groups, e.g., Net Enabled UJT
TA3.2.2 Conduct Close Air Support has two measures
• Continue review planned 2.01 Action Items in
preparation for technical cutoff
• DM2 PES XML Examples Work Update
• Others
Day
Monday
Tuesday
Wednesday
Thursday
Time
09:00 – 12:00
13:00 – 14:00
14:00 – 15:00
15:00 – 18:00
16:00 – 16:30
08:30 – 09:30
Event
Model Interchange Working Group (MIWG)
UPDM Initial Meeting and plan for the week
Presentation to the BMI Group on the UML profile for
BPMN and integration with UPDM
UPDM 1.1 Meeting
UPDM Update to the C4ISR Group
UPDM Presentation to the SE DSIG Group
09:30 – 18:00
09:30 – 12:00
UPDM 2.0 meetings
Segment Architecture Meetings
13:00 – 15:00
UPDM Presentation to the Business Architecture
Working group
Jim Rice
08:30 – 15:30
08:30—15:30
UPDM 2.0 meetings
All
15:30 – 17:00
Presentation to the ADTF Group on the UML profile for
BPMN and integration with UPDM
UPDM 2.0 meetings
Fatma presenting, all
please attend
All
Architecture Ecosystem Meeting
The purpose of this group is to determine how to
integrate UPDM and other OMG profiles together
We will do a presentation
Voting Session (No UPDM meetings)
All
08:30 – 17:30
17:30 – 19:00
Friday
08:30 – 12:00
People
All
All
Fatma presenting, all
please attend
All
Matthew Presenting
Jim/Graham
Presenting all attend
All
Jim Rice
All
DM2 Coord
DM2 Coord People
DM2
Comments and
Questions
Submitted Oct
2009
DMM – DM2
Mapping ReCalibration
McDaniel/Schaefer
/TBD*
DMM to DM2
Mapping
McDaniel/Schaefer
/TBD
DMM X DM2
Mapping
Schaefer/TBD
McDaniel/Schaefer
/TBD
TA 3.2.2 Conduct Close Air Support
Activity desc in DM2
• Description: To provide support for amphibious
and/or land operations by air assets through
attacking hostile targets in close proximity to
friendly forces. (JP 3-0, JP 3-09, JP 3-09.3)
– M1 Minutes Preplanned close air support (CAS)
missions execute weapons delivery/release within
MeasureType
____ minutes of air tasking order (ATO)-tasked timein DM2
on-target (TOT).
– M2 Minutes Airborne Alert or preplanned on-call CAS
missions arrive at Control Point (CP) within ____
minutes of ATO-tasked time-on-station (TOS).
Measures and MeasureTypes
Measures:
Value
MeasureTypes:
Name
3
2.5
1,000,000
{a, b}
Units
Name
Description
Kg
Mass
see physics 101
Mach
Speed in Mach
$
Cost
{{a, b, c}, {a, b}, {a, c}, {b, c}, {a}, {b}, {c}, null}
{a, b, c}
{a, b, c}
Description
{b, c}
4 December DM2 TWG Agenda
• News –
– OMG Technical Meeting – UPDM – DM2 work
•
•
•
•
Mapping of DMM to DM2
Comments and questions on DM2
Dave prepare an agenda for Tues-Thurs and send to UPDM Team
May need breakout rooms
– Others
• New References – OASIS SoA releases from Ellis
• Review planned 2.01 Action Items in preparation for
technical cutoff
• DM2 PES XML Examples Work Update
• Others
– 2.01 release process ASRG -> ARB -> DM2 TWG, DoDAF TWG,
DARS TWG – dave verify with mike
2.01 Defers
• Not all descriptions are information, e.g.,
– “Fire”
• Not all information is a description, e.g.,
– Names, numbers, etc. are information that
aren’t descriptions
• May have some importance in authenticity,
etc.
20 November DM2 TWG Agenda
VOIP -- https://www2.gotomeeting.com/join/806195954
•
•
Dave forward DM2 TWG – UPDM Group email to [email protected]
News –
– Carnegie-Mellon Software Engineering Institute (SEI) Army Strategic Software
Improvement Program (ASSIP) Action Group (AAG)
– Joint Architecture Integration Working Group (JAIWG) Architecture Federation
and Integration Project (JAFIP)
•
New References
– McDaniel file Ellis OASIS SOA RAF public release 2 in Refs folder
– Dave Fix REX references
•
•
UPDM Search and Rescue (SAR) DM2 PES XML Example
Update on In-Progress for 2.01 AI’s
–
–
–
–
–
•
316
326
335
341
365
Others –
Metamodel diagram per DoDAF Model
Example XML docs
JCA mapping
DDMS metacard for every document
Information and Data
New References
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
References and Research\Behavior\NIST09-08-05.pdf
References and Research\SEI\SEI AAG\Army Acquisition – The PEO Perspective.pdf
References and Research\SEI\SEI AAG\Wiltsie%20_10_18.pdf
References and Research\SOAML\SoaML-defns.docx
References\FSAM\FSAM_Complete_v1_1[1].pdf
References\FSAM\FSAM_Overview_Training_Slides_v1_0.ppt
References\FSAM\step5_Value_Measuring_Methodology_Cost_to_Value_Matrix.xls
References\FSAM\OMB_EAAF_v3_0_Self_Assessment_Template_Dec_2008.xls
References\FSAM\FSAM_Steps_Products.xlsx
References\FSAM\FSAM_Steps_Products_v2.xlsx
References\FSAM\step5_Modernization_Blueprint.doc
References\Services\Rex RIM1.docx
References\Systems Engineering\DoDAF Satisfaction of SE Needs - NDIA AFWG 2009-1007.doc
References\Systems Engineering\NDIA Recommendations Responses DMM 2009-10-25.doc
References\Systems Engineering\Systems Engineering Needs of the DoDAF - Report of the
Architecture Frameworks Working Group.ppt
References\DoD Governance\DoD Data Architecture - A Way Forward v1 3.pptx
In Progress
316 Metamodel diagram per DoDAF Model
Spiral IV Review Comment # 806. Schema
has not been provided in the Dictionary for the
DoDAF Ver. 2.0 Viewpoints. The only schemas
included are for the Meta-model Data Groups.
CADM included schemas that showed how each
View was characterized and constructed from a
data perspective. The Proposed Resolution:
Revise the Dictionary to add schemas for each AV,
CV, DIV, OV, PV, StdV, SvcV, and SV Viewpoint.
335 JCA mapping of function types to activities,
capabilities, and JCSFL
1.
2.
Finish CapabilityType defs, assns, alias to JCA
2. Assn for mapping Activity to CapabilityType
MODAF Capability Configuration
• A composite structure representing the
physical and human resources (and their
interactions) in an enterprise.A
CapabilityConfiguration is a set of
artefacts or an organisation configured to
provide a capability, and should be guided
by [doctrine] which may take the form of
Standard or OperationalConstraint
stereotypes.
341 DDMS metacard per PES XML document
•Mapped core DDMS elements
Need COI extension
There should be a DDMS metacard for every XSD to support discovery. DoD EA COI
extensions and what needs to discoverable about a DoDAF model (for which there is an
XSD.) Maybe be consistent with UCORE. Coordinate with DARS TWG and in
conjunction with all DoD. Need some kind of forums or WG to work on.
<ddms:Resource
xmlns:ddms="http://metadata.dod.mil/mdr/ns/DDMS/2.0/"
xmlns:mdr="http://metadata.dod.mil/"
xmlns:gml="http://www.opengis.net/gml"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:ICISM="urn:us:gov:ic:ism:v2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://metadata.dod.mil/mdr/ns/DDMS/2.0/ http://metadata.dod.mil/mdr/ns/DDMS/2.0/DDMS-v2_0.xsd">
<!-- G:\sbsi\ddmsv2\DDMS_2.0\ns\DDMS\2.0\DDMS-v2_0.xsd"> -->
<ddms:identifier
ddms:qualifier="URI"
ddms:value="AV1.XSD"/>
<ddms:title
ICISM:ownerProducer="USA"
ICISM:classification="U" >DoDAF 2.0 AV1 XML Schema</ddms:title>
<ddms:subtitle
ICISM:ownerProducer="USA"
ICISM:classification="U" ></ddms:subtitle>
<ddms:description
ICISM:ownerProducer="USA"
ICISM:classification="U" >Overview and Summary Information</ddms:description>
<ddms:language
ddms:qualifier="ISO 639-1"
ddms:value="en-us"/>
<ddms:dates
ddms:posted="2009-07-23"
ddms:created="2009-07-20"
ddms:validTil="2099-01-01"
ddms:infoCutOff="2009-07-01"/>
365
Information and Data: The element ServiceDescription is
understood as the key to any form of description of a service in a nonimplementation specific manner. Is this correctly understood and is this
then enough to convey all of the MODAF related non-implementation
specific information as regards services?
Yes, Service Description does both
MODAF's Service Interface Definition and
Service Interaction Specification.
Schaefer to post Sevice diagram and
notes in Working Copy LDM section for
Ellis to present / review by OASIS SoA
Ref Arch F/W. Question on Interaction vs
Interface description. Mod'd service
description to connect to describedBy
and added places for consumer and
provider. Verify the describedBy is
specific to service descriptions.
IDEAS Information and Data
Thing
thingDescribed
IndividualType
Resource
describedBy
descri ption
Representation
Inform ation
ServiceDe scription
13 November DM2 TWG Agenda
• News –
– FSAM and DM2, SoAML meeting
• Dave post FSAM info
• Cory send REA info for Dave to post – ownership,
possession, responsibility, …
• Fatma send 10 key SoA terms with multiple defs for Dave to
add to Data Dictionary
• SAR XML Example
• Update on In-Progress for 2.01 AI’s
– 316
Metamodel diagram per DoDAF Model
– 326
Example XML docs
– 335
JCA mapping
– 341
DDMS metacard for every document
– 365
Information and Data
• Others – revisit #251 – homework for Dave and
Clarence
In Progress
•
•
Dispostional:
–
A Property whose members are Individuals that have a property of being capable to manifest a
CategoricalProperty under certain conditions other things being equal. It is critical when
describing the disposition to specify the conditions both for the dispositional and the categorical
property that is capable of being manifested. These can range from quite stringent conditions,
the DispositionalProperty of 'being capable of flying at Mach 2, at a moment's notice' to the more
lax, the property of 'being capable of flying at Mach 2, once suitably configured'. Note that these
have the same manifestation - the categorical property of 'flying at Mach 2'. Similarly, it is often
critical to describe in detail the conditions that apply to the CategoricalProperty that can be
manifested, so, for example, 'flying at Mach 2, in good weather'.
–
Example:
–
–
–
–
–
–
Ability to fly at no more than (or at least) Mach 2
Ability to go 50 mph
Ability to strike a target 10km away
Ability to dissolve in water
F-22 has the ability to break the sound barrier
Ability to be 10 kg (a baby growing up)
Categorical:
–
A Property that is always exhibited by its instances (Individuals). Formally, a CategoricalProperty
is the set of things that have a property simpliciter without reference to the capability to manifest
another property (as is the case with DispositionalProperties (qv.)). So, for example, the property
of 'flying at Mach 2' is a CategoricalProperty, whereas 'being capable of flying at Mach 2' is not.
–
Examples:
–
–
–
–
–
10+/-.001mg kg
40cm
Fitting in an ISO container
This specific jet is flying at Mach 2
This specific state of the jet in front of dave’s window is always flying at 200 mph +/- a bit
6 November DM2 TWG Agenda
•
News –
– Scheduling of special UPDM sessions – DMM will always be core, MODAF only
extensions, DoDAF only extensions
• Central EU to TX 10AM EST – 2hr sessions. Wed, Thu DAVE GET REQUEST OUT TO
TWG AND UPDM GROUP
– German delegation visit to EA&S
– JIAWG – use of PES for use cases – candidates Greg provide at next TWG
•
Update on In-Progress for 2.01 AI’s
– 177
Command Relationships
– 251
OV-4
– 284
PerformerPerformerOverlap (specific case of 331
Supertype association usage guidance)
– 309
UCORE 2 sync
– 316
Metamodel diagram per DoDAF Model
– 326
Example XML docs
– 331
Supertype association usage guidance
– 335
JCA mapping
– 341
DDMS metacard for every document
– 365
Information and Data
• Others -- TBS
In Progress
177 Command Relationships
251 OV-4
• What is the formal
nature of
Command
Relationships
shown on Org
Charts?
• Is there always an
Agreement,
Guidance, Rule,
…?
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
IS AN ALTERNATE FOR SUBORDINATE ORGANIZATION
IS IN DIRECT SUPPORT (DS) OF SUBORDINATE ORGANIZATION
IS IN GENERAL SUPPORT (GS) OF SUBORDINATE ORGANIZATION
IS IN RESERVE TO SUBORDINATE ORGANIZATION
IS REINFORCING (R) SUBORDINATE ORGANIZATION
IS UNDER OPERATIONAL COMMAND (OPCOM) OF SUBORDINATE ORGANIZATION
IS UNDER OPERATIONAL CONTROL (OPCON) OF SUBORDINATE ORGANIZATION
IS UNDER TACTICAL COMMAND (TACOM) OF SUBORDINATE ORGANIZATION
IS UNDER TACTICAL CONTROL (TACON) OF SUBORDINATE ORGANIZATION
PROVIDES LOGISTICS SERVICES TO SUBORDINATE ORGANIZATION
GIVES PRIORITY OF SUPPORT TO SUBORDINATE ORGANIZATION
IS ATTACHED TO SUBORDINATE ORGANIZATION
IS DETACHED FROM SUBORDINATE ORGANIZATION
IS GENERAL SUPPORT/REINFORCING (GSR) FOR SUBORDINATE ORGANIZATION
IS ORGANIC TO/PART OF SUBORDINATE ORGANIZATION
IS UNDER COMMAND FOR ADMINISTRATION (UCADMIN) OF SUBORDINATE
ORGANIZATION
HAS FULL COMMAND OVER SUBORDINATE ORGANIZATION
IS UNDER COMMAND FOR MOVEMENT(CFM) OF SUBORDINATE ORGANIZATION
REPORTS TO SUBORDINATE ORGANIZATION
CONTROLS SUBORDINATE ORGANIZATION
REPLACES SUBORDINATE ORGANIZATION
DOES ACCOUNTING FOR SUBORDINATE ORGANIZATION
IS SAME AS SUBORDINATE ORGANIZATION
IS ON CALL TO/STANDSBY FOR (NOT OTHERWISE SPECIFIED) SUBORDINATE
ORGANIZATION
IS ATTACKING SUBORDINATE ORGANIZATION
IS DEFENDING FROM SUBORDINATE ORGANIZATION
IS HOLDING SUBORDINATE ORGANIZATION
IS CAPTURING SUBORDINATE ORGANIZATION
IS DETAINING SUBORDINATE ORGANIZATION
IS SURVEYING SUBORDINATE ORGANIZATION
IS EXPLOITING SUBORDINATE ORGANIZATION
IS TARGETING SUBORDINATE ORGANIZATION
IS MOBILIZED TO SUBORDINATE ORGANIZATION
IS PARENT REGIMENT OF COMBAT ARMS FOR SUBORDINATE ORGANIZATION
CONTROLS TECHNICALLY SUBORDINATE ORGANIZATION
IS A MEMBER OF SUBORDINATE ORGANIZATION
RECEIVES DATA FROM SUBORDINATE ORGANIZATION
SUPPORTS MAINTENANCE OF SUBORDINATE ORGANIZATION
SUPPORTS REPAIR OF SUBORDINATE ORGANIZATION
SUPPORTS COMMUNICATIONS OF SUBORDINATE ORGANIZATION
SUPPORTS INTELLIGENCE FOR SUBORDINATE ORGANIZATION
SUPPORTS TRAINING OF SUBORDINATE ORGANIZATION
SUPPORTS DURING PEACETIME SUBORDINATE ORGANIZATION
IS AN ALTERNATE FOR SUBORDINATE ORGANIZATION-TYPE
IS IN DIRECT SUPPORT (DS) OF SUBORDINATE ORGANIZATION-TYPE
IS IN GENERAL SUPPORT (GS) OF SUBORDINATE ORGANIZATION-TYPE
IS IN RESERVE TO SUBORDINATE ORGANIZATION-TYPE
IS REINFORCING (R) SUBORDINATE ORGANIZATION-TYPE
IS UNDER OPERATIONAL COMMAND (OPCOM) OF SUBORDINATE ORGANIZATIONTYPE
IS UNDER OPERATIONAL CONTROL (OPCON) OF SUBORDINATE ORGANIZATIONTYPE
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
IS UNDER TACTICAL COMMAND(TACOM) OF SUBORDINATE ORGANIZATIONTYPE
IS UNDER TACTICAL CONTROL (TACON) OF SUBORDINATE ORGANIZATIONTYPE
PROVIDES LOGISTICS SERVICES TO SUBORDINATE ORGANIZATION-TYPE
GIVES PRIORITY OF SUPPORT TO SUBORDINATE ORGANIZATION-TYPE
IS ATTACHED TO SUBORDINATE ORGANIZATION-TYPE
IS DETACHED FROM SUBORDINATE ORGANIZATION-TYPE
IS GENERAL SUPPORT/REINFORCING (GSR) OF SUBORDINATE
ORGANIZATION-TYPE
IS ORGANIC TO/PART OF SUBORDINATE ORGANIZATION-TYPE
IS UNDER COMMAND FOR ADMINISTRATION (UCADMIN) OF SUBORDINATE
ORGANIZATION-TYPE
HAS FULL COMMAND OVER SUBORDINATE ORGANIZATION-TYPE
IS UNDER COMMAND FOR MOVEMENT OF SUBORDINATE ORGANIZATIONTYPE
REPORTS TO SUBORDINATE ORGANIZATION-TYPE
CONTROLS SUBORDINATE ORGANIZATION-TYPE
REPLACES SUBORDINATE ORGANIZATION-TYPE
DOES ACCOUNTING FOR SUBORDINATE ORGANIZATION-TYPE
IS SAME AS SUBORDINATE ORGANIZATION-TYPE
IS ON CALL TO/ IS STAND BY FOR (NOT OTHERWISE SPECIFIED)
SUBORDINATE ORGANIZATION-TYPE
IS ATTACKING SUBORDINATE ORGANIZATION-TYPE
IS DEFENDING FROM SUBORDINATE ORGANIZATION-TYPE
IS HOLDING SUBORDINATE ORGANIZATION-TYPE
IS CAPTURING SUBORDINATE ORGANIZATION-TYPE
IS DETAINING SUBORDINATE ORGANIZATION-TYPE
IS SURVEYING SUBORDINATE ORGANIZATION-TYPE
IS EXPLOITING SUBORDINATE ORGANIZATION-TYPE
IS TARGETING SUBORDINATE ORGANIZATION-TYPE
IS MOBILIZED TO SUBORDINATE ORGANIZATION-TYPE
IS PARENT REGIMENT OF COMBAT ARMS FOR SUBORDINATE
ORGANIZATION-TYPE
CONTROLS TECHNICALLY SUBORDINATE ORGANIZATION-TYPE
IS A MEMBER OF SUBORDINATE ORGANIZATION-TYPE
RECEIVES DATA FROM SUBORDINATE ORGANIZATION-TYPE
SUPPORTS MAINTENANCE OF SUBORDINATE ORGANIZATION-TYPE
SUPPORTS REPAIR OF SUBORDINATE ORGANIZATION-TYPE
SUPPORTS COMMUNICATIONS OF SUBORDINATE ORGANIZATION-TYPE
SUPPORTS INTELLIGENCE FOR SUBORDINATE ORGANIZATION-TYPE
SUPPORTS TRAINING OF SUBORDINATE ORGANIZATION-TYPE
SUPPORTS DURING PEACETIME SUBORDINATE ORGANIZATION-TYPE
HAS OTHER RELATIONSHIP TO SUBORNIDATE ORGANIZATION-TYPE
IS A COMMAND POST CELL OF SUBORDINATE ORGANIZATION-TYPE
IS AN OPERATIONAL FACILITY FOR SUBORDINATE ORGANIZATION-TYPE
IS A COMPONENT OF SUBORDINATE ORGANIZATION-TYPE
IS ESSENTIALLY THE SAME AS SUBORDINATE ORGANIZATION-TYPE
REPLACES SUBORDINATE ORGANIZATION-TYPE
IS USUALLY COLLOCATED WITH SUBORDINATE ORGANIZATION-TYPE
SUPPORTS SUBORDINATE ORGANIZATION-TYPE
284 PerformerPerformerOverlap
(specific case of 331 Supertype
association usage guidance)
Provide guidance on when to use supertype and subtype associations
As for using superclass associations, perhaps the rule is, only of same classes.
Work on matrices more
309 UCORE 2 sync
Harmonize with UCORE 2.0 so
the "digest" can be generated from the PES dataset.
• UCORE SL
• UCORE being pulled into OASIS
emergency data exchange language
• Directed for C2 Core
• Brief / meet with Clay Robinson
316 Metamodel diagram per DoDAF Model
Spiral IV Review Comment # 806. Schema
has not been provided in the Dictionary for the
DoDAF Ver. 2.0 Viewpoints. The only schemas
included are for the Meta-model Data Groups.
CADM included schemas that showed how each
View was characterized and constructed from a
data perspective. The Proposed Resolution:
Revise the Dictionary to add schemas for each AV,
CV, DIV, OV, PV, StdV, SvcV, and SV Viewpoint.
326 Example XML docs
Core Process / model
XML doc examples
331 Supertype association usage guidance
Provide guidance on when to use supertype
and subtype associations
335 JCA mapping
JCA mapping of function
types to activities, capabilities, and JCSFL
341 DDMS metacard for every document
card per PES XML document
A
365 Information and Data: The element
ServiceDescription is understood as the key to any
form of description of a service in a nonimplementation specific manner. Is this correctly
understood and is this then enough to convey all of
the MODAF related non-implementation specific
information as regards services?
•
30 October DM2 TWG Agenda
News
–
UPDM meeting last week (take a look at minutes)
•
•
•
•
–
–
–
–
Microfocus demo
NDIA SE DoDAF report – Dave put in References folder if releasable + our
recommendations
NDIA SE Conference – Dave see if he can get briefs
Examples (Shelton and Greg)
•
•
–
•
SoAML next meeting – Dave advise TWG
456
457
Rules tied to Measures and Activities
Agreements, Guidance, Rules have parties
Update on In-Progress for 2.01 AI’s
–
–
–
•
J65 – OV-1, 2; SV-1; SvcV-4b done. Review with J65 and DM2 data. Wrapper and PES XML doc to
go along with. Figure out where they go.
UPDM S&R example. OV-2, 3, 4, 5 markup of diagrams, Greg parsing into DM2 database, XML
generator make PES XML docs
Develop response and assign actionee for new Action Items
–
–
•
UPDM Group is finalizing and prioritizing an issue list for DM2. UPDM Group consensus is that several
issues may require extended discussion (1 hour each?). UPDM Group would like to set up a special
teleconference at a mutually convenient time
Full group every Wed
Architects alternate with us 0900 ExT, 1300 ExT
Dave send to TWG and UPDM Group Architects for weekly 2 hr 6 week series
177
251
284
guidance)
Command Relationships
OV-4
PerformerPerformerOverlap (specific case of 331 Supertype association usage
UPDM Issues List
Unassigned
456 Rules tied to Measures and
Activities
• In DM2, Rules constrain Activities
– E.g., building codes constrain building activates
• Examples of rules with measures:
–
–
–
–
–
–
Speed limit
Disorderly conduct
Most Building codes
Part size limits – constraint on the building of the part
Weight of a tank = weight of sum of parts
When weighing tanks, it is OK to weigh the parts and then add
them up
• Rules that don’t have measures:
– Murder, robbery
– Wood must be used to make (making) good furniture
• Rule obligates a party to some state of some Resource
• Which core process use cases does this apply to?
– JCIDS, PPBE, DAS, SE, Ops Planning, CPM
457 Agreements, Guidance, Rules
have parties
• Agreement def in DM2: A consent among parties
regarding the terms and conditions of activities that said
parties participate in.
• Guidance def in DM2: An authoritative (enforcer)
statement intended to lead or steer the execution of
actions of the obligated party(s).
• Rule def in DM2: A principle or condition that governs
behavior; a prescribed guide for conduct or action
–
–
–
–
Rule maker
Rule enforcer
Rule-ee – the obligated party
Some rules are agreed-to, are there ones where not
• They also have Descriptions
IDEAS Activ ity
VA Govt
Driver driving in VA
VA State Police
IndividualType
Condition
IndividualType
Activity
overlapType
activityPerformableUnderCondition
overlapType
Control
LRP, ROE, …
ruleConstraintOfActivityValidUnderCondition
Input
Car
Road
Measure
Make rules
Enforce rules
Comply with rules
Output
Activity
M
Mechanism
overlapType
activityPerformedByPerformer
overlapType
activityPerformedByPerformerTypeInstanceOfRule
Performer
Duty of policemen -- agreement
Obligation of drivers – agreement
Speed limit
overlapType
ruleConstrainsActivity
Maker
Enforcer
Complier
Guidance
Rule
In Progress
177 Command Relationships
251 OV-4
• What is the formal
nature of
Command
Relationships
shown on Org
Charts?
• Is there always an
Agreement,
Guidance, Rule,
…?
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
IS AN ALTERNATE FOR SUBORDINATE ORGANIZATION
IS IN DIRECT SUPPORT (DS) OF SUBORDINATE ORGANIZATION
IS IN GENERAL SUPPORT (GS) OF SUBORDINATE ORGANIZATION
IS IN RESERVE TO SUBORDINATE ORGANIZATION
IS REINFORCING (R) SUBORDINATE ORGANIZATION
IS UNDER OPERATIONAL COMMAND (OPCOM) OF SUBORDINATE ORGANIZATION
IS UNDER OPERATIONAL CONTROL (OPCON) OF SUBORDINATE ORGANIZATION
IS UNDER TACTICAL COMMAND (TACOM) OF SUBORDINATE ORGANIZATION
IS UNDER TACTICAL CONTROL (TACON) OF SUBORDINATE ORGANIZATION
PROVIDES LOGISTICS SERVICES TO SUBORDINATE ORGANIZATION
GIVES PRIORITY OF SUPPORT TO SUBORDINATE ORGANIZATION
IS ATTACHED TO SUBORDINATE ORGANIZATION
IS DETACHED FROM SUBORDINATE ORGANIZATION
IS GENERAL SUPPORT/REINFORCING (GSR) FOR SUBORDINATE ORGANIZATION
IS ORGANIC TO/PART OF SUBORDINATE ORGANIZATION
IS UNDER COMMAND FOR ADMINISTRATION (UCADMIN) OF SUBORDINATE
ORGANIZATION
HAS FULL COMMAND OVER SUBORDINATE ORGANIZATION
IS UNDER COMMAND FOR MOVEMENT(CFM) OF SUBORDINATE ORGANIZATION
REPORTS TO SUBORDINATE ORGANIZATION
CONTROLS SUBORDINATE ORGANIZATION
REPLACES SUBORDINATE ORGANIZATION
DOES ACCOUNTING FOR SUBORDINATE ORGANIZATION
IS SAME AS SUBORDINATE ORGANIZATION
IS ON CALL TO/STANDSBY FOR (NOT OTHERWISE SPECIFIED) SUBORDINATE
ORGANIZATION
IS ATTACKING SUBORDINATE ORGANIZATION
IS DEFENDING FROM SUBORDINATE ORGANIZATION
IS HOLDING SUBORDINATE ORGANIZATION
IS CAPTURING SUBORDINATE ORGANIZATION
IS DETAINING SUBORDINATE ORGANIZATION
IS SURVEYING SUBORDINATE ORGANIZATION
IS EXPLOITING SUBORDINATE ORGANIZATION
IS TARGETING SUBORDINATE ORGANIZATION
IS MOBILIZED TO SUBORDINATE ORGANIZATION
IS PARENT REGIMENT OF COMBAT ARMS FOR SUBORDINATE ORGANIZATION
CONTROLS TECHNICALLY SUBORDINATE ORGANIZATION
IS A MEMBER OF SUBORDINATE ORGANIZATION
RECEIVES DATA FROM SUBORDINATE ORGANIZATION
SUPPORTS MAINTENANCE OF SUBORDINATE ORGANIZATION
SUPPORTS REPAIR OF SUBORDINATE ORGANIZATION
SUPPORTS COMMUNICATIONS OF SUBORDINATE ORGANIZATION
SUPPORTS INTELLIGENCE FOR SUBORDINATE ORGANIZATION
SUPPORTS TRAINING OF SUBORDINATE ORGANIZATION
SUPPORTS DURING PEACETIME SUBORDINATE ORGANIZATION
IS AN ALTERNATE FOR SUBORDINATE ORGANIZATION-TYPE
IS IN DIRECT SUPPORT (DS) OF SUBORDINATE ORGANIZATION-TYPE
IS IN GENERAL SUPPORT (GS) OF SUBORDINATE ORGANIZATION-TYPE
IS IN RESERVE TO SUBORDINATE ORGANIZATION-TYPE
IS REINFORCING (R) SUBORDINATE ORGANIZATION-TYPE
IS UNDER OPERATIONAL COMMAND (OPCOM) OF SUBORDINATE ORGANIZATIONTYPE
IS UNDER OPERATIONAL CONTROL (OPCON) OF SUBORDINATE ORGANIZATIONTYPE
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
IS UNDER TACTICAL COMMAND(TACOM) OF SUBORDINATE ORGANIZATIONTYPE
IS UNDER TACTICAL CONTROL (TACON) OF SUBORDINATE ORGANIZATIONTYPE
PROVIDES LOGISTICS SERVICES TO SUBORDINATE ORGANIZATION-TYPE
GIVES PRIORITY OF SUPPORT TO SUBORDINATE ORGANIZATION-TYPE
IS ATTACHED TO SUBORDINATE ORGANIZATION-TYPE
IS DETACHED FROM SUBORDINATE ORGANIZATION-TYPE
IS GENERAL SUPPORT/REINFORCING (GSR) OF SUBORDINATE
ORGANIZATION-TYPE
IS ORGANIC TO/PART OF SUBORDINATE ORGANIZATION-TYPE
IS UNDER COMMAND FOR ADMINISTRATION (UCADMIN) OF SUBORDINATE
ORGANIZATION-TYPE
HAS FULL COMMAND OVER SUBORDINATE ORGANIZATION-TYPE
IS UNDER COMMAND FOR MOVEMENT OF SUBORDINATE ORGANIZATIONTYPE
REPORTS TO SUBORDINATE ORGANIZATION-TYPE
CONTROLS SUBORDINATE ORGANIZATION-TYPE
REPLACES SUBORDINATE ORGANIZATION-TYPE
DOES ACCOUNTING FOR SUBORDINATE ORGANIZATION-TYPE
IS SAME AS SUBORDINATE ORGANIZATION-TYPE
IS ON CALL TO/ IS STAND BY FOR (NOT OTHERWISE SPECIFIED)
SUBORDINATE ORGANIZATION-TYPE
IS ATTACKING SUBORDINATE ORGANIZATION-TYPE
IS DEFENDING FROM SUBORDINATE ORGANIZATION-TYPE
IS HOLDING SUBORDINATE ORGANIZATION-TYPE
IS CAPTURING SUBORDINATE ORGANIZATION-TYPE
IS DETAINING SUBORDINATE ORGANIZATION-TYPE
IS SURVEYING SUBORDINATE ORGANIZATION-TYPE
IS EXPLOITING SUBORDINATE ORGANIZATION-TYPE
IS TARGETING SUBORDINATE ORGANIZATION-TYPE
IS MOBILIZED TO SUBORDINATE ORGANIZATION-TYPE
IS PARENT REGIMENT OF COMBAT ARMS FOR SUBORDINATE
ORGANIZATION-TYPE
CONTROLS TECHNICALLY SUBORDINATE ORGANIZATION-TYPE
IS A MEMBER OF SUBORDINATE ORGANIZATION-TYPE
RECEIVES DATA FROM SUBORDINATE ORGANIZATION-TYPE
SUPPORTS MAINTENANCE OF SUBORDINATE ORGANIZATION-TYPE
SUPPORTS REPAIR OF SUBORDINATE ORGANIZATION-TYPE
SUPPORTS COMMUNICATIONS OF SUBORDINATE ORGANIZATION-TYPE
SUPPORTS INTELLIGENCE FOR SUBORDINATE ORGANIZATION-TYPE
SUPPORTS TRAINING OF SUBORDINATE ORGANIZATION-TYPE
SUPPORTS DURING PEACETIME SUBORDINATE ORGANIZATION-TYPE
HAS OTHER RELATIONSHIP TO SUBORNIDATE ORGANIZATION-TYPE
IS A COMMAND POST CELL OF SUBORDINATE ORGANIZATION-TYPE
IS AN OPERATIONAL FACILITY FOR SUBORDINATE ORGANIZATION-TYPE
IS A COMPONENT OF SUBORDINATE ORGANIZATION-TYPE
IS ESSENTIALLY THE SAME AS SUBORDINATE ORGANIZATION-TYPE
REPLACES SUBORDINATE ORGANIZATION-TYPE
IS USUALLY COLLOCATED WITH SUBORDINATE ORGANIZATION-TYPE
SUPPORTS SUBORDINATE ORGANIZATION-TYPE
284 PerformerPerformerOverlap
(specific case of 331 Supertype
association usage guidance)
Provide guidance on when to use supertype and subtype associations
As for using superclass associations, perhaps the rule is, only of same classes.
Work on matrices more
"DM2 Concepts, Associations, and
Attributes"
describedBy
disjoint
b
b
b
namedBy
b
b
b
superSubType
b
b
typeInstance
union
b
t
b
wholePartType
wholePart
temporalWholePartType
b
temporalWholePart
temporalBoundaryType
temporalBoundary
startBoundaryTypeTypeInstanceOfMeasu
re
b
startBoundaryTypeInstanceOfMeasure
startBoundaryType
startBoundary
overlapType
overlap
endBoundaryTypeTypeInstanceOfMeasur
e
b
endBoundaryTypeInstanceOfMeasure
endBoundaryType
endBoundary
beforeAfterType
Activity
beforeAfter
284 PerformerPerformerOverlap
(specific case of 331 Supertype
association usage guidance)
b
23 October DM2 TWG Agenda
•
Proposed agenda:
–
News
•
•
PACOM DoDAF Outreach visit
SoAML meeting
–
–
•
DoDAF support for Services and SoA
–
–
•
–
UPDM – maybe Len next time
396
397
399
400
Is Vision truly distinct from DesiredEffect?
How does a ServiceChannel distinguish itself from activityResourceOverlap?
Address is name for locations in general
GML
Update on In-Progress for 2.01 AI’s
•
•
•
•
•
–
not just SvcV’s but also OV’s and CV’s
SoA is an implementation for accomplishment of Services –
» Service Oriented Architecture: a paradigm for defining, organizing, and utilizing distributed capabilities in
the form of loosely coupled software services that may be under the control of different ownership domains.
It provides a uniform means to offer, discover, interact with, and use capabilities to produce desired effects
that are consistent with measurable preconditions and expectations.
Develop response and assign actionee for new Action Items
•
•
•
•
–
References\SOAML\SoaMLDM2.ppt, MDR WG meeting
New AI’s
158
176
177
251
284
DM2 - IDEAS Foundation v1.0 sync
DDMS - DM2 sync
Command Relationships
OV-4
PerformerPerformerOverlap
Accept New Action Items – TBD
Unassigned
396 Is Vision truly distinct from
DesiredEffect?
• Related to # 342
397 How does a ServiceChannel
distinguish itself from
activityResourceOverlap?
Concept of a services architecture
or composite
399 Address is name for
locations in general
IDEAS Location
IndividualType
Representation
representedBy
namedBy
na me
Na me
1
realPropertyNamedByAddress
Loca tion
Address
GeoPoliticalExtent
RealProperty
400 GML
• GML profiles are logical restrictions to
GML, and may be expressed by a
document, an XML schema or both. These
profiles are intended to simplify adoption
of GML, to facilitate rapid adoption of the
standard.
In Progress
158 DM2 - IDEAS Foundation v1.0
sync
• Ian did:
–
–
–
–
States
PowerType instances de-reified
Representation model generalized
Measures using the Categorical and Dispostional properties
• Lowell did:
–
–
–
–
–
PowerType instance + TypeInstance
Naming Pattern
CoupleType and WholePartType as PowerTypes
PowerTypes vs Types
No mixed relationships between Individuals and IndividualTypes
158 DM2 - IDEAS Foundation v1.0
sync
158
DM2 - IDEAS
Foundation v1.0 sync
IDEAS Naming and Description Pattern
representedBy
RepresentationType
represe ntation
Representa tionScheme
namedBy
describedBy
1
scheme
Sign Type
Represe ntation
typeInstance
inst ance
-
exemplar: variant
representationSchemeInstance
descri ption
na me
NameType
Type nameS pace
nameIn stance
namingSchemeInstance
NamingScheme
IndividualType
Resource
Na me
Information
replace with
pla ce
DescriptionType
Descripti onScheme
scheme
descriptionSchemeInstance
176
DDMS - DM2 sync
• DDMS Core elements mapping to DM2
• COI extention for additional AV1
information
• DDMS xml for packages uploaded to MDR
• Metacards to NCES Enterprise Catalogue
09 October DM2 TWG Agenda
• Proposed agenda:
– News
• NSA Pedigree Brief, SoAML meeting scheduled 20 Oct
• Others
– OASIS SoA Ref Arch – voted out of committee, deals with AI 395. Should be
available next week.
– Others – UPDM comments / Lars email – old items cleanup
• Quarterly special vender – DM2 session – AI Levine to Wayson
– Develop response and assign actionee for new Action Items
•
•
•
•
•
•
389
OV-1 graphic in XSD
391
Naming convention for associations
392
There is no relationship between Capability and Project
395
Prescription of "role", basis of authority
396
Is Vision truly distinct from DesiredEffect?
397
How does a ServiceChannel distinguish itself from
activityResourceOverlap?
– Accept New Action Items – TBD
389 OV-1 graphic in XSD
• Two options:
– Use Dublin Core in XSD (but not in DM2
LDM)
– Add Graphic Representation as a
representation subtype
389 OV-1 graphic in XSD
Term Name: Image
URI:
http://purl.org/dc/dcmitype/Ima
ge
Label:
Image
Definition:
A visual representation other
than text.
Comment:
Examples include images and
photographs of physical
objects, paintings, prints,
drawings, other images and
graphics, animations and
moving pictures, film,
diagrams, maps, musical
notation. Note that Image
may include both electronic
and physical
representations.
389 OV-1 graphic in XSD
IDEAS Naming and Description Pattern
Thing
1
1
{subsets places}
{subsets places}
*
*
tuple
couple
thingDescribed
thingNamed
Resource
representedBy
Information
tuple
description
+
exemplarText: String
describedBy
representation
namedBy
1
SignType
Representation
name
-
exemplar: variant
RepresentationType
IndividualType
NameType
Name
Type
InformationType
nameInstance
IndividualTypeType
RepresentationScheme
Type
NamingScheme
nameSpace
representationSchemeInstance
namingSchemeInstance
391
•
•
Naming convention for
associations
•
•
EntityVerbEntity (e.g. activityChangesResource)
EntityReverseVerbEntity (e.g.
desiredEffectIsRealizedByProjectType)
EntityEntityVerb-Realization (e.g.
capabilityPerformerManifestation) –
performerManifestsCapability
EntityVerb (e.g. serviceEnablesAccessToResource)
Also: desiredEffect, capabilityOfPerformer
•
Use first two
•
392 There is no relationship
between Capability and Project.
Project
Capability
Resource
activityPartOfProjectType
capabilityOfPerformer
Realized-by
Performer
Project
Activities
producer
activityResourceOverlap
• The Project produces the Performer that realizes
the Capability
395 Prescription of "role", basis of
authority
• A set of similar or otherwise logically related activities,
implying a set of skills or capabilities, to which a
performer may be assigned.
• Rules divide Activities into ones following, ones not
following
• Service Joint Action – consumer, producer
• Authority vectors – Rules are made by someone,
enforced by others
– Geopolitical, law, … for flow of information
– Injection, …
• OV-4 indicates required information flows
• Authority modeling has additional roles in SoA
395 Prescription of "role", basis of
authority
Legal rules
Employment
Agreement
?
describes
?
?
Employment
Agreement
document or
utterance
Make lease agreement as a landlord
Performer A
Employer
Act I =
must pay
Make lease agreement as a tenant
Is-boss-of
Works-for
Responsibility?
Authority?
Delegation?
Performer
C Alternate
Employee
Constraint? (type of input)
Act n =
must
show up Consuming activities?
Performer B Employee
on time
Act n+1 =
do what
the boss
says
396 Is Vision truly distinct from
DesiredEffect?
397 How does a ServiceChannel
distinguish itself from
activityResourceOverlap?
02 October DM2 TWG Agenda
•
Proposed agenda:
– News
• AF DM2 – IDEAS – BORO briefing
• NIEM Conference – Conrad Bock and James Odell to help Dave Ellis with SoA RM
• Ontology in IC
– Develop response and assign actionee for new Action Items
•
•
•
•
•
•
•
•
383
385
386
388
389
390
391
392
Rules and Contexts
XSD encoding -- done
serviceEnablesAccessTo
SvcV9
OV-1 graphic in XSD
Fix Measures
Naming convention for associations
There is no relationship between Capability and Project.
– Accept New Action Items – TBD
– Others – questions on intent of model related to SoAML (Cory will send info)
383
Rules and Contexts
IDEAS Domain Class Hierarchy
IndividualType
Guidance
Rule
Individual-A Thing that has spatio-temporal extent.
IndividualType-The Powertype of Individual.
383
•
Are there examples of Rules that don't have spatio-temporal extent?
–
–
•
For example, does the Constitution exist separate from any printed copy?
–
•
Rules have representations, e.g., as printed documents, utterances, …
Should the context of a Performer WRT a rule constraining an Activity be generalized?
–
•
No examples but believed to exist in theory
Rules – ROE, Laws Regulation and Policy, not “laws” of physics
???
Rules and superrules?
–
Supertype of rule is proposition (e.g., subject predicate object)
•
•
All-cars will-drive under-45
45-mph-rule constrains Drive
•
See SBVR WRT rules, operative rules, and enforcement
•
The authority and maker of the rules
–
•
The authority makes the description of the rule (information)
Assertions and proposition
–
–
–
Utterances and information describe and represent assertions and propositions
Produced by Activities performed by performers
Consumed too
383
Rules and Contexts
•
SBVR:
•
Rules play a very important role in defining business semantics: they can influence or guide
behaviours and support policies, responding to environmental situations and events. This means
that rules represent the primary means by which an organization can direct its business, defining
the operative way to reach its objectives and perform its actions.
The rule-based approach aims to address two different kinds of users:
it addresses business communities, in order to provide them with a structured approach, based on
a clear set of concepts and used to access and manage business rules;
it addresses IT professionals, in order to provide them with a deep understanding about business
rules and to help them in models creation. The rules-based approach also helps bridge the rift that
can occur between the data managers and the software designers.
The essence of the rule-based conceptual formalizations is that rules build on facts, and facts
build on concepts as expressed by terms [8]
SBVR Structural Business Rules use two alethic modal operators:
•
•
•
•
•
–
–
•
it is necessary that …
it is possible that …
SBVR Operative Business Rules use two deontic modal operators:
–
–
it is obligatory that …
it is permitted that …
•
•
•
Modalities of necessity and possibility are called alethic modalities. They are also sometimes called
special modalities, from the Latin species. Modal logic was first developed to deal with these
concepts, and only afterward was extended to others. For this reason, or perhaps for their familiarity
and simplicity, necessity and possibility are often casually treated as the subject matter of modal
logic. Moreover it is easier to make sense of relativizing necessity, e.g. to legal, physical, nomological,
epistemic, and so on, than it is to make sense of relativizing other notions.
In classical modal logic, a proposition is said to be
possible if and only if it is not necessarily false (regardless of whether it is actually true or actually
false);
–
–
•
•
•
•
•
•
necessary if and only if it is not possibly false; and
contingent if and only if it is not necessarily false and not necessarily true (ie. possible but not necessarily true).
In classical modal logic, therefore, either the notion of possibility or necessity may be taken to be
basic, where these other notions are defined in terms of it in the manner of De Morgan duality. treats
possibility and necessity as not perfectly symmetric.
For those with difficulty with the concept of something being possible but not true, the meaning of
these terms may be made more comprehensible by thinking of multiple "possible worlds" (in the
sense of Leibniz) or "alternate universes"; something "necessary" is true in all possible worlds,
something "possible" is true in at least one possible world. These "possible world semantics" are
formalized with Kripke semantics.Deontic logic
Deontic logic
Likewise talk of morality, or of obligation and norms generally, seems to have a modal structure. The
difference between "You must do this" and "You may do this" looks a lot like the difference between "This is
necessary" and "This is possible". Such logics are called deontic, from the Greek for "duty". One
characteristic feature of deontic logics is that they lack the axiom T semantically corresponding to the
reflexivity of the accessibility relation in Kripke semantics: in symbols, . Interpreting as "it is obligatory that",
T informally says that every obligation is true. For example, if it is obligatory not to kill others (i.e. killing is
morally forbidden), then T implies that people actually do not kill others. This consequence is obviously false.
However, in Kripke semantics for deontic logic, T is supposed to hold at accessible worlds (relative to the
actual world w). These worlds are to be thought of as idealized in the sense that all obligations (in w) are
fulfilled there. Hence a sentence A is obligatory just in case A holds at all idealized worlds. So in order to
discuss obligations under Kripke semantics, there must be some world where , where everything that ought
to be the case, is the case. Though this was one of the first interpretations of the formal semantics, it has
recently come under criticism. See e.g. Sven Hansson, "Ideal Worlds--Wishful Thinking in Deontic Logic",
Studia Logica, Vol. 82 (3), pp. 329-336, 2006.
One other principle that is often (at least traditionally) accepted as a deontic principle is D, , which
corresponds to the seriality (or extendability or unboundedness) of the accessibility relation. It is an
embodiment of the Kantian idea that "ought implies can". (Clearly the "can" can be interpreted in various
senses, e.g. in a moral or alethic sense.)
385
XSD encoding
• <?xml version="1.0" encoding="UTF-8"?>
• <!-- Auto-Generated by Model Futures IDEAS Add-In for
Sparx EA -->
• <!-- XML Schema format designed by Model Futures Ltd
and Silver Bullet inc. on behalf of UK MOD and US DoD
-->
• <xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:dm2="http://www.ideasgroup.org/dm2"
xmlns:ism="urn:us:gov:ic:ism:v2"
xmlns:ideas="http://www.ideasgroup.org/xsd"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
386 serviceEnablesAccessTo
•
•
•
•
•
•
Access to the hamburger, or the cook?
Joint Action
Difference / relationship between Service and Service Port:
Service is a type of Performer
Service Port is a type of Performer that is a part of the Service performer
The Service Port is the part of the access mechanism that the service
consumer’s port interacts with
IDEAS Serv ices
IndividualResourceStateType
Resource
Performer
overlapType
serv iceEnablesAccessTo
Service
388
SvcV9
388
SvcV9
• Motivation for SV-9:
– Dave recalls
• Justify S&T programs by showing the PORs /
Capabilities they were transition or contribute
• Forecast commercial technologies DoD would look
to adopting someday
– Clarence, from C4ISR f/w
• Defines underlying current and expected
technologies, reasonably forecast for milestones
25 September DM2 TWG Agenda
•
Proposed agenda:
–
News
•
UCORE meeting – briefed DM2; COI class; NIEM Conference next week; UCORE Semantic Layer
(SL)
–
–
–
•
JCS J6 meeting
–
–
•
•
–
Automated database fed EISP tool algorithms, tools, queries, to help with interop assessment
» Use cases
Action Officer, not architect’s perspective
» Refine info rqmts
JIAWG Fed Arch Exch SWG
Others TBD
Develop response and assign actionee for new Action Items
•
•
•
•
•
•
–
–
Maybe look at NIEM someday
SOPES – UML profile for JC3IEDM / NIEM
FEA(F) / FSM – Federal CIO Council – maybe talk to about DM2
379
381
383
385
386
388
Service Ports -- done
Tuples instances of Measure – in progress
Rules and Contexts
XSD encoding -- done
serviceEnablesAccessTo
SvcV9
Accept New Action Items – TBD
Others -- TBD
379
Service Ports
• Operation, event, activity, function – UML
– DM2 “activity” ?= UML “activity”
IDEAS Serv ices
Performer
overlapType
serv iceEnablesAccessTo
Service
WholePa rtType
portPartOfPerformer
Port
ServicePort
http://www.modaf.org.uk/gSOV/
381 Tuples
instances of
Measure
381 Tuples instances of Measure
18 September DM2 TWG Agenda
•
Proposed agenda:
1. News
•
•
•
•
•
UPDM meeting
NARS DM2 possibility
Description documents
Collab site updates
Share EA model of SoA Ref Arch F/W
2. Develop response and assign actionee for new Action Items
•
•
•
•
•
372
373
376
377
378
Parts or overlaps of Performers
Skill and Activity link
Project definitions
Service channels and ports
Service describedBy
3. Accept New Action Items -- TBD
Description Docs & Briefs
#372
Parts or overlaps of
Performers
•
Examples of PersonType:
– Users of a given IT system
– a Military Occupational Specialty
(MOS) – GM1st class
– Billet = GM1st class on Arleigh
Burke
•
•
•
Skill “requiredby” to Person Type:
DM2 2.0 = WP
IDEAS & DM2 2.01 = propertyOfType
#366
materialPartOfPerformer
definition
• From Dave Ellis:
Role ~ PersonType,
Org, or Org Type
• Role transience?
• Billet/Post PO Org /
OT?)
• Skills – competency?
class Roles, rights and Responsibilities
member of
Social-Structure
adopts
defines
Participant
possesses
requires
Qualification
Right
Role
-
Responsibility
Transferable: boolean
Authority
enables
has
Task
requires
requires
permits
Action
ensures
competence
Skill
#373
Skill and Activity link
Possibly related
to Training /
Skill / Education
deferred AI’s
#18, # 31,
IDEAS Training, Skill, Education
DispositionalProperty
Ski ll
IDEAS Activ ity
propertyOfType
skillOfPersonType
IndividualType
Activity
Performer
PerformerCapableOfResponsibility
PersonType
overlapType
activityPerformedByPerformer
Performer
#376
Project definitions
IDEAS Proj ect
IndividualType
Vision
BeforeAfterType
visionIsRealizedByDesiredEffect
overlapType
desiredEffect
An overlap between the desired future state of a Vision and the Desired Effects that
provide the disposition for its manifestation
#377
Service channels and ports
IDEAS Serv ices
IndividualType
Activity
produces
consumes
overlapType
IDEAS Serv ices
serviceChannel
Performer
• The producing Activity is
performed by the provider’s
ServicePort?
• The consuming Activity is
performed by the
consumer’s ServicePort?
Service
Port
ServicePort
#378
Service describedBy
• Should use two tuples
• Probably should be
specialized
IDEAS Serv ices
consumerBei ngDescribed
tuple
descri ption
ServiceDe scription
describedBy
providerBei ngDescribed
ServicePort
11 September DM2 TWG Agenda
•
Proposed agenda:
1. News
•
•
•
TWG resched results – another week of afternoon, then alternate
to morning
TWG folder on collab site
Examples candidates – SAR, ISP (NCES, DRRS, Stryker, JHSV,
E-2D), …
– Would be good to have UML and non-UML, SysML, BPMN, examples
•
•
DM2 CM – need a DoD EA COI TOR or plan or MOA or …
OMG next week – changes to UPDM 1.0 and UPDM 2.0 groups
– UML Futures workshop on Sunday. RFI responses – e.g., Conrad
Bock’s. RFI responses are on the OMG server.
2. Develop response and assign actionee for new Action Items
3. New Action Items (UML 3, …)
– Download Open Group SoA standards body and put in references
– OASIS 2nd review of SoA ref arch by mid-Oct
#365
Information and Data
• MODAF Service Descriptions:
#366
materialPartOfPerformer
definition