Systems Assessment - Review
Upcoming SlideShare
Loading in...5
×
 

Systems Assessment - Review

on

  • 410 views

Post-Workshop Review

Post-Workshop Review

Statistics

Views

Total Views
410
Views on SlideShare
410
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Systems Assessment - Review Systems Assessment - Review Presentation Transcript

  • FMCSA Medical Program (MP) Information Architecture Post-Workshop Review March 19, 2008
    • Agenda
      • Introduction
        • FMCSA MP Information Architecture (IA) project deliverable
      • Recap workshop
        • Goal
        • Planned vs. actual workshop flow
        • Attendance
        • Workshop observations
      • Review selected deliverables with associated questions
      • IA observations
      • IA recommendations/roadmap
      • Next steps
    • FMCSA MP Information Architecture Project Deliverable
      • Cover page & TOC
      • Introduction
      • FMCSA MP Information Architecture Workshop Presentation
      • FMCSA MP Information Architecture Post-Workshop Presentation
      • Stakeholders & Projects/Activities
        • Stakeholders matrix
        • Projects & activities matrix
      • Requirements Sources
        • Intra-Program dependencies matrix
        • Inter-Program dependencies matrix
        • Related system matrix
        • MRB process progress matrix
        • Requirement sources & resulting drivers matrix
      • High Level Processes
        • Key system related MP process list
        • “ME application for listing in National Registry” process diagram
        • “Driver obtains medical certificate” process diagram
    View slide
    • FMCSA MP Information Architecture Project Deliverable (cont.)
      • High level system diagram
        • High level diagram
        • Sample lower level diagrams
      • Functional hierarchy w/ attributes
      • High level entity relationship diagrams
        • NRCME
        • Exemptions
          • Vision
          • Diabetes
          • SPE
      • Information Architecture observations
      • Information Architecture recommendations/roadmap
      • Appendix A – Workshop parking lot list
    View slide
    • Workshop Goal
      • Clear objective
      • Useful deliverables & purposeful result
    • Planned Session Flow & Supporting Content
      • Organized to facilitate structured but collaborative data gathering
      • Planned covered analysis from various perspectives
        • People, process, and technology
        • Internal / external
        • Relationships and dependencies
      • Aimed to collect a set of data from which a rationalized Information Architecture could be developed
    Introduction & Overview S1: Projects & Activities S2: Requirements Sources S3: Functional Hierarchy S4: HL Process & Info Requirements S5: Use Case Example S6: (HL)Design & Roadmap Wrap-Up & Next Steps Stakeholders Projects & Activities Intra- Program Dependencies Functional Hierarchy Use Case Table Use Case Diagrams Design & Roadmap Diagram Workshop Deliverables Sessions Overview Inter- Program Dependencies Inter- System Dependencies Req Sources & Drivers Functional Hierarchy Parking Lot Day 1 Day 2
    • Actual Session Flow & Supporting Content
      • Initial sessions fostered highly valuable discussion & discovery
        • Encouraged the exchange to obtain deeper understanding of issues and promote teambuilding
        • Resulted in highly valuable insight
      • Re-organized to build on the team’s high level of engagement
        • Switched to highly collaborative approach to covering the remaining topics
        • Resulted in greater than expected levels of detail and insight
    Introduction & Overview S1: Projects & Activities S2: Requirements Sources S3: Functional Hierarchy S4: HL Process & Info Reqs S5: Use Case Example S6: (HL)Design & Roadmap Wrap-Up & Next Steps Stakeholders Projects & Activities Intra- Program Dependencies Functional Hierarchy Use Case Table Use Case Diagrams Design & Roadmap Diagram Workshop Deliverables Sessions Overview Inter- Program Dependencies Inter- System Dependencies Req Sources & Drivers Functional Hierarchy Parking Lot Day 1 Day 2 Highly collaborative functional process, information, and data analysis (whiteboard)
  • Workshop Attendance
    • Workshop Observations
      • Selection of participants was a key to the success
      • Level of collaboration was high
      • All participants were completely engaged
      • Participants learned significant amounts
      • Clearly influenced the design of applications
      • Facilitators were flexible and sensitive to the need to change the approach to the second day based on the first day
      • Facility support was outstanding
      • Facility configuration was sub-optimal
      • Participants were unanimous in saying that “it was time well spent” and that “we should do this more often”
    • Review Selected Deliverables with Associated Questions
      • Stakeholders & projects/activities
        • Stakeholders matrix
        • Projects and Activities matrix
      • Requirements sources
        • Inter-Program dependencies matrix
        • Requirement sources & resulting drivers matrix
      • High level processes
        • Key system related MP process list
        • ME application for listing in National Registry diagram
        • Driver obtains medical certificate diagram
      • High level system design
        • Based on current approach
        • Potential considerations based on viewing the “big picture”
        • High level systems diagrams
        • Supporting lower level diagrams
    • Information Architecture Observations
      • On the positive side
        • Business processes, while mostly manual, are well understood by the practitioners
        • There is a lot of IT work going on and planned within the MP
        • IT work is early enough in the life cycle so that significant positive impact can be achieved in developing an integrated and well structured automation program
        • IT security and privacy are being considered and will continue to impact how systems will be built
    • Information Architecture Observations (cont.)
      • However
        • Process and application design are occurring in silos within the MP
        • Well structured and detailed application requirements do not appear to be driving design and development
        • Integrated set of systems requirements and associated documentation does not exist
        • Opportunity to leverage common functionality and sharable data are not being exploited across applications
          • Audit capability to track changes to the data after it is received
          • Reference tables
          • Medical professional
    • Information Architecture Observations (cont.)
      • However (cont.)
        • Medical Program was largely unaware of opportunities to leverage FMCSA Enterprise Architecture and Modernization efforts
          • COMPASS portal using single sign-on, working against an integration plan & timeline
          • CSA 2010 business process modernization
        • Unique identifiers for key entities not completely defined
        • The uncertainty in the timing and content of key legislation will likely result in significant system development challenges
        • Additional data fields may be required which are not reflected in legislation
          • Driver data from medical examinations
          • Data to feed to other FMCSA programs
    • Information Architecture Recommendations/Roadmap
      • Continue with collaboration initiated by this workshop
        • With additional workshops as appropriate within MP and other FMCSA organizations
      • Seek opportunities to influence details in pending legislation early in the process
      • Use a business analyst to formalize work on process evaluation
        • Capture the details of the business processes
        • Prepare system use cases
      • Use a system architect to continue work on developing rationalized system design
        • Data dictionary
        • Entity relationship diagrams
        • Systems diagrams
        • Systems integration points
    • Information Architecture Recommendations/Roadmap (cont.)
      • Adapt a common system development lifecycle approach and governance procedures for all applications
        • Requirements
        • Design
        • Development
        • Testing
        • Deployment/Roll-out
        • Operations
      • Ensure system requirements specifications contain the following (as a minimum)
        • Functional requirements
        • Data requirements
        • Physical/Hosting requirements
        • Operational requirements
    • Information Architecture Recommendations/Roadmap (cont.)
      • Continue work on developing rationalized system design
        • Data dictionary
        • Entity relationship diagrams
        • Systems diagrams
        • Systems integration points
        • Interface requirements specifications
          • COMPASS portal interface
          • CDL merger
      • Apply a common software development approach
        • Integrated development environment
        • Shared document and code repository
        • Common naming and coding conventions
        • Configuration management
    • Information Architecture Recommendations/Roadmap (cont.)
      • Plan & document a well structured testing strategy including
        • User acceptance testing
        • Load/stress testing
        • Business process fraud analysis
      • Evaluate & plan options for deployment/roll-out
        • Organizational change management including communication and training
        • Provisions for Continuity Of Operations (COOP) and Disaster Recovery (DR)
      • Design operations to optimize support to the user community
        • Knowledge transfer and helpdesk support
        • Data center operations
        • Software maintenance & enhancements approach
    • Next Steps
      • Incorporate feedback from this session
      • Complete deliverable