“New” things Discussed in London

Slides:



Advertisements
Similar presentations
Software Engineering 2003 Jyrki Nummenmaa 1 A BASIC OO SOFTWARE DEVELOPMENT PROCESS Earlier, we saw a number of different software lifecycle models.
Advertisements

Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.
Copyright © 2003 Bolton Institute Dept. of Computing and Electronic Technology - Multimedia Integration and Applications Lecture 3 - Project Planning.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Lecture 6 - Project Planning. Lecture 6: Project Planning Overview Creating an outline plan –Work Breakdown Structure –Identifying tasks Waterfall and.
TRAINING SOLUTIONS ISO 14001: DEVELOPMENT & IMPLEMENTATION For more information contact Victoria: (Tel) (Fax) ( )
FPDS- NG Reports Overview December 16, Today’s Goals Provide an overview of the FPDS-NG reporting capability Demonstrate each of the reporting tools.
CISB594 – Business Intelligence
© 2010 Health Information Management: Concepts, Principles, and Practice Chapter 5: Data and Information Management.
ESIP Semantic Web Products and Services ‘triples’ “tutorial” aka sausage making ESIP SW Cluster, Jan ed.
JNTC Joint Management Office
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
E- Patient Medical History System
Databases and DBMSs Todd S. Bacastow January 2005.
Project Management Business Management.
International Defence Enterprise Architecture Specification (IDEAS)
IDEAS Model for Coalition Architecture Interoperability
Partner Cloud Voice Offer Guidance
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Briefing to DoDAF 2.0 Development Team TBD 2007
Management & Planning Tools
IDEAS Data Exchange Format (RDFS)
Introduction to MODEM Building a Semantic Foundation for EA: Reengineering the MODAF™ Meta-Model Based on the IDEAS Foundation Model Lt Col Mikael Hagenbo,
Section 8: Model-View-Controller
Use Case Model.
International Defence Enterprise Architecture Specification (IDEAS)
Section 8: Model-View-Controller
Agenda All-Monday 15 Sep 0800 Welcome - Opening remarks
Project Title Presented By Student1 name - Roll no
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
IS442 Information Systems Engineering
Creating Reports Understanding various types of reports and writing persuasive Analytical Reports.
Select and Implement a Next Generation Firewall
The Open Group Architecture Framework (TOGAF)
Briefing to DoDAF 2.0 Development Team TBD 2007
Prototyping.
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Chapter 2: Database System Concepts and Architecture
Dr. Sudha Ram Huimin Zhao Department of MIS University of Arizona
Chapter 2 Database Environment.
Data, Databases, and DBMSs
Overview Course description: Course goal Course structure
Systems Analysis Overview.
IS&T Project Reviews September 9, 2004.
International Defence Enterprise Architecture Specification (IDEAS)
International Defense Enterprise Architecture Specification (IDEAS)
Object oriented analysis and design
Architecture Data Exchange Experiments Military Utility Demonstration
International Defence Enterprise Architecture Specification (IDEAS)
Architecture Data Exchange Experiments Military Utility Demonstration
International Defence Enterprise Architecture Specification (IDEAS)
IDEAS Core Model Concept
International Defence Enterprise Architecture Specification (IDEAS)
International Defence Enterprise Architecture Specification (IDEAS)
“New” things Discussed in London
“New” things Discussed in London
, editor October 8, 2011 DRAFT-D
Guided Research: Intelligent Contextual Task Support for Mails
Systems Architecture & Design Lecture 3 Architecture Frameworks
Power BI Streaming Datasets with MS Flow
Comparison of table-based and JSON-based chaincode
Use Case Process with Examples Kay Stefferud
Text to Illustration (E2I)
Joint Vision 2020.
Graduation Project Project Name
CHAPTER 5 THE DATA RESOURCE
“New” things Discussed in London
Presentation transcript:

“New” things Discussed in London Detailed planning for 4/08 demo Backtrack rehearsals, setups, … “Military Utility” Ops planning and data exchange scenario Useful results from exchange (ideas on later slide) Documentation Op Concept Doc AU started Model description Methodology (Data TWG could use too) Training on implementing data exchange (e.g., for federates, vendors) Model telecon’s between trips

1. Demo Preliminary Plan

2. Military Utility Contrast “as-is” way that Coalition Ops Planning is done with “to-be” Need to show relevant to procedures, tools, methods, … planners would actually use May not look like classic “architecture”

