Project P050302 ODMref1.0 Mitigation Experiment #1

ODMA>active> ODMref1.0> mitigate> P050302> 0.00 2006-01-20 -15:06 -0800

1. Concerns

• Establish that there is a minimal, inexpensive tool set for constructing the necessary DLL.
• Calibrating the effort involved in this simple activity, and the preparations for it.
• Being able to explain and easily reproduce the preparation and construction process is part of the overhead for making constructions demonstrable and trustworthy.

2. Approach (2005-03-27)

• 2005-03-09: Set up a simple compilation project using a freely available version of VC++
• 2005-03-07: Extract a skeleton from the source code of the ODMA 2.0 Sample DMS (DLL structure) and the ODMA 2.0 Connection Manager (logging functions).
• 2005-03-07: Find the ODMA header files that are required for implementation of a DMS DLL entry point (no interfaces)
• 2005-03-07: Find the ODMA header files for properly matching the signature and data types of the ODMGetODMInterface function prototype.
• Find the include files that are required to be able to compile all of the definitions used in the minimal skeleton DLL.  Everything that is not redistributable from Microsoft, identify how it is found and then document how someone else can obtain it.
• Successfully compile a simple DLL that has ODMGetODMInterface as its only function.
• Create a script for registering the ODMref10 DLL with ODMA so that it can be called as a default function.
• Try out the interface with TestODMA32 and one other application, such as Microsoft Word 2003.
• Insert code to log the parameters passed to ODMGetODMInterface and also log the NOINTERFACE response from the dummy function.
• Verify creation of the log by programs that initiate the interface.

3. Activities (2005-03-27)

• 2005-03-07: Extract the necessary skeleton and any local headers from the Sample DMS to the ODMref10DeRisk01 project.[dh:2005-03-27 moved to separate DeRisk01 project.]
  The result is a simple file (or two) that will compile to a simple stub, provided that the necessary definition files are available.

• Arrange for the function to simply return NOINTERFACE, along with a NULL interface-pointer value.

• Get the DLL to compile.

• Use DeRun01 to verify that the DLL can be called and it behaves properly, just as other DMS DLLs called by DeRun01.

• Create registration and deregistration scripts to register the dummy as the default DMS, then deregister it.

• Attempt to operate the DMS with TestODMA32 and also Microsoft Word 2003.

• Record enough to be able to fully document this part and the preparations later.

• Find out how to learn the location of the DLL that is being run (we need this for other reasons later on)

• Use that as the location for creating a log (we will later put the logs in the directory of the document base being used, but for now we put them with the DLL).

• Implement a simple log, similar to that produced by the ODMA 2.0 Connection Manager.

• Verify operation of the log and the entry failures with TestODMA32 and any Microsoft Office applications that are proposed to be ODMA-aware.

• P050302b: DeRun01 Test Harness
• P050302c: DeRisk01 Dummy DLL

0.00 2005-03-07 create  placeholder to morph into the necessary material

Incorporate job jar and use it to drive the completion of essential items here, which starts as a simple skeleton.