Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Hardware and software design

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. [Pg.587]

Hardware and Software Design for bespoke code/macros. [Pg.140]

Hardware and Software Design — program specihcations as necessary. [Pg.141]

Predelivery Inspections (PDI) are used to verify the system build against detailed hardware and software design, coding and configuration programming standards, hardware assembly practices... [Pg.244]

Instrumented human interface Overt human action (e.g., keys pressed) Task performers Applicable hardware and software Design Postdevelopment... [Pg.1307]

The architecture of most of the safety systems implemented by Schneider Electric and Framatome includes a redundancy of identical I C channels, i.e. using the same hardware and software design. When performing safety analyses on such architectures, software is identified as a potential source of Common Cause Failure (CCF). [Pg.37]

Wei H. Y. and Soleimani M., Hardware and software design for a National Instrument-based magnetic induction tomography system for prospective biomedical applications. Physiol. Meas., vol. 33, p. 863, doi 10.1088/0967-3334/33/5/863,2012. [Pg.665]

Design diversity This approach is rather costly. It combines hardware and software fault tolerance in different sets of computing channels. Each channel is developed in different hardware and software in redundant mode to provide the same function. This method is deployed to identify deviation of a channel from the others. The goal is to tolerate both hardware and software design faults [7]. After developing a fault tolerant design it is necessary to validate it from a reliability point of view, discussed later. [Pg.820]

Traditional design based on multiple redundant instrumentation chaimels with a voting arrangement, as commonly used in analog applications, has benefits for the hardware of computer systems. However, this type of redundancy does not prevent a failure of the system due to common cause faults in hardware and software design that could lead to impairment of all redundant chaimels. [Pg.11]

Existence of hardware and software design standards and defined hardware and software life-cycle models. ... [Pg.49]

Subsystem A system consists of a set of subsystems. A subsystem is composite hardware and software design element, which can be composed of further subsystems or components or modules. Examples for subsystems are power supply, input, output, logic unit, software,... [Pg.139]

Performance of this elegant, high precision measurement method is enhanced by several advances in hardware and software design. Sensor design features allow avoidance of non-axial transit and removal of the effects of variances in conductivity and transit velocity. Substantial expansion of ranges of particle size and sample concentration for a sensor and the theoretical bases for same have been developed. Correction for secondary coincidence allows sample concentrations without data distortion to be increased twenty-fold or more with corresponding reduction in data acquisition time. Fast, "hands-off , analysis capabilities are provided by auto-detection ai d clearance of sensor blockages and auto-execution of customized sequences of analytical steps. Operational ease is further aided by standardized size scales, default calibrations, and a full complement of data presentation techniques. [Pg.527]

Regarding hardware and software design and implementation, the requirements of ISO 26262 for the lower ASBLs (ASIL A and B) should most be fidfUled by a mature development process from ASIL C onward, requirements become harder and more costiy to fulfill. [Pg.529]

The Central On-Board Computer of the Philae Lander in the Context of the Rosetta Space Mission. Andras Baldzs, from the Wigner Research Centre for Physics in Budapest, Hungary, presented an overview of the major hardware and software design aspects of the central on-board computer of the Philae lander, which traveled over 10 years as the precious payload of the Rosetta spacecraft that recently made the historical encounter with the comet 67P/Churyumov-Gerasimenko. [Pg.235]

Other assertions stated but not proved would then be imposed as proof obligations of more detailed hardware and software design. For functional requirements, it was also necessary to make assotions about the well-behaved nature of the environment (eg that the number of changes occurring could be supported by the information rate of the low grade link). [Pg.252]

Regarding the eradication of systematic failures, the hardware and software design process, the methods and the tools will be constrained by the standard ... [Pg.368]

Moreover, the possibility of decomposition of the ASIL level using the principle of diversified redundancy is important in order to put less constraint on the process methods and tools for hardware and software design as well as validation activities. [Pg.373]

Fig. B4.3 A simplified view of how the three types of stakeholder requirements fit into the design process. Here Equipment Design includes all hardware and software design. Fig. B4.3 A simplified view of how the three types of stakeholder requirements fit into the design process. Here Equipment Design includes all hardware and software design.
The optimal amount of sample required for measurement can be determined from the attenuation of the incident light intensity (lAo) as measured by the beam monitor. The proper range of attenuation, in which the least biased result can be obtained, depends on the instrument s hardware and software design and is often predetermined by the manufacturer in the case of commercial instruments ... [Pg.136]


See other pages where Hardware and software design is mentioned: [Pg.648]    [Pg.392]    [Pg.151]    [Pg.91]    [Pg.216]    [Pg.136]    [Pg.94]    [Pg.109]    [Pg.606]    [Pg.915]    [Pg.180]    [Pg.1566]    [Pg.1229]    [Pg.85]    [Pg.164]    [Pg.165]    [Pg.296]    [Pg.148]    [Pg.382]    [Pg.375]    [Pg.19]    [Pg.129]    [Pg.232]    [Pg.98]    [Pg.27]    [Pg.62]   
See also in sourсe #XX -- [ Pg.39 ]




SEARCH



Hardware

Hardware design

Hardware software design

Software and hardware

Software design

© 2024 chempedia.info