1 / 18

The Functionality Matrix

“Handbook for the Acquisition of Technical Data Presentation Products” and “S1000D Chapter 6.4”. The Functionality Matrix. AIA / Tri-Services 2004 Publications Workshop San Antonio, TX Bill Wendel USAF MSG/MMF (BTAS, Inc.) 11 February 2004. Overview. Purpose Background

orinda
Télécharger la présentation

The Functionality Matrix

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. “Handbook for the Acquisition of Technical Data Presentation Products” and “S1000D Chapter 6.4” The Functionality Matrix AIA / Tri-Services 2004 Publications Workshop San Antonio, TX Bill Wendel USAF MSG/MMF (BTAS, Inc.) 11 February 2004

  2. Overview • Purpose • Background • Sponsorship and Organization • Recent Changes • Proposed Changes • Using the Matrix • Real World Input • Where to Find the Matrix

  3. Purpose • The AIA Functionality Matrix is an acquisition tool designed to facilitate requirements gathering and communication between an acquisition office and a vendor. • Provides accepted definitions and descriptions of common ETM/IETM terms and capabilities • Enables the creation of requirements definition documents and provides sample text for documenting requirements • The Matrix should not be placed on, or inserted into, a contract.

  4. Background • Initially developed in 1999 as a tool to aid ETM/IETM acquisitions • The Matrix received increased attention in early 2003 due to several factors: • Desire to include the Matrix in S1000D • Need to reflect advances in IETM technology and tools • Need from the DoD acquisition community to update the Matrix and demonstrate a commitment to its sustainment

  5. Functionality Matrix Sponsorship and Organization • Originally sponsored by the AIA Product Support Committee with support from the Tri-Service IETM Technology Working Group • Inclusion in S1000D necessitated a change in sponsorship • MOU between AIA and AECMA for joint ownership of S1000D in Mar 03 • AIA requested US EPWG accept sponsorship in Oct 03 • US EPWG established the Matrix sub-project working group • Added Look & Feel responsibilities to the “Functionality Matrix/Look & Feel Sub-Project Group” (FM/LnF)

  6. FM/LnF Sub-Project Group • Charlie Cartwright Lockheed Martin • Heidi Macfarlan Boeing/CDG • Pushpa Merchant PBM Associates • Mike Post Boeing • Bruce Schanck US Army (CSC) • Bob Sharrer NAVAIR • Danny Smith General Dynamics • Bill Wendel USAF (BTAS, Inc)

  7. Recent Changes • Version 2.0 – May 2003 • The Matrix was rotated 90° and divided into three sub-matrices • Linear - Paper ETM • Linear – Screen ETM • Non-linear IETP • Handbook was extensively rewritten • Improved introduction and guidance • Added and improved functionality definitions • The v2.0 Matrix was submitted to the EPWG in April and included as Ch. 6.4 of S1000D Issue 2

  8. Recent Changes • Version 2.1 – June 2003 • After the 2.0 submission, the committee received a number of change requests from the US Army and AIA Clearwater conference attendees • The committee met and worked through the following Matrix changes for v2.1 • Corrected inconsistencies with the Back, Forward, Next & Previous functionalities and ensured this same consistency throughout the entire S1000D Issue 2 document • 4 of 7 US Army suggestions were fully accepted and 2 others were accepted with minor modifications

  9. Recent Changes • Version 2.11 – August 2003 • The committee met again to make final modifications before the S1000D Issue 2 editorial meeting. • Editorial changes • Improved Handbook introduction • Error corrections

  10. Recent Changes • Version 2.12 – October 2003 • This version is the result of the decision to combine the two separate S1000D and AIA documents into one. • It does not include any content changes • It does identify the portions of the AIA document that are not included in S1000D

  11. Proposed Changes • New Functionalities: “Reset,” “Return,” “Change Marking Toggle,” “Check Boxes,”… • Consider removing acquisition paragraphs from the Handbook and developing a separate Cost/Acquisition Guide • Consider additional emphasis on non-standard display devises (PDA, Tablets, etc.) relative to functionality and look & feel • Consider development of an interactive Matrix • Make editorial changes and other corrections suggested by users • Better defining the items on the Horizontal Axis • Consider changing the official title of the handbook

  12. The Horizontal Axis: • Which content types require the functionality? • The Vertical Axis: • Identify the required functionality • Separate tabs for: • Linear – Paper • Linear – Screen (ETM) • Non-Linear – IETP (IETM) • Overall (combined view) Using the Matrix

  13. Final Deliverable Impact: • Location for identifying requirements ü H M L • Complexity Factor: • Provides a relative cost estimate for individual functionalities Using the Matrix Requirement identification can be tailored as desired. It could be a simple binary check, weighted identifier, color coded, etc…

  14. When all cells for a given functionality are shaded, that indicates that the functionality most-likely applies to every content type. When some cells are un-shaded, it indicates that the functionality may apply to certain content types, but not all… ü ü ü …in which case, the specific content types requiring the functionality should be identified Using the Matrix

  15. Using the Matrix • A completed Matrix will provide an initial requirements document. • After normal coordination and agreement, it can be shared with prospective vendors during the acquisition process. • The functionality descriptions in the Handbook can be used as template text for contract line items. • During the period of performance, a completed Matrix can be used to aid requirements tracking.

  16. Real World Input • Our objective is to have a tool that is useable and useful to both vendors and government The best way to successfully do that is to incorporate feedback based on real world use of the Matrix • We’ve received some, but want more • If you’ve used the tool, or when you use the tool, please provide feedback to…

  17. Bill Wendel USAF MSG/MMF (BTAS, Inc.) 937 904 0861 bill.wendel@wpafb.af.mil Pushpa Merchant PBM Associates 609 276 1020 push@pbmassoc.com Contacts FM/LnF Sub-Project Group Co-Chairs:

  18. Where to Find the Matrix • S1000D Issue 2 (Ch. 6.4) • www.s1000d.org • The AIA web site: • www.aia-aerospace.org/members/documents.cfm • The WPAFB web site: • www.ide.wpafb.af.mil/tmss/ietm.html

More Related