|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - download
Length: 2096 (0x830) Types: TextFile Notes: R1k Text-file segment
└─⟦8527c1e9b⟧ Bits:30000544 8mm tape, Rational 1000, Arrival backup of disks in PAM's R1000 └─ ⟦5a81ac88f⟧ »Space Info Vol 1« └─⟦847ef57df⟧ └─⟦this⟧
changes: there is no enclosing scope on nested design components [i.e. @DECOMPOSITION (Foo.Bar) is now simply @DECOMPOSITION (Bar)]. This is not how it is explained in the course. in generic PDL entry exercise: after semanticizing after doing second PDL Complete: many errors come up: the instructions refer to a SINGLE error "prompt illegal for" message has been changed to "Prompt is not permitted for the ________________ annotation." instructions tell students to fill in prompts with "NONE." instead of "NONE" after deleting annotation, the error message is "The __________ annotation must be specified." instead of "No ________ annotation specified" after adding @ALGORITHM annotation, the error message is "The ________ annotation is not permitted here." rather than "__________ annotation not permitted" prompting for PDL Complete resolves to Design_Implementation.Complete, not Design.Complete step 28.a. is not generic--talks about "use" clause summary exercise: page 115 5.a change "unsatisfied" to "unallocated" page 116 delete "The log will..." instructor note 4 page 117 4 needs @DESCRIPTION, @SOURCE, and @DESTINATION annotations page 120 4.c. @LIMITATIONS annotation should not be there we need to teach them about activity-relative traversal diagram of transaction processor needs second "add money" loop which leaves and enters the "accumulating transaction" bubble bugs: multiple @REQUIREMENT annotations currently don't work, so one of the traversals in the exercises does not work (supposed to be fixed in next release) traversal within a CSCI is activity-dependent, so instructions on summary exercise do not work (supposed to be fixed in next release) incremental compilation is very fragile, and it is used in some of the exercises, resulting in errors