WMA Architecture Federation and Integration Project

WMA Architecture Federation and Integration Project - Description

WG Meeting. 23 May 2013. (Draft). Bill Piazza. Architecture Federation Branch Chief. JS J6 DD C2I. 1. Agenda. Phase 4/Sprint 11 Wrap-up and Demo. JIE/JTSO architecture support updates. Portal improvements. ID: 719968 Download Presentation

8K - views

WMA Architecture Federation and Integration Project

WG Meeting. 23 May 2013. (Draft). Bill Piazza. Architecture Federation Branch Chief. JS J6 DD C2I. 1. Agenda. Phase 4/Sprint 11 Wrap-up and Demo. JIE/JTSO architecture support updates. Portal improvements.

Similar presentations


Download Presentation

WMA Architecture Federation and Integration Project




Download Presentation - The PPT/PDF document "WMA Architecture Federation and Integrat..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.



Presentation on theme: "WMA Architecture Federation and Integration Project"— Presentation transcript:

Slide1

WMA Architecture Federation and Integration ProjectWG Meeting23 May 2013(Draft)

Bill PiazzaArchitecture Federation Branch ChiefJS J6 DD C2I

1

Slide2

AgendaPhase 4/Sprint 11 Wrap-up and DemoJIE/JTSO architecture support updatesPortal improvements

WMA Architecture Governance UpdateInitial WMA Architecture Data Standards (Army/ArCADIE Issues/Comments)Phase 4/Sprint 12 outline

Partner Updates

2

Slide3

Phase 4 Key Focus AreasJIE/JTSO SupportAutomated structured data handling

Data-Enabled Standardized ViewsWMA Architecture Federation Formal GuidanceCurrently an ad-hoc WG w/o formal charterNo formal governance to use what is being developedPartner Support

Intelligence and Business Mission Area outreach

Requirements for key federation touch points

3

Slide4

Automated Structured Data Handling

Objective: Streamline and automate the accessibility and reusability of structured WMA (and JIE) architecture data sets using web services (when feasible)From*: WMA internal databases (JAR, JMTs)External Web Services (

ArCADIE

, AFEAR, NEAR, MARS)

External COTS exports (JIE/JTSO SA XML,

MagicDraw

XMI)

Excel Templates (i.e. USNORTHCOM)

Establish Requirements for sharing to: JS J6 Capability Analysis tools, T&E, M&S, DTIC, GTG-F (E-ISP)

*FEDERATION to these authoritative sources, not managing a “master data repository”

4

Slide5

Data-Enabled Standardized Views

Objective: Display structured architecture data, regardless of source, in a standardized template to support analysis processes (including validation and verification) and reuseFor Phase 4 the focus will be on:Taxonomies CV-2 and AV-2Capability Views

CV-4, CV-6

Operational Views

OV-2,

OV-3, OV-4

, OV-5a, OV-6a

System Views

SV-1, SV-2, SV-4, SV-5, SV-6

Service Views

SvcV-1, SvcV-2, SvcV-4, SvcV-5, SvcV-6

Standards View (StdV-1)Hybrid views to support NR-KPP analysis processBold/Underline indicates work started in Phase 3

5

Slide6

WMA Architecture Federation Formal GuidanceNeed formal guidance to ensure continued partner and stakeholder engagement.

Guidance for WMA architectures will be formalized under upcoming JS Charters/CJCSI to support JS J6 processes.Objectives: Establish formal guidance for following areas:WMA Architecture Discovery and Accessibility (coordinated with DoD CIO processes)Structured data formats for delivery of WMA architectures to support JCIDS, Operational and Capability Analysis Processes (Needs to be lock step with DoD CIO, partner, and JMT efforts)

Processes for delivery of structured architecture data sets, including Configuration Management/Lifecycle maintenance of WMA architectures

6

Slide7

Intelligence and Business Mission Area OutreachWMA processes now mature enough to start engagement with other mission areas

Objectives:Establish requirements for horizontal architecture federation to Business and Intelligence Mission AreaFocus on support to DoD CIO goal of building the

the

DoD

EA as a federation.

7

Slide8

Requirements for Key Federation Touch P

ointsNow that WMA architecture data (and JIE related data) is becoming available, there is ramping up demandObjectives:

Identify requirements for sharing WMA (and JIE) architecture data and architecture-based analysis with other critical

DoD

processes

S&T (DTIC)

T&E (foundational work done by

Visense

)

M&S (J7)

GTG-F

8

Slide9

Partner SupportObjectives: Expand Stakeholder and partner engagement to support WMA and

DoD CIO architecture federation goals and objectives (including other JS J2/J3/J7/J8 architecture efforts)Continue to work partner repository discovery and accessibility using enterprise servicesMake available for reuse all WMA already established processes and technical solutions* to mature partner repositories and save valuable resources

Develop capability to subscribe to portal/project updates

