ARMY MIL-PRF-49503 C-2013 GENERAL STYLE AND FORMAT TEST PROGRAM SETS FOR AUTOMATIC TEST EQUIPMENT.pdf

《ARMY MIL-PRF-49503 C-2013 GENERAL STYLE AND FORMAT TEST PROGRAM SETS FOR AUTOMATIC TEST EQUIPMENT.pdf》由会员分享，可在线阅读，更多相关《ARMY MIL-PRF-49503 C-2013 GENERAL STYLE AND FORMAT TEST PROGRAM SETS FOR AUTOMATIC TEST EQUIPMENT.pdf（81页珍藏版）》请在麦多课文档分享上搜索。

1、NOT MEASUREMENT SENSITIVE MIL-PRF-49503C (MI) 18 July 2013 - SUPERSEDING MIL-PRF-49503B(TM) NOTICE 1 18 March 2013 PERFORMANCE SPECIFICATION GENERAL STYLE AND FORMAT, TEST PROGRAM SETS FOR AUTOMATIC TEST EQUIPMENT This specification is approved for use by the Department of the Army, and is available

2、 for use by all Departments and Agencies of the Department of Defense. . l. SCOPE 1.1 Purpose. This specification contains the requirements for the preparation of operator instructions and operational features required in Test Program Sets (TPS) for all equipment. 1.2 Applicability. Generally, each

3、item specified herein will be included in the test program (TP) unless the item is not applicable to the particular equipment or an exception has been granted by the contracting activity. Additional information and instructions deemed necessary for a specific item of equipment, but not specified her

4、ein, will be included in the test program for that item of equipment, if authorized by the contracting activity. 1.3 Examples/figures. The figures used in this specification are examples only. The text of this specification takes precedence over examples. Comments, suggestions, or questions on this

5、document should be addressed to U.S. Army Research distribution is unlimited. Reinstated after 18 July 2013 and maybe used for new and existing design and acquisitions. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-49503C (MI) 2 2. APPLICAB

6、LE DOCUMENTS. 2.1 General. The documents listed in this section are specified in section 3 of this specification. This section does not include documents cited in other sections of this specification or recommended for additional information or as examples. While every effort has been made to ensure

7、 the completeness of this list, document users are cautioned that they must meet all specified requirements documents cited in section 3 of this specification, whether or not they are listed. 2.2 Government documents. 2.2.1 Standards. The following standards form a part of this document to the exten

8、t specified herein. Unless otherwise specified, the issues of these documents are cited in the solicitation or contract. STANDARDS DEPARTMENT OF DEFENSE MIL-STD-38784 Manuals, Technical: General Style and Format Requirements MIL-STD-1472 Human Engineering (Copies of these documents are available onl

9、ine at http:/assist.dla.mil/quicksearch/ or from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094.) 2.3 Non-Government publications. The following documents form a part of this document to the extent specified herein. Unless otherwise specified, t

10、he issues of these documents are those cited in the solicitation or contract. AMERICAN SOCIETY OF MECHANICAL ENGINEERS ASME Y14.38 Abbreviations and Acronyms (DoD Adopted) (Copies this document may be obtained at www.asme.org or mail your request to the American Society of Mechanical Engineers, 3 Pa

11、rk Avenue, New York, NY 10016-5990.) INSTITUTE OF ELECTRICAL AND ELECTRONIC ENGINEERS IEEE 716-1995 Common/Abbreviated Test Language for All Systems (C/ATLAS) Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-49503C (MI) 3 (Copies may be obtain

12、ed from http:/www.ieee.org/web/publications/home/index.html or from the Institute of Electrical and Electronic Engineers, IEEE Service Center, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08855-1331.) 2.4 Order of precedence. Unless otherwise noted herein or in the contract, in the event of a confli

13、ct between the text of this document and the references cited herein, (except for related specification sheets), the text of this document takes of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has document,

14、however, supersedes applicable laws and regulations unless a specific exemption has been obtained. 3. REQUIREMENTS. 3.1 Operator Automatic Test Equipment (ATE) Interface. 3.1.1 Standard design. A test program (TP) (see 6.5.4) shall be written so that: a. the system is easy to operate. b. the current