“As-is” We need to document how the Coalition Ops Planning scenario would be done today Manual? (paper, email, faxes, phone calls, meetings, …) Discovery of issues in the field (on-the-job interoperability)

“To-Be” Military Utility Scenario Visualization Environment Decision Environment “To-Be” Military Utility Scenario Relational DB Query Environment SQL Query OWL/RDFS DB Data Mining Environment RDFS Database IDEAS Data Exchange Format (RDFS)

How to compare? Process A Process B Activity 3 Activity 5 Activity 1

How to compare? Similarities in process flow … Process A Process B Activity 3 Activity 5 Activity 1 Activity 2 Activity 6 Activity 4 Process B Activity 3 Activity 1 Activity 2 Activity 6 Activity 4

How to compare? Differences in process flow … Process A Process B Activity 3 Activity 5 Activity 1 Activity 2 Activity 6 Activity 4 Process B Activity 3 Activity 1 Activity 2 Activity 6 Activity 4

How to compare? What about the information exchanged? Process A Activity 3 Activity 5 Activity 1 Activity 2 Activity 6 Activity 4 Process B Activity 3 Activity 1 Activity 2 Activity 6 Activity 4

How to compare? What about the information exchanged? Process A IE-03 IE-04 IE-05 IE-06 Process A IE-01 IE-02 IE-08 Activity 3 Activity 5 Activity 1 Activity 2 Activity 6 Activity 4 IE-07 IE-09 IE-06 IE-07 IE-03 IE-04 IE-05 Process B IE-01 IE-02 Activity 3 IE-08 IE-09 Activity 1 Activity 2 Activity 6 Activity 4

How to compare? Differences … What about the information exchanged? IE-03 IE-04 IE-05 IE-06 Process A IE-01 IE-02 IE-08 Activity 3 Activity 5 Activity 1 Activity 2 Activity 6 Activity 4 IE-07 IE-09 IE-06 IE-07 IE-03 IE-04 IE-05 Process B IE-01 IE-02 Activity 3 IE-08 IE-09 Activity 1 Activity 2 Activity 6 Activity 4

How to compare? TOOLS? Process A Process B Activity 3 Activity 5 IE-03 IE-04 IE-05 IE-06 Process A IE-01 IE-02 IE-08 Activity 3 Activity 5 Activity 1 Activity 2 Activity 6 Activity 4 IE-07 IE-09 IE-06 IE-07 IE-03 IE-04 IE-05 Process B IE-01 IE-02 Activity 3 IE-08 IE-09 Activity 1 Activity 2 Activity 6 Activity 4

How to compare? TOOLS?

How to compare? TOOLS?

How to compare? TOOLS?

How to compare? TOOLS?

How to compare? TOOLS?

How to compare? TOOLS?

Plan Mock-up some CA-US casualty mgmt process comparison displays (started): Highlight different processes, sequences, information flows, event triggers* Maybe side-by-side Post on IDEAS FTP site for review US review with Joint Forces Command Once OK, see what tool gets us close *truly different, names assumed aligned or mapped

3. Documentation Need some preliminary documentation available at conference

Need to revisit scope and structure IDEAS OCD Current structure: CAPABILITY IDENTIFICATION DEFINITION AND REFERENCE DOCUMENT SOLUTION INDEPENDENT CAPABILITY NEEDS EXISTING COALITION PLANNING SYSTEM SYSTEM SOLUTION DESCRIPTION Mostly TBS/TBD Need to revisit scope and structure

NOT EA-generated document; rather key information IDEAS Model (prelim) Sections for each layer: Foundation Common Patterns Domain Within each: For each package/diagram: Narrative description, diagram walkthru and items of special note Standard data dictionary information Examples NOT EA-generated document; rather key information

IDEAS Methodology (prelim) How IDEAS differs from other methodologies, e.g., “view from nowhere” approach BORO Methodology Set Theory The Naming Pattern Incremental Experimentation BORO overview “Sausage grinders”: Walk thru diagram Examples

IDEAS Usage Guide OWL/RDFS Specification Walk thru Special notes Examples Guidance from experimentation on: Generation from tools and databases Ingestion into tools and databases i.e., “lessons learned” Querying and “data mining”

4. Bi-weekly telecons More modeling, less stausing Track “critical path” issues for 4/08 demo and make sure management team is well aware of Track team action items