National Information Exchange Model Update for the Global Advisory Committee Spring 2008 Meeting April 10, 2008 NIEM Technical Architecture Committee (NTAC)

Slides:



Advertisements
Similar presentations
The Value of a Project Management Office Copyright: Kathy J. Lang, 2004.
Advertisements

Roadmap for Sourcing Decision Review Board (DRB)
Process and Procedure Documentation. Agenda Why document processes and procedures? What is process and procedure documentation? Who creates and uses this.
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Beta Testing: The Contractor’s Perspective Trns·port User Group Meeting October 2005.
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Global Business Blueprint Summary Presenters: Laurie Dempsey, CBP Lois McCluskey, eCP January 28, 2004.
NIEM Healthcare Domain FHIM/S&I Framework Strategy 4/7/2011.
1 LBNL Enterprise Computing (EC) January 2003 LBNL Enterprise Computing.
IT Strategic Planning Project – Hamilton Campus FY2005.
Project Process Discussion Adam D. Martinez Mgr, Market Ops Divisional Projects Organization ERCOT RMS Meeting May 10, 2006.
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
ECM Project Roles and Responsibilities
Release & Deployment ITIL Version 3
What is Business Analysis Planning & Monitoring?
3 Dec 2003Market Operations Standing Committee1 Market Rule and Change Management Consultation Process John MacKenzie / Darren Finkbeiner / Ella Kokotsis,
May Agenda  PeopleSoft History at Emory  Program Governance  Why Upgrade Now?  Program Guiding Principles  High-Level Roadmap  What Does This.
V ocabulary Subsets and Value Sets NCPDP Response Feb 23, 2010 HIT Standards Committee (HITSC) Task Force on Vocabulary.
Enterprise IT Decision Making
Distributed Monitoring and Mining Advisor: Dr. Stuart Faulk Team: Ahmed Osman, Isaac Pendergrass, Shail Shimpi, Tom Mooney OMSE-555/556 Software Engineering.
Web Development Process Description
Project Management Process Overview
Agenda Teams Responsibilities Timeline Homework and next steps.
Roles and Responsibilities
Doc.: IEEE COEX 02/016r1 Submission May 2002 Jim Lansford, Mobilian CorporationSlide 1 IEEE 802 Wireless Coexistence Study Group Update Jim Lansford
NIEM Domain Awareness June 2011 Establishing a Domain within NIEM.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
1561 INITIATIVE Lessons Learned and Future Considerations
1 What’s Next for Financial Management Line of Business (FMLoB)? AGA/GWSCPA 6 th Annual Conference Dianne Copeland, Director, FSIO May 8, 2007.
SacProNet An Overview of Project Management Techniques.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
DCIPS Implementation Project Plan Update Army G2 Intelligence Personnel Management Office (IPMO) April 6, 2009.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
普 华 永 道 Phase 1: Project Preparation Phase 1: Project Preparation Phase Overview Phase Overview.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
SIS Project Oversight Group Meeting Guide 12/13/05.
Sacramento Area Council of Governments ITS Partnership Meeting February 2, 2005.
Test Manager’s Role Best Practice By Gabriel Rodriguez.
1 Program Management Systems Committee Kickoff Session February 3, 2010 Program Management Outreach Working Group.
ITC Software ITC FUNCTIONAL TESTING SERVICES.
How do You Fit within the Process? Roles and Responsibilities – Pre CAB (1/2) 1 Change Requestor Initiates the Change Request (CR) in Service-now Includes.
DOT Implementing the Surface Transportation Domain Daniel Morgan 26 October 2015.
Developing a Project Management Standard for Your Organization Francine DiMicele, PMP June 08, 2015 NC Piedmont Triad Chapter.
12 ML X Welcome to the February 2001 Accredited Standards Committee X12 Meeting.
ESSRT In-Process Review September 10, Agenda 1.Work Completed Till Date 2.Scope of future activities and deliverables 2.
ELECTRONIC SERVICES & TOOLS Strategic Plan
Sustainability Principles for Land Use and Mobility Approved by City Council – January 2007.
Middle Fork Project Relicensing Process Plan April 25, 2006.
DEX Publication Project OASIS PLCS TC Face to Face meeting 10 March 2008 Trine Hansen.
Transmission Advisory Group NCTPC Process Update Rich Wodyka September 7, 2006.
IPDA Architecture Project International Planetary Data Alliance IPDA Architecture Project Report.
Agenda Leads work – Track Status Admin / Upcoming / Next Steps – RFP Document review – Vendor Question Review – GL Preparation – Orals – Harris.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Establish the NIEM Health Domain by focusing on high value data exchanges that can be modeled within NIEM in the context of the existing NIEM framework.
Software Configuration Management
DOCUMENTATION DEVELOPMENT LIFE CYCLE (DDLC)
IEEE 802 Wireless Coexistence Study Group Update
Project Process Discussion
Process Improvement With Roles and Responsibilities explained
Description of Revision
IT Governance Planning Overview
Project Process Discussion
Health Ingenuity Exchange - HingX
Adaptive Product Development Process Framework
Security Policies and Implementation Issues
{Project Name} Organizational Chart, Roles and Responsibilities
Process and Procedure Documentation
Project Name Here Kick-off Date
Presentation transcript:

