Integrating information towards Digital ATM

Slides:



Advertisements
Similar presentations
Future of NIEM Tools Delivery Public Sector NIEM Team, July 2012 Futureof NIEM Tools.
Advertisements

Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Free Mini Course: Applying UML 2.0 with MagicDraw.
28 October 2008CIS 340 # 1 Topics (continuing) To develop the concepts guiding SOA To define SOA components.
SOA Architecture Delivery Process by Dr. Robert Marcus SRI International 1100 Wilson Boulevard Arlington, VA
SWE Introduction to Software Engineering
- 1 - Component Based Development R&D SDM Theo Schouten.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
Lecture Nine Database Planning, Design, and Administration
1 1 Roadmap to an IEPD What do developers need to do?
SOA – Development Organization Yogish Pai. 2 IT organization are structured to meet the business needs LOB-IT Aligned to a particular business unit for.
XML Registry and Repository for the Education Community Holly Hyland, Federal Student Aid.
Chapter 9 Database Planning, Design, and Administration Sungchul Hong.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
Managing Software Quality
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Cmpe 471 Computer Crime: Techniques and Countermeasures.
PROJECT NAME: DHS Watch List Integration (WLI) Information Sharing Environment (ISE) MANAGER: Michael Borden PHONE: (703) extension 105.
1 Minggu 9, Pertemuan 17 Database Planning, Design, and Administration Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
WordFreak A Language Independent, Extensible Annotation Tool.
SOFTWARE REUSABILITY AJAYINDER SINGH CSC What is Software Reuse Software reuse is the process of implementing or updating software systems using.
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
Web Services based e-Commerce System Sandy Liu Jodrey School of Computer Science Acadia University July, 2002.
What is NIEM? 1 NIEM is a national program supported by the federal government to increase information sharing between organizations who share a common.
Software Engineering Quality What is Quality? Quality software is software that satisfies a user’s requirements, whether that is explicit or implicit.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
ICare Software Architecture Description: Principles, Decisions and Contradictions Team A Aggarwal Ashutosh Alungh Suman Appiah Stella Baddam Bhaskar Baghaie.
Database Planning, Design, and Administration Transparencies
Database System Development Lifecycle 1.  Main components of the Infn System  What is Database System Development Life Cycle (DSDLC)  Phases of the.
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
Massachusetts Open Standards Policy Claudia Boldman Director of Policy and Architecture Information Technology Division, MA.
Interoperable sharing of groundwater data across international boarders is essential for the proper management of global water resources. However storage.
Virtual techdays INDIA │ august 2010 ENTERPRISE CONTENT MANAGEMENT WITH SHAREPOINT 2010 Naresh K Satapathy │ Solution Specialist, Microsoft Corporation.
Service Component Registry and Repository (SCRR) April 26, 2007 Lico Galindo 2007 Exchange Network National Meeting.
Develop Use Cases Evaluate Existing Models Develop/Extend Model Test ModelDocument 1. Commercial This use-case involves identifying the location and properties.
Java Fundamentals Usman Ependi UBD
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
CS223: Software Engineering Lecture 14: Architectural Patterns.
IT323 - Software Engineering 2 1 Tutorial 4.  List the main benefits of software reuse 2.
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
Architectural Mismatch: Why reuse is so hard? Garlan, Allen, Ockerbloom; 1994.
Chapter 9 Database Planning, Design, and Administration Transparencies © Pearson Education Limited 1995, 2005.
Develop Use Cases Evaluate Existing Models Develop/Extend Model Test ModelDocument Use Cases 1. Commercial This use-case involves identifying the location.
PHP + Framework + MVC. What is Framework? Common code - Generic functionality Extensible - Specific functionality Unlike library – Flow Dictated.
Chapter 2 Object-Oriented Paradigm Overview
Introduction to Visual Basic. NET,. NET Framework and Visual Studio
16CS202 & Software Engineering
CompSci 280 S Introduction to Software Development
Object Oriented Programming
Information Systems Development
Modern Systems Analysis and Design Third Edition
N-Tier Architecture.
Physical Data Model – step-by-step instructions and template
Computer Aided Software Engineering (CASE)
Modern Systems Analysis and Design Third Edition
Design and realization of Payload Operation and Application system of China’s Space Station Wang HongFei 首页.
Project Topic 2: Migration to Java 9
Software Quality Engineering
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Modern Systems Analysis and Design Third Edition
Component-Level Design
Starting Design: Logical Architecture and UML Package Diagrams
Service Oriented Architecture (SOA)
Modern Systems Analysis and Design Third Edition
Data Model.
SWEN 5230 Your Project Title
Modern Systems Analysis and Design Third Edition
Architectural Mismatch: Why reuse is so hard?
Presentation transcript:

Integrating information towards Digital ATM AIXM Modularity Considerations Presented By: Katrina Wilson Date: August 29, 2013

Agenda What is our Vision? Information Service Reference Model What is Modularity? Why? Proposal 1

What is our Vision? Practitioners at all levels of aviation share accurate, complete, timely and appropriately secured information to ensure public safety. To produce “exchange schemas” which offer a high degree of clarity, interoperability and reusability while being agnostic to the actual deployment software tools. Alignment to domain data model components dictionary – interoperability across domain applications. 2

Information Service Reference Model 3

What is Modularity? From Wikipedia, “Modular design is an approach that subdivides a system into smaller parts (modules) that can be independently created and then used in different systems to drive multiple functionalities. Improve maintainability by enforcing logical boundaries between components”. 4

Why? Encourages reuse by creating well-defined modules that perform a particular task Increases flexibility and maintainability because single modules can be upgraded or replaced independently of others Eases development, testing, and maintenance by providing a logical, easy to understand, and consistent organization 5

Proposal Encapsulate Features and Usage Generate XSD by Subject Area/Domain data model components Evaluate Reorganizing Packages Common XML features XML Schema are XML documents themselves and therefore share many aspects of the languages they define. 6

7

Contact Information Questions - Please contact us at 9-ATO-ATF-910-InfoDelivery@faa.gov Katrina Wilson FAA – Computer Specialist Barbara Cordell FAA – Manager - Data and Information Architecture Team 8