DTIC ADA466711: Using a Combination of UML, C2RM, XML, and Metadata Registries to Support Long-Term Development/Engineering

70 Pages·1.3 MB·English

by  Defense Technical Information Center

Using a Combination of UML, C2RM, XML, and
Using a Combination of UML, C2RM, XML, and
Metadata Registries to Support Long-Term
Metadata Registries to Support Long-Term
Development/Engineering
Development/Engineering
Open Forum 2003 on Metadata Registries
Knowledge Management and Learning Technologies Track
10:30 – Noon, 23 January 2003
Author: Dr. Israel Mayk, CERDEC
Co-authors: MAJ (IDF) Avi Yariv (IDF/CERDEC ESEP) and
Bernard Goren (CERDEC)
Report Documentation Page Form Approved
OMB No. 0704-0188
Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and
maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,
including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington
VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it

does not display a currently valid OMB control number.
1. REPORT DATE 3. DATES COVERED
JAN 2003 2. REPORT TYPE 00-00-2003 to 00-00-2003
4. TITLE AND SUBTITLE 5a. CONTRACT NUMBER
Using a Combination of UML, C2RM, XML, and Metadata Registries to
5b. GRANT NUMBER
Support Long-Term Development/Engineering
5c. PROGRAM ELEMENT NUMBER
6. AUTHOR(S) 5d. PROJECT NUMBER
5e. TASK NUMBER
5f. WORK UNIT NUMBER
7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION
Army Communications-Electronics RD&E Center,Fort REPORT NUMBER
Monmouth,NJ,07703
9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)
11. SPONSOR/MONITOR’S REPORT
NUMBER(S)
12. DISTRIBUTION/AVAILABILITY STATEMENT
Approved for public release; distribution unlimited
13. SUPPLEMENTARY NOTES
The original document contains color images.
14. ABSTRACT
15. SUBJECT TERMS
16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF 18. NUMBER 19a. NAME OF
ABSTRACT OF PAGES RESPONSIBLE PERSON

