13.07.2015 Views

MAINTAINABILITY DESIGN TECHNIQUES METRIC - AcqNotes.com

MAINTAINABILITY DESIGN TECHNIQUES METRIC - AcqNotes.com

MAINTAINABILITY DESIGN TECHNIQUES METRIC - AcqNotes.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Downloaded from http://www.everyspec.<strong>com</strong> on 2011-10-29T14:56:01.DOD-HDBK-791(AM)6. Cost. Cost is always a factor in any trade-off studyof BITE versus ATE. It is generally more cost-effective toprovide specialized diagnostics for BITE and to providegeneral-purpose diagnostics for ATE.7-5.4 DIAGNOSTIC SOFTWAREDiagnostic software designers should consider1. Structured Programming. Structured programming—aset of programming principles that producessoftware modules that are easily understood and maintained—shouldbe used. In applying the programming,unconditional reverse transfers are to be avoided to eliminatelooping transfers.2. Language Selection. Higher level languages,approved by the Army, may be necessary to develop<strong>com</strong>puter programs that simulate human behavior or toemploy artificial intelligence or expert systems (see par.7-3.5.3) in problem solving. The higher level languagesalso are more readily understandable, but the lower levellanguages (assembler) are often more efficient. ATLAS(Abbreviated Test Language for All Systems) is an exampleof a high-level directed standard test language whosemajor features are (Ref. 14)a. Standard testing terminology to reduce erroneousinterpretationsb. UUT-oriented test statements to increase portability,i.e., ability to be used with different test equipmentconfigurations.3. Debugging. The debugging of diagnostic software, can be a lengthy and tedious process because of thenumerous ways in which fault sources can occur andbecause some sources appear infrequently but haveserious consequences when they do occur. Thus it isimportant that the diagnostic system mature with thedevelopment of the major system, i.e., being employedthroughout the phases of system development and notwhen the prime system is released to troops.4. Automatic Inspection, Diagnostic, and PrognosicSystem (AIDAPS) Software. AIDAPS software resultingfrom various contracts have resulted in developingdiagnostic <strong>com</strong>puter programs that can be transferredfrom one application to another (Ref. 18).7-5.5 TEST POINT IDENTIFICATIONThe identification of test points involves the followingsteps in the order indicated:1. List system parameters to be measured.2. List the output signals that, if present and withintolerance, would indicate that the system is in normaloperating condition.3. Identify internal functions that could cause thesystem output signal to fail and, therefore. should bemonitored.4. Decide on required test points and their locutions.Each of the selected test points with its output signalshould be evaluated for its <strong>com</strong>patibility with the diagnostictechnique—manual, BIT, or ATE—to determinethose signals adaptable to direct measurement and thoserequiring signal conditioning via a transducer.Fig. 7-1 (Ref. 19) depicts a simplified example of a testFigure 7-1. Liquid Coolant Subsystem Showing Transducers and Parameters of Interest (Ref.19)7-12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!