T

1
ADL-R VCS Post-Award Meeting Contract No.
N61339-05-C-0105-P00003 25 May 2007
Dr. Ken Pisel Dean, Joint Continuing Distance
Education School Angela Lindsey Project
Manager/Principal InvestigatorGreg Frederick
Researcher/Analyst
2
Agenda

• Introduction
• Background
• Objectives
• Project Overview
• Sample Version Control System (VCS) Interface
• Our Joint Approach
• Roles Responsibilities
• Task Breakdown
• Proposed Project Schedule/Deliverables

3
Background

• Northrop Grumman partnership with JFSC
• Developed 51 SCORM lessons (2002-2003)
• Staffs JFSC Distance Learning Division
• Maintains AJPME courseware
• Provides technical expertise for DL issues
• Participates in Distance Learning Coordination
  Committee (DLCC) community of practice (COP)
• Relationship with ADL team
• Active in Registry pilot team ADL-R users group
• Began FY05 ADL-RC prototype project Oct 2005
• Completed Phase I requirements Mar 2007

4
Objectives

• Goal to support content currency promote
  sharing
• Version control system (VCS) notifies users of
  changes to registered content
• Two pronged approach
• Local ADL-Registry Client (ADL-RC) application
• Web-based VCS
• Phase I Develop the ADL-RC prototype
• Compares registered data to local data emails
  change alerts
• Network security restrictions limit its use DoD
  wide
• Need for alternative web-based solution
• Phase II Implement a web-based VCS
• Develop best practices for ADL-R updates
• Create VCS functionality for the ADL-R Portal
• Customize content alert notifications

5
Project Overview

• Gather requirements user input
• Survey multiple user groups
• Document results best practices
• Design VCS around user needs
• Account/profile management required
• Design entails multiple web modules
• Registration for customized alert notifications
• Subscription to RSS feeds
• Enhanced searches on version history
  documentation
• Initially deployed on test portal for future
  migration

6
Sample Version Control System GUI
RSS Feeds
Email Alerts
Documentation
Version History
7
Roles Responsibilities

• Northrop Grumman Prototype Team Responsible for
  Research Development
• Technical Director
• Sean Decker
• Project Manager/Principal Investigator
• Angela Lindsey
• Researcher/Analyst
• Greg Frederick

8
Roles Responsibilities

• Joint Forces Staff College (JFSC)
• Concept/Vision Lead
• Dr. Ken Pisel hosts the Northrop Grumman team
  at JFSC during the period of performance
  provides direction
• Knowledge-Media, Inc. (KMI)
• KM Specialist/Senior Programmer
• Bill Redeen provides technical support VCS
  prototype development function

9
Roles Responsibilities

• Northrop Grumman PMO
• Contract Program Manager
• Tony Shafer responsible to the JADL Co-Lab and
  to the company for technical and financial
  performance of the contract
• Delivery Order Manager
• Gary Baker supports business operations
  (technical and financial reporting, etc.) for
  assigned delivery orders
• Contract Administration
• Ann Kirkpatrick authorized to communicate with
  the Government Contracting Officer
• Dawn Macpherson serves as alternate contract
  administrator

10
Phase II Task Breakdown

• Task 1 Research Analysis
• Task 2 System Design
• Task 3 New Prototype Development
• Task 4 Quality Assurance
• Task 5 Demonstration
• Task 6 Evaluation Implementation (Optional)

11
Proposed Project Schedule (Phase II)

• Kickoff Meeting 25 May 07
• Monthly Progress Reports 10th of each month
• Modified Milestone Chart 45 days after award
  (11 Jun 07)
• Research Results 60 days after award (26 Jun
  07)
• DLCC COP Best Practices Guide 90 days after
  award (26 Jul 07)
• Design Document 120 days after award (26 Aug
  07)
• JADL Implementation Fest 28-30 Aug 07
• Test Scripts/Test Incident Reports available as
  requested
• Mid IPR 200 days after award (15 Nov 07)
• Final IPR 365 days after award (25 Apr 08)
• Programmed Code 365 days after award (25 Apr
  08)
• Project Final Report 365 days after award (25
  Apr 08)
• (Formal deliverables are in bold italics.)

12
Questions?