15、 status of the TP is evident to the operator. c. the system responds to each operator input. d. the next operation is easily determined. 3.1.2 Software structure. The TP structure shall provide context, consistency, and flexibility to the operator in executing the test program set (TPS) (see 6.5.6).

16、 3.1.3 Display design. The software structure and display design shall be a transparent interface between the operator and the task. It shall appear to the operators that they are directly acting on the screen representations and the Unit Under Test (UUT) without interference from the TPS. 3.1.4 Int

17、erface design objectives. The interface design shall be understandable, learnable, controllable, mappable, responsive, tolerant, and flexible. 3.1.4.1 Understandable. a. The operator shall be able to move through to. The TP shall provide the operator a means to be able to move through the various fu

18、nctions of the TP while maintaining and understanding the test. b. Information shall be presented in clear representations. c. There shall be a consistent use of terminology throughout the TP. d. Information that is essential to making a decision or performing an action shall be Provided by IHSNot f

19、or ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-49503C (MI) 4 given at one time. 3.1.4.2 Learnable. The TP software shall be designed: a. to prevent errors to the extent possible. b. to allow easy recovery from errors. c. to display a help message or visual indi

20、cation prompt the user when they make an input errors. d. to provide instructions at the appropriate time and place. e. to provide the operator with a dominant, clearly marked path through the operational logic. f. to reduce the demands on the operators memory by providing “prompting“ information at

21、 appropriate times. 3.1.4.3 Controllable. The TP shall promote the sense of operator control over the TP by: a. keeping the operator informed as to what the test program is doing. b. keeping the operator oriented as to where the test is, what test has been completed, and where the operator will be a

22、llowed to direct the test. c. responding the same way to the same operator input. d. ensuring that all system actions have a detectable cause. 3.1.4.4 Mappable. The TP shall provide routing information to the operator. It shall: a. provide the operator instructions to get started. b. provide clearly

23、 defined landmarks and routes. c. provide continuity between landmarks. d. never allow the operator to reach a “dead end“ or loop, with no place to go or options to try. e. keep the operators aware of progress in reaching their goals. f. support forward and backward movement through the operational

24、logic. Backward Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-49503C (MI) 5 movement shall be restricted to multiple graphic screens or successful UUT adjustments which allow testing to resume at the original failure. 3.1.4.5 Responsive. Th

25、e TP shall provide effective, consistent, timely, and meaningful feedback. The TP responses shall reflect what the test program is doing as well as system responses to operator actions. 3.1.4.6 Tolerant. The TP shall facilitate easy recovery from errors. Error handling support features such as “undo

26、“ commands, clear and constructive error messages, and help directories shall be used to recover from errors. The TP design shall include procedural verification. This verification shall identify instances where the operator may not have correctly performed a procedure, and prompt the operator to ch

27、eck the previous procedure before the test can continue. 3.1.4.7 Flexible. The TP shall provide for ease of menu/interface upgrades in the future revision releases based upon input from operator filed comments. 3.1.4.8 Language. Common nouns and verbs, as well as special terminology, shall be used c

28、onsistently. For example, the user shall not be told to “press“ a switch in one message and “depress“ it in another. 3.1.4.9 Equipment identification. Items of equipment shall be identified only by nomenclature used in the repair parts and special tools list (RPSTL) or in other terms specifically ap

29、proved by the Government. 3.1.4.10 Abbreviations and acronyms. Information shall be displayed in plain concise text wherever possible. Abbreviations and acronyms not peculiar to a specific system shall be from appendix A of this document or from ASME Y14.38. 3.1.4.11 Display codes. Approved abbrevia

30、tions, acronyms, or display codes shall be used where space does not permit plain text. 3.1.4.12 Feedback. Feedback shall be provided to the operator to indicate the status of test program processing and provide for user confidence. Feedback shall conform to the following: a. Periodic feedback shall

31、 be provided to the operator to indicate normal system operation when test program processing requires the operator to stand by for more than 15 seconds without making a response. b. The operator shall be informed at least once before the test or tests are initiated when a testing event or a series

32、of testing events technically prohibits interruption to inform the operator. c. Positive indication shall be presented to the operator about the outcome of the process and the requirements for subsequent operator actions when a process or sequence is completed or aborted by the system or TPS. d. Fee

