ODMA Project

 P010200: Bring ODMA Incident Reports Current

Last updated 2002-06-04-16:12 -0700 (pdt)
The latest version of this information is available on the AIIM DMware ODMA site.

---

Type: ODMA Support	Project ID: P010200
Style: Ad hoc	Status: Underway
Objective:  1. Have all logged incidents reflected by reports. 2. Have all new logged incidents reflected.  Note: It is not the objective of this project to resolve all incidents.  It is to have them all documented.	Related information/projects: ODMA Incident Log ODMA 2.0 Specification Errata P000800: Capture All ODMA Questions and Problem Reports as FAQ and Incidents P000701: ODMA Specification Errata
Assigned To: Dennis Hamilton	Defined By:  Dennis Hamilton (2001-03-01)
Date Opened: 2001-02-27	Date Completed: none

1. Requirements (2001-02-27):

Rank the known ODMA incidents and organize the creation of supporting reports, using the following prioritization scheme:

• Critical incidents involving production integrations are reported first
• Serious and Dangerous incidents are reported next
• Reports impacting the creation/use of ODMA Libraries
  including critical, serious, and dangerous
• Reports impacting the creation/use of ODMA Connection Managers
  including critical, serious, and dangerous
• Reports impacting the completion of accurate documentation and errata for ODMA 2.0
  including critical, serious, and dangerous
• All other incidents, including requests for enhancements

2. Activities (2001-02-27)

2.1 Incidents Involving ODMA Integrations
2.2 Incidents Impacting the ODMA Documentation Set
2.3 Incidents Impacting ODMA Development Libraries
2.4 Incidents Impacting ODMA Connection Managers
2.5 Miscellaneous Incidents and Enhancement Requests

The purpose of these activities is to have each logged incident supported by a report that describes the incident in more detail, and provides for expansion with investigation, ways of reproducing/confirming the incident, and any workarounds and resolution that becomes available.  

These activities do not involve closing the incident.  It is having the incident itself better known and documented.  The closing of the incident backlog is a second project.

The grouping reflects the relative importance to users of ODMA systems, followed by ones impacting developers.

All new incidents that are logged after this project starts always have reports filed immediately.

The assigned dates for the incident being reported are based on a rate of approximately one report per day.   This allows for new activities and other projects to continue in parallel.

2.1 Incidents Involving ODMA Integrations

Problems with ODMA integrations are ones that impact users of ODMA applications and DMS components.  These are incidents that impact the reliable usage of ODMA in operational settings.

Those incidents already logged are to be recorded first, so that those impacted by these incidents can contribute to trouble-shooting, and others can check to see if they are experiencing the same or different incident.

2.2 Incidents Impacting the ODMA Documentation Set

Incidents involving the ODMA Documentation Set must be reported so that the provision of a stable documentation library can be established.  In addition, the accuracy of the specification is critical to the arbitration and resolution of other incidents involving development and implementation of the ODMA Connection Managers.

2.3 Incidents Impacting ODMA Development Libraries

Accurate, complete development libraries are critical to the confident creation of ODMA-compliant components by the development community.  

2.4 Incidents Impacting ODMA Connection Managers

Having clear understanding of the incidents that arise with Connection Managers, and being able to tell if they arise in practice, is also critical to the development and the application communities having confidence in the reliability of the critical ODMA middleware.

2.5 Miscellaneous Incidents and Enhancement Requests

These incidents are generally about activities that were underway at some point,  or have been requested.  The additional utility may be clear, and there may already be new activity in these areas.  However, in terms of the urgency of reporting, these items are not so urgent as ones involving potential defects, problems, and misunderstandings.

created 2001-02-27-13:11 -0800 (pst) by orcmid
$$Author: Orcmid $
$$Date: 04-11-18 14:16 $
$$Revision: 15 $