From: James P. T. <jpt...@us...> - 2007-09-16 15:05:05
|
Update of /cvsroot/aaf/AAF/Utilities/AAFAnalyzer/Requirements In directory sc8-pr-cvs11.sourceforge.net:/tmp/cvs-serv7328/Utilities/AAFAnalyzer/Requirements Modified Files: AAFRequirements.xml Log Message: Resolve bug that caused resolution errors when multiple references to the same mob existed in a file. The ResolveRefVisitor.cpp::GetChildComponents function was considering all references when it should have been considering only contained objects. Restore regression test to workign order. Resolved several problems in recent code changes exposed by reactivating the tests. Update EPTrackContentsTest to include MobSlot::UserPos test. Improved layout of TestFile/GNUmakefile by factoring out repeated boiler plate test code. Updated the requirements xml element to include "annotation" and "note" sub elements and an "action" attribute. The action attribute is a place to record the fact that something needs to be done to bring the requirement in the xml file into sync with the written spec. The annotation is intended to record some additional text that is proposed (or agreed) should go into the spec. The note is there to comment on the implementation or interpretation of the spec. Update the TestResult to include concept of covered and noted test results. Requirements covered by an associated test are now initialized as covered requirements. From there they move to noted, passed, warned, or failed. when the detailed test results are consolidated. This is a step towared reporting requirements that are covered by a particular file rather than simple reporting all requirements associated with a test as passed (which wasn't the original goal but was the original implementation). Resolve tracker item 1388284 "Missclassifed Requirements". Change REQ_EP_013,014,039 to app requirements. Resolve tracker item 1388314 "Test MIDI files". Changed REQ_EP_143 to app requirment because the analyzer is not responsible for verifying the contents of the external midi file. And, partially resolve 1388290 - REQ_EP_023 should be app requirement not file. And partially resolve tracker item 1388290 - REQ_EP_097 - Pulldown may be used... should be app requirement. And resolve tracker item 1388299 - REQ_EP_160 misclassifed, changed to app. Resolve tracker item 1388140 ] "TimelineMobSlot Edit Points". Split REQ_EP_108 into .1/.2/.3/.4 parts to isolate individual reporting items. Updated the test to note the presence of mark in/out points and user position. The only thing tested is that mark out is greater than mark in if both exist. No long warn if one of mark in/out is present but not the other. Index: AAFRequirements.xml =================================================================== RCS file: /cvsroot/aaf/AAF/Utilities/AAFAnalyzer/Requirements/AAFRequirements.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -C2 -d -r1.16 -r1.17 *** AAFRequirements.xml 21 Aug 2007 14:08:34 -0000 1.16 --- AAFRequirements.xml 16 Sep 2007 15:04:36 -0000 1.17 *************** *** 1186,1193 **** </requirement> ! <requirement type="file" category="metadata"> ! <id>REQ_EP_108</id> ! <name>IN, OUT and User Position Point Specification</name> ! <desc>The marked IN and OUT points and user position shall be specified using the TimelineMobSlot::MarkIn, TimelineMobSlot::MarkOut and TimelineMobSlot::UserPos optional properties respectively.</desc> <ref> <doc>&DOC_AAF_EP;</doc> --- 1186,1212 ---- </requirement> ! ! ! <!-- start REQ_EP_108_X --> ! ! <requirement type="file" category="metadata" action="reconcile"> ! <id>REQ_EP_108.1</id> ! <name>Mark IN Position</name> ! <desc>The mark IN point shall be specified using the TimelineMobSlot::MarkIn optional property.</desc> ! <annotate>If mark IN is not specified then the beginning of the seqment is implied.</annotate> ! <note></note> ! <ref> ! <doc>&DOC_AAF_EP;</doc> ! <version>&VER_EP_1.0;</version> ! <section>7.7</section> ! </ref> ! </requirement> ! ! <requirement type="file" category="metadata" action="reconcile"> ! <id>REQ_EP_108.2</id> ! <name>Mark OUT Position</name> ! <desc>The mark OUT point shall be specified using the TimelineMobSlot::MarkOut optional property.</desc> ! <annotate>If mark OUT is not specified then the end the seqment is implied.</annotate> ! <note></note> <ref> <doc>&DOC_AAF_EP;</doc> *************** *** 1197,1200 **** --- 1216,1245 ---- </requirement> + <requirement type="file" category="metadata" action="reconcile"> + <id>REQ_EP_108.3</id> + <name>Marked Region Length</name> + <desc>The length of the marked region is OUT-IN. OUT shall be greater than IN.</desc> + <note>This is coded to FAIL, formerly it warned because this wasn't stated in the EP spec. This should be clear in the specification to avoid off by one errors, and to avoid the assumption that OUT equals IN is acceptable.</note> + <ref> + <doc>&DOC_AAF_EP;</doc> + <version>&VER_EP_1.0;</version> + <section>7.7</section> + </ref> + </requirement> + + <requirement type="file" category="metadata" action="reconcile"> + <id>REQ_EP_108.4</id> + <name>User Position</name> + <desc>The user position shall be specified using the TimelineMobSlot::UserPosition optional property.</desc> + <note></note> + <ref> + <doc>&DOC_AAF_EP;</doc> + <version>&VER_EP_1.0;</version> + <section>7.7</section> + </ref> + </requirement> + + <!-- end REQ_EP_108.X --> + <requirement type="app" category="metadata"> <id>REQ_EP_109</id> |