*Non-COTS/proprietary

9

Slide10

Sprint 11 Deliverables: April 29 – May 17

Standardized Data-Enabled Views on Portal:Along with required data sets from JAR, Sparx EA, DM2 XML,

MagicDraw

XMI, System Architect XML, Army XML, Excel Template

Continue

to work data section of implementation guide (to support Bullet 1)

Improve capability to search by view type

Update/Improve WMA Dictionary functionality and search

Looking at Ontology/Lexicon tools

Capability to subscribe to email notifications about updates

Create enterprise collection for JCPAT legacy and DARS SIPR Legacy Catalogs

Outreach J7/J3/J8, GTG-F, AF, INTEL/Business MARole Management10

Slide11

Sprint-11 Data Enabled ViewsCreated data templates most DoDAF

views:Working pages on how data should be represented in a standardized fashionWorking federation methodology to show relationships between data from multiple sourcesWiki page lays out templates https://

software.forge.mil/sf/wiki/do/viewPage/projects.joint_architecture_integration_w/wiki/HomePage

Comments and Discussion

11

AV1

OV3

SvcV3b

SV2

AV2

OV4

SvcV4

SV3

CV1

OV5a

SvcV5

SV4

CV2

OV5b

SvcV6

SV5a

CV3

OV6a

SvcV7

SV5b

CV4

OV6b

SvcV8

SV6

CV5

OV6c

SvcV9

SV7

CV6

PV1

SvcV10aSV8CV7PV2SvcV10bSV9DIV1PV3SvcV10cSV10aDIV2SvcV1StdV1SV10bDIV3SvcV2StdV2SV10cOV2SvcV3aSV1

Ready

for Review

In Work

No Sample

Data Sets

Slide12

General comment on Architecture Data (1)List number and parent list number are explicit parent - child relationship. We always map from child up to parent, to simplify data tables (i.e. you would require a separate table to maintain all the child relationships for each parent vice just including a parent id on the child entry)

We map all our objects to their authoritative sources through our definitions table (foundation is in the AV-2). Do not need to map multiple times if mapped in the AV-2 to the AS

Fully understand some vendors may not support some properties (i.e. most do not have the capability to meta-data tag with classification markings). This is a shortfall that will require architects to do additional work in some cases.

12

Slide13

General comment on Architecture Data (2) For things like "sort order" those are to ensure that the objects are listed in an order identified by the user. For example if activities are numbered 1.1, 1.2, 1.3, etc., without the sort order, 1.1 , 1.10, and 1.100 would be first in the list. It is a data property we can usually extract if not provided.

As part of our WMA EA concept it is planned to ensure that all activities are mapped at the top level to Services Tasks or UJTs, Capabilities to JCA's just like functions are required to be mapped to JCSFL in 6212.

Relationship types (i.e. OV-4) are required to define the line as an object type. Almost all OV-4/OV-2 etc... type views have definitions or types for the connectors and we needed a way to represent that connection type (i.e. command relationship,

operation

al control, admin control)

SV-4s do not normally include performers since the SV-4 is a hierarchy of functions for the entire capability (Product Name

)

13

Slide14

Army Comments Architecture Data standards: issues and lessons learned

14

Slide15

Sprint 12: May 27 – June 21WMA Architecture Data Standards out for review

Architecture data sets populated for DoD CIO RA’s, JTSO, WMA (JS J6) developed architecturesWMA Enterprise Architecture Foundation (JCAs, UJTs, JCSFL)Legacy DISR TV-1 traceabilityDoD CIO Governance SupportWMA Governance

NR-KPP

Module

(Legacy CDTM) Assessment

Search Capability

Dictionary improvements

Partner Support

15

Slide16

Sprint ScheduleSprint 12: May 28 – June 21Cleanup 24-26 Jun

Federation WG Meeting 27 JunPhase 5: 8 July – Sep 27

16

Slide17

Status UpdatesDoD CIO

GovernanceDM2 WGDISAAT&LInteroperability IPTJS

J6

NR/KPP, JCIDS

JMT

JC2

J2

J3

J7

J8/JIAMDO

CCMDs

SOCOMNORTHCOMEUCOMCENTCOMPACOMSTRATCOMCYBERCOM

AFRICOM

SOUTHCOM

5/23/2013

17

Services

Army

G6

SMDC

AIMD

Navy

DASN RDT&E

CIO

CYBERCOM

AF

SAF/A6

USMC

HQ

MCSC

MCCDC

Slide18

LinksWMA-AFIP NIPR Production Portal

https://sadie.nmci.navy.mil/jafe/WMA-AFIP SIPR Portal (Development)

https://ssadie.spawar.smil.mil/sjafe

Community Forge

Used for group collaboration

https://community.forge.mil//group/joint-architecture-federation-and-integration

Software Forge

Used for technical development

https://software.forge.mil/sf/projects/joint_architecture_integration_w

18