NDIA SE Division – Annual Planning MeetingDecember 12-13, 2012

1

Feb 4, 2013 Arch Committee Mtg

Agenda:- Status of DoDAF White Paper

- Feb 13 F2F

- INCOSE MBSE Working Group Mtg Report Out

http://www.omgwiki.org/MBSE/doku.php?id=mbse:incose_mbse_iw_2013

- 2013 Activities1. Metrics2. Delivery of the paper3. Survey

NDIA SE Division – Annual Planning MeetingDecember 12-13, 2012

2

Feb 13 F2F

Location: General Dynamics, 1201 M St SE (Maritime Plaza)

Time: 1:30 – 3:30 pm ET

Agenda:- 2013 Tasking- Completion of DoDAF paper- SE Effectiveness Survey discussion

- ask Al Brown to attend

NDIA SE Division – Annual Planning MeetingDecember 12-13, 2012

3

Architecture Committee - 2013 Task Plan

Proposed 2013 Tasks:

• Complete DoDAF Recommendations Report• Validation of recommended metrics• Investigate an addendum to SE Effectiveness

Survey on architecture subjects (both DoDAF and metrics)

• Possibilities:• How to use arch earlier in trade

space?• Encourage papers in area of Model-

based for X and arch for soldiers• UAF awareness• SoS Pain Points

Deliverables/Products

• DoDAF Recommendations Final Report• Survey Results (if pursued)

Schedule / Resources

• Continue bi-weekly virtual meetings• Face-to-face meetings, aligned with SE Division

meetings• Architecture Track at SE Conference

• Complete DoDAF Report by mid 2013

Issues / Concerns:

• Time availability of contributing committee members

NDIA SE Division – Annual Planning MeetingDecember 12-13, 2012

4

Architecture Metrics

Appeal to Architecture WG 12/18/2013 – no responses to date• “Please consider helping us validate [proposed architecture

measures] by providing feedback as follows:• “Are you already using any of them (please identify)? How do

they help your programs make decisions specifically about the architecture, and more generally about the program?

• “For any that you use, please provide feedback regarding:- Difficulty in using (level of effort, ease/difficulty in using,

clarity, consistency)- Perceived benefit as lagging or leading indicator- Perceived benefit for near-term and long-term decision

making.• “What architecture-related measures are you using that are not

included in this table, how are they used, and how do they provide benefit?”

4

NDIA SE Division – Annual Planning MeetingDecember 12-13, 2012

5

Summary of Proposed Architecture Measures and Means*

Measurement Category Proposed Measures Definition/Description Means

Size / Stability Number of elementsCount of constituent parts to be bought or developed, at each architectural level vs. time (stability)

Report of number of classes, objects, logical elements vs. time

Size / Stability / Complexity Number of external interfaces Count of logical and physical interfaces vs. time Report of number of external interfaces to each element vs. time.

Size / Stability / Complexity Number of external relationships

Count of organizational relationships (stakeholders) vs. time Report of number of program interfaces vs. time.

Size / Stability Number of requirements Count of requirements at each architectural level vs. time

Report of number of requirements by element and/or architectural level vs. time.

Complexity / Stability Number of internal interfaces Count of logical and physical interfaces vs. time Report of number of interfaces to each element vs. time.

Complexity / Stability Number of interactions Transaction types or messages, frequency vs. timeReport of number of unique messages or other exchanges among two or more elements at lowest architectural level available.

Complexity Number of states Count of number of defined states and/or modes Report of number of defined states and/or modes

Completeness Requirements addressed Count of number of top-level requirements addressed by the architecture

Report of number of top-level requirements that are addressed by the architecture (traced to architecture element)

Completeness Artifacts produced Count of number of architecture artifacts (e.g., viewpoints) produced vs. time

Report of number of architecture artifacts completed, by type

Completeness Artifacts total expected Count of number of architecture artifacts (e.g., viewpoints) needed vs. time Report of number of architecture artifacts needed, by type

Quality of solution Degree of requirements satisfaction

Count of number of requirements satisfied, normalized by the number of requirements

Report of ratio of number of requirements that are satisfied by the architecture to number of requirements (derived measure)

Quality of solution Degree of Mission Assurance (suitability)

User/program-defined multivariate function of weighted suitability attributes.

Derived measure from base measures of individual attributes or surrogates above required thresholds.

Quality of representation Degree of consistency of representation

User/program defined measure of adherence to internal standards or templates (data content and format), by artifact vs. time

Report of missing data per artifact; analysis of format conformance to templates

Quality of representation Degree of standards compliance

Measures of adherence to external standards(data content and format), by artifact vs. time

Report of missing data per artifact; analysis of format conformation to standards

5*Carson and Kohl draft paper for INCOSE

NDIA SE Division – Annual Planning MeetingDecember 12-13, 2012

6

System Development Performance Measurement Working Group

From Al Brown (Chair): “The work of the System Development Performance Measurement Working Group is completed with the publication of their final report with no  specific indicator recommendation at this time for Architecture.”

6

NDIA SE Division – Annual Planning MeetingDecember 12-13, 2012

7

INCOSE Model-Based SE Workshop

Presentations at http://www.omgwiki.org/MBSE/doku.php?id=mbse:incose_mbse_iw_2013

Emphasis on open services lifecycle collaboration (OSLC) for managing model data in federated architectures throughout the lifecycle

• Recognition that SysML isn’t the only modeling language• Need for tools that interface among databases (e.g., SLIM)• Implementation of STEP standards for data exchanges

(AP233 (ISO10303 Part 433))Consideration of PLM tools for variant management

7