AETL-IM (25-1a)
MEMORANDUM FOR CINCUSAREUR, AEAIM-AR-AA, APO 09403
SUBJECT: Staffing of draft USAREUR Pamphlet 25-DOCSTDS, Documentation Requirements for Automated Information System
1. Reference.
a. AR 25-1. Army Information Resources Management Program.
b. DA Pam 25-1. Army Information Architecture.
c. Annual HQDA Information Management Planning Guidance, 27 Jan 88.
d. 32d AADCOM Memorandum, AETL-RM-IM, Subject: USAREUR Information Management Program, Data Administration, dtd 14 Apr 89.
e. USAREUR Memorandum, AEAIM-AR-AA, SAB, dated 12 Jun 90.
2. Recommended changes to the regulation are submitted on attached DA Form 2028.
3. POC, this headquarters is Mr. Roy Roebuck, 348-6533/7155.
FOR THE COMMANDER:
Encl YOLANDA K. CRIDER
Captain, AG
Assistant Adjutant General
16 Aug 90
1 of 4
CINCUSAREUR COMMANDER, 32d AADCOM
ATTN: AEAIM-AR-AA ATTN: AETL-IM
APO 09403 APO 09175
Documentation Requirements
DRAFT USAREUR PAMPHLET 8 JUN 90 for Automated Information
25-DOCSTD Systems
| Summary. | This document, like its DoD counterpart, is inadequately integrated with the life cycle management process of automated information systems (AIS) as defined in AR 25-3, and with the information engineering process, as outlined in AR 25-1, DA Pam 25-1, and HQDA IM Planning Guidance. The document at enclosure 1 is a suggested approach to integrate these activities at all levels of the Army. The enclosure could be incorporated into this pamphlet, or issued as a separate circular or pamphlet. Put this publication into a hypertext format and issue it in a read-only fashion or extendable fashion to all MSC and DOIM/CDOIM. The hypertext will facilitate the learning and application of this information. Enclosure 1 could be used as a base framework for this hypertext publication. If a hypertext publication is not accepted, then include detailed references within this publication to its higher level publications, at the location where the reference information applies. |
| Applicability, Para a. | A standard similar to this document needs to be applied at the SUBMACOM/MSC level of USAREUR for their internal Class VI development. |
ROY E. ROEBUCK III 348-6533
GS 12
16 Aug 90
2 of 4
CINCUSAREUR COMMANDER, 32d AADCOM
ATTN: AEAIM-AR-AA ATTN: AETL-IM
APO 09403 APO 09175
Documentation Requirements
DRAFT USAREUR PAMPHLET 8 JUN 90 for Automated Information
25-DOCSTD Systems
| This publication leaves too much leeway in the MSC hands, which will inevetiably perpetuate the near lack of documentation below the MACOM level. A note on the minimum applicable standards for MSC could be included as a footnote throughout the publication, as an appendix, or as a separate publication. |
| Applicability, Para b. | Change to read: ... developing single user or multiuser software on microcomputers, network workstations or terminals, network servers, or host computers .... |
| CONTENTS, Section IV | Divide the Documentation Types into Management Documentation and Technical Documentation Categorites to correspond with AR 25-3. |
| Para 2b. | Define the role of MSC functional proponents vis-a-vis MACOM functional proponents it relationship to the AIS documentation/development process. |
| Para 2c. | Define Initiator of AIS in relationship to MSC/MACOM functional responsibilities versus User responsibilities. Differentiate between User, End-User, Operator, and Functional Proponent. A User could be the MSC/MACOM functional proponent, but the End-User could not. |
16 Aug 90
3 of 4
CINCUSAREUR COMMANDER, 32d AADCOM
ATTN: AEAIM-AR-AA ATTN: AETL-IM
APO 09403 APO 09175
Documentation Requirements
DRAFT USAREUR PAMPHLET 8 JUN 90 for Automated Information
25-DOCSTD Systems
| Para 6a(1) | Change to read: ... - to remain within that organization or office. |
| Para 6a(2) | Change to read: Providing an organizational activity, (e.g., USAREUR MSC, etc.) with automated information system support - to remain within that organizational activity. |
| Para 6b | Add: Para 6b(4) On a Local Area Network, Facility Area Network, Community Area Network, or Wide Area Network, which could encompass all of those types of computer systems identified in the preceeding three subparagraphs. |
| Para 39b | Define Sustaining Base in relation to: garrison/installation/MILCOM Combat Support/Combat Service Support Peace, Transition, War Internal to Theater, External to Theater. |
| Para 43 | The portions of this paragraph that relate to individual purchase contracts are not appropriate to this |
16 Aug 90
4 of 4
CINCUSAREUR COMMANDER, 32d AADCOM
ATTN: AEAIM-AR-AA ATTN: AETL-IM
APO 09403 APO 09175
Documentation Requirements
DRAFT USAREUR PAMPHLET 8 JUN 90 for Automated Information
25-DOCSTD Systems
| publication. Copyrights would relate to this publication only in terms of individual development of software. |
| Para 44 | The contents of this paragraph need to be reconciled with UR 25-1 and UR 380-380. This paragraph needs to include End-User development documentation standards. This is the most potentially wasteful area of development if some standards are not developed, taught, and applied. These standards should apply to all interpreted programs such as spreadsheet, dBase III applications, Word Processing Templates, form designer/fillers, GWBasic, etc. |
| All Appendices | Rather than duplicate so much information that is contained in DoD-Std 7935a, only supplement where more information is needed, or waive where the standard is not applicable. This would same much paper, and reduce the potential for inconsistency. |
| Appendix G | Since the Functional Description requires inclusion of Data Flow Diagrams and the logical data models for the AIS, specify that a CASE analysis and data modeling tool may be used. Specify the symbol sets that must be used for the DFD and logical data model (e.g., Yourdon, Gane and Sarson, etc.) |