1 / 8

Presentation to the Association of Enterprise Architects - DC

Presentation to the Association of Enterprise Architects - DC. Enterprise Architecture Reviews of Systems. Update. Date: January 20, 2011. August 10, 2011 Terry Horning, Office of Aviation Safety, FAA. Purpose of Architecture Review. Focus areas

ivy
Télécharger la présentation

Presentation to the Association of Enterprise Architects - DC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Presentation to the Association of Enterprise Architects - DC Enterprise Architecture Reviews of Systems Update Date: January 20, 2011 August 10, 2011 Terry Horning, Office of Aviation Safety, FAA

  2. Purpose of Architecture Review • Focus areas • New development projects or any significant change to existing systems • Benefits of an architecture review • Identify similar systems--planned, under development, or operational • Leverage guidelines and ensure compliance • Create EA content to be shared and communicated

  3. EA Review Process Lifecycle AVS EA Team PM includes AVS EA team 5 Operation Phase Project Kick-Off Meeting Updated documents and project reports 1 Maintain EA Repository, load project data, generate reports and diagrams Introduction to EA Review status log and value preposition to Projects AVS EA Presents Project Engagement Package Projects Reports and feedback Receives SDLC Required Documents (Concept, PMP, Requirements, System Boundary Document.) Project provide Concept Document Project provide Design, Development documents Reviews the documents provided , answers the EA Review questions, identify the gaps Gather consistent data on projects and prepare to load data in EA Repository Feedback , EA reports, and request for response on missing information Design Phase Concept Phase 4 2 Data validation, feedback , reports and Request for response on missing information Provides Requirements, Planning documents Development Phase Requirements Phase 3 Planning Phase

  4. SDLC Data Collection Questions

  5. Dashboard Template with Sample Data Concept Planning Requirements Design Development Integration/Test Implementation Ops & Maint Disposition Strategy PMP CONOPS SBD Func Reqs Doc System Design ICD BPM Use Cases IT Project Information Project Description Review Date Name: HR 5900 Pilot Database Project Manager: Jane Doe Project Start Date: Aug 2010 Investment: SharePoint Site: HR 5900, the “Airline Safety and Federal Aviation Administration Extension Act of 2010”, was signed into law, on August 1, 2010 by President Obama. This act significantly changed several areas of Title 49, United Stated Code of Federal Regulations. Section 203 of the Act requires the creation of a database, which would enable airlines seeking to hire a prospective pilot, immediate electronic access to a pilots flying record. March 28, 2011 Project SDLC Phase EA Team Technical Solution • Abraham Lincoln A Web based Pilot Records system integrating several data sources such that a single interface can access and provide the historical records on pilots to air carriers in accordance with the provisions of H.R. 5900 EA Artifacts Systems Impacted ISUG Meetings • EA Review Process Presentation • EA Review Questions with Rationale and guidance Project Documents • Registry • EIS • AIDS • C9 and C10 answered in 12/15/10 meeting EA Repository EA Review Questions – Outstanding issues • Developing To-Be System Interface Diagram • C1 – Will be provided at next review • C2 & C3 – Require clarification • C5 –BRM mappings not done SOA Services • Reusing PGM XYZ Services • Developing new services Next Steps Notes • EA Team to review System Boundary Document (SBD) • Schedule next EA review meeting in 3rd week of Jan 2011 • EA team will be invited to ISUG meetings • EA team to come back and report on reuse of PGM XYZ SOA Services • Needs EA support looking into Process Overlaps • Needs EA support looking into strategic line of sight activities – example, mapping to Flight Plan goals

  6. EA Review - Final Analysis Report

  7. EA Data Analysis

  8. EA Data Analysis, continued

More Related