Hardware software design

Hegge, F.W. et al., The Unified Tri-Service Cognitive Performance Assessment Battery (UTC-PAB), 11 Hardware Software Design and Specification, U.S. Army Medical Research and Development Command, Fort Detrick, MD, 1985. 

Almost all applications programming in chemistry, and structural chemistry in particular, is performed in the FORTRAN language and the molecular mechanics calculations for which this hardware/software design exercise was undertaken is no exception. There are two problems which must be solved in order to build a FORTRAN microcomputer system with good scalar and array computational performance and these are firstly, the design of an efficient scalar processor with a transparent FORTRAN interface to the hardware and secondly, the design of an efficient AFPP,... 

Hardware/Software Design Audit. The standards references in this group include sections that ... 

Assure that the interlock (hardware, software, and I/O) continues to function as designed. The design must also determine the time interval on which this must be done. Often these tests must be done with the plant in full operation. 

Design can be as simple as replacing the motor in an existing vehicle with one of a different specification, or as complex as the design of a new automobile or any of its subsystems. Design can be of hardware, software (or a mixture of both). 

Predefined context design. Throughout this study, we conjecture that we re concerned with building a computer System that will work within some human context. Of course, many of the contracts that software designers have with their clients or employers are about building components within a larger piece of software or a system embedded within a complex design of many pieces of hardware. 

Where loss of control could lead to severe consequences, the integrity of the basic process control system and the protective safeguards must be designed, operated and maintained to a high standard. Industry standards such as ANSI/ISA-S84.01 (1996) and IEC 61508 (2000) address the issues of how to design, operate and maintain safety instrumented systems such as high temperature interlocks to achieve the necessary level of functional safety. The scope of these standards includes hardware, software, human factors and management (HSE 2000). 

OTHER AUTHORITY.— The Attorney General shall develop such computer software, design and obtain such telecommunications and computer hardware, and employ such personnel, as are necessary to establish and operate the system in accordance with this section. 

Software is not a physical entity and, unlike some hardware failures, software failures occur without advanced warning. One of the most common software failures is branching, that is, the ability to execute alternative series of commands based on differing inputs. The software branching capacity makes the commands extremely complex and difficult to validate once errors occur as an answer of a specific input, and until the introduction of that specific input error has not been detected. Software input can be almost any data and, and since it is impossible to introduce all data into a software, validation of data is extremely difficult. Thus, results are considered to be of high confidence level. The majority of software problems occur as a consequence of errors in the software design and development and are not directly related to the software manufacture. It is simple to manufacture several software copies that work perfectly and as the original one. 

It is recommended that wherever possible the structure of the URS be used as the basis for the presentation format of the FDS and hardware and software design specifications this helps ensure design decisions are auditable back to the source requirement. Traceability should also be carried forward to the qualification test procedures, where it can link each test and qualification acceptance criterion directly to a specific requirement. 

To support requirements and critical parameter traceability the FDS should, where possible, adopt the format of the URS. (See Secs. V and VI.) It is important that these primary corresponding specifications are fully understood by both the user and the supplier and are formally reviewed and approved before the supplier prepares the design specifications for hardware, software, and the control and monitoring instrumentation and regulating devices. 

Integration test specification—for testing the software module integration against the software design specification on suitable hardware. 

Project Quality Plan Software Quality Assurance Program Functional Design Specification Hardware Design Specification Software Design Specification Software Module Design Specification Software Review Software Module Test Records Hardware Test Records Integration Test Records Instrument Spccs/Data Sheets Instrument Calibration Records Material Certificates... 

Detailed hardware and/or software design specifications are documented... 

Qualifications are formal examinations of the completed system in order to determine and record the acceptability of the design, fabrication/development, and integration of the hardware/ software and associated utilities. 

The IQ must identify the hardware, software, and interfaces used by the computer system and demonstrate their installation, in accordance with the design drawings, specifications, and supplier recommendations. These requirements are established and documented in the technical design specification deliverable. 

There must be a written procedure for the acceptance/rejection of computer hardware/ software that is included in the finished device, and a designated individual(s) must cany out this process. 

Lek 00] Lekatsas, H., J. Henkel, and W. Wolf, Code compression as a variable in hardware/software co-design, Proceedings International Workshop on Hardware/Software Codesign, 2000, pp. 120-124. 

User Reqnirements Specification Functional Specification Hardware Design Specification Software Design Specification Software Controls Testing and Qnalification... 

---