AWG 17 April 2012 Candidate Topics

Slides:



Advertisements
Similar presentations
Phase 2: Identifying Sumber Kepustakaan : gunston.gmu.edu/ecommerce/mba731/doc/BP R_all_Part_I.ppt 1 Construct high-level process map Develop a process.
Advertisements

DoDAF V2.0 Community Update Overview
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
UNIVERSITY OF DUNDEE ONE IT. Professor Pete Downes - Principal & Vice-Chancellor One Dundee / One IT / One Approach Individual Consultations Collective.
All Rights Reserved: JusticeExperts.com Enterprise? What Enterprise? Enterprise Development.
SE 470 Software Development Processes James Nowotarski 21 April 2003.
CSE 111: Object Oriented Design. Design “To program is human but to design is divine” (WEH)
Systems Analysis and Design for Electronic Commerce, Networked Business Processes, and Virtual Enterprises Walt Scacchi, Ph.D. GSM 271 and FEMBA 271 Spring.
A Combat Support Agency Defense Information Systems Agency Model Based Systems Engineering and Systems Modeling Language Chris Gedo Chief, Architecture.
Enterprise Architecture
System Design/Implementation and Support for Build 2 PDS Management Council Face-to-Face Mountain View, CA Nov 30 - Dec 1, 2011 Sean Hardman.
Proposed MITHI Concept Paper
Enterprise Business Information Model Enterprise Data Services.
Developing Enterprise Architecture
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
RUP Design RUP Artifacts and Deliverables
Planning the project Project Management (lecture).
Architectural Framework
1 TDT4252/DT8802 Assignment Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252,
For internal use only 1© Nokia Siemens Networks R 255 G 211 B 8 R 255 G 175 B 0 R 127 G 16 B 162 R 163 G 166 B 173 R 137 G 146 B 155 R 175 G 0 B 51 R 52.
Chapter 7 Applying UML and Patterns Craig Larman
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
Work Breakdown Structure Kathy S. Schwaig. What is a Work Breakdown Structure (WBS)? A WBS is a logical hierarchy of work packages involved in a project.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Domain Model Refinement Larman, chapter 31 CSE 432: Object-Oriented Software Engineering Glenn D. Blank, Lehigh University.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
TIDEN Node Management Texas Integrated Data Exchange Node Partnered with.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Module 1: Introducing Windows Server 2003 Network Infrastructure Planning, Tools, and Documentation.
1 OCIO Kickoff Production Release Solution Acceptance Retirement Sales, AgreementPlanning, Execution, TestingDeployment, PilotProduction Support 234 Signed.
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
Business Intelligence Pathway Method 5 th Meeting Course Name: Business Intelligence Year: 2009.
PDS4 Project Report PDS MC F2F University of Maryland Dan Crichton March 27,
SUPPORT THE WARFIGHTER MPE Reference Architecture Development Kick-off Meeting Deputy Director Architecture & Interoperability Office of the DoD CIO Thomas.
Information Architecture WG: Report of the Fall 2004 Meeting November 16th, 2004 Dan Crichton, NASA/JPL.
© Everware-CBDI Inc V & Everware-CBDI Service Offerings Service Oriented Architecture.
Example Presentation: Alignment, Launch & Adoption
Elaboration popo.
Chapter 12: Architecture
Design Rules for NBD – Network Based Defence
ARIS Extension Pack TOGAF April 2016
Business (Agency) Process Discovery and Documentation Workshop
Update on the Architecture CAT
DoD CIO Architecture and Interoperability Directorate December 2014
IC Conceptual Data Model (CDM)
DoDAF Version 2.03 Update 05 Jan 2012 DoDAF Team 1 1.
Azure Stack Foundation
Brief to Extraordinary NATO A-CAT Mr. Walt Okon January 2013
Brief to Extraordinary NATO A-CAT Mr. Walt Okon January 2013
Agenda All-Monday 15 Sep 0800 Welcome - Opening remarks
Introduction DoDAF 2.0 Meta Model (DM2) TBS dd mon 2009 VERSION 15
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
AWG 20 April 2012 Candidate Topics
AWG 27 April 2012 Candidate Topics
Version 3 April 21, 2006 Takahiro Yamada (JAXA/ISAS)
Software Architecture & Design Pattern
CIMI Enterprise Architecture Proposal
Proposed Software Development Process
[Project Name] Project Report
FFM TC status Thinh Nguyenphu as FFM TC Chair NSN
AWG 24 April 2012 Candidate Topics
[Project Name] Project Report
AWG 20 April 2012 Candidate Topics
AWG 17 April 2012 Candidate Topics
Systems Architecture & Design Lecture 3 Architecture Frameworks
Architecture & Interoperability Directorate
Web Application Diagram Template
Presentation transcript:

