/*Milestone3.txt*/ 1 31 Next, turn this User Requirements doc into an Engineering Req'ts document: 32 33 For each major subsystem in Appendix 1, there should be a 34 a Configuration Item (CI) defined in ToFS. These can be defined 35 using the 'File' menu/'New CI' Menu Item. Requirements Mgt systems 36 (like TOFS) manage data in a database along with formatted documents. 37 TOFS uses an Inprise DB (formerly Borland), Word97 documents with 38 templates that you can change for each document type. 39 40 Using the 'Document' menu , choose 'CI Document' and fill in the 41 'System Overview' section - describing the overview of this piece of 42 the system. You will be placed in Word97 to do this editting. 43 44 Using cut/paste from the User Requirements, fill in the 45 'Original Requirements' section with any User requirements that 46 are applicable to this CI. 47 48 Using the 'Requirements' menu/'Insert' menu item, 49 enter numbered requirements (specific, complete, testable) into TOFS. 50 The numbering of these should be consistent with the User requirements 51 (e.g., if user reqt was 2, engineering requirements can be 2.1, 2.2, ...). 52 53 If there are interfaces to the "outside" that this CI should 54 implement, these should be documented in the 'Offered Interface' section; 55 any data referenced should be described in the 'Glossary' section. 56 This could include data entered/displayed to the user -or- data 57 received/sent to other CI's. 58 59 Other sections of the Document can be left blank. 60 61 To print the Document, use the 'Prepare Print' menu/'CI Document' 62 menu item. Word97 allows you to save the document in .html format 63 so it can be added to your Team website. 64 65 After all the CI documents are generated, the package will be ready to be 66 reviewed. The Review information and Object status can be entered into TOFS 67 by using the 'Object' menu/'Current Object - Change Properties' Menu Item. 68 DUE IN DRAFT FORM: 9/20 PEER REVIEW: 9/22 DUE IN FINAL FORM (on website): 9/24