Latest versions of STAM Scope, Purpose and Need, brought together for review:
This standard: 1) defines a representation of conforming behavioral descriptions of interfaces and transformations, 2) defines new methods for utilizing those representations to enhance the test management and access to sub-assembly test assets. This will allow, in conjunction with existing methods, for the coordination and control of a variety of digital interfaces to devices, boards, and sub-systems to extend test access to board and system levels. The standard does not replace or provide an alternative to existing test interface standards, but aims instead to enable their usage throughout the hierarchy of systems.
The purpose of this standard is to provide a means to seamlessly integrate component access topologies, interface constraints, and other dependencies at the board and system level by using standardized descriptions focusing on topology, interfaces and behavior (as opposed to physical structure). This will ease the burden on those preparing test, maintenance and support applications, including ATPGs, in particular where the application requires to co-ordinate control of and data transfer through multiple interfaces and/or protocols. The providers of these conforming descriptions are the producers of devices or
assemblies with digital interfaces that are intended to be used in an automated fashion within a larger assembly. This standard will include a methodology to ensure access to particular destination registers in the correct time order.
Standards exist to access diverse feature sets for device level test and instrumentation. However, there is currently no standard that provides for the aggregate management and coordination of such standards for higher level assemblies, such as boards or systems.
Users of board and system level automated test equipment need to be able to command their tools and instruments, identifying the dependencies, constraints, and required coordination. Embedded applications also need to have access to these same instruments at higher levels during run-time.
Standardization is needed to facilitate such automation and to enhance testability, test coverage, and diagnostics resolution in the higher level assemblies.
Please make any final observations on these ASAP as we aim to start a process of formally accepting these texts for our PAR at the June 11 meeting.
Additionally, one thing that we've overlooked so far is that the PAR also asks us to identify the "stakeholders":
The stakeholders (e.g., telecom, medical, environmental) for the standard consist of any parties that have an interest in or may be impacted by the development of the standard.