ODMA: Open Document Management API

Project P050302 ODMref1.0 
 Mitigation Experiment #1
DeRun01 Test Harness

ODMA>active>
ODMref1.0>
mitigate>

P050302b>
0.01 2006-01-20 -15:07 -0800

DeRun01 is the test harness for Mitigation Experiment #1.  DeRun01 confirms the minimum development setup required to begin development of ODMref 1.0 and its test fixture(s).

1. Operation

1.1 Command-Line

DeRun01 is a console-mode application that operates with the command-line

C:/> DeRun01 --dll file-name

causes the test to run with the specified DLL.  The DLL is loaded and the test performed.

1.2 Output

DeRun01 presents all of its output to the system console, where it can be redirected.

The output text provides the following information:

  1. An announcement of the application, its version and title.

  2. The Command and options that are being processed.

  3. Report of the loading of the specified DLL.

  4. Report of the entry-point call being performed to the loaded DLL.

  5. Report of the results obtained from the call

  6. Report of any released COM interfaces (in case the DLL returns an interface)

  7. Report of the unloading of the DLL.

  8. Report of the completion of the DeRun01 execution.

All of the output lines are time-stamped.  Hmm, maybe not, because that makes it impossible to compare the results of different runs.  We'll sort that out later.

1.3 Confirmation

  1. The program is first confirmed by being able to load, activate, and unload the ODMA Sample DMS for ODMA 2.0. 

  2. The second confirmation is by being able to load, activate, and unload the DeRisk01 DLL properly.  This fixture can be used to confirm further risk mitigation software, and builds of ODMref10 as well.

2. Design Considerations

2.1 General Approach

This is a simple program that will be developed in C Language.  Except for loading and invoking code in the DLL, it should be a pretty pure POSIX source program.  The load and invoking code should be encapsulated in a suitable way.  In the future, this code could be a C++ class that manifests the coordinated lifecycle of the loaded DLL.

The ODMGetODMInterface definition is maintained in a header file.  This header is included and we manage that appropriately.

2.2 Potential Resources

  1. A general library for processing command-line parameters would be useful.  It would be great to define and develop one of those or even rely on a standard one that is available in the open-source world.

  2. A general stdio library along the lines of my Java conio interface(s) would also be very useful.  I can also get examples from my collection of Java goodies.

  3. The existing ODMA header files and the ODMA Sample DMS, the Test32 client, and pieces of the classes used in building the ODMA32 2.0 Connection Manager.

  4. Find existing definitions and declarations for the ODMGetODMInterface operation.

2.3 Packaging

[to be defined.  There will be a simple Zip packaging of the completed DeRun01 experiment and everything needed to run it.]

3. Bugs

 

0.01 2005-03-26-19:46 Create Initial Skeleton Work Item
A sketch of the the DeRun01 approach is created that is the basis for working through the initial construction.
Construction Zone (Hard Hat Area) You are navigating the
ODMA Interoperability Exchange.

created 2005-03-26-18:38 -0800 (pst) by orcmid
$$Author: Orcmid $
$$Date: 10-08-29 20:11 $
$$Revision: 21 $