Simplify INTERVAL_EVENT for archetyping and paths
Raise CR
Analysis
Resolution
Raise CR
Analysis
Resolution
Description
Activity
Show:
Fixed
Assignee

Reporter

Priority
Created January 16, 2006 at 12:00 AM
Updated January 20, 2006 at 12:00 AM
Resolved January 20, 2006 at 12:00 AM
The enhanced HISTORY model created by CR-000185 is semantically
correct, and probably the most accurate rendition of the requirements.
However, the use of the Hash table on INTERVAL_EVENT to represent
a multiplicity of values for any INTERVAL_EVENT poses some technical
problems for archetyping and paths.