National Information Exchange Model Update for the Global Advisory Committee Spring 2008 Meeting April 10, 2008 NIEM Technical Architecture Committee (NTAC) Highlights Co-Chairpersons Tom Clarke Jeremy Warren Committee Support Manager Pisey Frederick

2 Agenda Whitepapers Process Whitepaper Topics NTAC Operational Documents NBAC Participation NTAC Future Initiatives

3 NTAC Whitepapers Process Whitepapers Process –Whitepapers review kick-off – February 11, 2008 –Technical conference calls held on various whitepaper topics - weekly –NTAC face-to-face meeting - April 21-22, 2008 Key Focus Areas –Revitalize and refocus on NTAC responsibilities and productivity –Promote discussion, review, and decision prior to the NTAC face-to-face meeting –Reassess technical priorities –Gain NTAC approval for technical implementation of architecture

4 NTAC Whitepapers Topics 1.Draft Version Architecture Decision –Establish a scheme for versioning of NIEM artifacts 2.Draft NIEM Tool Strategy (Part 1) –Establish a working action plan to guide, focus, and facilitate the development of software tools 3.Draft NIEM Tool Architecture (Part 2) –Detail the key NIEM processes, users and use cases, interfaces, I/O, and formats 4.NDR v. 1.3 (Part 1 & 2) –Refinement of NDR 1.2 and document as-is with additional architectural changes 5.UML Profile for NIEM –Describe NIEM concepts for which an analogous representation exists in UML 6.NIEM Design Quality Metrics –Propose metrics to measure “design quality” (degree of adherence to established design principles) 7.NIEM Data Model Strategy & Plan –Extension of NIEM Design Quality Metrics with a focus on QA in Operational, Data, and Harmonization

5 NTAC Operational Documents Finalize NTAC Charter Develop NTAC Project Schedule Develop Project Management Plan Key Focus Areas –Provide specific requirements of NTAC membership –Understand the NTAC organization, roles and responsibilities, and relationships to the other NIEM committees and NIEM PMO. –Understand and articulate the interrelationships and dependencies of committee responsibilities and activities –Execute NTAC in accordance to the Management Plan to better prepare or future tasks –Monitor risks and resolve issues in a timely manner

6 NBAC Participation Provide a governance structure for handling NIEM releases and versioning of NIEM artifacts Identify and prioritize tool strategies Identify use case scenarios for the Federated Registry business requirements Analyze the NIEM Configuration Control Tool (NCCT) inventory to better prioritize solutions Key Focus Areas –NTAC works with NBAC to ensure technical recommendations are considered from a business perspective. –User and community input into the identification and prioritization of NIEM’s implementation is important.

7 NTAC Future Initiatives Additional Follow-Up on Approved Whitepapers –Examples: Version Architecture proposal (i.e. design document, build solution) Prioritization of Tool Strategy & Architecture –Define interface specification –Publish detailed draft specification document –Model/build tool(s) Review/approve federated registry specification prior to distribution to the public Resolve NTAC NCCT issues and incorporate tasks to project schedule Execute NTAC tasks according to the PM plan and project schedule Publish additional technical whitepapers to help make key decisions

8