OctetView
0x00000…00100 (0, 0, 0) Sector 00144130303134 ┆ A0014A ┆
0x00100…00200 (0, 0, 1) Sector 00000000000000 ┆ ┆
0x00200…00300 (0, 0, 2) Sector ffff3fff0080ff ┆ ? ~` ` p p` ` x ┆
0x00300…00306 (0, 0, 3) WangDocument {d00=0x00, d01=0x74, d02=0x41, ptr=(34,0, 0), d05=0x00}
0x00306…0030c WangDocument {d00=0x00, d01=0x83, d02=0x41, ptr=(39,0, 0), d05=0x00}
0x0030c…00312 WangDocument {d00=0x00, d01=0x85, d02=0x41, ptr=(36,0, 0), d05=0x00}
0x00312…00318 WangDocument {d00=0x01, d01=0x07, d02=0x41, ptr=(72,0, 8), d05=0x00}
0x00318…0031e WangDocument {d00=0x01, d01=0x08, d02=0x41, ptr=(19,0, 0), d05=0x00}
0x0031e…00324 WangDocument {d00=0x01, d01=0x09, d02=0x41, ptr=(19,0, 8), d05=0x00}
0x00324…0032a WangDocument {d00=0x01, d01=0x20, d02=0x41, ptr=(15,0, 0), d05=0x00}
0x0032a…00330 WangDocument {d00=0x01, d01=0x26, d02=0x41, ptr=(24,0, 8), d05=0x00}
0x00330…00336 WangDocument {d00=0x01, d01=0x27, d02=0x41, ptr=(14,0, 8), d05=0x00}
0x00336…0033c WangDocument {d00=0x01, d01=0x29, d02=0x41, ptr=( 7,0, 0), d05=0x00}
0x0033c…00342 WangDocument {d00=0x01, d01=0x34, d02=0x41, ptr=(16,0, 8), d05=0x00}
0x00342…00348 WangDocument {d00=0x01, d01=0x48, d02=0x41, ptr=(69,0, 0), d05=0x00}
0x00348…0034e WangDocument {d00=0x01, d01=0x51, d02=0x41, ptr=(28,0, 0), d05=0x00}
0x0034e…00354 WangDocument {d00=0x01, d01=0x52, d02=0x41, ptr=(32,0, 0), d05=0x00}
0x00354…0035a WangDocument {d00=0x01, d01=0x55, d02=0x41, ptr=(33,0, 8), d05=0x00}
0x0035a…00360 01 55 41 21 08 00 ┆ UA! ┆
0x00360…00380 01 55 41 2b 08 00 01 55 41 2b 08 00 01 55 41 2b 08 00 01 55 41 2b 08 00 01 55 41 2b 08 00 01 55 ┆ UA+ UA+ UA+ UA+ UA+ U┆
0x00380…003a0 41 2b 08 00 01 55 41 2b 08 00 01 55 41 2b 08 00 01 55 41 2b 08 00 02 66 41 4b 08 42 00 00 00 00 ┆A+ UA+ UA+ UA+ fAK B ┆
0x003a0…003c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ┆ ┆
[…0x1…]
0x003e0…00400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5a ┆ Z┆
0x00400…00500 (0, 0, 4) Sector 00000000000000 ┆ ┆
0x00500…00600 (0, 0, 5) Sector 00144130303134 ┆ A0014A ┆
0x00600…00700 (0, 0, 6) Sector 421c402600415b ┆B @& A[' . X% % PO P ; Az* C f x f V Wf O 7 :V, -+# 0085A f T < {C < { ; 6 ` i1 C@ ?f ?ff ' m 8 : 9 # t x 0085A W%-+W+x" $ ┆
0x00700…00800 (0, 0, 7) Sector 00000000000000 ┆ ┆
[…0x8…]
0x01000…01100 (1, 0, 0) Sector 0101fe00007441 ┆ ~ tAder Spacing 1 blank line shall separate the heading from the first line of its associated text. 4.3 INDENTATION The first line of a partition on all levels shall be indented 5 character positions. Indentation shall not normally be used excm┆
0x01100…01200 (1, 0, 1) Sector 0000f000007441 ┆ p tAept as described under subindicies. 5 TABLE OF CONTENTS 5.1 CONTENT The table of contents shall contain all Headers from the document preceded by their indicies. All entries shall be written with same characters as in text., the resulting┆
0x01200…01300 (1, 0, 2) Sector 00000000000000 ┆ ┆
[…0x5…]
0x01800…01900 (1, 0, 8) Sector 0109ff00007441 ┆ tAte)". 3.2.5 NATO particular On documents particularly produced for NATO the page number shall be placed centered in the bottom of each page. This may be done solely or in addition to the standard page numbering in the page heading. 3.3 APPE┆
0x01900…01a00 (1, 0, 9) Sector 010aff00007441 ┆ tANDICES 3.3.1 Level An appendix is considered to be at the same level as a chapter and the chapter rules for headers, spacing etc applies. 3.3.2 Designator Appendices shall be given a capital letter as designator. This letter is written i┆
0x01a00…01b00 (1, 0, 10) Sector 010bff00007441 ┆ tAn front of all indices, page numbers, and Table/Figure numbers in the appendix. 4 SPACING AND HEADERS 4.1 SPACING 4.1.1 Line Spacing Line spacing shall be 1.1/2 line. 4.1.2 Separation of Partitions 4.1.2.1 Chapter a) Small docum┆
0x01b00…01c00 (1, 0, 11) Sector 010cff00007441 ┆ tAents (see 3.2.1) Chapters shall normally start at the top of a page. If a chapter ends high on a page a new chapter may start on the same page after 10 blank lines, provided at least 10 lines of the new chapter are accomodated on that page. ┆
0x01c00…01d00 (1, 0, 12) Sector 010dff00007441 ┆ tAb) Medium size through large documents (see 3.2.2). Chapter shall always start on a new page. 4.1.2.2 Sections 4 blank lines shall separate the end of a section from the header of the next. 4.1.2.3 Sub-sections and paragraphs 2 blank li┆
0x01d00…01e00 (1, 0, 13) Sector 010eff00007441 ┆ tAnes shall separate the end of a sub-section or paragraph from the heading of the next. 4.2 HEADINGS 4.2.1 Chapter Headings Chapter headings shall be written in capital letters preceded by the chapter number. Chapter headings shall be center┆
0x01e00…01f00 (1, 0, 14) Sector 010fff00007441 ┆ tAed over the text. Example: 6 CHAPTER HEADING 4.2.2 Section Headings Section headings shall be written in capitals and aligned with the left margin. 4.2.3 Sub-section & paragraph headings Sub-section and paragraph-headers shall be writ┆
0x01f00…02000 (1, 0, 15) Sector 0100ff00007441 ┆ tAten with all words starting with capitals, except internal conjunctions, prepositions, and articles. (Words like "and", "or", "in", "of", "the", and aligned with the left margin. 4.2.4 Underlining All headers shall be underlined. 4.2.5 Hea┆
0x02000…02100 (2, 0, 0) Sector 0201ff00008441 ┆ A 1 15. indent eller tab til 27. 16. skriv anden kolonne navne, kun plads til 8 i hver kolonne. 17. Tab til 52 18. skriv under 'copies participants' 19. slut med 6 return. Format┆
0x02100…02200 (2, 0, 1) Sector 0202ff00008441 ┆ Alinie:, tab p> 3, 16, 20, 24 Side 2 ('Header') 20. Tab p> 20, 65 21. Liniel`ngde 68 22. G> i 'insert'. 23. 6 retur. 24. Tab p> 20 (skriv navn p> m]de) 25. ingen return, start med det samme 26. Tab p> 65, skriv nummertegn for sidenummerering┆
0x02200…02300 (2, 0, 2) Sector 02033200008441 ┆ 2 A. 27. Slut med 7 return. 28. 'execute' 5M 2M[- RA5Cq5:^=~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x02300…02400 (2, 0, 3) Sector 0000fb00008441 ┆ { AFormatlinie: tab p> 3, 16, 20, 24 29. Start tekst (ACTION) i pos. 3 30. Tab til 16, tal 31. Indent til 20, tekst p> 24 32. Liniel`ngde p> side 1 (teksten) skal slutte p> 55 33. Efterf]lgende sider m> liniel`ngden kun v`re p> 50 karakterer. ┆
0x02400…02500 (2, 0, 4) Sector 0205ff00007441 ┆ tAe removed, one page may be used to serve this purpose, numbered with the first and last page number of the removed pages. The above instructions for amendments of page numbering apply to revisions carried out by distributing only a number of the ┆
0x02500…02600 (2, 0, 5) Sector 0206ff00007441 ┆ tApages of which a document exists. When a document is thoroughly revised and distributed as a completely new issue, the page nu`mbering shall be completely revised in accordance with the rules put down in par 3.2.1 and 3.2.2. 3.2.4 References A┆
0x02600…02700 (2, 0, 6) Sector 0207ff00007441 ┆ tAs a consequence of the amendment rules laid down in par 3.2.3 any reference to a page number shall be avoided within a document or between documents. (one deviation is that revision record and table of contents refer to the page numbers). Refere┆
0x02700…02800 (2, 0, 7) Sector 0108ff00007441 ┆ tAnce to a certain part of text thus must be done by chapter, section, etc. number. Hence, if a text entity should be omitted, its index number should be retained and the text replaced by "This chapter (section,....) omitted by revision No. X of (da┆
0x02800…02900 (2, 0, 8) WangDocumentBody
0x02900…02a00 (2, 0, 9) Sector 020aff00008441 ┆ Alinie:, tab p> 3, 16, 20, 24 Side 2 ('Header') 20. Tab p> 20, 65 21. Liniel`ngde 68 22. G> i 'insert'. 23. 6 retur. 24. Tab p> 20 (skriv navn p> m]de) 25. ingen return, start med det samme 26. Tab p> 65, skriv nummertegn for sidenummerering┆
0x02a00…02b00 (2, 0, 10) Sector 020b3200008441 ┆ 2 A. 27. Slut med 7 return. 28. 'execute' 5M 2M[- RA5Cq5:^=~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x02b00…02c00 (2, 0, 11) Sector 0000fb00008441 ┆ { AFormatlinie: tab p> 3, 16, 20, 24 29. Start tekst (ACTION) i pos. 3 30. Tab til 16, tal 31. Indent til 20, tekst p> 24 32. Liniel`ngde p> side 1 (teksten) skal slutte p> 55 33. Efterf]lgende sider m> liniel`ngden kun v`re p> 50 karakterer. ┆
0x02c00…02d00 (2, 0, 12) Sector 020dff00008441 ┆ Axxxxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxxxxxxxxxx xxxxxxxxxxxxx xxxxxxxxxxxxxx xxxxxxxxx┆
0x02d00…02e00 (2, 0, 13) Sector 020eff00008441 ┆ Axxxxxx xxxxxxxxxxxxx 1 STANDARD FOR HOVED TIL MINUTES OF MEETINGS 1. Op i formatlinie. 2. Tabulator p> 3, 13, 16, 20, 27, 30, 45, 52. 3. Liniel`ngde p> 68. 4. 4 retur┆
0x02e00…02f00 (2, 0, 14) Sector 020fff00008441 ┆ A. 5. Tab til 3, skriv f.eks. 'Progress' 6. 1 return. 7. Tab til 30, skriv dato. 8. Tab til 45, skriv nr. 9. Tab til 52, skriv f.eks. 'SHAPE' 10 2 return. 11. Tab. til 13, skriv subject ........... 12. 5 return 13. indent eller tab ┆
0x02f00…03000 (2, 0, 15) Sector 02003300008441 ┆ 3 Atil 3 14. skriv f]rste kolonne med navne. = R<2M/,:g=~ BG2M")M2&! "(=~~ BW2I! <6 M /M?.I*:="8=IM2&MP'Mc2! m"2< [MI !?=6 : #wI>K!8=>R 2!8=6 #4 E*8=k L<M% :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x03000…03100 (3, 0, 0) Sector 0301ff00007441 ┆ tAer the pages are numbered consecutively with an integer t the right of the period. 3.2.3 Amendments a) When a document is revised resulting in an increase in the number of pages, this cannot be added to the end of a chapter (or the entire docum┆
0x03100…03200 (3, 0, 1) Sector 0302ff00007441 ┆ tAent in case of small documents) new pages shall be inserted in their proper place and numbered by lower case letters in addtion to the number of the preceding page. If, for instance, 2 new pages shall be added between pages 7 and 8, the resulting┆
0x03200…03300 (3, 0, 2) Sector 0303ff00007441 ┆ tA numbering shall be: original page 7 new page 7a first additional page - 7b second additional page - 7c b) When a document is revised resulting in a decrease in the number of pages that cannot be removed from t┆
0x03300…03400 (3, 0, 3) Sector 0304ff00007441 ┆ tAhe end of a chapter (or the entire document in case of small documents) a page shall be inserted with the original page number and the following text in the middle of the page: THIS PAGE INTENTIONALLY LEFT BLANK If several consecutive pages ar┆
0x03400…03500 (3, 0, 4) Sector 0305ff00007441 ┆ tAe removed, one page may be used to serve this purpose, numbered with the first and last page number of the removed pages. The above instructions for amendments of page numbering apply to revisions carried out by distributing only a number of the ┆
0x03500…03600 (3, 0, 5) Sector 0306ff00007441 ┆ tApages of which a document exists. When a document is thoroughly revised and distributed as a completely new issue, the page nu`mbering shall be completely revised in accordance with the rules put down in par 3.2.1 and 3.2.2. 3.2.4 References A┆
0x03600…03700 (3, 0, 6) Sector 0307ff00007441 ┆ tAs a consequence of the amendment rules laid down in par 3.2.3 any reference to a page number shall be avoided within a document or between documents. (one deviation is that revision record and table of contents refer to the page numbers). Refere┆
0x03700…03800 (3, 0, 7) Sector 0208ff00007441 ┆ tAnce to a certain part of text thus must be done by chapter, section, etc. number. Hence, if a text entity should be omitted, its index number should be retained and the text replaced by "This chapter (section,....) omitted by revision No. X of (da┆
0x03800…03900 (3, 0, 8) Sector 03099c00009741 ┆ Aions i.e. brief description with reference to the Maintenance manual. 5. Drawings, Illustrations, Photographs, Circuit Diagrams. 6. Parts Lists. T AND CONDUCTION OF TRAINING COURSES The development of the individual courses which make up the ┆
0x03900…03a00 (3, 0, 9) Sector 030aff00009741 ┆ A 1 The handbooks will support operators and maintenance technicians at site and at the same tiem serve the purpose of training documentation. As stated in the previous paragraph the┆
0x03a00…03b00 (3, 0, 10) Sector 030bff00009741 ┆ A editors and technical writers will carry out part of the formal training of customers personnel. 5.4 PLANS AND PROCEDURES The following documentation will be developed. Some of the plans listed below may make reference to subplans and procedur┆
0x03b00…03c00 (3, 0, 11) Sector 030cfa00009741 ┆ z Aed which already are in existance or will be developed under the program. Items identified by (d) are contractally deliverable items. 1. Training Plan (d) 2. Training Methods (d) 3. Training Material (d) 4. Documentation Plan s. On┆
0x03c00…03d00 (3, 0, 12) Sector 00002700009741 ┆ ' A (d) 5. Equipment Handbooks (d) ogramming language may be offered by the programming department of the Electronics Division. Since the maintenance philosophy is based on module replacement no hardware courses on circuit card level is required. In g┆
0x03d00…03e00 (3, 0, 13) Sector 030eff00007441 ┆ tA Text 3.2 PAGE NUMBERING 3.2.1 Small Documents Small documents, i.e. documents originally not exceeding 8 pages, shall be page numbered consecutively with front page as page 1, revision record as page 2 and so on. 3.2.2 Medium size thro┆
0x03e00…03f00 (3, 0, 14) Sector 030fff00007441 ┆ tAugh large documents Documents originally exceeding 8 pages `shall be page numbered according to the following rules: 3.2.2.1 Auxiliary Pages Auxiliary pages, i.e. front page, revision records, and table of contents, are numbered by roman nume┆
0x03f00…04000 (3, 0, 15) Sector 0300ff00007441 ┆ tArals written as lower case letters i, ii, iii, iv, etc. 3.2.2.2 Ordinary text pages Page numbers of ordinary text pages are divided in two parts separated by a period. To the left of the period is used the chapter number. Within each chapt┆
0x04000…04100 (4, 0, 0) WangDocumentBody
0x04100…04200 (4, 0, 1) Sector 00009d00008341 ┆ A ------------------------------------------------------------------------- HAWK/AMC/QAP/001/CRA Software Quality Ass. Plan (HAWK) 0071A 0002A ┆
0x04200…04300 (4, 0, 2) Sector 04031f00008341 ┆ App. Plan 0097A 0005A MB' R*5Cq5M[2 R45Cq5M 2M[- RA5Cq5:^=~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x04300…04400 (4, 0, 3) Sector 0404ff00008341 ┆ A 1 CPS/210/SYS/0001 System Req. Spec. kap. 1 - 3 0062A 0071A 3.1 0052A 0006A 3.2 0063A 0071A 3.2.1 0044A 0071A 3.2.2 0046A 0071A 3┆
0x04400…04500 (4, 0, 4) Sector 0405ff00008341 ┆ A.2.3 0026A 0006A 3.2.4 0038A 0006A 3.2.5 0039A 0071A 3.2.6 0059A 0006A 3.2.7 0042A 0071A 3.2.8 0048A 0006A 3.3 0056A 0071A 3.4 - 3.4.1 0028A 0009A 3.4.2 - 3.4.4 0067A 0071A ┆
0x04500…04600 (4, 0, 5) Sector 0406f400008341 ┆ t A 3.4.5 0051A 0006A 3.5 0055A 0006A 3.6 0060A 0009A 3.7 0068A 0071A 3.7.1 0034A 0009A 3.7.2 0061A 0006A 3.7.4 0045A 0071A 4 4380A 0071A indh.fort. 0066A 0006A tually end ┆
0x04600…04700 (4, 0, 6) Sector 00009d00008341 ┆ A ------------------------------------------------------------------------- HAWK/AMC/QAP/001/CRA Software Quality Ass. Plan (HAWK) 0071A 0002A 335 31 07 80 15 21 31 07 80 16 12 0014A 3 2 10 40 3483 f0! *J 0 _┆
0x04700…04800 (4, 0, 7) Sector 0308ff00009741 ┆ Amation: 1. Equipment Specifications Installation and Commissioning Instructions. 2. Operating instructions i,e, equipment related instructions for various operator categories. 3. Technical Description. 4. Alignment and Maintenance Instruct┆
0x04800…04900 (4, 0, 8) WangDocumentBody
0x04900…04a00 (4, 0, 9) Sector 040aff00008541 ┆ A 1 3.7.1 Verifiable Design The structure of a software unit shall be chosen in a way which makes verification as easy as possible. Structures which cannot be verified must be avoide┆
0x04a00…04b00 (4, 0, 10) Sector 040bab00008541 ┆ + Ad. 3.7.2 Definition of Verification The activities (test, analysis, etc.) which are necessary to verify a unit shall be defined as part of the design activity, s) it shall be a goal to reach as high a cohesion level, and as low a coupling level┆
0x04b00…04c00 (4, 0, 11) Sector 00005e00008541 ┆ ^ Aand the necessary test procedures shall be part of the documentation which are produced. from good to bad and into one of which all modules should fall. 3.4.2.1 Cohesion levels: 1 ┆
0x04c00…04d00 (4, 0, 12) Sector 040dff00009741 ┆ Aly a short course in assembler programming language may be offered by the programming department of the Electronics Division. Since the maintenance philosophy is based on module replacement no hardware courses on circuit card level is required. In g┆
0x04d00…04e00 (4, 0, 13) Sector 040eff00009741 ┆ Aeneral, the Technical Hardware Training Program is a subset of the training offered customer's Resident Field Technicians (see Re 4 below). Re.2. This course will be conducted on Site at Customer's full responsibility. Development of the course ┆
0x04e00…04f00 (4, 0, 14) Sector 040fff00009741 ┆ Amaterial will be carried out by the training section. If software exercises are required to be part of the course, these will be written by the CAMPS software team. Re. 3. This course will provide OJT to both operators and maintenance technician┆
0x04f00…05000 (4, 0, 15) Sector 0400ff00009741 ┆ As. The course will be conducted at site at customer's full responsibility supervised by customer's RST. Course material will be developed by the training section based on the material developed for the formal technical course and operator training c┆
0x05000…05100 (5, 0, 0) WangDocumentBody
[…0x16…]
0x06700…06800 (6, 0, 7) Sector 0508ff00010741 ┆ Asing A/S. The Manual is established in accordance with Configuration Management Plan SD/PLN/006. 1.1 PURPOSE It is the purpose of this manual to describe the rules for Configuration Management and the responsibilities and authority of the Syste┆
0x06800…06900 (6, 0, 8) WangDocumentBody
[…0x2…]
0x06b00…06c00 (6, 0, 11) Sector 060cff00007441 ┆ tA 1 5 TABLE OF CONTENTS 5.1 CONTENT The table of contents shall contain all headers from the document preceded by their indicies. All entries shall be written with same charac┆
0x06c00…06d00 (6, 0, 12) Sector 060dff00007441 ┆ tAters as in text. 5.2 LAYOUT Chapter headings shall be aligned with left margin and be preceeded and succeeded by one blank line. Chapter entries shall be underlined, all other entries shall be written without underlining and indented two charac┆
0x06d00…06e00 (6, 0, 13) Sector 060ec600007441 ┆ F tAter positions for each index level. 5.3 PAGE AND NUMBERS For each entry shall be given the page interval where the text is found. The number table shall be aligned with the right margin. 3.2.1 and 3.2.2. ve integer numbering within each sub┆
0x06e00…06f00 (6, 0, 14) Sector 060f6e00007441 ┆ n tA 1 APPENDIX A FORM SHEETS e of the amendment rules laid down in par. 3.2.3 any reference to a page number shall be avoided within a document or between documents. (One d┆
0x06f00…07000 (6, 0, 15) Sector 00004c00007441 ┆ L tA 1 ge numbers). Reference to a certain part of text thus must be done by chapter, section, etc. number. Hence, if a text entity should be omitted, its index number should be reta┆
0x07000…07100 (7, 0, 0) WangDocumentHead {hdr=WangSectHead {next=( 7,0, 1), len=0xff, h3=41012941}, f00=»0129A «, f01=»Doc Layout Std App B «, f02=»kfl «, f03=»KFL «, f04=»Frabedes venligst!!! «, f05=07-08-80 15:56, f06=» «, f07=»26 «, f08=» 1773 «, f09=07-08-80 16:33, f10=» «, f11=»00 «, f12=» 4 «, f13=07-08-80 16:45, f14=07-08-80 16:48, f15=»0014A «, f16=» 2 «, f17=» «, f18=»26 «, f19=» 28 «, f20=» 1777 «, f21=» «, f22=» «, f99=020010000120056610a10a80aaca15050000000000000037030b00df}
0x07100…07200 (7, 0, 1) WangDocumentBody
[…0x9…]
0x07b00…07c00 (7, 0, 11) Sector 070cff00007441 ┆ tApter (or the entire document in case of small documents) a page shall be inserted with the original page number and the following text in the middle of the page: THIS PAGE INTENTIONALLY LEFT BLANK If several consecutive pages are removed, one ┆
0x07c00…07d00 (7, 0, 12) Sector 070dff00007441 ┆ tApage may be used to serve this purpose, numbered with the first and last page number of the removed pages. The above instructions for amendments of page numbering apply to revisions carried out by distributing only a number of the pages of which ┆
0x07d00…07e00 (7, 0, 13) Sector 070edb00007441 ┆ [ tAa document exists. When a document is thoroughly revised and distributed as a completely new issue, the page numbering shall be completely revised in accordance with the rules put down in par 3.2.1 and 3.2.2. ve integer numbering within each sub┆
0x07e00…07f00 (7, 0, 14) Sector 070fff00007441 ┆ tA 1 3.2.4 References As a consequence of the amendment rules laid down in par. 3.2.3 any reference to a page number shall be avoided within a document or between documents. (One d┆
0x07f00…08000 (7, 0, 15) Sector 0700ff00007441 ┆ tAeviation is that revision record and table of contents refer to the page numbers). Reference to a certain part of text thus must be done by chapter, section, etc. number. Hence, if a text entity should be omitted, its index number should be reta┆
0x08000…08100 (8, 0, 0) WangDocumentBody
[…0x67…]
0x0e800…0e900 (14, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(14,0, 9), len=0xff, h3=41012741}, f00=»0127A «, f01=»CPS sys spec content «, f02=»vhn «, f03=»HKI «, f04=»CPS/SDS/0001 «, f05=06-08-80 11:13, f06=» «, f07=»34 «, f08=» 2743 «, f09=20-08-80 12:13, f10=» «, f11=»22 «, f12=» 198 «, f13=08-08-80 12:24, f14=04-11-80 13:33, f15=»0014A «, f16=» 5 «, f17=» 1 «, f18=»30 «, f19=» 80 «, f20=» 5884 «, f21=» «, f22=» «, f99=020030000120056650a10a80aaca15050000000000000037031b00df}
0x0e900…0ea00 (14, 0, 9) WangDocumentBody
[…0x6…]
0x0f000…0f100 (15, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(15,0, 1), len=0xff, h3=41012041}, f00=»0120A «, f01=»Problem Hdl. std. «, f02=»vhn «, f03=»SVO «, f04=»SD/STD/007 «, f05=31-07-80 12:44, f06=» 1 «, f07=»17 «, f08=» 4133 «, f09=21-11-80 09:10, f10=» «, f11=»01 «, f12=» 28 «, f13=21-11-80 09:47, f14=21-11-80 10:05, f15=»0014A «, f16=» 5 «, f17=» 2 «, f18=»01 «, f19=» 76 «, f20=» 4818 «, f21=» «, f22=» «, f99=020030000120056610a10a80aaca15050000000000000037031900df}
0x0f100…0f200 (15, 0, 1) WangDocumentBody
[…0x16…]
0x10800…10900 (16, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(16,0, 9), len=0xff, h3=41013441}, f00=»0134A «, f01=»Software Doc. Std. «, f02=»kk «, f03=»SVO «, f04=»SD/STD/008 «, f05=14-08-80 11:20, f06=» 3 «, f07=»00 «, f08=» 5069 «, f09=22-04-81 09:38, f10=» «, f11=»05 «, f12=» 54 «, f13=25-11-80 09:31, f14=22-04-81 09:44, f15=»0014A «, f16=» 6 «, f17=» 12 «, f18=»05 «, f19=» 96 «, f20=» 35187 «, f21=» «, f22=» «, f99=020030000120056610a10a80aaca15050000000000000030032000df}
0x10900…10a00 (16, 0, 9) WangDocumentBody
[…0x12…]
0x11c00…11d00 (17, 0, 12) Sector 110d2400013341 ┆ $ 3Alarify scope of the question. Flyt positions-viser Funktion annulleret Ukendt kommando JA eller ANNULLER Kun tal Kun mellemrum eller retur Under redigering nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x11d00…11e00 (17, 0, 13) Sector 110eff00013341 ┆ 3A 1 A13 Desirability for supervisory and maintenance position powered thru shielded cage. - Installation point-of-view: can be done, but is not desirable. ARC - please clarify sc┆
0x11e00…11f00 (17, 0, 14) Sector 110fff00013341 ┆ 3Aope of question A14 Air conditioning capacity, necessary air flow, permissable static pressure drop in ducts, location of thermostat. - see question A11 - CR responsibility: to supply information on the equipment: heat generation, details on ┆
0x11f00…12000 (17, 0, 15) Sector 1100ff00013341 ┆ 3Athe cage. Customer responsibility: Design and installation of air condition. ARC - Please clarify scope of question A15 Power requirement, permissable deregulation of mains voltage, peak (not rms) load current. CR - CR will supply informatio┆
0x12000…12100 (18, 0, 0) WangDocumentBody
[…0xf…]
0x13000…13100 (19, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(19,0, 1), len=0xff, h3=41010841}, f00=»0108A «, f01=»[velse flet «, f02=»vhn/am] «, f03=»am] «, f04=»ans]gningsstandard «, f05=29-07-80 09:56, f06=» «, f07=»33 «, f08=» 463 «, f09=15-08-80 11:21, f10=» «, f11=»00 «, f12=» 4 «, f13=15-08-80 11:04, f14=15-08-80 13:21, f15=»0014A «, f16=» 1 «, f17=» 1 «, f18=»05 «, f19=» 4 «, f20=» 652 «, f21=» «, f22=» «, f99=990010000120056610a10a11aaca15050000000000000037030400df}
0x13100…13200 (19, 0, 1) WangDocumentBody
[…0x2…]
0x13400…13500 (19, 0, 4) Sector 00008b00010841 ┆ A . S>fremt tidspunktet er ubelejligt for Dem, bedes De kontakte p> lokalnummmer . Med venlig hilsen CHRISTIAN ROVSING A/S :g=~ J /Mj'! "(=~ R*/!/=6jM (*(=~ R;/!/=6nM (*(=~ RM/!/=6iM (*(=~ R`/!/=6WM (*(=~ Rt/!/=6lM (*(=~ R ┆
0x13500…13600 (19, 0, 5) Sector 00000000000000 ┆ ┆
[…0x2…]
0x13800…13900 (19, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(19,0, 9), len=0xff, h3=41010941}, f00=»0109A «, f01=»variabel til 0108A «, f02=»vhn/am] «, f03=»am] «, f04=»Ans]gningsstandard «, f05=29-07-80 10:31, f06=» «, f07=»04 «, f08=» 156 «, f09=15-08-80 10:52, f10=» «, f11=»01 «, f12=» 2 «, f13=29-07-80 12:37, f14=15-08-80 13:21, f15=»0014A «, f16=» 1 «, f17=» «, f18=»05 «, f19=» «, f20=» 158 «, f21=» «, f22=» «, f99=020010000120056610a10a11aaca15050000000000000037030300df}
0x13900…13a00 (19, 0, 9) WangDocumentBody
[…0x1…]
0x13b00…13c00 (19, 0, 11) Sector 00000000000000 ┆ ┆
[…0x4…]
0x14000…14100 (20, 0, 0) WangDocumentBody
[…0x47…]
0x18800…18900 (24, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(24,0, 9), len=0xff, h3=41012641}, f00=»0126A «, f01=»Inst. for Doc. Cont. Cent «, f02=»vhn «, f03=»KFL «, f04=»SD/AUX/001 «, f05=06-08-80 10:37, f06=» 2 «, f07=»02 «, f08=» 8755 «, f09=19-09-80 12:23, f10=» «, f11=»01 «, f12=» 6 «, f13=19-09-80 12:25, f14=19-09-80 12:51, f15=»0014A «, f16=» 9 «, f17=» 2 «, f18=»57 «, f19=» 148 «, f20=» 10473 «, f21=» «, f22=» «, f99=990030000120056610a10a80aaca15050000000000000037033000df}
0x18900…18a00 (24, 0, 9) WangDocumentBody
[…0x36…]
0x1c000…1c100 (28, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(28,0, 1), len=0xff, h3=41015141}, f00=»0151A «, f01=»SOFTWARE DOC. STANDARD «, f02=»vhn «, f03=»SVO «, f04=»APPENDIX B «, f05=25-08-80 11:13, f06=» «, f07=»11 «, f08=» 193 «, f09=25-08-80 13:44, f10=» «, f11=»01 «, f12=» 19 «, f13=25-11-80 11:19, f14=25-11-80 12:16, f15=»0014A «, f16=» 23 «, f17=» «, f18=»12 «, f19=» 172 «, f20=» 212 «, f21=» «, f22=» «, f99=020010000120056610a10a80aaca15050000000000000037034400df}
0x1c100…1c200 (28, 0, 1) WangDocumentBody
[…0x3e…]
0x20000…20100 (32, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(32,0, 1), len=0xff, h3=41015241}, f00=»0152A «, f01=»SOFTWARE DOC. STANDARD «, f02=»vhn «, f03=»SVO «, f04=»APPENDIX A «, f05=25-08-80 14:57, f06=» «, f07=»06 «, f08=» 181 «, f09=21-10-80 13:55, f10=» «, f11=»00 «, f12=» 2 «, f13=25-11-80 11:34, f14=25-11-80 12:17, f15=»0014A «, f16=» 12 «, f17=» «, f18=»23 «, f19=» 200 «, f20=» 449 «, f21=» «, f22=» «, f99=020010000120056610a10a80aaca15050000000000000037034000df}
0x20100…20200 (32, 0, 1) WangDocumentBody
[…0x9…]
0x20b00…20c00 (32, 0, 11) Sector 200cff00013241 ┆ 2Abe accomplished will be evaluated. 1.6.12 Elements of maintainability program plans shall be analysed to determine that each task has been initiated towards achieving specified requirements. 1.6.13 Considerations will be given to optimizing the sy┆
0x20c00…20d00 (32, 0, 12) Sector 200dff00013241 ┆ 2Astem from maintainability and maintenance viewpoint and that it is supportable within the maintenance concept as developed. 1.6.14 The model, analyses and calculations shall be refined and changed as necessary, as system design progresses. ┆
0x20d00…20e00 (32, 0, 13) Sector 200e0700013241 ┆ 2A ements. 1.5.11 Identify planned actions when predictions are less than specicified requirements. 1.5.12 Review margins of safety between functional requirements and design provisions for elements, i.e. power supplies. Similarly review structura┆
0x20e00…20f00 (32, 0, 14) Sector 200fff00013241 ┆ 2A 1 R & M PLAN SECTION 1.2 Two failure modes are evaluated for each component and for each functional block (module). 1) The part is short-circuited 2) The part is open-circuite┆
0x20f00…21000 (32, 0, 15) Sector 2000ff00013241 ┆ 2Ad. The failures are subdivided in three categories 1) Catastrophic i.e. failure that are both sudden and complete 2) Critical i.e. failure that causes loss of a unit 3) non critical failures which are divided in major and minor break down. ┆
0x21000…21100 (33, 0, 0) WangDocumentBody
[…0x7…]
0x21800…21900 (33, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(33,0, 9), len=0xff, h3=41015541}, f00=»0155A «, f01=»Software Doc. Std. «, f02=»vhn «, f03=»SVO «, f04=»Appendix D «, f05=26-08-80 13:50, f06=» «, f07=»15 «, f08=» 1665 «, f09=28-10-80 10:06, f10=» «, f11=»00 «, f12=» 20 «, f13=25-11-80 12:13, f14=25-11-80 12:17, f15=»0014A «, f16=» 2 «, f17=» «, f18=»19 «, f19=» 28 «, f20=» 1711 «, f21=» «, f22=» «, f99=020010000120056610a10a80aaca15050000000000000037030b00df}
0x21900…21a00 (33, 0, 9) WangDocumentBody
[…0x6…]
0x22000…22100 (34, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(34,0, 1), len=0xff, h3=41007441}, f00=»0074A «, f01=»Doc. Layout Standard «, f02=»kk «, f03=»SVO «, f04=»1. Scope and purp. «, f05=19-06-80 10:31, f06=» 5 «, f07=»06 «, f08=» 16925 «, f09=12-01-81 09:52, f10=» «, f11=»00 «, f12=» 4 «, f13=12-01-81 10:04, f14=13-01-81 09:45, f15=»0014A «, f16=» 18 «, f17=» 8 «, f18=»00 «, f19=» 208 «, f20=» 19887 «, f21=» «, f22=» «, f99=020030000120056610a10a80aaca94050000000000000037034800df}
0x22100…22200 (34, 0, 1) WangDocumentBody
[…0x1e…]
0x24000…24100 (36, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(36,0, 1), len=0xff, h3=41008541}, f00=»0085A «, f01=»Software. design guidel. «, f02=»vhn «, f03=»SVO «, f04=»SD/STD/005 «, f05=04-06-80 09:23, f06=» 3 «, f07=»10 «, f08=» 8823 «, f09=10-06-81 15:06, f10=» «, f11=»01 «, f12=» 14 «, f13=10-06-81 15:08, f14=19-06-81 11:18, f15=»0014A «, f16=» 16 «, f17=» 10 «, f18=»05 «, f19=» 296 «, f20=» 25417 «, f21=» «, f22=» «, f99=020010000120056610110480aaca15050000000000000030035900df}
0x24100…24200 (36, 0, 1) WangDocumentBody
[…0x6…]
0x24800…24900 (36, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(36,0, 9), len=0xff, h3=41013341}, f00=»0133A «, f01=»ARC Report «, f02=»kk «, f03=»BHB «, f04=»No. 52-7234 «, f05=14-08-80 08:35, f06=» 1 «, f07=»48 «, f08=» 6974 «, f09=14-08-80 11:05, f10=» «, f11=»11 «, f12=» 113 «, f13=14-08-80 11:16, f14=14-08-80 16:08, f15=»0014A «, f16=» 6 «, f17=» 1 «, f18=»59 «, f19=» 120 «, f20=» 7087 «, f21=» «, f22=» «, f99=020010000120056610a10a80aaca15050000000000000030032200df}
0x24900…24a00 (36, 0, 9) Sector 240a0600013341 ┆$ 3A $ $ $ $ # # # DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / ┆
0x24a00…24b00 (36, 0, 10) Sector 240bae00013341 ┆$ . 3A 1 1980-08-08 page # ANSWER AND COMMENTS TO CONFERENCE REPORT NO. 1, ARC NO. 52-7234 =MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x24b00…24c00 (36, 0, 11) Sector 240cff00013341 ┆$ 3A 1 Appendices show design details and are referenced in the following. A. Preliminary Planning for Shield Cage Specifications Action A1 Maximum outside dimensions. - See A┆
0x24c00…24d00 (36, 0, 12) Sector 240dff00013341 ┆$ 3App. 6, sketches No. 5. - Max. volume: 5 x 3.7 x 2.5 (height) m 3 A2 Presence of obstructions. - No A3 Unevenness or out-of-level floors. - Max. unevenness within cage floor area: 30 mm. A4 Presence of floor drains under shield cage. ┆
0x24d00…24e00 (36, 0, 13) Sector 240eff00013341 ┆$ 3A - No A5 Dampness of location - "Normal computer environment" - humidity: 40 - 90% RH. A6 Prospect for water dripping onto shield cage roof. - No. A7 Clearance thru hallways for largest shield cage item. - Access dimensions are equa┆
0x24e00…24f00 (36, 0, 14) Sector 240faf00013341 ┆$ / 3Al or better than: Height: 1.70 m Width: 0.65 m Length: 3.70 m This has been confirmed on visiting by site surveys. ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x24f00…25000 (36, 0, 15) Sector 2400ff00013341 ┆$ 3A 1 A8 Proximity to secure area perimeter, to include electrical or telephone cables in area. ARC - Please clarify scope of this question. A9 Proximity to secure area perimeter an┆
0x25000…25100 (37, 0, 0) Sector 25019200008541 ┆% Adecision points enclosed. The transformation in question may be any which can be translated into a short piece of purely sequential code. e with other units f) produces documentation of the unit g) defines input to and output from the unit h┆
0x25100…25200 (37, 0, 1) Sector 2502ff00008541 ┆% A 1 c) Simple compound processes. Compound processes will be such which are composed of two or more of the above defined strictly elementary processes. A simple compound process ma┆
0x25200…25300 (37, 0, 2) Sector 2503ff00008541 ┆% Ay be considered elementary and thus needs no further breakdown in the design provided: - it contains only a few elements - it have low complexity - it has only one entry and one exit - it handles only one elementary data item. The docume┆
0x25300…25400 (37, 0, 3) Sector 2504ff00008541 ┆% Antation resulting from the design shall contain descriptions of all elementary processes in plain language. This description shall be phrased in such a way that a programmer can understand it and translate it into code without difficulty. Furthe┆
0x25400…25500 (37, 0, 4) Sector 2505ff00008541 ┆% Ar, the description shall fit into the source code as a comment to the code performing the process. In all diagrams (HIPO and flowgrams) the elementary processes shall be represented with each one entry. 3.4 STRUCTURED DESIGN 3.4.1 Control S┆
0x25500…25600 (37, 0, 5) Sector 2506ff00008541 ┆% Atructures When defining the control flow within a software module the principles known as "Structured Design" shall be applied. These principles prescribe that the control flow must be a combination of only 3 simple control flow structures a) ┆
0x25600…25700 (37, 0, 6) Sector 25077800008541 ┆% x ASequence b) Loop c) Branching (IF THEN ELSE or CASE) Fig 2 shows the flow charts describing those structure. hich are to be coded as separate code units and the description of those units must be detailed enough to be used as direct input for c┆
0x25700…25800 (37, 0, 7) Sector 19005b00008541 ┆ [ A 1 fig 2. he branches meet. No interaction is allowed at lower levels. 3.3.2 Level by Level Documentation Each unit shall be designed as an independent entity. The onl┆
0x25800…25900 (37, 0, 8) Sector 2509ff00008541 ┆% Ay input which shall be necessary to design a unit shall be the documentation of its parent unit and its ancestors. The design of a unit must therefore result in a documentation which can serve as such input to the design of the units of the next low┆
0x25900…25a00 (37, 0, 9) Sector 250a1100008541 ┆% Aer level. ifiable Design .................... 18 3.7.2 Definition of Verification ........... 18 1 (=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x25a00…25b00 (37, 0, 10) Sector 250b5c00008541 ┆% \ A 1 fig. 1 standard is a derivative of software standard manual SD/STM/003 and has the same scope and applicability. 2 PURPOSE The purpose of this standard is┆
0x25b00…25c00 (37, 0, 11) Sector 250cff00008541 ┆% A 1 The documentation of a unit shall be able to answer the following questions in a clear and unambiguous way: a) what am I part of b) what am I c) who do I interact with (and how┆
0x25c00…25d00 (37, 0, 12) Sector 250dff00008541 ┆% A) d) what do I consist of 3.3.3 Final Documentation The final software documentation may be organized in only a few levels (1 to 3 typically) for practical reasons. This shall not limit the design break down to the same low number of levels, i┆
0x25d00…25e00 (37, 0, 13) Sector 250eff00008541 ┆% Anstead several levels of design breakdown shall be fitted into each documentation level. 3.3.4 Elementary Processes The Top down breakdown shall eventually lead to a breakdown of the system into elementary processes. Elementary processes can ┆
0x25e00…25f00 (37, 0, 14) Sector 250fff00008541 ┆% Abe of 3 types: a) Decisive processes: A process containing one single decision point with the associated examination of a data item. A decisive process may when coding be translated into - an if-then-else construct - the control of a lo┆
0x25f00…26000 (37, 0, 15) Sector 2500ff00008541 ┆% Aop - a case construct. b) Data handling processes. A process which performs some kind of transformation on an elementary data item (an elementary data item in this context is a single ... or a group of closely related data items) without any ┆
0x26000…26100 (38, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(38,0, 1), len=0xff, h3=41013541}, f00=»0135A «, f01=»Ans]gningssvar «, f02=»kk «, f03=»kk «, f04=»Bruges som standard «, f05=15-08-80 11:05, f06=» 1 «, f07=»00 «, f08=» 572 «, f09=15-08-80 12:38, f10=» «, f11=»01 «, f12=» 10 «, f13=15-08-80 12:39, f14=15-08-80 13:21, f15=»0014A «, f16=» 1 «, f17=» 1 «, f18=»03 «, f19=» 4 «, f20=» 621 «, f21=» «, f22=» «, f99=990010000120056610a10a11aaca15050000000000000037030400df}
0x26100…26200 (38, 0, 1) Sector 26020100013541 ┆& 5A & DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S┆
0x26200…26300 (38, 0, 2) Sector 2603a200013541 ┆& " 5A 1 W *-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x26300…26400 (38, 0, 3) Sector 0000b100013541 ┆ 1 5AVedr.: Deres ans]gning om ans`ttelse i vort selskab Vi har modtaget Deres ans]gning af og vender tilbage snarest muligt. Med venlig hilsen CHRISTIAN ROVSING A/S .> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x26400…26500 (38, 0, 4) Sector 00000000000000 ┆ ┆
[…0x3…]
0x26800…26900 (38, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(38,0, 9), len=0xff, h3=41013641}, f00=»0136A «, f01=»Oplysning til dok. 135A «, f02=»kk «, f03=»kk «, f04=» «, f05=15-08-80 11:15, f06=» «, f07=»13 «, f08=» 263 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13= - - : , f14=15-08-80 13:21, f15=»0014A «, f16=» 1 «, f17=» «, f18=»13 «, f19=» 4 «, f20=» 263 «, f21=» «, f22=» «, f99=020010000120056610a10a80aaca15050000000000000037030400df}
0x26900…26a00 (38, 0, 9) Sector 260a0100013641 ┆& 6A & DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S┆
0x26a00…26b00 (38, 0, 10) Sector 260bb100013641 ┆& 1 6A 1 Fr. Gina Dorning R`veskovsvej 24 2820 Gentofte 15. august 1980 AM[/kk 13. august 1980 Anne Marie [rum , > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x26b00…26c00 (38, 0, 11) Sector 00006d00013641 ┆ m 6A Birthe Wunsche Skandrups All} 22 3500 V`rl]se 15. august 1980 AM[/kk 14. august 1980 Anne Marie [rum )-MI,:^=~ B~.> IMB'IM2& 9x2"<!Z="(=^#Vk"$<:]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x26c00…26d00 (38, 0, 12) Sector 00000000000000 ┆ ┆
[…0x3…]
0x27000…27100 (39, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(39,0, 1), len=0xff, h3=41008341}, f00=»0083A «, f01=»Oversigt over dokumenter «, f02=»rt «, f03=»KFL «, f04=»SD/DOC/001 «, f05=01-07-80 12:47, f06=» «, f07=»25 «, f08=» 813 «, f09=26-08-80 13:08, f10=» «, f11=»11 «, f12=» 228 «, f13=18-08-80 13:15, f14=26-08-80 13:20, f15=»0014A «, f16=» 4 «, f17=» 2 «, f18=»44 «, f19=» 60 «, f20=» 4622 «, f21=» «, f22=» «, f99=020010000120056630a10a80aaca15050000000000000030031100df}
0x27100…27200 (39, 0, 1) WangDocumentBody
[…0x6…]
0x27800…27900 (39, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(39,0, 9), len=0xff, h3=41013741}, f00=»0137A «, f01=»CR CAMPS TEAM «, f02=»kk «, f03=»OWE «, f04=»ingen «, f05=15-08-80 12:41, f06=» «, f07=»25 «, f08=» 1272 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13=15-08-80 13:09, f14=15-08-80 13:21, f15=»0014A «, f16=» 2 «, f17=» «, f18=»25 «, f19=» 20 «, f20=» 1272 «, f21=» «, f22=» «, f99=020010000120056610a10a80aaca15050000000000000037030800df}
0x27900…27a00 (39, 0, 9) Sector 270a0200013741 ┆' 7A ' ' ' DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : ┆
0x27a00…27b00 (39, 0, 10) Sector 270b8d00013741 ┆' 7A 1 OWE/19800815 # CR CAMPS TEAM CAMPS /=6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x27b00…27c00 (39, 0, 11) Sector 270cff00013741 ┆' 7A 1 Extension PROGRAM MANAGEMENT Program Manager Mr. Lars Stig Nielsen 131 Deputy Prog. Manager Mr. Gert Jensen 192 Contracts Manager Mr. Kim Hjorth 145 Contract Admin┆
0x27c00…27d00 (39, 0, 12) Sector 270dff00013741 ┆' 7Aistrator Mr. Boje Rinhart 146 QUALITY ASSURANCE Quality Assurance Manager Mr. Svend Olsen 285 SYSTEM ENGINEERING Principle Systems Engineer Mr. Jens Peter Ringgaard 193 System Engineering Manager Mr. Kurt Nybroe-Nielsen 194 HARDWARE DEVE┆
0x27d00…27e00 (39, 0, 13) Sector 270e7d00013741 ┆' } 7ALOPMENT Hardware Manager Mr. Bjarne Berthold 272 SOFTWARE DEVELOPMENT Software Manager Mr. Gert Jensen 192 0! <6 M1' R 0C 0! <6 M1' Z 0CR0Mc&!.=6 ! <6 M1' R40C.1! <6 M1' RC0C.1! <6 M1' RR0C.1!$<5CQ0!$<6 !&<6 Mc&! "(=6 E '<M% ! "2<┆
0x27e00…27f00 (39, 0, 14) Sector 270fbe00013741 ┆' > 7A 1 LOGISTICS DEPARTMENT Department Manager Mr. Ole W. Eskedal 178 - Installation Mr. Kurt Mikkelsen 175 - M {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x27f00…28000 (39, 0, 15) Sector 0000e500013741 ┆ e 7Aaintenance Mr. Finn Caspersen - Training and Manuals Mr. Ole W. Eskedal (acting) 178 Address: Christian Rovsing A/S Lautrupvang 2 DK-2750 Ballerup Danmark Phone: 02-65 11 44 Telegram: Datateknik Telex: 35111 cr dk.Rl2> IC13!?=4~~ B|2> I:A=!┆
0x28000…28100 (40, 0, 0) Sector 2801c800013441 ┆( H 4Ais shown in fig. 1. In this chart each partial process is represented by a box containing a descriptive title of the process and a reference to the paragraph in which it is further described. .. 1 D.3 CHARACTER LEVEL DIAGRAMS .................┆
0x28100…28200 (40, 0, 1) Sector 2802ff00013441 ┆( 4A 1 4.2 INPUT - PROCESS - OUTPUT CHARTS For each of the partial processes defined in the overview chart shall be produced a chart showing the relation between the inputs, the outputs,┆
0x28200…28300 (40, 0, 2) Sector 2803ff00013441 ┆( 4A and the subprocesses within the process. The standard for those charts are shown in Appendix B which is an extract from IBM's HIPO manual. Note that the following restriction to the normal HIPO concept must be adhered to: - The process box sh┆
0x28300…28400 (40, 0, 3) Sector 2804ff00013441 ┆( 4Aall only contain a listing of the subprocesses, ordered as closely as possible to the sequence in which they will be performed. - No attempt shall be made to show the logic relation or control flow between subprocesses. 4.3 FLOWGRAMS For each┆
0x28400…28500 (40, 0, 4) Sector 2805ff00013441 ┆( 4A of the partial processes defined in the overview chart shall be produced a flowgram showing the logical interrelation between the subprocesses. These flowgrams shall be produced in accordance with the rules given in Appendix C. (In preliminary i┆
0x28500…28600 (40, 0, 5) Sector 2806ff00013441 ┆( 4Assue is used an offprint of an article in Electronic design). 4.4 DATA CHARTS In the sections of specification containing data descriptions, this is mainly section 3b Interfaces 3c Storage 4b Inputs ┆
0x28600…28700 (40, 0, 6) Sector 2807d700013441 ┆( W 4A 4c Outputs shall be used Data Charts to show the layout of data items of any complexity higher than single words or simple arrays. These Data Charts shall have a format as shown in Appendix D. absolutely necessary. *J 0 _┆
0x28700…28800 (40, 0, 7) Sector 00004a00013441 ┆ J 4A 1 3.2 LAYOUT The editorial style of all documents shall be as described in Document Layout Standard SD/STD/002. 3.3 CONTENT The main content of all parts of the specification s┆
0x28800…28900 (40, 0, 8) Sector 2809ff00013441 ┆( 4Ahall be narrative descriptions written in plain English language. 3.3.1 Language Style The paramount consideraion in a specification is its technical essence, and this should be presented in a language free of vague and ambiquous terms and usin┆
0x28900…28a00 (40, 0, 9) Sector 280aff00013441 ┆( 4Ag the simplest words and phrases which convey the intended meaning. Inclusion of essential information shall be complete, either by direct statements or by reference to other documents. Consistency in terminology and organization of material will ┆
0x28a00…28b00 (40, 0, 10) Sector 280bff00013441 ┆( 4Acontribute to the specification's clarity and usefulness. Sentences shall be as short and concise as possible. Punctuation should aid in reading and prevent misreading. Well-planned word order requires a minimum of punctuation. When extensive pu┆
0x28b00…28c00 (40, 0, 11) Sector 280cff00013441 ┆( 4Anctuation is necessary for clarity, the sentence(s) shall be rewritten. Sentences with compound clauses shall be converted into short and concise separate sentences. 3.3.2 Diagrams A series of diagramtic aids shall be used extensively to enhan┆
0x28c00…28d00 (40, 0, 12) Sector 280dff00013441 ┆( 4Ace the understandability of the text. These aids, their form and use will be described in detail in chapter 4. Note that although diagrams in some cases may constitute the major part of a section they shall still be considered an aid for the text┆
0x28d00…28e00 (40, 0, 13) Sector 280e2600013441 ┆( & 4A and never a replacement of it. .. 5 3.3.1 Language Style ....................... 5 4 DIAGRAMS ..................................... 6 4.1 HIERARCHICAL OVERVIEW CHART .............. 6 4.2 INPUT - PROCESS - OUTPUT CHARTS .......... ┆
0x28e00…28f00 (40, 0, 14) Sector 280fff00013441 ┆( 4A 1 4 DIAGRAMS 4.1 HIERARCHICAL OVERVIEW CHART A major point in describing the processing of a software module is the breakdown of the processing into subprocesses which again┆
0x28f00…29000 (40, 0, 15) Sector 2800ff00013441 ┆( 4A may be broken down into sub-subprocesses through several levels. To describe the interrelationship between the partial processes and define their level in the breakdown hierarchy an overview chart shall be used. An example of an overview chart ┆
0x29000…29100 (41, 0, 0) Sector 29018300014141 ┆) AA 1 Fig. 6.1 p 6 The team leader will use one or two days for inspection of remote terminals and remote TARE locations depending of the ┆
0x29100…29200 (41, 0, 1) Sector 2902ff00014141 ┆) AA 1 6.6 DOCUMENTATION The installation team is responsible for installation of the equipment in accordance with the As-To-Be-Built drawings. A copy of the A-T-B-B drawings will be m┆
0x29200…29300 (41, 0, 2) Sector 2903ff00014141 ┆) AAarked up during the installation to reflect deviations, if any. A log book will follow the system from start of integration at factory throughout the lifetime of the system. All activities during the installation phase will be recorded in the log┆
0x29300…29400 (41, 0, 3) Sector 2904ff00014141 ┆) AAbook with the date of completion. The logbook will remain at site after installation and the recording will be continued by the test team performing site acceptance test. Any inspections such as quality assurance inspection, ACE COMSEC inspection┆
0x29400…29500 (41, 0, 4) Sector 29058c00014141 ┆) AAs should be recorded in the log book. After site provisional acceptance (PSA) the site will be responsible for keeping the logbook. typical CAMPS site is approx. 100. Step 9,10 The user terminals (up to 24) are to be installed in different room┆
0x29500…29600 (41, 0, 5) Sector 00003d00014141 ┆ = AA 1 s) are already installed by Host Nation. The cables are to be terminated and connected to the user terminals. Close to each terminal location a power outlet and a secure ground connection ┆
0x29600…29700 (41, 0, 6) Sector 2907ff00014141 ┆) AAhe CAMPS room is 15 connected to power, modules are unpacked and mounted, and the test of hardware is started. step 16 When the hardware at a mainsite is functioning a final hardware test is performed at the remote location. step 17 An inv┆
0x29700…29800 (41, 0, 7) Sector 2508ff00014141 ┆% AAentory check is carried out at the completion of installation with representatives from the site and or SHAPE. The inventory check shall prove that the equipment is delivered and installed in accordance with the inventory list and the as-to-be-buil┆
0x29800…29900 (41, 0, 8) Sector 29093500014141 ┆) 5 AA terminals has been used for this evaluation. 6.3 SHIPMENT OF EQUIPMENT CR intends to schedule the shipment of CAMPS so that the installation team will be present at site to receive the equipment. In order to take into account any slippages┆
0x29900…29a00 (41, 0, 9) Sector 290aff00014141 ┆) AA 1 The installation task at a Remote TARE location will consist of the installation of 1 rack plus 1 modem; because of the considerable distance to some of the Remote TARE location┆
0x29a00…29b00 (41, 0, 10) Sector 290bff00014141 ┆) AA it might be necessary to use extra manpower for the installation. At both locations equipment is installed and the hardware tested. Final test can first be performed when the mainsite equipment is functioning. step 13, 14 The equipment in t┆
0x29b00…29c00 (41, 0, 11) Sector 290cff00014141 ┆) AAhe CAMPS room is 15 connected to power, modules are unpacked and mounted, and the test of hardware is started. step 16 When the hardware at a mainsite is functioning a final hardware test is performed at the remote location. step 17 An inv┆
0x29c00…29d00 (41, 0, 12) Sector 290dff00014141 ┆) AAentory check is carried out at the completion of installation with representatives from the site and or SHAPE. The inventory check shall prove that the equipment is delivered and installed in accordance with the inventory list and the as-to-be-buil┆
0x29d00…29e00 (41, 0, 13) Sector 290eff00014141 ┆) AAt drawings. step 18 A nucleus test (subset of the factory acceptance test is performed to verify that all hardware is functioning. A test procedure for this nucleus test will be prepared. The test is regarded as an informal test to prove t┆
0x29e00…29f00 (41, 0, 14) Sector 290fff00014141 ┆) AAhat installation is completed, and that the site is ready to be taken over by CR's test team. The test results will be recorded in the log book. The test team will arrive to site when installation is completed to perform the site adaptation in soft┆
0x29f00…2a000 (41, 0, 15) Sector 29004600014141 ┆) F AAware and to conduct the site provisional acceptance test (SPA). site officials, make all necessary arrangements, inspect the installation areas and move in. A checklist will be prepared for the inspection. Step 5 Before any equipment is brought┆
0x2a000…2a100 (42, 0, 0) Sector 2a01ff00014141 ┆* AA into the CAMPS room the signal cables must be installed. Cable ducts will already have been installed by Host Nation. Step 6 The team leader will use one or two days for inspection of remote terminals and remote TARE locations depending of the ┆
0x2a100…2a200 (42, 0, 1) Sector 2a024b00014141 ┆* K AAtravel distance. A checklist will be prepared for the inspections. .6 SITE VERIFICATION CR will perform a verification of each site prior to installation. The verification shall prove that the site is ready for installation of the CAMPS equipm┆
0x2a200…2a300 (42, 0, 2) Sector 2a03ff00014141 ┆* AA 1 Step 7 Racks, terminal equipment and furniture is unpacked, and moved to the CAMPS and CRYPTO-room. Since the access routes on the majority of sites are long and on some part of ┆
0x2a300…2a400 (42, 0, 3) Sector 2a04ff00014141 ┆* AAthe route extremely narrow it will be impossible to move more than two racks per day. Assistance from the site will be needed to this job in form of trolleys and manpower. The availability of assistance has been investigated during the site survey┆
0x2a400…2a500 (42, 0, 4) Sector 2a05ff00014141 ┆* AAs and recorded in the site survey report. Step 8 The signal cables is to be terminated and connected. The quantity of cables for a typical CAMPS site is approx. 100. Step 9,10 The user terminals (up to 24) are to be installed in different room┆
0x2a500…2a600 (42, 0, 5) Sector 2a06ff00014141 ┆* AAs located all over the site. The cables (optical fibres) are already installed by Host Nation. The cables are to be terminated and connected to the user terminals. Close to each terminal location a power outlet and a secure ground connection ┆
0x2a600…2a700 (42, 0, 6) Sector 2a07ff00014141 ┆* AApoint has been installed by Host Nation. Step 11,12 Both the Remote Terminal installations and Remote Tares are considered here. The installation task concerning Remote Terminals will vary from site to site, because of the number of remote te┆
0x2a700…2a800 (42, 0, 7) Sector 2908ff00014141 ┆) AArminal locations connected to a main site. The installation effort of remote terminals is, therefore, to be analyzed site by site in connection with the analysis of each main site. A typical remote terminal installation consisting of 1 rack plus 5┆
0x2a800…2a900 (42, 0, 8) Sector 2a09ff00013441 ┆* 4A........ 5 B.4 PROCESS SECTION .......................... 17 APPENDIX C APPENDIX D D.1 BIT LEVEL DIAGRAMS ....................... 1 D.2 WORD LEVEL DIAGRAMS ...................... 1 D.3 CHARACTER LEVEL DIAGRAMS .................┆
0x2a900…2aa00 (42, 0, 9) Sector 2a0a0a00013441 ┆* 4A 2 '4:"<~ B 4C#4*.;:i=>B#4IM?.IM?. MD ! m":="<=!;=4!A=6A:g= RK4Cg4:^=~ BV4C75:g=~ Bf4 ZMo Ck4 KMo Mj ~ B 4:g=~ J 4Cq5M")IMy,M1' R 4 'M, CV4:g=~ Bg4M73~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x2aa00…2ab00 (42, 0, 10) Sector 2a0bff00013441 ┆* 4A 1 1 SCOPE This standard is a derivative of software standard man- ual SD/STM/003 and has the same scope and applicability. 2 PURPOSE This standard describes the organi┆
0x2ab00…2ac00 (42, 0, 11) Sector 2a0cff00013441 ┆* 4Asation and layout to be used for documents containing specification of Software units of module or lower levels (see system design guideline for definition of module level). 3 ORGANISATION 3.1 SYNOPSIS The content of Software module s┆
0x2ac00…2ad00 (42, 0, 12) Sector 2a0dff00013441 ┆* 4Apecifications shall be organized as described in NATO's ADP standard 007-3 annex D. This standard is found as Appendix A 3.1.2 Tayloring of Synopsis Software modules may vary considerably in size, complexity and content, therefore, this synops┆
0x2ad00…2ae00 (42, 0, 13) Sector 2a0eff00013441 ┆* 4Ais may need some tayloring to adapt it to the actual case. Some of the paragraphs in the synopsis may be redundant as no information exists which fits in them. They shall be kept in the Table of Contents but marked "Not Applicable". Information ┆
0x2ae00…2af00 (42, 0, 14) Sector 2a0fed00013441 ┆* m 4Amay exist which does not fit directly into any paragraph. In this case an interpretation of the synopsis must be made to find the best fit. Invention of new paragraphs or rearranging shall be avoided unless absolutely necessary. *J 0 _┆
0x2af00…2b000 (42, 0, 15) Sector 2808ff00013441 ┆( 4A 1 3.2 LAYOUT The editorial style of all documents shall be as described in Document Layout Standard SD/STD/002. 3.3 CONTENT The main content of all parts of the specification s┆
0x2b000…2b100 (43, 0, 0) Sector 2b01ff00015541 ┆+ UAustrating in total n+1 words. The lowest number shall be placed at the top of the drawing. D.3 Character Level Diagrams Data items consisting of character strings, that is mainly Key board or card input and CRT on printer output may be descri┆
0x2b100…2b200 (43, 0, 1) Sector 2b02ff00015541 ┆+ UAbed by diagrams of the following form. The character appearing first in the input or output string shall be shown in the lefthand end of the diagram. The characters of the string shall be numbered consecutively beginning with number 1 (one). ┆
0x2b200…2b300 (43, 0, 2) Sector 00000700015541 ┆ UA q5!@96 :f= R 5M_* R 5Cq5MB' R*5Cq5M[2 R45Cq5M 2M[- RA5Cq5:^=~ BL5C`5M{) RV5Cq5M . R`5Cq5M@1MI1:h= Rp5Cr4IMM.:^=~ B}5I:g=~ J 5IC$3I > S C_* ┆
0x2b300…2b400 (43, 0, 3) Sector 2b04b300013441 ┆+ 3 4Athe entire process section to the edge of the entire output section. Frequently, a wide arrow is used for emphasis here. This is particularly useful for overview diagrams. g data items is to indicate that all of the items within the box are include┆
0x2b400…2b500 (43, 0, 4) Sector 2b05ff00013441 ┆+ 4A 1 i) Arrows may cross over each other or may join to show that they point to the same process step number. Crossing arrows should be kept to a minimum. Many times they can be avoided┆
0x2b500…2b600 (43, 0, 5) Sector 2b06d100013441 ┆+ Q 4A by rearranging the data items, enclosing data items within a box (data group), leaving space between process steps, or using keyed data arrows (see below). The following example shows crossing arrows. ies that the item contains other fields not re┆
0x2b600…2b700 (43, 0, 6) Sector 2b07ff00013441 ┆+ 4A 1 From the above, a user can tell that the arrow to step 1 is from FLDA and FLDC, and that the arrow to step 2 crosses the other arrow and is from data FLDB. j) It is more difficu┆
0x2b700…2b800 (43, 0, 7) Sector 2a084300013441 ┆* C 4Alt to illustrate crossing arrows with data reference arrows. xtended description). It is often useful to rearrange fields or groups of data items to facilitate a better layout of data related to process steps and avoid the crossing of data movement ┆
0x2b800…2b900 (43, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(43,0, 9), len=0xff, h3=41015541}, f00=»0155A «, f01=»Software Doc. Std. «, f02=»vhn «, f03=»SVO «, f04=»Appendix D «, f05=26-08-80 13:50, f06=» «, f07=»15 «, f08=» 1665 «, f09=28-10-80 10:06, f10=» «, f11=»00 «, f12=» 20 «, f13=28-10-80 10:07, f14=28-10-80 10:09, f15=»0014A «, f16=» 2 «, f17=» «, f18=»19 «, f19=» 28 «, f20=» 1711 «, f21=» «, f22=» «, f99=100010000120056610a10a80aaca15050000000000000037030b00df}
0x2b900…2ba00 (43, 0, 9) Sector 2b0a0200015541 ┆+ UA + + + DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : ┆
0x2ba00…2bb00 (43, 0, 10) Sector 2b0ba500015541 ┆+ % UA 1 SD/STD/008 SVO/800826 D-# SOFTWARE DOCUMENTATION STANDARD DRAFT GENERAL /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x2bb00…2bc00 (43, 0, 11) Sector 2b0cff00015541 ┆+ UA 1 APPENDIX D D.1 BIT LEVEL DIAGRAMS Whenever a computer word or register are not used as an entity but split into fields, possibly to the level of a single bit, a diagram of the┆
0x2bc00…2bd00 (43, 0, 12) Sector 2b0dff00015541 ┆+ UA following form shall be used to enhance the description: The rightmost end of the diagram shall represent the least significant bit, and the leftmost the most significant bit. Bits shall be numbered from 0 through 15 with the lowest number d┆
0x2bd00…2be00 (43, 0, 13) Sector 2b0eff00015541 ┆+ UAesignating the least significant bit. D.2 Word Level Diagrams Word level diagrams shall be used to enhance description of all data items of more than one word size of tables and of whole memory layouts. The diagrams shall have the following f┆
0x2be00…2bf00 (43, 0, 14) Sector 2b0f1c00015541 ┆+ UAorm: 1C.1! "(=> w#6 I! "(=6 *(=#"(=6 IM2&! w"2< hMI sM & E 0= u M% :^=~ Bl1{M40sI:^=~ J 1!"<6;!#<6 !&<6 ! "$<! <6 {M;(s! 9"c=! "(= Z=q#p!"<6 !&<6 ! "$<!#<6 ! <6 {M)(sC I! <6 ! "(= <q#p!"<6 !#<6 ! "$<!&<6$`i6 {M)(sM &M7 ┆
0x2bf00…2c000 (43, 0, 15) Sector 2b00ff00015541 ┆+ UA 1 The relative size of the boxes shall as close as possible resemble the relative size of the data items illustrated. The numbering shall be per word and range from 0 through n ill┆
0x2c000…2c100 (44, 0, 0) Sector 2c01ff00015241 ┆, RAon to include collection of data to be retained, format, storage medium, and time parameters. (2) Data for periodic reports; e.g., time retained after report generation for summary reports. (3) Data for summary reports such as time retained ┆
0x2c100…2c200 (44, 0, 1) Sector 2c02c800015241 ┆, H RAafter summary report. g) Program Relationships. Interrelationships of a program with the data base(s) should be described to show how those files and tables are used in each program function. ssage forms. and implementation date of any changes to ┆
0x2c200…2c300 (44, 0, 2) Sector 2c03ff00015241 ┆, RA 1 h) Program Logic. Logical flow may be presented primarily in the form of flow charts or structured design diagrams (when structured programming is used to code programs). A narrati┆
0x2c300…2c400 (44, 0, 3) Sector 2c04ff00015241 ┆, RAve presentation, when appropriate, should be used to supplement the charts/diagrams. All charts/diagrams should be keyed to the higher-order charts in the SS, if applicable, or the FD. Provide a detailed description of the processing performed by th┆
0x2c400…2c500 (44, 0, 4) Sector 2c05ff00015241 ┆, RAe program. For each program function, in paragraph 2b of the PS, describe the operation of the program and include the algorithmic or logic data manipulations and decision processes involved. Conditions being tested for purposes of branching, the me┆
0x2c500…2c600 (44, 0, 5) Sector 2c067900015241 ┆, y RAthods for identifying error conditions, and the resulting actions of the program should be explained in detail. . (6) Describe plots or graphic displays and include the coordinates and symbols to be used, type of graphic technique (i.e., poin┆
0x2c600…2c700 (44, 0, 6) Sector 2c074a00015241 ┆, J RA 1 ed form requirements. (8) Means of display; e.g., VDU, printer, typewriter, projector, alarm type. (9) Length of output, including special handling requirements due to varia┆
0x2c700…2c800 (44, 0, 7) Sector 00000600015241 ┆ RAtions in length (such as pages of printout, feet of paper tape, etc.). (10) Expected volume and frequency, including special handling (such as queuing and priority) for high density periods. , number of words/field, number of fields, drum, number┆
0x2c800…2c900 (44, 0, 8) Sector 2c09ff00014141 ┆, AAdentify major areas of installation completion. 6.3 SHIPMENT OF EQUIPMENT CR intends to schedule the shipment of CAMPS so that the installation team will be present at site to receive the equipment. In order to take into account any slippages┆
0x2c900…2ca00 (44, 0, 9) Sector 2c0aff00014141 ┆, AA of this schedule (delays caused by customs, transportation of delay of the installation at the previous site) arrangements for each site to handle the receipt of the equipment will be made. The equipment for remote terminals and remote TARE will ┆
0x2ca00…2cb00 (44, 0, 10) Sector 2c0ba700014141 ┆, ' AAeither be unloaded at the main site and brought to the remote location by the installation team or transported directly after main site equipment is unloaded. and clarify the impact if any. 4.8 CAMPS AREA MODIFICATION The scheduled date for c┆
0x2cb00…2cc00 (44, 0, 11) Sector 2c0cff00014141 ┆, AA 1 6.4 INSTALLATION AT REMOTE LOCATIONS CR will integrate the installation of remote terminals and remote tares into the main site installation. This approach will benefit both manp┆
0x2cc00…2cd00 (44, 0, 12) Sector 2c0dff00014141 ┆, AAower allocation and installation schedule. CR expects that some remote site installations will require extra manpower in order to accomplish this joint installation within the schedule. 6.5 INSTALLATION PHASE ACTIVITIES Figure 6.1 is an analys┆
0x2cd00…2ce00 (44, 0, 13) Sector 2c0eff00014141 ┆, AAis of the installation effort to be carried out at a typical site. A similar analysis will be made for each site, when the site configurations are finalized. A step by step description of figure 6.1 follows: Step 1 One week s buffer between si┆
0x2ce00…2cf00 (44, 0, 14) Sector 2c0fff00014141 ┆, AAtes seems necessary in regard to the distance between sites and in order to make up for delay in the installation of the previous site or shipment of equipment. The necessary buffer will be calculated when the final installation sequence is decided┆
0x2cf00…2d000 (44, 0, 15) Sector 2a00ff00014141 ┆* AA. Step 2,3,4 The first 2 days on site will be used to contact site officials, make all necessary arrangements, inspect the installation areas and move in. A checklist will be prepared for the inspection. Step 5 Before any equipment is brought┆
0x2d000…2d100 (45, 0, 0) Sector 2d012700014141 ┆- ' AAied during site verification. During the site surveys early in the preparation phase a Data Baseline was created concerning the preparation of each site for CAMPS installation. However, this baseline is still ┆
0x2d100…2d200 (45, 0, 1) Sector 2d02ff00014141 ┆- AA 1 5.6 SITE VERIFICATION CR will perform a verification of each site prior to installation. The verification shall prove that the site is ready for installation of the CAMPS equipm┆
0x2d200…2d300 (45, 0, 2) Sector 2d03ff00014141 ┆- AAent. The proving will consist of inspections and tests according to a Site Verification Procedure. The procedure will be prepared on basis of CR's civil engineering requirements as-to-be-built drawings and Host Nation civil works drawings. The┆
0x2d300…2d400 (45, 0, 3) Sector 2d04ff00014141 ┆- AA procedure is to be signed off by the participants and issued as a Site Verification Report. Discrepancies found during the verification will be recorded together with corrective actions to be taken and completion date of action taken. The site ┆
0x2d400…2d500 (45, 0, 4) Sector 2d057000014141 ┆- p AAis first to be considered as handed over to contractor upon successfull completion of the verification. the contract. The CER will contain the equipment related information needed to enable Host Nation to prepare the installation for CAMPS. T┆
0x2d500…2d600 (45, 0, 5) Sector 2d06ff00014141 ┆- AA 1 6 INSTALLATION 6.1 PREPARATION OF INSTALLATION Final arrangements concerning CR's arrival to site are to be made at time of site verification. The site representatives will ┆
0x2d600…2d700 (45, 0, 6) Sector 2d07ff00014141 ┆- AAbe informed about how CR intends to accomplish the installation. Also the responsibilities of the site personnel will be discussed. The purpose of this is to assure that CR can carry out the installation in an efficient way without interference of t┆
0x2d700…2d800 (45, 0, 7) Sector 2c08ff00014141 ┆, AAhe daily operations at the site. 6.2 INSTALLATION TASK SCHEDULE During the installation phase the team will be working in accordance to a detailed task schedule, which will itemize work functions at the site for all installation personnel and i┆
0x2d800…2d900 (45, 0, 8) Sector 2d09ff00014141 ┆- AANation. 3. Physical characteristics of the CAMPS equipment. The CER will cover the following: 1. Physical layout of major equipment. 2. All cable ducts and conduits in the CAMPS room. 3. Record of Host Nation/ACE COMSEC cable runs outside ┆
0x2d900…2da00 (45, 0, 9) Sector 2d0aff00014141 ┆- AAthe CAMPS room. 4. Requirement to power and grounding systems including number of required power outlets and grounding connections point in conjunction with major equipment. 5. Airconditioning requirements. 6. Other civil requirements, if any.┆
0x2da00…2db00 (45, 0, 10) Sector 2d0b0a00014141 ┆- AA ) are completed 1 month prior to installation, this seems only to have an impact on the user terminal installations. CR would like SHAPE to investigate this and clarify the impact if any. 4.8 CAMPS AREA MODIFICATION The scheduled date for c┆
0x2db00…2dc00 (45, 0, 11) Sector 2d0cff00014141 ┆- AA 1 5.4 AS-TO-BE-BUILT DRAWINGS CR will provide as-to-be-built drawings for each site as required in the contract. These drawings will be used for the installation of CAMPS equipmen┆
0x2dc00…2dd00 (45, 0, 12) Sector 2d0dff00014141 ┆- AAt on each site. The A-T-B-B drawings will be based on the following information: 1 The site documentation required to prepare the CER. 2. The equipment configuration and equipment interface data. 3. The CER. The A-T-B-B drawings will be pr┆
0x2dd00…2de00 (45, 0, 13) Sector 2d0eff00014141 ┆- AAepared to cover the following: 1. Physical layout of major equipment. 2. Floor and wall plans showing cable runs of all interface cables and interconnecting cables to be run inside the CAMPS room. Signal cable runs from CAMPS room to user termin┆
0x2de00…2df00 (45, 0, 14) Sector 2d0fff00014141 ┆- AAals. 3. Equipment interface to power and grounding systems. 4. Airconditioning interface to existing systems, if any. 5. Cable diagrams and cable details. 6. Distribution frames and patch panels details. 5.5 DELIVERY OF SIGNAL CABLES All┆
0x2df00…2e000 (45, 0, 15) Sector 2d00ff00014141 ┆- AA signal cables to be run by host nation will be delivered at least 6 months prior to installation as agreed during the site survey meetings, together with necessary installation documentation. The correct installation of these cables will be verif┆
0x2e000…2e100 (46, 0, 0) Sector 2e01ff00014141 ┆. AA 1 During the site surveys early in the preparation phase a Data Baseline was created concerning the preparation of each site for CAMPS installation. However, this baseline is still ┆
0x2e100…2e200 (46, 0, 1) Sector 2e02ff00014141 ┆. AAincomplete for a majority of sites, and it was agreed at the site survey meetings to complete it by submittal of the missing documentation to CR. This submittal will enable contractor to start site design and to prepare the CER and A-T-B-B drawing┆
0x2e200…2e300 (46, 0, 2) Sector 2e03ff00014141 ┆. AAs. Later updates received in time i.e. at least 3 months prior to CR's delivery of CER will be incorporated. 5.2 SITE SURVEYS AND SITE VISITS CR will perform site surveys at each site as required. Site No. 1 through 13 has been surveyed in Ma┆
0x2e300…2e400 (46, 0, 3) Sector 2e04ff00014141 ┆. AAy and June 1980. The survey of the remaining sites (site No. 14 and 15) plus the remote terminal locations is to be planned and performed. Visit to some sites during the preparation phase might be necessary. CR will notify SHAPE if such visits a┆
0x2e400…2e500 (46, 0, 4) Sector 2e05ff00014141 ┆. AAre needed. 5.3 CIVIL ENGINEERING REQUIREMENTS (CER). CR will provide CER for each site as required in the contract. The CER will contain the equipment related information needed to enable Host Nation to prepare the installation for CAMPS. T┆
0x2e500…2e600 (46, 0, 5) Sector 2e06ff00014141 ┆. AAhe CER will be based on the following information: 1. Host nation drawings/documents handed over to CR during the site surveys or submitted to CR as agreed to during the survey meetings. The drawings/documents include cable runs outside CAMPS-roo┆
0x2e600…2e700 (46, 0, 6) Sector 2e076000014141 ┆. ` AAm and location of user terminals and other equipment which has to be connected to CAMPS. ucts already exist or are planned as part of the main installations). CR will include the cable(s) in the para 3.1 delivery of signal cables. CR will perform t┆
0x2e700…2e800 (46, 0, 7) Sector 2d08ff00014141 ┆- AA 1 2. The information gathered during the surveys and contained in the survey report including the proposed site layouts or an amended site layout if received in time from SHAPE/Host ┆
0x2e800…2e900 (46, 0, 8) Sector 2e09ff00014141 ┆. AAhe plan. 4.6 DELIVERY OF SIGNAL CABLES The due date for CR delivery of signal cables (6 months prior to start of installation) is shown. 4.7 HOST NATION CONSTRUCTION OR RECONSTRUCTION. The scheduled date for completion of construction or r┆
0x2e900…2ea00 (46, 0, 9) Sector 2e0aff00014141 ┆. AAeconstruction as obtained from Host Nation during the Site Surveys are shown. Please notice that some sites (AFSOUTH, AFNORTH and COMNON) have not completed the construction or reconstruction at time of installation. Since the CAMPS area modificatio┆
0x2ea00…2eb00 (46, 0, 10) Sector 2e0bff00014141 ┆. AAn (8) are completed 1 month prior to installation, this seems only to have an impact on the user terminal installations. CR would like SHAPE to investigate this and clarify the impact if any. 4.8 CAMPS AREA MODIFICATION The scheduled date for c┆
0x2eb00…2ec00 (46, 0, 11) Sector 2e0ce800014141 ┆. h AAompletion of CAMPS area modification as obtained from Host Nation during the Site Surveys are shown. 4.9 H/N INSTALLATION OF SIGNAL CABLES Host Nations scheduled completion date for signal cable installation is shown. ill be installed close ┆
0x2ec00…2ed00 (46, 0, 12) Sector 2e0dff00014141 ┆. AA 1 4.10 SITE VERIFICATION The Site Verification by CR is to be performed, when the preparation works are finished. As shown only one month is scheduled between completion of Site Pre┆
0x2ed00…2ee00 (46, 0, 13) Sector 2e0eff00014141 ┆. AAparation works and start of installation. 4.11 SITE INSTALLATION The scheduled completion date of site installation is shown. 5 SITE PREPARATION AND VERIFICATION 5.1 SITE PREPARATION The site preparation phase can be defined as ┆
0x2ee00…2ef00 (46, 0, 14) Sector 2e0fff00014141 ┆. AAthe time span from contract award to start of each site installation. During this phase CR's main activities concerning installation are placed on preparation of Civil Engineering Requirements and as-to-be built drawings for each site. During t┆
0x2ef00…2f000 (46, 0, 15) Sector 2e00e000014141 ┆. ` AAhe same phase Host Nation's main activities are concentrated on completion of the design and construction or reconstruction of each site, and preparation of the site area for installation (for schedule see fig. 4.1). the CAMPS room. At remote TA┆
0x2f000…2f100 (47, 0, 0) Sector 2f01b800014141 ┆/ 8 AA 1 Figure 3.3 Typical Communication Link to Remote Terminals. ve available space for the SHAPE furnished crypto. CR will connect the┆
0x2f100…2f200 (47, 0, 1) Sector 2f02ff00014141 ┆/ AA 1 4. SITE IMPLEMENTATION PLAN Figure 4.1 shows the milestones of the efforts to be accomplished during the site preparation phase, related to each site. The plan is composed of┆
0x2f200…2f300 (47, 0, 2) Sector 2f03ff00014141 ┆/ AA the date for completion of site preparation given by Host Nation during the site surveys and the schedules of the contract. Each milestone is represented by a dot and reference number of effort. The referenced efforts are listed at the bottom of ┆
0x2f300…2f400 (47, 0, 3) Sector 2f04ff00014141 ┆/ AAthe plan. A discussion of each effort follows. 4.1 SITE SURVEYS As shown in the plan site No. 1 through 13 have been surveyed during May-June 1980. Surveys of MEDEAST and SONOR and of remote terminals are to be scheduled by SHAPE and perform┆
0x2f400…2f500 (47, 0, 4) Sector 2f05ff00014141 ┆/ AAed. 4.2 H/N DATA SUBMITTALS It was agreed during the site surveys by SHAPE/Host Nation to provide missing documentation requested by CR at the dates shown in the plan. 4.3 CIVIL ENGINEERING REQUIREMENTS (CER) The contractual due date (12 m┆
0x2f500…2f600 (47, 0, 5) Sector 2f06b200014141 ┆/ 2 AAonths prior to start of installation of each site) is shown. 4.4 AS-TO-BE-BUILT DRAWINGS The contractual due date (9 months prior to start of installation) is shown. ovide the cable(s) to be run by Host Nation between the CAMPS room and the cr┆
0x2f600…2f700 (47, 0, 6) Sector 2f074a00014141 ┆/ J AA 1 s assumed that cable ducts already exist or are planned as part of the main installations). CR will include the cable(s) in the para 3.1 delivery of signal cables. CR will perform t┆
0x2f700…2f800 (47, 0, 7) Sector 2e08ff00014141 ┆. AA 1 4.5 HOST NATION DESIGN Some sites are already under construction (site 1 and 2) or under reconstruction (site 5 and 6). The related design milestones are therefore not marked in t┆
0x2f800…2f900 (47, 0, 8) Sector 2f09ff00015241 ┆/ RA 1 (11) Priority, e.g., routine, emergency. (12) Timing requirements, e.g., response time. (13) Program recipients and their use of displays; e.g., notification, trends, or bri┆
0x2f900…2fa00 (47, 0, 9) Sector 2f0aff00015241 ┆/ RAefings. (14) Disposition, including logging, film and hard copy printout reproduction and storage, number of copies required for distribution, place of storage, person responsible for permanent copy, retention period, and special handling require┆
0x2fa00…2fb00 (47, 0, 10) Sector 2f0bff00015241 ┆/ RAments because of bulk, classification, or timing. (15) Security classification of output and individual items. (16) Explanation of symbols. (17) Conditional and status indicators (code and conditional definition). Include examples of progra┆
0x2fb00…2fc00 (47, 0, 11) Sector 2f0cff00015241 ┆/ RAm outputs. d) Data Environment. Provide a detailed description of the files, tables, dictionaries, program interrelationship with the tables, storage allocation, intermediate data structures, and data retention requirements to include as applicabl┆
0x2fc00…2fd00 (47, 0, 12) Sector 2f0dff00015241 ┆/ RAe: (1) Title and tag. (2) Content description. (3) Parameter - start and end of file. (4) Number of records or entries. (5) Record parameter - start and end of record. (6) Relationship of each record to the common data base. ┆
0x2fd00…2fe00 (47, 0, 13) Sector 2f0e6a00015241 ┆/ j RA (7) Storage, to include type and amount required and, if known, beginning and ending addresses. (1) Title and tag (2) Number of items (3) Item description to include number and type of characters (numeric, alpha, decimal, signed, uns┆
0x2fe00…2ff00 (47, 0, 14) Sector 2f0fff00015241 ┆/ RA 1 (8) Normal file order; other orders if required for special purpose. (9) Classification. e) Storage Allocation. Describe the allocation of internal and auxiliary storage as┆
0x2ff00…30000 (47, 0, 15) Sector 2c00ff00015241 ┆, RA follows: (1) Storage media. (2) Available storage on each medium. (3) Addresses of available storage. (4) Erasable working storage. f) Data Retention. Describe requirements for data retention as follows: (1) Historic informati┆
0x30000…30100 (48, 0, 0) Sector 3001ff00015241 ┆0 RAf input, storage location, and custodian. (9) Security classification of input and individual items. (10 Flexibility, such as capability of omitting or adding items. (11) Requirements for timeliness. (12) Throughput time. (13) Speci┆
0x30100…30200 (48, 0, 1) Sector 3002d500015241 ┆0 U RAal handling, such as specification of special control cards. This paragraph should provide examples of prepared inputs and preparation forms, such as input creation sheets and communication message forms. and implementation date of any changes to ┆
0x30200…30300 (48, 0, 2) Sector 3003ff00015241 ┆0 RA 1 c) Outputs. This paragraph should describe each type of output applicable to the program. This description may be by the program or subprograms. Categorise each output by type (suc┆
0x30300…30400 (48, 0, 3) Sector 3004ff00015241 ┆0 RAh as quality control, data type A, B, etc.) and provide the following information as applicable: (1) Title and tag. (2) Format to include headings, line spacing, arrangement, totals, etc. (3) Number of items. (4) Describe each item p┆
0x30400…30500 (48, 0, 4) Sector 3005ff00015241 ┆0 RAroviding number and type of characters (alpha, numeric, symbol, etc) range of values, accuracy requirements, supporting background information (e.g. maps) which will be presented. (5) Include the criteria for data selection for display, e.g., se┆
0x30500…30600 (48, 0, 5) Sector 3006ff00015241 ┆0 RAlection of a maintenance report may be on the basis of active records in a file of aircraft type and aircraft usage. (6) Describe plots or graphic displays and include the coordinates and symbols to be used, type of graphic technique (i.e., poin┆
0x30600…30700 (48, 0, 6) Sector 3007ff00015241 ┆0 RAts or continuous), number of curves per sheet, etc. (7) Preprinted form requirements. (8) Means of display; e.g., VDU, printer, typewriter, projector, alarm type. (9) Length of output, including special handling requirements due to varia┆
0x30700…30800 (48, 0, 7) Sector 2f08c800015241 ┆/ H RAtions in length (such as pages of printout, feet of paper tape, etc.). (10) Expected volume and frequency, including special handling (such as queuing and priority) for high density periods. , number of words/field, number of fields, drum, number┆
0x30800…30900 (48, 0, 8) Sector 3009ff00015241 ┆0 RA of drum assemblies. (3) Disk storage, number or words/zone or bytes/cylinder, number of zones/disk or cylinders/disk, number of disks/disk unit, number of disk units. (4) Tape storage, number of adapters, number of tape drives/adapter, number┆
0x30900…30a00 (48, 0, 9) Sector 300aff00015241 ┆0 RA of tapes. In addition, allocate the machine storage into permanent and temporary areas. d. Security. Describe the computer program, its classified components, the inputs, outputs, and the data bases. e. Controls. Include in this paragraph ┆
0x30a00…30b00 (48, 0, 10) Sector 300bff00015241 ┆0 RAprogram controls such as record counts, accumulated counts, batch controls, etc. State if no specific controls are to be established at the program level. A.4 DESIGN DETAILS a) Program Operating Procedures. Delineate any special require┆
0x30b00…30c00 (48, 0, 11) Sector 300c9f00015241 ┆0 RAments necessary for the implementation of system operating procedures, and discuss how the executive support programs interact with the other programs. (3) Response time of major program functions. (4) Sequential relationships of program fun┆
0x30c00…30d00 (48, 0, 12) Sector 300dff00015241 ┆0 RA 1 b) Inputs. Describe in detail each type of input applicable to the program. This description may be with the program or subprogram. Type each input according to its use in the pro┆
0x30d00…30e00 (48, 0, 13) Sector 300eff00015241 ┆0 RAgram (such as parameter, data type A, B, etc.) and provide the following information as applicable: (1) Title and tag (2) Number of items (3) Item description to include number and type of characters (numeric, alpha, decimal, signed, uns┆
0x30e00…30f00 (48, 0, 14) Sector 300fff00015241 ┆0 RAigned), range of values, accuracy requirements. (4) Means of entry and initiation procedures; e.g., typewriter, card, tape, sensor, internal. (5) Length of input including special handling requirements due to variations in length. (6) Ex┆
0x30f00…31000 (48, 0, 15) Sector 3000ff00015241 ┆0 RApected volume and frequency including special handling (such as queueing and priority handling) for high density periods. (7) Priority; e.g. routine, emergency. (8) Disposition other than processing, such as logging, hard copy reproduction o┆
0x31000…31100 (49, 0, 0) Sector 3101ff00015241 ┆1 RA 1 a) Support Software Environment. Describe support software which will interact with the computer programs being developed. Provide the nomenclature and documentation references of ┆
0x31100…31200 (49, 0, 1) Sector 3102ff00015241 ┆1 RAeach such system, subsystem, and program for both support and test software. Indicate which languages (compiler, assembler, program, query, etc) and operating system will be used. Discuss the nature, status and implementation date of any changes to ┆
0x31200…31300 (49, 0, 2) Sector 3103ff00015241 ┆1 RAsupport software which will impact on the computer programs being developed. b) Interfaces. Describe the interfaces with other applications computer programs, including those of other operational capabilities or military organizations. These indiv┆
0x31300…31400 (49, 0, 3) Sector 3104ff00015241 ┆1 RAidual interfaces should include the following: (1) Types of interface, such as operator control of a terminal or program interfaces with other programs. (2) Operational implications of data transfer, including security requirements. (3) Req┆
0x31400…31500 (49, 0, 4) Sector 3105ff00015241 ┆1 RAuirements for data transfer to and from the subject program (including data content, sequence, timing, format, volume and processing), and characteristics of communications media/systems used. (4) Formats of interchanged data. (5) Interface pr┆
0x31500…31600 (49, 0, 5) Sector 3106ff00015241 ┆1 RAocedures, including telecommunications considerations. (6) Interface equipment. (7) Data conversion requirements. c) Storage. Describe the requirements and usage for both internal and auxiliary program storage. Provide the following informat┆
0x31600…31700 (49, 0, 6) Sector 31073a00015241 ┆1 : RAion for the various storage media for each program: mentation of higher order systems/subsystems and related programs, as required. b) Program Functions. Describe the functions of the program. Note, if a program does not in itself satisfy system ┆
0x31700…31800 (49, 0, 7) Sector 3008ff00015241 ┆0 RA 1 (1) Internal storage, number of words/auxiliary core bank or bytes/auxiliary core bank, number of banks. (2) Drum storage, number of words/field, number of fields, drum, number┆
0x31800…31900 (49, 0, 8) Sector 3109ff00015241 ┆1 RAa manner that program environment can be related to them. c) Accuracy and Validity. Describe the requirements for program accuracy. Changes in the accuracy requirements from the next higher order document will be explicitly identified. Accuracy re┆
0x31900…31a00 (49, 0, 9) Sector 310aff00015241 ┆1 RAquirements for mathematical calculations, input and output data must be considered. d) Timing. Describe any timing requirements placed on the program. Changes in the timing requirements from the next higher order document should be identified. The┆
0x31a00…31b00 (49, 0, 10) Sector 310b3400015241 ┆1 4 RA following requirements should be considered: SD/STD/008 SVO/800814 A-# SOFTWARE DOCUMENTATION STANDARD DRAFT GENERAL /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x31b00…31c00 (49, 0, 11) Sector 310cff00015241 ┆1 RA 1 (1) Throughput time. (2) Response time to queries and for updates of data files. (3) Response time of major program functions. (4) Sequential relationships of program fun┆
0x31c00…31d00 (49, 0, 12) Sector 310dff00015241 ┆1 RActions and data flows. (5) Priorities imposed by inputs or changes in modes of operation. (6) Requirements for varying traffic loads. (7) Sequencing and interleaving programs and systems (including the ability to interrupt a program without┆
0x31d00…31e00 (49, 0, 13) Sector 310eff00015241 ┆1 RA loss of data). (8) Transfer time required for I/O devices (disk, drum, tape, etc.) (9) Internal processing time. e) Flexibility. Describe any requirements for the program to deal with changing systems, e.g. operational changes, and interact┆
0x31e00…31f00 (49, 0, 14) Sector 310fff00015241 ┆1 RAion with new or improved programs. Identify those components and procedures which may be subject to change. A.3 ENVIRONMENT Specify the current environment of the system and indicate any changes from what is described in the System/Sub┆
0x31f00…32000 (49, 0, 15) Sector 31001d00015241 ┆1 RAsystem Specifications. A.1 GENERAL a) Purpose Statement. Describe the purpose of the Program Specification (PS) using the following as a guide: The objective of this Program Specification for (Projec┆
0x32000…32100 (50, 0, 0) Sector 3201ff00015241 ┆2 RAt Name) (Project number) is to describe the program design in sufficient detail to permit the programmer/coder to produce a program. b) Project References. This paragraph should summarize the references applicable to the history and development of┆
0x32100…32200 (50, 0, 1) Sector 3202ff00015241 ┆2 RA the project. Specify the general nature of the computer programs (tactical, inventory control, war gaming, management information, etc) to be developed and state its purpose and uses. Indicate the project sponsor, user, and operating centre(s) whic┆
0x32200…32300 (50, 0, 2) Sector 3203ff00015241 ┆2 RAh will run the completed computer programs. List all applicable documents and specify their source or author, reference number, title and security classification. As a minimum, include the following: (1) Functional Description/Requirement Specifi┆
0x32300…32400 (50, 0, 3) Sector 3204ff00015241 ┆2 RAcation. (2) Associated System/Subsystem Specifications. (3) Related Program Specifications. (4) Other pertinent documentation or significant correspondence not specified in the Functional Description. c) Terms and Abbreviations. List or ┆
0x32400…32500 (50, 0, 4) Sector 3205a200015241 ┆2 " RAinclude in an appendix any terms, definitions, or acronyms unique to this document and subject to interpretation. Do not include item names or data codes. g nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x32500…32600 (50, 0, 5) Sector 3206ff00015241 ┆2 RA 1 A.2 SUMMARY OF REQUIREMENTS a) Program Description. This paragraph should describe the program to provide a frame of reference for the remainder of the document. It should sum┆
0x32600…32700 (50, 0, 6) Sector 3207ff00015241 ┆2 RAmarize the system requirements and refer to the documentation of higher order systems/subsystems and related programs, as required. b) Program Functions. Describe the functions of the program. Note, if a program does not in itself satisfy system ┆
0x32700…32800 (50, 0, 7) Sector 3108ff00015241 ┆1 RAor subsystem functions, state how the aggregate of programs completely satisfies the functions. Although the descriptions of the functions may be refined and more detailed, they must relate to the subsystem or system functions and be stated in such ┆
0x32800…32900 (50, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(50,0, 9), len=0xff, h3=41013441}, f00=»0134A «, f01=»Software Doc. Std. «, f02=»kk «, f03=»SVO «, f04=»SD/STD/008 «, f05=14-08-80 11:20, f06=» 3 «, f07=»00 «, f08=» 5069 «, f09=21-10-80 13:20, f10=» «, f11=»46 «, f12=» 1951 «, f13=21-10-80 14:28, f14=21-10-80 15:23, f15=»0014A «, f16=» 6 «, f17=» 12 «, f18=»00 «, f19=» 96 «, f20=» 35128 «, f21=» «, f22=» «, f99=300050000120056610a10a80aaca15050000000000000030032000df}
0x32900…32a00 (50, 0, 9) Sector 320a0600013441 ┆2 4A 2 2 * * ( ( ( DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: S S Dokumentnavn: Operat]r: Forfatter: Kommentarer: S S┆
0x32a00…32b00 (50, 0, 10) Sector 320ba300013441 ┆2 # 4A 1 SD/STD/008 SVO/801010 # SOFTWARE MODULE DOCUMENTATION STANDARD GENERAL -!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x32b00…32c00 (50, 0, 11) Sector 320cff00013441 ┆2 4A 1 1 TABLE OF CONTENTS 1 SCOPE ........................................ 4 2 PURPOSE .......................┆
0x32c00…32d00 (50, 0, 12) Sector 320dff00013441 ┆2 4A............... 4 3 ORGANIZATION ................................. 4 3.1 SYNOPSIS ................................. 4 3.1.2 Tayloring of Synopsis ................ 4 3.2 LAYOUT ................................... 5 3.3 CONTENT ┆
0x32d00…32e00 (50, 0, 13) Sector 320eff00013441 ┆2 4A.................................. 5 3.3.1 Language Style ....................... 5 4 DIAGRAMS ..................................... 6 4.1 HIERARCHICAL OVERVIEW CHART .............. 6 4.2 INPUT - PROCESS - OUTPUT CHARTS .......... ┆
0x32e00…32f00 (50, 0, 14) Sector 320fff00013441 ┆2 4A 7 4.3 FLOWGRAMS ................................ 7 4.4 DATA CHARTS .............................. 7 APPENDIX A A.1 GENERAL .................................. 2 A.2 SUMMARY OF REQUIREMENTS .................. 3 A.3 ENVIRONMENT ┆
0x32f00…33000 (50, 0, 15) Sector 2a08ff00013441 ┆* 4A.............................. 4 A.4 DESIGN DETAILS ........................... 6 APPENDIX B B.1 GENERAL FORMAT ........................... 2 B.2 DATA ITEMS AND DATA GROUPS ............... 2 B.3 ARROWS ...........................┆
0x33000…33100 (51, 0, 0) Sector 3301ff00014141 ┆3 AAween black patch and MDF. At remote locations CR will install the black equipment (modems and black patch) in the crypto rack provided and installed by Host Nation. CR will provide and make the connections between the modem and black patch and bet┆
0x33100…33200 (51, 0, 1) Sector 3302ff00014141 ┆3 AAween the crypto and black patch. Host Nation will provide and make the connection between the MDF and black patch. CR will install the red equipment (rack with red patch, multiplexer and optical MUX/DEMUX) in the room specified by Host Nation CR┆
0x33200…33300 (51, 0, 2) Sector 3303ff00014141 ┆3 AA will provide the cable to be run by Host Nation between the crypto and the red patch. Host Nation will provide and install the cable duct for this cable. CR will install the terminals in the rooms specified by Host Nation. CR will provide the opt┆
0x33300…33400 (51, 0, 3) Sector 33048400014141 ┆3 AAo-cables to be run between the red rack and the terminals. Host Nation will install the cable ducts and run the opto-cables. ground connection points installed by Host Nation. The power outlets and ground connection points will be installed close ┆
0x33400…33500 (51, 0, 4) Sector 3305ff00014141 ┆3 AA 1 CR will terminate the opto-cables at the terminal and in the red rack. CR will connect the terminal to power outlets and ground connection points installed by Host Nation. The powe┆
0x33500…33600 (51, 0, 5) Sector 3306ff00014141 ┆3 AAr outlets and ground connection points will be installed close to each terminal. Host Nation will be responsible for all power and ground installations. CR will specify equipment power load, number of outlets and other civil engineering requiremen┆
0x33600…33700 (51, 0, 6) Sector 3307ff00014141 ┆3 AAts to be used by Host Nation to prepare the remote terminal site. CR will include the cables to be run by Host Nation in the para 3.1 delivery. At sites which are implemented with optical links between the CAMPS room and remote terminals (i.e. Uka┆
0x33700…33800 (51, 0, 7) Sector 2f006800014141 ┆/ h AAir, Afnorth, Non and Sonor) the principles outlined for the main site user terminals shall apply. lar will be Host Nation responsibility. Host Nation will make the connection between the crypto-equipment and the IDF in the CAMPS room. At remote TA┆
0x33800…33900 (51, 0, 8) Sector 3309ff00014141 ┆3 AARE locations CR will install a rack with modem and connect it to power and ground installed by Host Nation. CR will specify his requirements to power and ground. The rack will have available space for the SHAPE furnished crypto. CR will connect the┆
0x33900…33a00 (51, 0, 9) Sector 330a9a00014141 ┆3 AA modem to the crypto and black patch in the rack. The connection between the black patch and the MDF or similar will be Host Nation responsibility. s. 3.1.2 Site Preparation CR will deliver CER 12 months prior to installation of each site to be┆
0x33a00…33b00 (51, 0, 10) Sector 330ba200014141 ┆3 " AA 1 Figure 3.1 Typical CAMPS Room Layout tation supplied during the site surveys. Last submittal of data from SHAPE/Host Nation is 3 m┆
0x33b00…33c00 (51, 0, 11) Sector 330c8400014141 ┆3 AA 1 Figure 3.2 Cable Connections at a Typical Main Site. pproval. The approved drawings will be used for installation of the CAMPS equipment. 2 ORGANIZATION ..................┆
0x33c00…33d00 (51, 0, 12) Sector 330dff00014141 ┆3 AA 1 3.2.3 Remote Terminals In the following please refer to figure 3.3 At main sites CR will install the red part of the remote terminal equipment in the CAMPS room (i.e. rack with ┆
0x33d00…33e00 (51, 0, 13) Sector 330eff00014141 ┆3 AAmultiplexer(s) and red patch). The black equipment (modems and black patch) will be installed by CR in the crypto-rack provided and installed by Host Nation. CR will provide the cable(s) to be run by Host Nation between the CAMPS room and the cr┆
0x33e00…33f00 (51, 0, 14) Sector 330fff00014141 ┆3 AAypto-rack in cable ducts provided and installed by Host Nation (it is assumed that cable ducts already exist or are planned as part of the main installations). CR will include the cable(s) in the para 3.1 delivery of signal cables. CR will perform t┆
0x33f00…34000 (51, 0, 15) Sector 3300ff00014141 ┆3 AAhe cable(s) run in the CAMPS room as part of the main installation. CR will provide the cables and make the connection between crypto and black patch and between modem and black patch. Host Nation will provide the cable and make the connection bet┆
0x34000…34100 (52, 0, 0) Sector 3401ff00014141 ┆4 AAn racks and I.D.F. if not incorporated in the central equipment. Host Nation will install all signal cable ducts in the CAMPS Equipment room. CR will connect the above equipment to power outlets and ground connection points installed by Host Natio┆
0x34100…34200 (52, 0, 1) Sector 3402b900014141 ┆4 9 AAn. The power outlets and ground connection points will be located close to each piece of equipment. The CER will specify number of outlets and maximum distance from equipment. =M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x34200…34300 (52, 0, 2) Sector 3403ff00014141 ┆4 AA 1 Host Nation will be responsible for all power and ground installations. The CER will contain CR's requirements to these installations. CR will install the user terminals in the ┆
0x34300…34400 (52, 0, 3) Sector 3404ff00014141 ┆4 AArooms specified by host nation; connect the signal cables to the terminals and connect the terminals to the power outlets and ground connection points installed by Host Nation. The power outlets and ground connection points will be installed close ┆
0x34400…34500 (52, 0, 4) Sector 3405ff00014141 ┆4 AAto the terminals accordingly to the CER. Host Nation will install the cable ducts and run the cables from the CAMPS equipment room to each user terminal. CR will deliver the signal cables (OPTO) Host nation will install the TRC and/or low spee┆
0x34500…34600 (52, 0, 5) Sector 3406ff00014141 ┆4 AAd teleprinters and make all connections in the terminal end. The cables from these terminals will be run to the CAMPS room and terminated at the IDF by Host Nation. Host Nation will also provide cables and cable ducting. CR will deliver and run t┆
0x34600…34700 (52, 0, 6) Sector 3407ff00014141 ┆4 AAhe cables from the IDF to the computer. The same principle will be used regarding the CCIS, SCARS and collocated tare connections. 3.2.2 Remote Tares At main site CR will install the modem(s) in the crypto room and connect it to adjacent equi┆
0x34700…34800 (52, 0, 7) Sector 3308ff00014141 ┆3 AApment (crypto and black patch located in the same rack.) The further connection to the MDF or similar will be Host Nation responsibility. Host Nation will make the connection between the crypto-equipment and the IDF in the CAMPS room. At remote TA┆
0x34800…34900 (52, 0, 8) Sector 3409ff00015141 ┆4 QAlear enter look up record terminate close establish maintain reinstate test complete examine make release transfer construct execute merge resolve translate control exit modify restore update convert extract monitor return use copy find move s┆
0x34900…34a00 (52, 0, 9) Sector 340a9f00015141 ┆4 QAcan validate create fix obtain schedule verify decrement format open search write 1 arrow. These approaches may be combined. tem or data group, and terminate at the number of ┆
0x34a00…34b00 (52, 0, 10) Sector 340bff00015141 ┆4 QA 1 e) The content of the process section should show function rather than code statements, for example, what the loop, branch, or condition test is intended to accomplish. f) No dec┆
0x34b00…34c00 (52, 0, 11) Sector 340cff00015141 ┆4 QAision symbols should be contained within the input/output diagram. g) Process steps may contain a subroutine function. The subroutine block is shown as follows: where the label is the name of the subroutine, and NN is the identification┆
0x34c00…34d00 (52, 0, 12) Sector 340d4900015141 ┆4 I QA number of another input/output diagram, describing this function. of arrows in the output path. It is unclear in the first example whether the input was FLDA or all data, or whether the input was for step 1 or 2. uld be shown as a 1 or 0. ┆
0x34d00…34e00 (52, 0, 13) Sector 340eca00015141 ┆4 J QA 1 The subroutine may be internal to the process described or be an external routine. The subroutine should be shown as follows: techniques as in (2) above may be used, but the word ┆
0x34e00…34f00 (52, 0, 14) Sector 340fff00015141 ┆4 QA 1 h) Interactive functions may be shown by enclosing these functions within a box, for example: i) There is a practical limit to the levels of nesting that c┆
0x34f00…35000 (52, 0, 15) Sector 1e08ff00015141 ┆ QAan be seen easily on an input/output diagram. If more than two levels are needed, the innermost nested items can be shown in a lower-level input/output diagram, or referenced in the extended description. Note that the intent of the diagram is not┆
0x35000…35100 (53, 0, 0) Sector 3501ff00014141 ┆5 AAlations may, therefore, have to be reconsidered and clarified during and after the survey. 3.1 SITE PREPARATION AND VERIFICATION 3.1.1 Site Surveys CR will perform site surveys in conjunction with SHAPE. SHAPE will assist CR in collecting r┆
0x35100…35200 (53, 0, 1) Sector 3502ff00014141 ┆5 AAelevant information and site documentation during the surveys for the preparation of civil engineering requirements (CER) and as-to-be-built drawings. 3.1.2 Site Preparation CR will deliver CER 12 months prior to installation of each site to be┆
0x35200…35300 (53, 0, 2) Sector 3503ff00014141 ┆5 AA used by host nation to prepare the CAMPS installation. SHAPE will deliver additional site documentation, requested by CR, or updates to the site documentation supplied during the site surveys. Last submittal of data from SHAPE/Host Nation is 3 m┆
0x35300…35400 (53, 0, 3) Sector 3504db00014141 ┆5 [ AAonths prior to CR's submittal of CER. CR will deliver As-To-Be-Built drawings to SHAPE 9 months prior to installation for approval. The approved drawings will be used for installation of the CAMPS equipment. 2 ORGANIZATION ..................┆
0x35400…35500 (53, 0, 4) Sector 3505ff00014141 ┆5 AA 1 SHAPE will approve the CER and A-T-B-B drawings to meet the national regulations and ACE COMSEC requirements. CR will deliver signal cables to be run by host nation, with the nec┆
0x35500…35600 (53, 0, 5) Sector 3506ff00014141 ┆5 AAessary installation documentation 6 months prior to start of installation. 3.1.3 Site Verification CR will perform a verification of each site's readiness for installation. SHAPE or SHAPE representatives will participate. 3.2 INSTALLATION ┆
0x35600…35700 (53, 0, 6) Sector 3507ff00014141 ┆5 AA CR will perform installation of the CAMPS equipment in accordance with the requirements of the contract and CAMPS Requirements Specification. In the following please refer to figure 3.1 and 3.2. 3.2.1 Main Sites CR will install the compu┆
0x35700…35800 (53, 0, 7) Sector 3400ff00014141 ┆4 AAter racks, supervisor positions and maintenance position in the room designated as the CAMPS equipment room. CR will install all signal cables between racks, between racks and maintenance position, between racks and supervisor positions and betwee┆
0x35800…35900 (53, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(53,0, 9), len=0xff, h3=41014241}, f00=»0142A «, f01=»contract/subsystem CAMPS «, f02=»am] «, f03=»bhb «, f04=»underleverand]rer «, f05=20-08-80 09:33, f06=» 1 «, f07=»26 «, f08=» 3693 «, f09=20-08-80 14:38, f10=» «, f11=»04 «, f12=» 84 «, f13=20-08-80 12:00, f14=20-08-80 16:21, f15=»0014A «, f16=» 4 «, f17=» 1 «, f18=»33 «, f19=» 64 «, f20=» 4007 «, f21=» «, f22=» «, f99=100010000120056610a10a80aaca15050000000000000037031200df}
0x35900…35a00 (53, 0, 9) Sector 350a0400014241 ┆5 BA 5 5 5 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : ┆
0x35a00…35b00 (53, 0, 10) Sector 350b7000014241 ┆5 p BA 1 19800820 # CAMPS 6 C{-! <6 M1' Z -C7-:!<~ B -!/=6'C*-:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x35b00…35c00 (53, 0, 11) Sector 350cff00014241 ┆5 BA 1 to: E-Division/ASM From: CAMPS, S-Division/GJ Subject: Contract for delivery of Subsystems to CAMPS 1 INTRODUCTION This paper gives some preliminary information on t┆
0x35c00…35d00 (53, 0, 12) Sector 350dff00014241 ┆5 BAhe project status and the plans in the CAMPS project. We consider J]rgen Larsen to be our contact person within E-Division on matters concerning the Subsystem delivery contract. Please supply a plan supporting the delivery schedule. 2 ┆
0x35d00…35e00 (53, 0, 13) Sector 350efe00014241 ┆5 ~ BAEQUIPMENT MATRIX 2.1 In order to get the CAMPS system configuration settled and fixed, following activities are conducted: 2.1.1 Negotiations with the purchaser. 2.1.2 Analysis on the CR80D system specifications and the CAMPS requirements. <┆
0x35e00…35f00 (53, 0, 14) Sector 350fff00014241 ┆5 BA 1 2.2 A development contract between CAMPS and E-Division for a DSMT/S-system is planned to be settled before 1. sept. 80. The DSMT/S-system contains the CR80D standard subsystems. Th┆
0x35f00…36000 (53, 0, 15) Sector 1e00ff00014241 ┆ BAis contract will contain the development up to First Article Qualification Test for the following Subsystems: a. Processor Units. b. I/O-unit with disk controllers and LTU's (see section 2.3). 2.3 Appendix A contains a list of items which are t┆
0x36000…36100 (54, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(54,0, 1), len=0xff, h3=41013241}, f00=»0132A «, f01=»R & M programme plans «, f02=»rt «, f03=»LP «, f04=»arbejdsplan «, f05=12-08-80 09:28, f06=» 2 «, f07=»01 «, f08=» 8527 «, f09=22-08-80 09:16, f10=» «, f11=»13 «, f12=» 256 «, f13=22-08-80 09:30, f14=22-08-80 09:49, f15=»0014A «, f16=» 9 «, f17=» 4 «, f18=»26 «, f19=» 196 «, f20=» 11980 «, f21=» «, f22=» «, f99=020010000120056610a10a80aaca15050000000000000030033400df}
0x36100…36200 (54, 0, 1) Sector 36020900013241 ┆6 2A 6 6 " ! ! DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettetet┆
0x36200…36300 (54, 0, 2) Sector 36039d00013241 ┆6 2A 1 CPS/PLN/004 19800812 # R & M PROGRAMME PLANS CAMPS /=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x36300…36400 (54, 0, 3) Sector 3604ff00013241 ┆6 2A 1 1. RELIABILITY DESIGN PLAN 1.1 Quantitative reliability requirements are specified in IFB sec. 4 and in System Requirements, sec. 3.4. Preliminary apportionment have to be compa┆
0x36400…36500 (54, 0, 4) Sector 3605ff00013241 ┆6 2Ared with specified requirements. 1.2 Failure rate sources shall be identified and reviewed, and a complete and thorough definition of "failure" as applied to the equipment shall be developed. Categories of failures that apply to the equipment shall┆
0x36500…36600 (54, 0, 5) Sector 3606ff00013241 ┆6 2A be defined such as catastrophic, critical and non critical. 1.3 Derating policies based on MIL-STD-217C RDH-376: Reliability Design Handbook IPC-ML-910: Design and End product specification for rigid multilager PCB will be performed. 1.4 Pr┆
0x36600…36700 (54, 0, 6) Sector 3607ff00013241 ┆6 2Aediction methods are based on MIL-STD-217C and subdivided in the following two parts which will constitute the Reliability model. 1.4.4 Matematical Models 1.4.2 Blockdiagrams 1.5 ANALYSIS OF THE R-MODEL 1.5.1 Identification of equipment item┆
0x36700…36800 (54, 0, 7) Sector 2200ff00013241 ┆" 2As, quantities and software packages constituing a unit, and the type and quantity of units consistituing a sub-system. 1.5.2 Identify hardware and software elements required for execution and support of each function and assign R-values to appropri┆
0x36800…36900 (54, 0, 8) Sector 3609ff00015141 ┆6 QA 1 B.4 PROCESS SECTION a) This section should contain a single column of process steps. The steps should be sequentially numbered, beginning with 1 as the number of the first step on┆
0x36900…36a00 (54, 0, 9) Sector 360aff00015141 ┆6 QA the first page of an input/output diagram. Substeps should be lettered sequentially. b) There is no maximum to the number of steps per diagram; however, when the number is above the range of 7 to 10, the user has more difficulty comprehending the┆
0x36a00…36b00 (54, 0, 10) Sector 360bff00015141 ┆6 QA material quickly. Putting too many steps or too much detail in the process section is often the cause of a problem. The problem may be corrected by putting some of the information in the extended description section or by subdividing the functions ┆
0x36b00…36c00 (54, 0, 11) Sector 360cff00015141 ┆6 QAinto lower-level input/output diagrams. c) To indicate that a process step is described in further detail in another diagram a box should be drawn around the process step, and the identification number of the lower-level diagram should be placed i┆
0x36c00…36d00 (54, 0, 12) Sector 360dff00015141 ┆6 QAn the lower right-hand corner of the box. d) The content of the process steps varies by development stage, complexity of the process, and intended audience. In general it is best to begin the process statement with the imperative form of a verb, s┆
0x36d00…36e00 (54, 0, 13) Sector 360e0e00015141 ┆6 QAuch as: ue is suggested. When an arrow merges with another arrow, the merging arrow should terminate with an arrowhead; if it crosses another arrow, there should not be an arrowhead at the intersection. k) Data movement or data┆
0x36e00…36f00 (54, 0, 14) Sector 360fff00015141 ┆6 QA 1 1 accept delete get perform select add dequeue handle place set allocate detach identify position simulate alte┆
0x36f00…37000 (54, 0, 15) Sector 3408ff00015141 ┆4 QAr determine increment post specify analyze display initialize process start assign do until insert provide stop begin do while issue purge store build edit locate put supply calculate encode link queue suspend check enqueue load read switch c┆
0x37000…37100 (55, 0, 0) Sector 3701ff00015141 ┆7 QAimum. m) When data is used repeatedly, the following may be done: (1) If a data item is input to several steps, but not output from them, the following alternatives are given: a) Use a single arrow from the data to the steps (which for this┆
0x37100…37200 (55, 0, 1) Sector 3702cd00015141 ┆7 M QA approach be consecutive and grouped by boxing) b) Use a multiple arrow (one tail, several heads) from the data to each step. c) Use a keyed data arrow. These approaches may be combined. tem or data group, and terminate at the number of ┆
0x37200…37300 (55, 0, 2) Sector 3703ff00015141 ┆7 QA 1 (2) If a data item is output from one step and then becomes input to a later step(s): a) Use a single or multiple arrow back from the output data to the later step(s), using a┆
0x37300…37400 (55, 0, 3) Sector 3704ff00015141 ┆7 QA keyed data arrow if necessary. b) Repeat the data on the input side. In this case the reader must be told that the data item is not original input, by adding text (e.g. "created in step 3" or "from step 3") to the data on the input side. The┆
0x37400…37500 (55, 0, 4) Sector 37056700015141 ┆7 g QA first option should be used except where it would cause confusion of arrows in the output path. It is unclear in the first example whether the input was FLDA or all data, or whether the input was for step 1 or 2. uld be shown as a 1 or 0. ┆
0x37500…37600 (55, 0, 5) Sector 3706ff00015141 ┆7 QA 1 (3) If a data item is input to a step that modifies it, and then is input (in its modified form) to a later step(s), the same techniques as in (2) above may be used, but the word ┆
0x37600…37700 (55, 0, 6) Sector 3707ff00015141 ┆7 QA"updated" rather than "created" should be used. Note that the use of the words "created" and "updated" with output data items may be helpful even when they are not used as input later. n) When data shown in the output ar┆
0x37700…37800 (55, 0, 7) Sector 36086700015141 ┆6 g QAea is used as both input and output in the same process step, a double-headed arrow may be used. used for emphasis here. This is particularly useful for overview diagrams. g data items is to indicate that all of the items within the box are include┆
0x37800…37900 (55, 0, 8) Sector 3709ff00015141 ┆7 QA 1 i) Arrows may cross over each other or may join to show that they point to the same process step number. Crossing arrows should be kept to a minimum. Many times they can be avoided┆
0x37900…37a00 (55, 0, 9) Sector 370ad100015141 ┆7 Q QA by rearranging the data items, enclosing data items within a box (data group), leaving space between process steps, or using keyed data arrows (see below). The following example shows crossing arrows. ies that the item contains other fields not re┆
0x37a00…37b00 (55, 0, 10) Sector 370bff00015141 ┆7 QA 1 From the above, a user can tell that the arrow to step 1 is from FLDA and FLDC, and that the arrow to step 2 crosses the other arrow and is from data FLDB. j) It is more difficu┆
0x37b00…37c00 (55, 0, 11) Sector 370c4300015141 ┆7 C QAlt to illustrate crossing arrows with data reference arrows. xtended description). It is often useful to rearrange fields or groups of data items to facilitate a better layout of data related to process steps and avoid the crossing of data movement ┆
0x37c00…37d00 (55, 0, 12) Sector 370dff00015141 ┆7 QA 1 In the above example, FLDC may go to both steps 1 and 2. In order to clarify that the arrow from FLDC goes to step 2, and the arrows from FLDA and FLDC go to step l, the following┆
0x37d00…37e00 (55, 0, 13) Sector 370eff00015141 ┆7 QA technique is suggested. When an arrow merges with another arrow, the merging arrow should terminate with an arrowhead; if it crosses another arrow, there should not be an arrowhead at the intersection. k) Data movement or data┆
0x37e00…37f00 (55, 0, 14) Sector 370fab00015141 ┆7 + QA reference arrows should not point from the process steps to the input area. l) Keyed data arrows are associated by means of the same letter and are of the form: nt-width arrows should be explained in the legend and extended descriptions, as appr┆
0x37f00…38000 (55, 0, 15) Sector 3700ff00015141 ┆7 QA 1 The letters may be circled or boxed. Keyed data arrows are used when multiple arrows in the input and output paths would be confusing to the user. Their use should be kept to a min┆
0x38000…38100 (56, 0, 0) Sector 38018600015141 ┆8 QA associated process step(s). e) The data pointer arrow indicates the address of another data item tion to be placed in that box. 6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x38100…38200 (56, 0, 1) Sector 3802ff00015141 ┆8 QA 1 The arrow may connect the data items: f) A data arrow in the input path should begin at the right-hand edge of a data item or data group, and terminate at the number of ┆
0x38200…38300 (56, 0, 2) Sector 3803ff00015141 ┆8 QAthe process step that uses this item(s). For output it should begin at the right-hand edge of the text for the process step, and terminate at the left-hand edge of a data item or data group in the output section. The beginning of all output arrows m┆
0x38300…38400 (56, 0, 3) Sector 3804a600015141 ┆8 & QAay be aligned. The exception to this is, that arrows may be drawn in such a manner as to prevent crossing text with an arrow. See example on the next page. rrows and updating the data item. Example 3 ket? Bytte med? S]ge hvilket? ┆
0x38400…38500 (56, 0, 4) Sector 3805e500015141 ┆8 e QA 1 It is unclear in the first example whether the input was FLDA or all data, or whether the input was for step 1 or 2. uld be shown as a 1 or 0. ┆
0x38500…38600 (56, 0, 5) Sector 3806a600015141 ┆8 & QA 1 g) Arrows should be as straight as possible so the eye can easily follow them. For example:wn in the extended description or a separate figure to permit easier updating, should the┆
0x38600…38700 (56, 0, 6) Sector 3807ff00015141 ┆8 QA 1 h) If there is only one data movement arrow in a given diagram, it may go from the edge of the entire input section to the edge of the entire process section, and from the edge of ┆
0x38700…38800 (56, 0, 7) Sector 3708b300015141 ┆7 3 QAthe entire process section to the edge of the entire output section. Frequently, a wide arrow is used for emphasis here. This is particularly useful for overview diagrams. g data items is to indicate that all of the items within the box are include┆
0x38800…38900 (56, 0, 8) Sector 3809a800015141 ┆8 ( QAd in the data flow of arrows that touch the edge of this box. The value of placing data items within a data group is to reduce the number of arrows. For example: ┆
0x38900…38a00 (56, 0, 9) Sector 380aff00015141 ┆8 QA 1 c) Only the fields used should be shown in the input. A space left before or after a field in a data item implies that the item contains other fields not re┆
0x38a00…38b00 (56, 0, 10) Sector 380bff00015141 ┆8 QAlevant to this input. A space does not necessarily indicate how many fields have been omitted or their lengths. Also, the ordering of fields within a data item does not necessarily imply the actual order in the record, table, etc. (unless it is a pr┆
0x38b00…38c00 (56, 0, 11) Sector 380cff00015141 ┆8 QAogram dependency, in which case it must be so stated in the extended description). It is often useful to rearrange fields or groups of data items to facilitate a better layout of data related to process steps and avoid the crossing of data movement ┆
0x38c00…38d00 (56, 0, 12) Sector 380df800015141 ┆8 x QAand data reference arrows. B.3 ARROWS a) Arrows are used to indicate either the movement/manipulation of data, or data references/pointers. b) The flow of control is not indicated by arrows but is alone shown in associated flowgrams. ms are ┆
0x38d00…38e00 (56, 0, 13) Sector 380eff00015141 ┆8 QA 1 c) The width of the arrow does not depict a function difference. A wide arrow of a given arrow type may be used for emphasis; two sizes of arrows are shown on the HIPO template. Wh┆
0x38e00…38f00 (56, 0, 14) Sector 380fff00015141 ┆8 QAile the narrow arrow is the one most frequently used, the wide arrow may be used when there is only one arrow in the input and output paths. Any other use of different-width arrows should be explained in the legend and extended descriptions, as appr┆
0x38f00…39000 (56, 0, 15) Sector 3800ff00015141 ┆8 QAopriate. If required, arrows may join each other or may cross over each other, as described later in this section. d) The data movement arrow indicates which data item or group of data items is moved or manipulated, or produced or modified, by the┆
0x39000…39100 (57, 0, 0) WangDocumentBody
[…0x4…]
0x39500…39600 (57, 0, 5) Sector 00000000000000 ┆ ┆
[…0x2…]
0x39800…39900 (57, 0, 8) WangDocumentBody
[…0xb7…]
0x45000…45100 (69, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(69,0, 1), len=0xff, h3=41014841}, f00=»0148A «, f01=»DN's «, f02=»am] «, f03=»gj «, f04=»sys req. spec. «, f05=22-08-80 13:10, f06=» 11 «, f07=»07 «, f08=» 39653 «, f09=23-08-80 18:30, f10=» «, f11=»58 «, f12=» 656 «, f13=23-08-80 20:07, f14=25-08-80 11:28, f15=»0014A «, f16=» 35 «, f17=» 12 «, f18=»14 «, f19=» 816 «, f20=» 40801 «, f21=» «, f22=»:0 «, f99=020033000120056610a10a80aaca1505000000000000003003c500df}
0x45100…45200 (69, 0, 1) WangDocumentBody
[…0x6…]
0x45800…45900 (69, 0, 8) Sector 4509a600015141 ┆E & QA may be labeled. Note that the size of a data item box has no functional significance; it is determined by the amount of information to be placed in that box. 6 !f=6 !g=6 !h=6 Ml+M;) RE3C#4: 2i=:g=~ JV3C/4!"<6 #6 MB&! =6 !,<6 :]=2'< AMD MB&!,<6 ! ┆
0x45900…45a00 (69, 0, 9) Sector 450aff00015141 ┆E QA 1 Example 1 A single data item symbol. This may be a field, register, record, storage area, etc. The label identifies the item and should be the name actually used in the┆
0x45a00…45b00 (69, 0, 10) Sector 450bff00015141 ┆E QA program if one has been assigned. If this is the case, it should be in capital letters. The text can briefly describe the data item. The extended description section may identify important attributes. Example 2 A record with a layout of ┆
0x45b00…45c00 (69, 0, 11) Sector 450cd900015141 ┆E Y QAfields within it, shown several to a line. A record with a layout of fields within it, shown one to a line. This format can facilitate drawing the arrows and updating the data item. Example 3 ket? Bytte med? S]ge hvilket? ┆
0x45c00…45d00 (69, 0, 12) Sector 450dff00015141 ┆E QA 1 A flag block. A data item that has a lenght of one or more bytes. Each of the 8 bits within each byte may be tested or modified. The significant bits should be shown as a 1 or 0. ┆
0x45d00…45e00 (69, 0, 13) Sector 450eff00015141 ┆E QAThe remaining bits should be shown as periods. If a bit may be significant but may be 0 or 1, an X may be used. Preferably, the layout of a flag block is shown in the extended description or a separate figure to permit easier updating, should the┆
0x45e00…45f00 (69, 0, 14) Sector 450fff00015141 ┆E QA contents change. Example 4 External devices. The standard flowchart symbols may be used to depict external media such as cards, documents, tape, online storage, and display devices. When physical device dependency is not important┆
0x45f00…46000 (69, 0, 15) Sector 3808ff00015141 ┆8 QA or does not exist, a data item symbol should be used. b) A data group is one or more of the data items discussed above which are enclosed in a box. The purpose of grouping data items is to indicate that all of the items within the box are include┆
0x46000…46100 (70, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(70,0, 1), len=0xff, h3=41015141}, f00=»0151A «, f01=»SOFTWARE DOC. STANDARD «, f02=»vhn «, f03=»SVO «, f04=»APPENDIX B «, f05=25-08-80 11:13, f06=» «, f07=»11 «, f08=» 193 «, f09=25-08-80 13:44, f10=» «, f11=»01 «, f12=» 19 «, f13=21-10-80 13:01, f14=21-10-80 15:25, f15=»0014A «, f16=» 23 «, f17=» «, f18=»12 «, f19=» 172 «, f20=» 212 «, f21=» «, f22=» «, f99=220010000120056610a10a80aaca15050000000000000037034400df}
0x46100…46200 (70, 0, 1) Sector 46021700015141 ┆F QA F F F E E 8 8 8 8 8 8 7 7 7 7 7 7 6 6 4 4 4 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S┆
0x46200…46300 (70, 0, 2) Sector 4603a500015141 ┆F % QA 1 SD/STD/008 SVO/800814 B-# SOFTWARE DOCUMENTATION STANDARD DRAFT GENERAL /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x46300…46400 (70, 0, 3) Sector 46047200015141 ┆F r QA 1 APPENDIX B HIPO CHARTS STANDARD :^=~ B~.> IMB'IM2& 9x2"<!Z="(=^#Vk"$<:]=2#<:^=~ J6.! <6 M8) R6.> I! <6 M8)I!h=6 ! =6 M")IM"):g=~ J /:h=2>=M?.Mj': < Zn.C / E*:=k 0wM% !;=4C┆
0x46400…46500 (70, 0, 4) Sector 4605ff00015141 ┆F QA 1 B.1 GENERAL FORMAT - The HIPO Worksheet should be used. - Input/output diagrams limited to one page are more readable than multiple-page diagrams. If multiple page diagrams are ┆
0x46500…46600 (70, 0, 5) Sector 4606ff00015141 ┆F QAused, the process steps should be numbered sequentially throughout the diagram. - Each diagram should contain certain information for identification. The HIPO Worksheet provides a heading for the following information: - The name of the process┆
0x46600…46700 (70, 0, 6) Sector 4607ff00015141 ┆F QA being documented - The number of the document in which the diagram is appearing - The issue number of the document - The diagram identification (which should correspond to the one used in the overview chart) - The diagram revision numbe┆
0x46700…46800 (70, 0, 7) Sector 4508ff00015141 ┆E QAr (consecutive numbering) - The date - The page number in the document. B.2 DATA ITEMS AND DATA GROUPS a) The following are examples of data items that may be shown within the input or output section of an input/output diagram. The items┆
0x46800…46900 (70, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(70,0, 9), len=0xff, h3=41015241}, f00=»0152A «, f01=»SOFTWARE DOC. STANDARD «, f02=»vhn «, f03=»SVO «, f04=»APPENDIX A «, f05=25-08-80 14:57, f06=» «, f07=»06 «, f08=» 181 «, f09=21-10-80 13:55, f10=» «, f11=»00 «, f12=» 2 «, f13=21-10-80 12:19, f14=21-10-80 15:37, f15=»0014A «, f16=» 12 «, f17=» «, f18=»23 «, f19=» 200 «, f20=» 449 «, f21=» «, f22=» «, f99=110010000120056610a10a80aaca15050000000000000037034000df}
0x46900…46a00 (70, 0, 9) Sector 460a0c00015241 ┆F RA F F F 2 1 1 1 0 0 / / , , DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S┆
0x46a00…46b00 (70, 0, 10) Sector 460ba500015241 ┆F % RA 1 SD/STD/008 SVO/800814 A-# SOFTWARE DOCUMENTATION STANDARD DRAFT GENERAL /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x46b00…46c00 (70, 0, 11) Sector 460cff00015241 ┆F RA 1 APPENDIX A 1 1. GENERAL a. Purpose Statement b. Project References c. Terms and Abbreviations ┆
0x46c00…46d00 (70, 0, 12) Sector 460dff00015241 ┆F RA 2. SUMMARY OF REQUIREMENTS a. Program Description b. Program Functions c. Accuracy and Validity d. Timing e. Flexibility 3. ENVIRONMENT a. Support Software Environment b. Interfaces c. Storage d. Security e. Co┆
0x46d00…46e00 (70, 0, 13) Sector 460eff00015241 ┆F RAntrols 4. DESIGN DETAILS a. Program Operating Procedures b. Inputs c. Outputs d. Data Environment e. Storage Allocation f. Data Retention g. Program Relationships h. Program Logic TABLE A.1 1 ┆
0x46e00…46f00 (70, 0, 14) Sector 460ff500015241 ┆F u RA The above table lists all the sections into which the content of a software module (program) specification shall be organized. The following contains a description of the content of each section. (sM &M7 ┆
0x46f00…47000 (70, 0, 15) Sector 3200ff00015241 ┆2 RA 1 A.1 GENERAL a) Purpose Statement. Describe the purpose of the Program Specification (PS) using the following as a guide: The objective of this Program Specification for (Projec┆
0x47000…47100 (71, 0, 0) Sector 4701ff00014141 ┆G AAo site and installation arrangement with site. - inspection of main site and remote terminal location. - documentation incl. correction of A-T-B-B drawings. - correspondence with CR, Denmark. - accomodation arrangements and transportation (p┆
0x47100…47200 (71, 0, 1) Sector 47029900014141 ┆G AAersonnel and equipment). - inventory check. - log book. - site tests (M & D software). - interface to local COMSEC and other authorities. Bg4M73~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x47200…47300 (71, 0, 2) Sector 4703ff00014141 ┆G AA 1 The team member A will be responsible for: - power and power connections - rack integration - mechanics - cables and cabling The team member B will be responsible for: ┆
0x47300…47400 (71, 0, 3) Sector 4704ff00014141 ┆G AA- terminal equipment and interfaces - test of equipment - OPTO-installations 2.3 SECURITY CLEARANCE OF INSTALLATION PERSONNEL During the site surveys CR was informed that special clearance (other than NATO secret) was required for some inst┆
0x47400…47500 (71, 0, 4) Sector 4705a500014141 ┆G % AAallation areas. (Refer to each site survey report). SHAPE should investigate this and clarify the required security clearance for CR personnel at each site. u Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x47500…47600 (71, 0, 5) Sector 4706a100014141 ┆G ! AA 1 FIGURE 2.2 (CAMPS INSTALLATION TEAM) rning site preparation and installation. It describes how CR intends to manage and perform th┆
0x47600…47700 (71, 0, 6) Sector 4707ff00014141 ┆G AA 1 3 SITE PREPARATION AND INSTALLATION RESPONSIBILITIES The following outlines CR's and SHAPE's/Host Nations responsibilities concerning site preparation and installation. An at┆
0x47700…47800 (71, 0, 7) Sector 3500ff00014141 ┆5 AAtempt has been made to translate the requirements of the contract into specific installation tasks to be performed by each organization. The remote terminals have not yet been surveyed and some installation responsibilities concerning these instal┆
0x47800…47900 (71, 0, 8) Sector 4709ff00014141 ┆G AA]r P.A. Bakkejord A/S (PAB) to perform the following tasks on the CAMPS program: 1. Site Survey 2. Site Civil Engineering Requirements 3. As Built Drawings 4. Site Verification Under supervision by Logistics Department PAB will ensure that┆
0x47900…47a00 (71, 0, 9) Sector 470aff00014141 ┆G AA SHAPE will provide sufficient and timely information to enable delivery to SHAPE of items 2 and 3 above. PAB will act as contractor's representative in relation to SHAPE in the following areas: 1. Obtain necessary information from SHAPE to gener┆
0x47a00…47b00 (71, 0, 10) Sector 470bb900014141 ┆G 9 AAate Civil Works Requrements and As Built Drawings. 2. Submit Civil Works Requirements and As Built Drawings to SHAPE. Update these if necessary. 3. Perform Site Verification. 6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x47b00…47c00 (71, 0, 11) Sector 470ca700014141 ┆G ' AA 1 FIGURE 2.1 CAMPS INSTALLATION ORGANIZATION. SCOPE AND PURPOSE .......................... 5 2 ORGANIZATION ..................┆
0x47c00…47d00 (71, 0, 12) Sector 470dff00014141 ┆G AA 1 2.2 INSTALLATION The installation of CAMPS will be performed by 2 teams. Each team will install a complete site. The organization of the CAMPS installation team is shown on figu┆
0x47d00…47e00 (71, 0, 13) Sector 470eff00014141 ┆G AAre 2.2 Each team will be composed of a teamleader and 2 installation technicians. As a back up 2 technicians will be available at CR's plant to relieve a team member in case of sickness, vacation etc. The back-up will also be used for the install┆
0x47e00…47f00 (71, 0, 14) Sector 470fff00014141 ┆G AAation of some of the mainsites with more than one remote terminals location connected, and for some of the remote TARE sites located far away from the mainsites. The team will be organized so that each member will be responsible for specific tasks┆
0x47f00…48000 (71, 0, 15) Sector 4700ff00014141 ┆G AA, within the installation program; but all will be trained in the whole program so they are able to substitute each other if necessary. The team leader will be responsible for: - day by day organization of the installation tasks. - interface t┆
0x48000…48100 (72, 0, 0) Sector 4801ff00014141 ┆H AASTALLATION ............................... 26 6.1 PREPARATION OF INSTALLATION ............ 26 6.2 INSTALLATION TASK SCHEDULE ............. 26 6.3 SHIPMENT OF EQUIPMENT .................. 26 6.4 INSTALLATION AT REMOTE LOCATIONS ....┆
0x48100…48200 (72, 0, 1) Sector 48027800014141 ┆H x AA... 27 6.5 INSTALLATION PHASE ACTIVITIES .......... 27 6.6 DOCUMENTATION .......................... 31 J 4Cq5M")IMy,M1' R 4 'M, CV4:g=~ Bg4M73~ B)4Cq5! ="(=*(=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x48200…48300 (72, 0, 2) Sector 4803ff00014141 ┆H AA 1 LIST OF FIGURES 2.1 CAMPS INSTALLATION ORGANIZATION ........ 6 2.2 CAMPS INSTALLATION TEAM ................ 9 3.1 TYPICAL CAMPS ROOM LAYOUT .............. 13 3.2┆
0x48300…48400 (72, 0, 3) Sector 4804ff00014141 ┆H AA CABLE CONNECTIONS AT A TYPICAL MAIN SITE. 14 3.3 TYPICAL COMMUNICATION LINK TO REMOTE TERMINALS .............................. 17 4.1 SITE IMPLEMENTATION PLAN ............... 19 6.1 INSTALLATION PHASE ACTIVITY AT A ┆
0x48400…48500 (72, 0, 4) Sector 48053700014141 ┆H 7 AA TYPICAL SITE ........................... 31 ser Funktion annulleret Ukendt kommando JA eller ANNULLER Kun tal Kun mellemrum eller retur Under redigering nu Ukendt dokument Fundet I brug nu Allerede p> systemdiskette ┆
0x48500…48600 (72, 0, 5) Sector 4806ff00014141 ┆H AA 1 1 SCOPE AND PURPOSE This plan outlines the various tasks to be accomplished concerning site preparation and installation. It describes how CR intends to manage and perform th┆
0x48600…48700 (72, 0, 6) Sector 4807ff00014141 ┆H AAe job and outlines the responsibilities of CR and SHAPE/host nation concerning installation. Milestones of the site implementation schedule have been identified and an analysis of the site installation task is performed. 2 ORGANIZATION Si┆
0x48700…48800 (72, 0, 7) Sector 4708ff00014141 ┆G AAte preparation and installation is a functional section within the Logistic Department. Figure 2.1 shows the installation organization. 2.1 SITE PREPARATION AND VERIFICATION The Systems Division has contracted with a Norwegian company, Ingeni┆
0x48800…48900 (72, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(72,0, 9), len=0xff, h3=41010741}, f00=»0107A «, f01=»CONF. MAN. STAND. MANUAL «, f02=»VHN «, f03=»SVO SD/STD/006 «, f04=»FRA 0081A «, f05=28-07-80 14:45, f06=» «, f07=»07 «, f08=» 267 «, f09=19-09-80 12:25, f10=» «, f11=»01 «, f12=» 10 «, f13=19-09-80 12:32, f14=19-09-80 12:51, f15=»0014A «, f16=» 4 «, f17=» 1 «, f18=»19 «, f19=» 72 «, f20=» 2817 «, f21=» «, f22=» «, f99=020030000120056610a10a80aaca15050000000000000037031700df}
0x48900…48a00 (72, 0, 9) WangDocumentBody
[…0x6…]
0x49000…49100 (73, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(73,0, 1), len=0xff, h3=41014141}, f00=»0141A «, f01=»Installation Plan «, f02=»kk «, f03=»KM «, f04=»CPS/PLN/005 «, f05=18-08-80 12:17, f06=» 2 «, f07=»20 «, f08=» 9536 «, f09=26-09-80 12:49, f10=» «, f11=»08 «, f12=» 92 «, f13=26-09-80 13:27, f14=26-09-80 13:53, f15=»0014A «, f16=» 30 «, f17=» 18 «, f18=»52 «, f19=» 468 «, f20=» 34371 «, f21=» «, f22=» «, f99=020030000120056610a10a80aaca15050000000000000030038600df}
0x49100…49200 (73, 0, 1) Sector 49021e00014141 ┆I AA I I H H G G G G G 5 4 3 3 3 3 / / / / . . . - - - , * ) ) ) ) ┆
0x49200…49300 (73, 0, 2) Sector 49039300014141 ┆I AA 1 CPS/PLN/005 19800926 # CAMPS INSTALLATION PLAN CAMPS -:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x49300…49400 (73, 0, 3) Sector 4904ff00014141 ┆I AA 1 1 TABLE OF CONTENTS 1 SCOPE AND PURPOSE .......................... 5 2 ORGANIZATION ..................┆
0x49400…49500 (73, 0, 4) Sector 4905ff00014141 ┆I AA............. 5 2.1 SITE PREPARATION AND VERIFICATION ...... 5 2.2 INSTALLATION ........................... 7 2.3 SECURITY CLEARANCE OF INSTALLATION PERSONNEL .............................. 8 3 SITE PREPARATION AND INSTAL┆
0x49500…49600 (73, 0, 5) Sector 4906ff00014141 ┆I AALATION RESPONSIBILITIES ........................... 10 3.1 SITE PREPARATION AND VERIFICATION ...... 10 3.2 INSTALLATION ........................... 11 3.2.1 Main Sites ......................... 11 3.2.2 Remote Tares ........┆
0x49600…49700 (73, 0, 6) Sector 4907ff00014141 ┆I AA............... 12 3.2.3 Remote Terminals ................... 15 4 SITE IMPLEMENTATION PLAN ................... 18 5 SITE PREPARATION AND VERIFICATION .......... 21 5.1 SITE PREPARATION ....................... 21 5.2 SITE SURVEY┆
0x49700…49800 (73, 0, 7) Sector 4800ff00014141 ┆H AAS AND SITE VISITS ........... 22 5.3 CIVIL ENGINEERING REQUIREMENTS (CER) ... 22 5.4 AS-TO-BE-BUILT DRAWINGS ................ 24 5.5 DELIVERY OF SIGNAL CABLES .............. 24 5.6 SITE VERIFICATION ...................... 25 6 IN┆
0x49800…49900 (73, 0, 8) Sector 4909ff00008541 ┆I A number of subfunctions d) defines the structure of the control flow within the unit. e) defines the interaction which the unit must have with other units f) produces documentation of the unit g) defines input to and output from the unit h┆
0x49900…49a00 (73, 0, 9) Sector 490aff00008541 ┆I A) defines data to be used in the unit i) defines the test(s) to be necessary to verify the design. No specific methodology will be prescribed for the design process except as follows: a) The resulting documentation must comply to standard and ┆
0x49a00…49b00 (73, 0, 10) Sector 490be600008541 ┆I f Afit into the hierarchical structure. b) The material produced must be kept in accordance with the UDF standard c) The following guidelines shall be considered seriously and be followed to the largest possible extend. ! <6 M&&:!<~ J#.:!<2.=M2┆
0x49b00…49c00 (73, 0, 11) Sector 490cff00008541 ┆I A 1 3.3 TOP DOWN DESIGN Software Design shall proceed in a top down manner, that is, the overall aspects of the product shall be processed first, continuing with succesive steps proce┆
0x49c00…49d00 (73, 0, 12) Sector 490dff00008541 ┆I Assing an increasing level of details in each step. 3.3.1 Hierarchical Structure The design shall result in a split of the product into a number of units (modules). Interrelations between units shall be defined in such a way that the system can ┆
0x49d00…49e00 (73, 0, 13) Sector 490eff00008541 ┆I Abe described as a treelike hierarchical structure as the example shown in fig. 1. The number of levels in the hierarchy shall be as many as necessary to give a clear and understandable description of the system, with units which can be described i┆
0x49e00…49f00 (73, 0, 14) Sector 490fff00008541 ┆I An independent entities of documentation of reasonable size. The lowest level of the tree shall represent units which are to be coded as separate code units and the description of those units must be detailed enough to be used as direct input for c┆
0x49f00…4a000 (73, 0, 15) Sector 2508ff00008541 ┆% Aoding. All interaction between two branches must be defined within the unit where the branches meet. No interaction is allowed at lower levels. 3.3.2 Level by Level Documentation Each unit shall be designed as an independent entity. The onl┆
0x4a000…4a100 (74, 0, 0) Sector 4a01ff00008541 ┆J A General ............................. 16 3.6.2 Credibility Check ................... 16 3.6.3 Traceability Counters ............... 17 3.6.4 Checksum ............................ 17 3.7 VERIFICATION ............................. 17 ┆
0x4a100…4a200 (74, 0, 1) Sector 4a02af00008541 ┆J / A 3.7.1 Verifiable Design .................... 18 3.7.2 Definition of Verification ........... 18 1 (=N#FMC 2.=M ':>=V V u:A=!>= AH1 R^4 ]M, C 4:>=2A=Ms!:g=~ Jr4Mj2:g=~ B}4C75! ┆
0x4a200…4a300 (74, 0, 2) Sector 4a03ff00008541 ┆J A 1 1 SCOPE This standard is a derivative of software standard manual SD/STM/003 and has the same scope and applicability. 2 PURPOSE The purpose of this standard is┆
0x4a300…4a400 (74, 0, 3) Sector 4a04ff00008541 ┆J A to define a series of aspects of software design which is critical for the attainment of reliable software and therefore must be considered carefully by software designers. 3 DESIGN GUIDELINES 3.1 DEFINITION Software design can be d┆
0x4a400…4a500 (74, 0, 4) Sector 4a05ff00008541 ┆J Aefined as a process in which the requirements of a software product is transformed into a description of software which will actually be able to perform the required functions. The outcome of this transformation shall be a set of documents which c┆
0x4a500…4a600 (74, 0, 5) Sector 4a066200008541 ┆J b Aan be utilized directly as the input for the programmers who shall implement the software. ┆
0x4a600…4a700 (74, 0, 6) Sector 4a07ff00008541 ┆J A 1 The produced documentation must be complete except for general information on such items as programing language compiler/assembler hardware other development tools 3.2 ┆
0x4a700…4a800 (74, 0, 7) Sector 4908ff00008541 ┆I ATHE DESIGN PROCESS The design of a unit shall be a process in which the designer performs at least the following functions: a) evaluates the input b) defines the functions to be performed by the unit c) defines a split of the function into a┆
0x4a800…4a900 (74, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(74,0, 9), len=0xff, h3=41008541}, f00=»0085A «, f01=»Software. design guidel. «, f02=»vhn «, f03=»SVO «, f04=»SD/STD/005 «, f05=04-06-80 09:23, f06=» 3 «, f07=»10 «, f08=» 8823 «, f09=29-10-80 08:56, f10=» «, f11=»01 «, f12=» 7 «, f13=29-10-80 08:58, f14=29-10-80 10:09, f15=»0014A «, f16=» 16 «, f17=» 10 «, f18=»01 «, f19=» 284 «, f20=» 25335 «, f21=» «, f22=» «, f99=990030000120056610a10a80aaca15050000000000000030035900df}
0x4a900…4aa00 (74, 0, 9) Sector 4a0a1000008541 ┆J A J J J J I % % % % DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettretttt┆
0x4aa00…4ab00 (74, 0, 10) Sector 4a0b9300008541 ┆J A 1 SD/STD/005 801020 # SOFTWARE DESIGN GUIDELINE GENERAL -:!<~ B%-!/=6WC*-!/=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4ab00…4ac00 (74, 0, 11) Sector 4a0cff00008541 ┆J A 1 TABLE OF CONTENTS 1 SCOPE ....................................... 4 2 PURPOSE ..................................... 4 3 DESIGN GUIDELINES ..........................┆
0x4ac00…4ad00 (74, 0, 12) Sector 4a0dff00008541 ┆J A. 4 to 18 3.1 DEFINITION ............................... 4 3.2 THE DESIGN PROCESS ....................... 5 3.3 TOP DOWN DESIGN .......................... 6 3.3.1 Hierarchical Structure ............... 6 3.3.2 Level by Level Docume┆
0x4ad00…4ae00 (74, 0, 13) Sector 4a0eff00008541 ┆J Antation ......... 6 3.3.3 Final Documentation .................. 8 3.3.4 Elementary Processes ................. 8 3.4 STRUCTURED DESIGN ........................ 9 3.4.1 Control Structures ................... 9 3.4.2 Modularity ..┆
0x4ae00…4af00 (74, 0, 14) Sector 4a0fff00008541 ┆J A......................... 11 3.4.2.1 Module Strength .................. 11 3.4.2.2 Module Coupling .................. 13 3.4.2.3 Reference ........................ 14 3.5 OTHER MEASURES ............................15 3.5.1 Simplic┆
0x4af00…4b000 (74, 0, 15) Sector 4a00ff00008541 ┆J Aity .......................... 15 3.5.2 Visibility .......................... 15 3.5.3 Module Size ......................... 15 3.5.4 Common Subfunctions ................. 16 3.6 ACTIVE DEFENSIVE MEASURES ................ 16 3.6.1 ┆
0x4b000…4b100 (75, 0, 0) WangDocumentHead {hdr=WangSectHead {next=(75,0, 1), len=0xff, h3=41015241}, f00=»0152A «, f01=»SOFTWARE DOC. STANDARD «, f02=»vhn «, f03=»SVO «, f04=»APPENDIX A «, f05=25-08-80 14:57, f06=» «, f07=»06 «, f08=» 181 «, f09=20-10-80 14:55, f10=» «, f11=»08 «, f12=» 82 «, f13=25-08-80 15:35, f14=20-10-80 17:00, f15=»0014A «, f16=» 12 «, f17=» «, f18=»23 «, f19=» 216 «, f20=» 447 «, f21=» «, f22=» «, f99=100010000120056610a10a80aaca15050000000000000037034000df}
0x4b100…4b200 (75, 0, 1) Sector 4b020c00015241 ┆K RA K K K 2 1 1 1 0 0 / / , , DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S┆
0x4b200…4b300 (75, 0, 2) Sector 4b03a500015241 ┆K % RA 1 SD/STD/008 SVO/800814 A-# SOFTWARE DOCUMENTATION STANDARD DRAFT GENERAL /=6)M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4b300…4b400 (75, 0, 3) Sector 4b04ff00015241 ┆K RA 1 APPENDIX A 1 1. GENERAL a. Purpose Statement b. Project References c. Terms and Abbreviations ┆
0x4b400…4b500 (75, 0, 4) Sector 4b05ff00015241 ┆K RA 2. SUMMARY OF REQUIREMENTS a. Program Description b. Program Functions c. Accuracy and Validity d. Timing e. Flexibility 3. ENVIRONMENT a. Support Software Environment b. Interfaces c. Storage d. Security e. Co┆
0x4b500…4b600 (75, 0, 5) Sector 4b06ff00015241 ┆K RAntrols 4. DESIGN DETAILS a. Program Operating Procedures b. Inputs c. Outputs d. Data Environment e. Storage Allocation f. Data Retention g. Program Relationships h. Program Logic TABLE A.1 1 ┆
0x4b600…4b700 (75, 0, 6) Sector 4b07f500015241 ┆K u RA The above table lists all the sections into which the content of a software module (program) specification shall be organized. The following contains a description of the content of each section. (sM &M7 ┆
0x4b700…4b800 (75, 0, 7) Sector 3200ff00015241 ┆2 RA 1 A.1 GENERAL a) Purpose Statement. Describe the purpose of the Program Specification (PS) using the following as a guide: The objective of this Program Specification for (Projec┆
0x4b800…4b900 (75, 0, 8) WangDocumentHead {hdr=WangSectHead {next=(75,0, 9), len=0xff, h3=41026641}, f00=»0266A «, f01=»Softw.Subs.Docum. Stand. «, f02=»kk «, f03=»SVO «, f04=» «, f05=20-10-80 15:09, f06=» «, f07=»21 «, f08=» 528 «, f09= - - : , f10=» «, f11=» «, f12=» «, f13= - - : , f14=20-10-80 17:03, f15=»0014A «, f16=» 4 «, f17=» «, f18=»21 «, f19=» 36 «, f20=» 528 «, f21=» «, f22=» «, f99=020010000220056610a10a80aaca15050000000000000037030e00df}
0x4b900…4ba00 (75, 0, 9) Sector 4b0a0400026641 ┆K fA K K 2 2 2 DOKUMENTOVERSIGT Dokument nr: Dokumentnavn: Operat]r: Forfatter: Kommentarer: STATISTIK AKTIVITET DATO TID ANV.TID ANSLAG Oprettet / / : : S┆
0x4ba00…4bb00 (75, 0, 10) Sector 4b0ba800026641 ┆K ( fA 1 SD/STD/0013 SVO/801020 # SOFTWARE SUBSYSTEM DOCUMENTATION STANDARD GENERAL )M2&*/=MM, > I!e=6 !Z="(=e*$<kas#r 9x2"<! <6 M8)I:^=~ B#.!#<6 ! <6 M&&:!<~ J#.:!<2.=M2┆
0x4bb00…4bc00 (75, 0, 11) Sector 4b0cff00026641 ┆K fA 1 1 SCOPE This standard is a derivative of software standard man- ual SD/STM/003 and has the same scope and applicability. 2 PURPOSE This standard describes the organi┆
0x4bc00…4bd00 (75, 0, 12) Sector 4b0dff00026641 ┆K fAsation and layout to be used for documents containing specification of Software subsystems. 3 ORGANIZATION 3.1 SYNOPSIS The content of Software module specifications shall be organized as described in NATO's ADP standard 007-3 annex D┆
0x4bd00…4be00 (75, 0, 13) Sector 4b0eff00026641 ┆K fA. This standard is found as Appendix A 3.1.2 Tayloring of Synopsis Software modules may vary considerably in size, complexity and content, therefore, this synopsis may need some tayloring to adapt it to the actual case. Some of the paragraphs┆
0x4be00…4bf00 (75, 0, 14) Sector 4b0fff00026641 ┆K fA in the synopsis may be redundant as no information exists which fits in them. They shall be kept in the Table of Contents but marked "Not Applicable". Information may exist which does not fit directly into any paragraph. In this case an interpr┆
0x4bf00…4c000 (75, 0, 15) Sector 32089b00026641 ┆2 fAetation of the synopsis must be made to find the best fit. Invention of new paragraphs or rearranging shall be avoided unless absolutely necessary. *8=k L<M% :8=F 28=I!#<:"<>R<2> I E*#<& "< DM L<M% :#<F 2#<> I:g= Ro2M/2 Rl2> IC13!?=4~~ B|2> I:A=!┆
0x4c000…4c100 (76, 0, 0) Sector 00000000000000 ┆ ┆
[…0xf…]