33、dback shall be provided to indicate the reason for rejection and the required corrective action if the system rejects an operator input. Feedback shall be self-explanatory or coded in a manner clearly understood by the target audience. Provided by IHSNot for ResaleNo reproduction or networking permi

34、tted without license from IHS-,-,-MIL-PRF-49503C (MI) 6 3.2 Operator Interface Requirements. 3.2.1 Test Program Structure. The test program structure shall be simple, logical, and consistent. The selection of the dialogue used in the TP shall support the design structure. 3.2.2 Types of dialogue. Th

35、e types of dialogue that shall be used are: a. question and answer, b. menu selection, and c. function keys. 3.2.2.1 Question and answer. Questions shall be presented one at a time and shall not require the operator to answer more than one question at once. When the system must ask a series of quest

36、ions, and the answer to the current question is dependent upon the answer to a previous question, answers to all questions within the series shall be displayed until all questions have been answered. 3.2.2.2 Menu selection. a. Each menu display shall require only one selection by the operator. b. Th

37、e format of menu displays shall present only one option per displayed line. c. The active area for menu option selection via touch screen shall be the area of the displayed option label. The selection of a menu option for a non-touch screen shall be accomplished by the operator positioning the curso

38、r or mouse type pointer within the area to be selected (the displayed option label) and then pressing either “RETURN“ or “ENTER“ on the keyboard, or the left button of the mouse or trackball. If a mouse or trackball is not available, arrow keys on the keyboard shall be used to position an on screen

39、pointer. d. The menu display shall provide an immediate acknowledgment that an entry was made. e. Menu options shall be phrased as commands to the test set (computer), and not as questions to the operator. f. The displayed menu options working structure and syntax shall be consistent for all TPs ind

40、ependent of the defined elements and structure of the command language chosen. g. Each option code shall represent the meaning of the option. Codes shall not consist of arbitrary alpha, numeric, or alpha numeric designations. h. Menus shall display all options available at the current step in the te

41、st sequence. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-PRF-49503C (MI) 7 i. All menu options shall be consistent in their wording, ordering, and location, so that they are readily distinguishable from any other information contained on the

42、display. j. Menu options shall be listed in a logical sequence or in descending order of frequency of use. k. Menus shall be formatted to indicate related groups of options rather than an unrelated string of alternatives. Groups of related options shall be given a descriptive label that is distincti

43、ve in format from the option labels. Should there be any conflict between this paragraph and j (above), this paragraph takes precedence. l. A hierarchic sequence of menu selection shall be provided rather than a single multipage menu. m. As a minimum, the menu hierarchy shall start at a “Main“ menu

44、(top most) to the 3 submenus of ATE, ICD, and UUT. After running tests, the hierarchy shall return user to a “Print“ menu before returning to the “Main“ menu. The structure shall provide immediate access to critical or frequently used options and minimize the number of steps required to complete the

45、 sequence. The structure shall also provide the operator with his position within the sequence structure. n. Options that accomplish control entries shall be distinguished from options that branch to other menu frames. 3.2.2.3 Function keys. a. Each function key shall be labeled to indicate the func

46、tion(s) it performs. The labels shall be sufficiently descriptive to prevent operator confusion. Multifunction keys shall indicate to the operator which function is currently active. b. Function keys shall perform their designated function with a single activation. The function of a key shall not ch

47、ange with repeated activations. c. The TP shall provide an immediate acknowledgment of function key activation. d. A key assigned a given function in one test shall be assigned the same function in all other tests. 3.2.2.4 Displays. a. The TP shall be designed to display all the data that the operat

48、or needs at any step in the test sequence. Display screens shall not contain information that is not related to the current task. Data shall be sufficient as to not require the operator to recall data from previous displays. Provided by IHSNot for ResaleNo reproduction or networking permitted withou

49、t license from IHS-,-,-MIL-PRF-49503C (MI) 8 b. Data shall be displayed in usable, consistent, and distinctive formats. Once a format has been devised, it shall be maintained to ensure consistent design of the displays. The operator shall not be required to transpose, compute, interpolate, or mentally translate d