DataMuseum.dk

top - metrics - download

    Length: 2504 (0x9c8)
    Types: TextFile
    Names: »READ_ME«

└─⟦180fe333a⟧ Bits:30000405 8mm tape, Rational 1000, SW CATALOG, 10_20_0
└─⟦180fe333a⟧ Bits:30000537 8mm tape, Rational 1000, SW Catalog 10_20_0
    └─⟦5cb1d1d7f⟧ »DATA« 
        └─⟦3b1ee7bd8⟧ 
            └─⟦this⟧ 

TextFile

The Cm_Generic provides a mechanism to define a forms system that will
interface to Rational Work Orders.  This tool is really meant to be used
as the base for a user defined CM system.  Once instantiated with the
desired Items to Forms, the toolsmith should then write routines on
top of the instantiation to best fit the projects CM methodologies.
For example, having routines to bring up the defined forms.  These
routines will most likely only call the Cm_Instantiation.Edit routine
passing it the work order and the corresponding form.

A sample instantiation would be:

package Definitions is

    -- defines the fields of the forms
    type Items is (Date, Username, Description, Analysis, Fix);

    -- defines work order forms
    type Forms is (Bug, Analysis, Fix);

end Definitions;
----
with Definitions;
with Cm_Generic;
package Project_Cm is
   new Cm_Generic (Items => Definitions.Items,
                   Forms => Definitions.Forms,
                   Work_Order_Path => "!projects.cm_project_area",
                   Work_List_Path => "!projects.cm_project_area",
                   Venture_Path =>
                      "!projects.cm_project_area.project_venture");

----                      
with Project_Cm;
package body Definitions is
    package Fd renames Project_Cm.Form_Definition;
begin

    -- Bug form
    Fd.Add (Date, "Date", Bug);
    Fd.Add (Username, "User", Bug);
    Fd.Add (Description, "Description of Problem", Bug);

    -- Analysis form
    Fd.Add (Analysis, "Analysis of Problem", Analysis);

    -- Fix form
    Fd.Add (Fix, "Description of Fix", Fix);

end Definitions;
----

Some of the prerequisites for this tool:
    
   You must manually create the venture in the right place.
   
   You must manually create each field in the venture. Making sure they
      correspond to the Definitions.Items'image.  This can be done
      interactively by doing an Object-I in the Venture's Fields section.

   You need to do a Wo.Create_List ("project_tasks") in the work_order_path
      directory.  The tool places all new work orders on this list.
      
   The Cm_Generic subsystem depends on the Window_Io_Utilities subsystem in
      the S/W Catalog, therefore the proper imports must be make before
      compiling.
      
   Cm.Initialization.Init_Index must be run once.  this will set the work
      order index counter to 0.

   When entering data into a form the user must hit enter or promote
      to actually place the information in the work order.