a. REPORT b. ABSTRACT c. THIS PAGE 69
unclassified unclassified unclassified
Standard Form 298 (Rev. 8-98)
Prescribed by ANSI Std Z39-18
Objective
Objective
• To facilitate C2 Architecture and Applications
development in terms of a formal language for C2 based
upon a C2RM
• To derive the rules for analyzing and parsing C2
Products from Natural Language to Machine Language
for use by C2 Applications.
• To leverage commercial representation and modeling
languages such as the Unified Modeling Language
(UML) and Extensible Markup Language (XML and
associated tools.
Open Forum 2003 on Metadata Registries Israel Mayk, US Army CERDEC 2 of 67
Why Reference Models
Why Reference Models
• “ By creating compelling reference models of (domain) knowledge, we lead
our organizations into the appropriate conclusions.”
• “Reference models are the patterns of the solution for transforming
perception into real-world success.”
• “Reference models simplify problem solving, so that ordinary professionals
can practice their discipline with world-class results”
• “Software professionals need reference models in order to understand
abstractions”
• “20% of adults have the appropriate world-perspective to define
abstractions.”
• “Reference models (and reference architectures) are necessity in the
confusing, rapidly changing technology environment in which we practice”
• “Reference models are commonplace in fields of human endeavor”
See Software Architect Bootcamp, Raphael Malveau and Thomas J.
Mowbray, Prentice Hall, 2001, p.238-239
Open Forum 2003 on Metadata Registries Israel Mayk, US Army CERDEC 3 of 67
Relationship of C2UML to C2RM C2RA, and C2XML
Relationship of C2UML to C2RM C2RA, and C2XML
Model Driven
C2RM C2RA
Process
C2XML C2UML
Open Forum 2003 on Metadata Registries Israel Mayk, US Army CERDEC 4 of 67
KEY XML SPECIFICATIONS AND STANDARDS
KEY XML SPECIFICATIONS AND STANDARDS
Adapted from Zapthink
Adapted from Zapthink
Public Sector
nity ary Math & Sciences GovLeergnamlent Pu&b lPisrhinintg ScLieinfec es Command Finance CusItnofmoer CoLnsatnrdu/ct’n T(Rreacvieple/FMoLod)
mu bul Chemistry Math & Education & (ACORD)
Com Voca A(CshtreomnMomL)y Numerics (Le(gEaMlXLM)L) ((NDeowcBsMooLk)) ((BGIEOMMLL)) C(Co2nMtrLo)l ((MXBDRDLL)) ((xxCCRILL)) (L(aNnVdXMMLL) ) RHesuomuracnes
(SIF)
ADML MathML (HR-XML)
Document-Oriented Specifications
E-Business Rosetta eMktPlaces eCommerce
cXML, xCBL XML/EDI
s Vocabulary Net Internet &
n Security Content Semantic Presentat’n Computing
Universal Business Language (UBL)
o
i Web
t
a User Services
c Encrypt’n Graphics /
Interface Directory
fi WSXL (XKMS) Multimedia (DSML)
i
c (SVG) (SPML)
e
ebXML (SMIL)
p Workflow / Resource
PIP Authenticat’n Content (VRML)
d S Process WSFL BPSS (XCBF) (MDnAgmSLnt) D(eRscDripFt)’n Inte(rTnatM’naSliz)at’n
e Web
t (WebDAV) (XLIFF)
n Authorizat’n
e Registry Registry/ (XHTML)
ri UDDI Repository (XACML) (LogML) Device
O (SAML) Content Ontology Interface
Syndicat’n (OML)
- Voice (SpecML)
e Privacy (OWL)
g (ICE)
a Service WSDL PIP CPP/A (RSS) (CCXML) Database
s (P3P) Tonic (WML) (XQuery)
s
e Digital Rights Maps
M RNIF MSS Management (XTM) Telecommunicat’n Instant
Messaging (WML) Messaging/
SOAP Transport Protocol (XrML) (CPL) P2P
(HTTP/SMPT/FTP) (Jabber)
s Document Linking Style & Transformation Schema & Validation
L n
Mtio (XPath) (XSL & XSLT) (XML Schema)
Xa
c
e fi
Corpeci
S EXTENSIBLE MARKUP LANGUAGE (XML)
Open Forum 2003 on Metadata Registries Israel Mayk, US Army CERDEC 5 of 67
C2 Product Example: Operations Order (OPORD)
C2 Product Example: Operations Order (OPORD)
Five-Paragraph Meta-model based upon
(cid:139)Situation FM 101-5, Staff Organization and Operations
(cid:139)The Enemy Forces
(cid:139)Who are they? What kind of unit is it? What kind of Equipment do they have?
(cid:139)Where are they? How strong are they? Where are they effective?
(cid:139) How capable are they? What are they likely to do?
(cid:139)The Friendly Forces
(cid:139)What is our higher echelon mission and Concept of Operation? What is the mission of adjacent units?
(cid:139)Mission
(cid:139)A clear concise, statement of what the unit is to do to include who,where, when, and
why of the operation.
(cid:139)Execution
(cid:139)What is the Concept of Operation? How to maneuver, how to fire, how to deal with
obstacles? In Offense: what unit formations, movement techniques, routes of
advance? On Defense: what battle positions to establish, weapon orientation,
engagement plan, +more.
(cid:139)Service Support
(cid:139)Where is refueling, How? Where is the collection point of damaged vehicles?
(cid:139)Command and Signal
(cid:139)How communications will be maintained?
(cid:139)What is the command succession?
Open Forum 2003 on Metadata Registries Israel Mayk, US Army CERDEC 6 of 67
C2RM Generic Entity
C2RM Generic Entity
Identification
Sensors
(Images)
Communication
Infliction
Transceiver
Weapon C2
(Messages)
(Ordnance)
Transportation
Vehicle (Cargo)
Open Forum 2003 on Metadata Registries Israel Mayk, US Army CERDEC 7 of 67
C2RM Generic Package Classes
C2RM Generic Package Classes
Image
Message
Photons, Sounds, Scent,
Voice, Text,
Touch, Electromagnetic,
Alert,
Radiation Sensor Sensor
Electronic
C2 C2
Wpn Tcvr Tcvr Wpn
Ordnance
Vehicle Vehicle
Bombs, Bullets, Shells,
Missiles, Photons,
Cargo
Gas, Water, Stones
Crate,Pallet,
Own Weight,
Supply, Stowage
Open Forum 2003 on Metadata Registries Israel Mayk, US Army CERDEC 8 of 67
Fundamental types of Interactions
Fundamental types of Interactions
F F F1
a) Infliction/Effects
b) Identification
G G F2
d) Transportation
Legend:
F1 Resource
F1
Friend Foe
F G
Inflictions/effects
c) Communication
Identifications
F
Communications
F2
F2
Transportations
Open Forum 2003 on Metadata Registries Israel Mayk, US Army CERDEC 9 of 67