AWG 17 April 2012 Candidate Topics Artifact applicability to scope Core vs Top-Level Scope Plan for 30 April deliverable CA Appendix E Blend with DoDAF v2.03 Downselect to Core / Top-Level Scope only? Names only? “One-liners”? Description sketches? High-level Metamodel? Low-hanging fruit? Post 30 April phases? Assignments / volunteers (by individual, topic area?) Next meeting? 17 April 2012 AWG Working Papers -- FOUO

Artifact applicability to scope Sub-Architecture Domain Core Artifact Strategy Concept Overview Diagram Business High-Level Process Diagram Data High-Level Logical Data Model Applications Application Interface Diagram Infrastructure High-Level Network Diagram Security Control List Core vs Top-Level Scope Remove for 30 April deliverable 17 April 2012 AWG Working Papers -- FOUO

Plan for 30 April deliverable CA Appendix E Blend with DoDAF v2.03 Downselect to Core / Top-Level Scope only? No Names only? “One-liners”? Description sketches? High-level Metamodel? Low-hanging fruit? Post 30 April phases? 17 April 2012 AWG Working Papers -- FOUO

AWG Working Papers -- FOUO “One liners” Model Description CV-1: Capability Effects Presents effects caused by capabilities and measures for these effects. CV-2: Capability Hierarchies Presents one or more hierarchies of capabilities and the types of hierarchical relationships between these capabilities. CV-3: Capability Schedules Presents schedules for the deployment of capabilities in terms of timelines. CV-4: Capability Dependencies Presents dependencies among effects caused by capabilities. CV-5: Capability Deployments Presents schedules for the deployment of capabilities in terms of organizations and locations. CV-6: Capability Activities Presents activities that are performed to cause the desired effects of a capability. CV-7: Capabilities and Services Presents a mapping of capabilities to services. 17 April 2012 AWG Working Papers -- FOUO

Description sketches? – in an Appendix later 17 April 2012 AWG Working Papers -- FOUO

High-level meta model – post 30 April Figure 3.3.1‑1: DoDAF meta-model diagram for CV-1 models 17 April 2012 AWG Working Papers -- FOUO

Low-Hanging Fruit – use to harvest some “one liners” 17 April 2012 AWG Working Papers -- FOUO

AWG Working Papers -- FOUO Others? 17 April 2012 AWG Working Papers -- FOUO

Next Steps & Assignments / volunteers Start with 17 DoDAF “one liners” that match (~freebies) Look through other 33 CA artifacts and see which ones you’d like to nominate for 30 April. Others as well, e.g., from DoDAF, CPM, or other agency sources ones Informal criteria is we think it’s Important in your agency Fills a vacuum in the CA domains. Rule: Nomination must accompanied by a “one liner”. (ALL, 20 April) Add the one-liners to the new lists (DoD) Review and iterate (ALL, 25 April) Modify domain descriptions to be consistent (lead, co-lead, members) 26 April Send signup matrix (DoD, 17 April) Strategic (TBD, TBD, TBD) Business (TBD, TBD, TBD) Application (TBD, TBD, TBD) Data (TBD, TBD, TBD) Infrastructure (TBD, TBD, TBD) Security (Bill Garvin lead unclass, TBD, TBD) Review whole package (ALL, 28 April) Deliver 30 April Next meeting DCO and GTM 20 April AM 1300-1400 17 April 2012 AWG Working Papers -- FOUO