dodaf cadm/ap233 interoperability project
DESCRIPTION
DODAF CADM/AP233 Interoperability Project. David Price OSJTF March 2006. System-of-systems engineering requires Greater collaboration and tool interoperability, and … Using robust modeling techniques for describing systems architectures. Request. System Model. Response. - PowerPoint PPT PresentationTRANSCRIPT
®
DODAF CADM/AP233 Interoperability Project
David PriceOSJTF
March 2006
®
Our Focus is on SE Standards
• Enable communication between SAs/SEs and the tools they use– Approach described in white paper : Using
Systems Engineering Standards In an Architecture Framework
– Influenced by DoD, INCOSE, ISO STEP and OMG communities
•System-of-systems engineering requires •Greater collaboration and tool interoperability, and …•Using robust modeling techniques for describing systems architectures
Request
Response
SystemModel
®
MoDAF or UPDMArchitectureRepository
Request
Response
SystemModel
DoD ArchitectureRepository System
DOD CADM
Operational
Systems
Technical
DODAF
Any SE Tool
specifies requirements for
ISO STEP-enabledDownstream Tool
®
ISO TC184/SC4 Industrial Data
®
AP233 Systems Engineering
• On-schedule for AP233 modules to go out for ISO ballot starting in the summer– Committee Draft ballot (July-October 2006)– After ballot completes, workshops are held to address
ballot comments– AP233 modules should be published 1Q2007
• The complete AP233 Application Protocol that includes Business Use Cases, etc. takes a bit longer
Critical Testing Happens Here
ISO Ballot
®
AP233 Scoperequirements
text-based
property-based
breakdownsstatic
structure
PDM
link to analysisbehaviour
productstructure
systemsub-system
functionalbreakdown
WBS
verification &validationfunction-based
model presentation
configcontrol
security
risk measurement
person &org
Complete Edition 2
Legend
state-based
rules(moved to AP210)
®
AP233 Testing
• AP233 Development Team is working strategy for critical testing– Includes internal team testing– Includes approaching vendors to participate
• AP233 Team developing a “test harness”– Fitting into the “test harness” is now the main
focus for the DODAF CADM/AP233 demo work– Dwayne made significant contribution to the
architecture of this – The bad news though: Previous “cool
CADM/AP233 demos” are broken into bits at the moment
®
AP233 Test harness
Repository
Test data creation tools
VisioFreemindExcelUML 2/SysMLCADM examples…
XML AP233 XMLTranslate via:
Import/Export
Web Viewers, Graphical Viewersand Available SE Tools
XSLTRubyJava
®
DoDAF CADM/AP233 Project
®
DoDAF CADM/AP233 Project
• Purpose– Evaluate feasibility of system architecture data
exchange using emerging ISO AP233 Systems Engineering standard
• Not a fully validated design effort
– Provide a body of work that future efforts can build upon
®
Proving this path
®
CADM/AP233 Process Steps
Id CADM vs.AP233 Gaps
Complete AP233Modules for Gaps
Produce AP233Draft
Define CADM/AP233Mappings
Create AP233Test CasesDevelop CADM/AP233
Translator
DemonstrateCADM/AP233
Translator
TOOLS
®
Operational
Systems
Technical
Operational Concept Description (OV-1)
Node Connectivity Description (OV-2)
X YXZ
XY
Y
Systems InterfaceDescription (SV-1)
Operational Activity Model (OV-5)
Information Exchange Matrix
(OV-3)
Activity to System Function (SV-5)
System Functionality Description (SV-4)
Organizational Relationships Chart (OV-4)
Systems Data Exchange Matrix (SV-6)
Operational Activity Sequence and Timing
Description (OV-6 a/b/c)
NODE A
Local Area Net
System 1 System 2
System 3 System 4
System 5
EXTERNALCONNECTION(OUTSIDE THENODES OF INTEREST)
CONNECTIONTO NODE B
CONNECTIONTO NODE B
CONNECTIONTO NODE C
Two-WayCommunicationsLinks
One-WayCommunicationsLink
Systems Communications Description (SV-2)
System - System Matrix (SV-3)
Systems Technology Forecast (SV-9)
Standards Technology Forecast (TV-2)
Technical Architecture Profile (TV-1)
Systems Performance Parameters Matrix (SV-7)
• ----------------------------------------------------------------
• .....• .....• .....
Logical Data Model (OV-7)
Systems Functionality Sequence and Timing
Description (SV-10 a/b/c)
Systems Evolution Description (SV-8)
Physical SchemaSV-11
A B C
T1T2T3
NODESTIME
A B C
T1T2T3
NODESTIME
DoDAF Views Coverage
®
Operational
Systems
Technical
Operational Concept Description (OV-1)
Node Connectivity Description (OV-2)
X YXZ
XY
Y
Systems InterfaceDescription (SV-1)
Operational Activity Model (OV-5)
Information Exchange Matrix
(OV-3)
Activity to System Function (SV-5)
System Functionality Description (SV-4)
Organizational Relationships Chart (OV-4)
Systems Data Exchange Matrix (SV-6)
Operational Activity Sequence and Timing
Description (OV-6 a/b/c)
NODE A
Local Area Net
System 1 System 2
System 3 System 4
System 5
EXTERNALCONNECTION(OUTSIDE THENODES OF INTEREST)
CONNECTIONTO NODE B
CONNECTIONTO NODE B
CONNECTIONTO NODE C
Two-WayCommunicationsLinks
One-WayCommunicationsLink
Systems Communications Description (SV-2)
System - System Matrix (SV-3)
Systems Technology Forecast (SV-9)
Standards Technology Forecast (TV-2)
Technical Architecture Profile (TV-1)
Systems Performance Parameters Matrix (SV-7)
• ----------------------------------------------------------------
• .....• .....• .....
Logical Data Model (OV-7)
Systems Functionality Sequence and Timing
Description (SV-10 a/b/c)
Systems Evolution Description (SV-8)
Physical SchemaSV-11
A B C
T1T2T3
NODESTIME
A B C
T1T2T3
NODESTIME
DoDAF Views CoverageDelivered now
®
Operational
Systems
Technical
Operational Concept Description (OV-1)
Node Connectivity Description (OV-2)
X YXZ
XY
Y
Systems InterfaceDescription (SV-1)
Operational Activity Model (OV-5)
Information Exchange Matrix
(OV-3)
Activity to System Function (SV-5)
System Functionality Description (SV-4)
Organizational Relationships Chart (OV-4)
Systems Data Exchange Matrix (SV-6)
Operational Activity Sequence and Timing
Description (OV-6 a/b/c)
NODE A
Local Area Net
System 1 System 2
System 3 System 4
System 5
EXTERNALCONNECTION(OUTSIDE THENODES OF INTEREST)
CONNECTIONTO NODE B
CONNECTIONTO NODE B
CONNECTIONTO NODE C
Two-WayCommunicationsLinks
One-WayCommunicationsLink
Systems Communications Description (SV-2)
System - System Matrix (SV-3)
Systems Technology Forecast (SV-9)
Standards Technology Forecast (TV-2)
Technical Architecture Profile (TV-1)
Systems Performance Parameters Matrix (SV-7)
• ----------------------------------------------------------------
• .....• .....• .....
Logical Data Model (OV-7)
Systems Functionality Sequence and Timing
Description (SV-10 a/b/c)
Systems Evolution Description (SV-8)
Physical SchemaSV-11
A B C
T1T2T3
NODESTIME
A B C
T1T2T3
NODESTIME
DoDAF Views CoverageNext month
®
Operational
Systems
Technical
Operational Concept Description (OV-1)
Node Connectivity Description (OV-2)
X YXZ
XY
Y
Systems InterfaceDescription (SV-1)
Operational Activity Model (OV-5)
Information Exchange Matrix
(OV-3)
Activity to System Function (SV-5)
System Functionality Description (SV-4)
Organizational Relationships Chart (OV-4)
Systems Data Exchange Matrix (SV-6)
Operational Activity Sequence and Timing
Description (OV-6 a/b/c)
NODE A
Local Area Net
System 1 System 2
System 3 System 4
System 5
EXTERNALCONNECTION(OUTSIDE THENODES OF INTEREST)
CONNECTIONTO NODE B
CONNECTIONTO NODE B
CONNECTIONTO NODE C
Two-WayCommunicationsLinks
One-WayCommunicationsLink
Systems Communications Description (SV-2)
System - System Matrix (SV-3)
Systems Technology Forecast (SV-9)
Standards Technology Forecast (TV-2)
Technical Architecture Profile (TV-1)
Systems Performance Parameters Matrix (SV-7)
• ----------------------------------------------------------------
• .....• .....• .....
Logical Data Model (OV-7)
Systems Functionality Sequence and Timing
Description (SV-10 a/b/c)
Systems Evolution Description (SV-8)
Physical SchemaSV-11
A B C
T1T2T3
NODESTIME
A B C
T1T2T3
NODESTIME
DoDAF Views CoverageMay - July
®
Delivered as of March 2006
• Web site documenting AP233 and CADM/AP233 mapping
®
Delivered as of March 2006 (2)
• New additions to AP233 covering– State machines suite– Assigning descriptions to anything– Some gaps filled in Interface schemas
• New API for creating the AP233 XML– Ruby is a language for proof-of-concept
implementation, not designed for production software support
®
CADM/AP233 Testing
• Fitting into the “AP233 test harness” is current focus of my the DODAF CADM/AP233 demo work– Dwayne made a significant contribution to the
architecture of this – Also changing test tools to enabling other AP233
team members to create test data
• So, earlier “cool CADM/AP233 demos” are broken into bits at the moment– Can show a few test harness components today
®
Conclusions
• Confirmed ideas from white paper that AP233 can support DOD DODAF/CADM data interchange requirements– Will complete DODAF CADM/AP233 Gap Analysis
before AP233 ballot ends – Keeping an eye on the OMG SysML, UPDM, etc. to
identify gaps in AP233
• Positive, direct impact on AP233 completeness by this OSJTF project
• DOD in a position for future validation to build on these efforts (e.g. AP233, SysML, UPDM)
®
Many things are coming together
Critical Testing Happens Here
ISO Ballot
®
Contact Information
• David Price– [email protected]– +1 336 283-0606 or +44 20 7221 7307– exff Systems Engineering
• http://www.exff.org/ap233
• AP233– NASA AP233 Page at http://www.ap233.org
• DoDAF– DoD NII Archive at http://www.defenselink.mil/nii/doc
• SysML– OMG SysEng SIG at http://syseng.omg.org/
• The International Council on Systems Engineering– INCOSE at http://www.incose.org
®
Operational
Systems
Technical
Operational Concept Description (OV-1)
Node Connectivity Description (OV-2)
X YXZ
XY
Y
Systems InterfaceDescription (SV-1)
Operational Activity Model (OV-5)
Information Exchange Matrix
(OV-3)
Activity to System Function (SV-5)
System Functionality Description (SV-4)
Organizational Relationships Chart (OV-4)
Systems Data Exchange Matrix (SV-6)
Operational Activity Sequence and Timing
Description (OV-6 a/b/c)
NODE A
Local Area Net
System 1 System 2
System 3 System 4
System 5
EXTERNALCONNECTION(OUTSIDE THENODES OF INTEREST)
CONNECTIONTO NODE B
CONNECTIONTO NODE B
CONNECTIONTO NODE C
Two-WayCommunicationsLinks
One-WayCommunicationsLink
Systems Communications Description (SV-2)
System - System Matrix (SV-3)
Systems Technology Forecast (SV-9)
Standards Technology Forecast (TV-2)
Technical Architecture Profile (TV-1)
Systems Performance Parameters Matrix (SV-7)
• ----------------------------------------------------------------
• .....• .....• .....
Logical Data Model (OV-7)
Systems Functionality Sequence and Timing
Description (SV-10 a/b/c)
Systems Evolution Description (SV-8)
Physical SchemaSV-11
A B C
T1T2T3
NODESTIME
A B C
T1T2T3
NODESTIME
DoDAF Views CoverageDelivered now
Next monthMay - July
®
Delivered as of March 2006
• Web site documenting AP233 and CADM/AP233 mapping covering:– SV-1 Systems Interface– SV-2 System Communications– SV-3 System Functionality– SV-4 System-System Matrix– SV-10b, SV-10c System Sequence and States– OV-5 Operational Activity Model– OV-6b, OV-6c Operational Activity Sequence and
States– TV-1 Technical Standards Profile
• See http://www.exff.org/ap233
®
NIST Project April – July 2006 (1)
• DODAF/AP233 Deliverable Set 1– OV-4 Organizational Relationships Chart– OV-3 Operational Information Exchange Matrix– OV-2 Operational Node Connectivity Description
• DODAF/AP233 Deliverable Set 2– SV-5 Operational Activity to Systems Function
Traceability Matrix– SV-7 Systems Performance Parameters Matrix– SV-6 Systems Data Exchange Matrix
®
NIST Project April – July 2006 (2)
• DODAF/AP233 Deliverable Set 3– OV-6a Operational Rules Model– SV-10a Systems Rules Model– SV-8 Systems Evolution Description– SV-9 Systems Technology Forecast– TV-2 Technical Standards Forecast
• DODAF/AP233 Deliverable Set 4– AV-2 Integrated Dictionary– AV-1 Overview and Summary Information– OV-1 High-Level Operational Concept Graphic
• DODAF/AP233 Deliverable Set 5– OV-7 Logical Data Model– SV-11 Physical Schema