"... In PAGE 13: ... Depending on the gesture commands are sent to the devices and feedback is applied. The correlation of gestures and commands is shown in Table3 . If the dialogue nishes by time out or by the pointing gesture or a certain termination gesture the control ow enters the direction determination (Figure 12).... In PAGE 30: ...evice at a time. First a device is selected by the unique pointer click. Depending on the selected device, the gesture will execute a certain command. Table3 shows a possible mapping. The stars indicate that the device in that column supports the function of the row.... ..."

"... In PAGE 6: ...2486 The Plant Cell of these 17 genes was tested in each case using the same cDNA samples that were used for the microarray hybridiza- tion experiment. Table2 shows that the real-time PCR data were similar to the microarray data: in most cases, genes that showed high expression in the microarray experiment showed high expression in the real-time PCR experiment. In a few cases ( Zat12 , ADH1 , unknown protein At3g11930, and pectin methylesterase), the expression ratios were dif- ferent, although both approaches indicated strong gene induction.... ..."

"... In PAGE 12: ... If so, what are good pressure-wave features? Programs were written to extract a large number of simple features from each pressure wave #28listed in Table 6#29, No good univariate #0Ct is available #28the best, over all gtypes has ne xve total =0:52#29. The GMBL cross-validation algo- rithms were each run on the dataset, with the results shown in Table7 . Due to the shortage of data, no independent test set validation was performed.... ..."

"... In PAGE 6: ... The traditional software process, as per IEEE standard 1074-1991, is composed of four main processes, each grouping a series of activities that are responsible for implementing their associated goals [22]. These processes are shown in Table2 . Although it has not been formally defined by any organization or document, the KE software process can be considered to be composed primarily of the processes shown in Table 2, as all of these activities appear in one way or another in the most well-known KE development methodologies [8] [9] [10] [11] [12].... In PAGE 6: ... These processes are shown in Table 2. Although it has not been formally defined by any organization or document, the KE software process can be considered to be composed primarily of the processes shown in Table2 , as all of these activities appear in one way or another in the most well-known KE development methodologies [8] [9] [10] [11] [12]. Below we discuss which of the activities of SE could be applied in KE and vice versa.... ..."

"... In PAGE 8: ...able 2-3 Hazard Causes and Controls - Examples .........................................................16 Table3 -1 NASA Software Lifecycle - Reviews and Documents.... In PAGE 8: ...able 3-1 NASA Software Lifecycle - Reviews and Documents......................................20 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix.... In PAGE 8: ...able 3-2 MIL-STD-882C Software Hazard Criticality Matrix.......................................28 Table3 -3 Software Sub-system categories.... In PAGE 8: ...able 3-3 Software Sub-system categories........................................................................29 Table3 -4 Required Software Safety Effort .... In PAGE 8: ...able 3-4 Required Software Safety Effort .......................................................................30 Table3 -5 Software Requirements Phase.... In PAGE 8: ...able 3-5 Software Requirements Phase...........................................................................33 Table3 -6 Software Architectural Design Phase.... In PAGE 8: ...able 3-6 Software Architectural Design Phase................................................................34 Table3 -7 Software Detailed Design Phase .... In PAGE 8: ...able 3-7 Software Detailed Design Phase .......................................................................34 Table3 -8 Software Implementation Phase.... In PAGE 8: ...able 3-8 Software Implementation Phase........................................................................35 Table3 -9 Software Testing Phase .... In PAGE 8: ...able 3-9 Software Testing Phase .....................................................................................35 Table3 -10 Dynamic Testing .... In PAGE 8: ...able 3-10 Dynamic Testing .............................................................................................36 Table3 -11 Software Module Testing .... In PAGE 27: ...19 3.1 Software Development Lifecycle Approach Table3 -1 NASA Software Lifecycle - Reviews and Documents (page 20)shows the typical NASA software waterfall design lifecycle phases and lists the reviews and deliverable project documents required at each lifecycle phase. Each of these reviews and project documents should contain appropriate references and reports on software safety.... In PAGE 28: ...20 Table3 -1 NASA Software Lifecycle - Reviews and Documents LIFECYCLE PHASES MILESTONE REVIEWS SOFTWARE SAFETY TASKS DOCUMENTS Software Concept and Initiation (Project System and Subsystem Requirements and Design Development) SCR - Software Concept Review Software Management Plan Review Phase-0 Safety Review Scoping Safety Effort 2.1.... In PAGE 31: ... The system development phases are separated by system design reviews. Each system design review is conducted approximately in parallel with a corresponding system safety review as shown in Table3 -1 NASA Software Lifecycle - Reviews and Documents on page 20. The software development effort may or may not be synchronized with the system development effort.... In PAGE 35: ... 3.3 Scoping of Software Subsystem Safety Effort The level of required software safety effort for a system (shown in Table3 -3) is determined by its System Category, derived from Table 2-2 Hazard Prioritization - System Risk Index (Page 8), and the hazard severity level from Section 2.... In PAGE 36: ...28 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix HAZARD CATEGORY CONTROL CATEGORY CATASTRO- PHIC CRITICAL MODERATE NEGLIGIBLE / MARGINAL I1135 II 1 2 4 5 III 2 3 5 5 III 3 4 5 5 Software Hazard Risk Index Suggested Criteria 1 High Risk - significant analysis and testing resources 2 Medium risk - requirements and design analysis and in-depth testing required 3-4 Moderate risk - high level analysis and testing acceptable with management approval 5 Low Risk - Acceptable 3.3.... In PAGE 37: ...29 Table3 -3 Software Sub-system categories System Category Descriptions I Partial or total autonomous control of safety critical functions by software. (System Risk Index 2) Complex system with multiple subsystems, interacting parallel processors, or multiple interfaces.... In PAGE 38: ...30 Table3 -4 Required Software Safety Effort SYSTEM CATEGORY HAZARD SEVERITY LEVEL from Section 2.... In PAGE 39: ... Ultimately, the range of selected techniques must be negotiated and approved by project management, software development, software quality assurance, and software systems safety. Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing are modifications of tables that appear from an early International Electrotechnical Committee (IEC) draft standard IEC 1508, quot;Software For Computers In The Application Of Industrial Safety-Related Systems quot; [5]. This document is currently under review by national and international representatives on the IEC to determine its acceptability as an international standard on software safety for products which contain Programmable Electronic Systems (PESs).... In PAGE 39: ... These tables provide guidance on the types of assurance activities which may be performed during the lifecycle phases of safety-critical software development. For this guidebook, the Required Software Safety Efforts values displayed in Table3 -4 Required Software Safety Effort (page 30), will determine which development activities are required for each level of effort. Each of the following tables lists techniques and recommendations for use based on safety effort level for a specific software development phase or phases.... In PAGE 40: ... The final list of techniques to be used on any project should be developed jointly by negotiations between project management and safety assurance. All the following tables, Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table 3-5 Software Requirements Phase Section 4.... In PAGE 40: ... All the following tables, Table 3-5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table3 -5 Software Requirements Phase Section 4.1 Section 5.... In PAGE 40: ...1 Section 5.1 Software Requirements Table3 -5 Software Requirements Phase Section 4.2 Section 5.... In PAGE 40: ...2 Section 5.1 Software Architectural Design Table3 -5 Software Requirements Phase Section 4.3 Section 5.... In PAGE 40: ...3 Section 5.1 Software Detailed Design Table3 -7 Software Detailed Design Phase Section 4.4 Section 5.... In PAGE 40: ...4 Section 5.3 Software Implementation Table3 -8 Software Implementation Phase Section 4.5 Section 5.... In PAGE 40: ...5 Section 5.1 Software Test Table3 -9 Software Testing Phase Table 3-10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...5 Section 5.1 Software Test Table 3-9 Software Testing Phase Table3 -10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...5 Section 5.1 Software Test Table 3-9 Software Testing Phase Table 3-10 Dynamic Testing Table3 -11 Software Module Testing Section 4.6... In PAGE 41: ...33 Table3 -5 Software Requirements Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 2.1 Preliminary Hazard Analysis (PHA) MMM 5.... In PAGE 42: ...34 Table3 -6 Software Architectural Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.2.... In PAGE 42: ....2.4.2 Independence Analysis HR M M Table3 -7 Software Detailed Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.3.... In PAGE 43: ...35 Table3 -8 Software Implementation Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.4.... In PAGE 44: ...36 Table3 -10 Dynamic Testing TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Typical sets of sensor inputs HR M M Test specific functions HR M M Volumetric and statistical tests R HR HR Test extreme values of inputs R M M Test all modes of each sensor R M M Path testing R M M Every statement executed once HR M M Every branch tested at least once HR M M Every predicate term tested R HR M Every loop executed 0, 1, many times R M M Every path executed R HR M Every assignment to memory tested NR HR HR Every reference to memory tested NR HR HR All mappings from inputs checked NR HR HR All timing constraints verified R M M Test worst case interrupt sequences R R... In PAGE 45: ...37 Test significant chains of interrupts R R NR Test Positioning of data in I/O space HR M M Check accuracy of arithmetic NR HR M All modules executed at least once M M M All invocations of modules tested HR M M Table3 -11 Software Module Testing TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Simulation (Test Environment) R HR M Load Testing (Stress Testing) HR M M Boundary Value Tests R HR M Test Coverage Analysis R HR M Functional Testing M M M Performance Monitoring R HR M Formal Progress Reviews R M M Reliability Modeling NR HR HR Checklists of Tests R HR... ..."

"... In PAGE 8: ...able 2-3 Hazard Causes and Controls - Examples .........................................................16 Table3 -1 NASA Software Lifecycle - Reviews and Documents.... In PAGE 8: ...able 3-1 NASA Software Lifecycle - Reviews and Documents......................................20 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix.... In PAGE 8: ...able 3-2 MIL-STD-882C Software Hazard Criticality Matrix.......................................28 Table3 -3 Software Sub-system categories.... In PAGE 8: ...able 3-3 Software Sub-system categories........................................................................29 Table3 -4 Required Software Safety Effort .... In PAGE 8: ...able 3-4 Required Software Safety Effort .......................................................................30 Table3 -5 Software Requirements Phase.... In PAGE 8: ...able 3-5 Software Requirements Phase...........................................................................33 Table3 -6 Software Architectural Design Phase.... In PAGE 8: ...able 3-6 Software Architectural Design Phase................................................................34 Table3 -7 Software Detailed Design Phase .... In PAGE 8: ...able 3-7 Software Detailed Design Phase .......................................................................34 Table3 -8 Software Implementation Phase.... In PAGE 8: ...able 3-8 Software Implementation Phase........................................................................35 Table3 -9 Software Testing Phase .... In PAGE 8: ...able 3-9 Software Testing Phase .....................................................................................35 Table3 -10 Dynamic Testing .... In PAGE 8: ...able 3-10 Dynamic Testing .............................................................................................36 Table3 -11 Software Module Testing .... In PAGE 27: ...19 3.1 Software Development Lifecycle Approach Table3 -1 NASA Software Lifecycle - Reviews and Documents (page 20)shows the typical NASA software waterfall design lifecycle phases and lists the reviews and deliverable project documents required at each lifecycle phase. Each of these reviews and project documents should contain appropriate references and reports on software safety.... In PAGE 28: ...20 Table3 -1 NASA Software Lifecycle - Reviews and Documents LIFECYCLE PHASES MILESTONE REVIEWS SOFTWARE SAFETY TASKS DOCUMENTS Software Concept and Initiation (Project System and Subsystem Requirements and Design Development) SCR - Software Concept Review Software Management Plan Review Phase-0 Safety Review Scoping Safety Effort 2.1.... In PAGE 31: ... The system development phases are separated by system design reviews. Each system design review is conducted approximately in parallel with a corresponding system safety review as shown in Table3 -1 NASA Software Lifecycle - Reviews and Documents on page 20. The software development effort may or may not be synchronized with the system development effort.... In PAGE 35: ... 3.3 Scoping of Software Subsystem Safety Effort The level of required software safety effort for a system (shown in Table3 -3) is determined by its System Category, derived from Table 2-2 Hazard Prioritization - System Risk Index (Page 8), and the hazard severity level from Section 2.... In PAGE 36: ...28 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix HAZARD CATEGORY CONTROL CATEGORY CATASTRO- PHIC CRITICAL MODERATE NEGLIGIBLE / MARGINAL I1135 II 1 2 4 5 III 2 3 5 5 III 3 4 5 5 Software Hazard Risk Index Suggested Criteria 1 High Risk - significant analysis and testing resources 2 Medium risk - requirements and design analysis and in-depth testing required 3-4 Moderate risk - high level analysis and testing acceptable with management approval 5 Low Risk - Acceptable 3.3.... In PAGE 37: ...29 Table3 -3 Software Sub-system categories System Category Descriptions I Partial or total autonomous control of safety critical functions by software. (System Risk Index 2) Complex system with multiple subsystems, interacting parallel processors, or multiple interfaces.... In PAGE 38: ...30 Table3 -4 Required Software Safety Effort SYSTEM CATEGORY HAZARD SEVERITY LEVEL from Section 2.... In PAGE 39: ... Ultimately, the range of selected techniques must be negotiated and approved by project management, software development, software quality assurance, and software systems safety. Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing are modifications of tables that appear from an early International Electrotechnical Committee (IEC) draft standard IEC 1508, quot;Software For Computers In The Application Of Industrial Safety-Related Systems quot; [5]. This document is currently under review by national and international representatives on the IEC to determine its acceptability as an international standard on software safety for products which contain Programmable Electronic Systems (PESs).... In PAGE 39: ... These tables provide guidance on the types of assurance activities which may be performed during the lifecycle phases of safety-critical software development. For this guidebook, the Required Software Safety Efforts values displayed in Table3 -4 Required Software Safety Effort (page 30), will determine which development activities are required for each level of effort. Each of the following tables lists techniques and recommendations for use based on safety effort level for a specific software development phase or phases.... In PAGE 40: ... The final list of techniques to be used on any project should be developed jointly by negotiations between project management and safety assurance. All the following tables, Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table 3-5 Software Requirements Phase Section 4.... In PAGE 40: ... All the following tables, Table 3-5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table3 -5 Software Requirements Phase Section 4.1 Section 5.... In PAGE 40: ...1 Section 5.1 Software Requirements Table3 -5 Software Requirements Phase Section 4.2 Section 5.... In PAGE 40: ...2 Section 5.1 Software Architectural Design Table3 -5 Software Requirements Phase Section 4.3 Section 5.... In PAGE 40: ...3 Section 5.1 Software Detailed Design Table3 -7 Software Detailed Design Phase Section 4.4 Section 5.... In PAGE 40: ...4 Section 5.3 Software Implementation Table3 -8 Software Implementation Phase Section 4.5 Section 5.... In PAGE 40: ...5 Section 5.1 Software Test Table3 -9 Software Testing Phase Table 3-10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...5 Section 5.1 Software Test Table 3-9 Software Testing Phase Table3 -10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...5 Section 5.1 Software Test Table 3-9 Software Testing Phase Table 3-10 Dynamic Testing Table3 -11 Software Module Testing Section 4.6... In PAGE 41: ...33 Table3 -5 Software Requirements Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 2.1 Preliminary Hazard Analysis (PHA) MMM 5.... In PAGE 42: ...34 Table3 -6 Software Architectural Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.2.... In PAGE 42: ....2.4.2 Independence Analysis HR M M Table3 -7 Software Detailed Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.3.... In PAGE 43: ...35 Table3 -8 Software Implementation Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.4.... In PAGE 43: ...4.9 Formal Methods NR HR HR Table3 -9 Software Testing Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Testing Defensive Programming NR HR M Boundary Value Tests R HR M Error Guessing NR NR R Test Coverage Analysis R HR M Functional Testing M M M Fagan Formal Inspections (Test Plans) HR HR M Reliability Modeling NR HR HR Checklists of Tests R HR... In PAGE 44: ...36 Table3 -10 Dynamic Testing TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Typical sets of sensor inputs HR M M Test specific functions HR M M Volumetric and statistical tests R HR HR Test extreme values of inputs R M M Test all modes of each sensor R M M Path testing R M M Every statement executed once HR M M Every branch tested at least once HR M M Every predicate term tested R HR M Every loop executed 0, 1, many times R M M Every path executed R HR M Every assignment to memory tested NR HR HR Every reference to memory tested NR HR HR All mappings from inputs checked NR HR HR All timing constraints verified R M M Test worst case interrupt sequences R R... ..."

"... In PAGE 8: ...able 2-3 Hazard Causes and Controls - Examples .........................................................16 Table3 -1 NASA Software Lifecycle - Reviews and Documents.... In PAGE 8: ...able 3-1 NASA Software Lifecycle - Reviews and Documents......................................20 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix.... In PAGE 8: ...able 3-2 MIL-STD-882C Software Hazard Criticality Matrix.......................................28 Table3 -3 Software Sub-system categories.... In PAGE 8: ...able 3-3 Software Sub-system categories........................................................................29 Table3 -4 Required Software Safety Effort .... In PAGE 8: ...able 3-4 Required Software Safety Effort .......................................................................30 Table3 -5 Software Requirements Phase.... In PAGE 8: ...able 3-5 Software Requirements Phase...........................................................................33 Table3 -6 Software Architectural Design Phase.... In PAGE 8: ...able 3-6 Software Architectural Design Phase................................................................34 Table3 -7 Software Detailed Design Phase .... In PAGE 8: ...able 3-7 Software Detailed Design Phase .......................................................................34 Table3 -8 Software Implementation Phase.... In PAGE 8: ...able 3-8 Software Implementation Phase........................................................................35 Table3 -9 Software Testing Phase .... In PAGE 8: ...able 3-9 Software Testing Phase .....................................................................................35 Table3 -10 Dynamic Testing .... In PAGE 8: ...able 3-10 Dynamic Testing .............................................................................................36 Table3 -11 Software Module Testing .... In PAGE 27: ...19 3.1 Software Development Lifecycle Approach Table3 -1 NASA Software Lifecycle - Reviews and Documents (page 20)shows the typical NASA software waterfall design lifecycle phases and lists the reviews and deliverable project documents required at each lifecycle phase. Each of these reviews and project documents should contain appropriate references and reports on software safety.... In PAGE 28: ...20 Table3 -1 NASA Software Lifecycle - Reviews and Documents LIFECYCLE PHASES MILESTONE REVIEWS SOFTWARE SAFETY TASKS DOCUMENTS Software Concept and Initiation (Project System and Subsystem Requirements and Design Development) SCR - Software Concept Review Software Management Plan Review Phase-0 Safety Review Scoping Safety Effort 2.1.... In PAGE 31: ... The system development phases are separated by system design reviews. Each system design review is conducted approximately in parallel with a corresponding system safety review as shown in Table3 -1 NASA Software Lifecycle - Reviews and Documents on page 20. The software development effort may or may not be synchronized with the system development effort.... In PAGE 35: ... 3.3 Scoping of Software Subsystem Safety Effort The level of required software safety effort for a system (shown in Table3 -3) is determined by its System Category, derived from Table 2-2 Hazard Prioritization - System Risk Index (Page 8), and the hazard severity level from Section 2.... In PAGE 36: ...28 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix HAZARD CATEGORY CONTROL CATEGORY CATASTRO- PHIC CRITICAL MODERATE NEGLIGIBLE / MARGINAL I1135 II 1 2 4 5 III 2 3 5 5 III 3 4 5 5 Software Hazard Risk Index Suggested Criteria 1 High Risk - significant analysis and testing resources 2 Medium risk - requirements and design analysis and in-depth testing required 3-4 Moderate risk - high level analysis and testing acceptable with management approval 5 Low Risk - Acceptable 3.3.... In PAGE 37: ...29 Table3 -3 Software Sub-system categories System Category Descriptions I Partial or total autonomous control of safety critical functions by software. (System Risk Index 2) Complex system with multiple subsystems, interacting parallel processors, or multiple interfaces.... In PAGE 38: ...30 Table3 -4 Required Software Safety Effort SYSTEM CATEGORY HAZARD SEVERITY LEVEL from Section 2.... In PAGE 39: ... Ultimately, the range of selected techniques must be negotiated and approved by project management, software development, software quality assurance, and software systems safety. Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing are modifications of tables that appear from an early International Electrotechnical Committee (IEC) draft standard IEC 1508, quot;Software For Computers In The Application Of Industrial Safety-Related Systems quot; [5]. This document is currently under review by national and international representatives on the IEC to determine its acceptability as an international standard on software safety for products which contain Programmable Electronic Systems (PESs).... In PAGE 39: ... These tables provide guidance on the types of assurance activities which may be performed during the lifecycle phases of safety-critical software development. For this guidebook, the Required Software Safety Efforts values displayed in Table3 -4 Required Software Safety Effort (page 30), will determine which development activities are required for each level of effort. Each of the following tables lists techniques and recommendations for use based on safety effort level for a specific software development phase or phases.... In PAGE 40: ... The final list of techniques to be used on any project should be developed jointly by negotiations between project management and safety assurance. All the following tables, Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table 3-5 Software Requirements Phase Section 4.... In PAGE 40: ... All the following tables, Table 3-5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table3 -5 Software Requirements Phase Section 4.1 Section 5.... In PAGE 40: ... Table3 -5 Software Requirements Phase Section 4.3 Section 5.... In PAGE 40: ...3 Section 5.1 Software Detailed Design Table3 -7 Software Detailed Design Phase Section 4.4 Section 5.... In PAGE 40: ...4 Section 5.3 Software Implementation Table3 -8 Software Implementation Phase Section 4.5 Section 5.... In PAGE 40: ...5 Section 5.1 Software Test Table3 -9 Software Testing Phase Table 3-10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...5 Section 5.1 Software Test Table 3-9 Software Testing Phase Table3 -10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...5 Section 5.1 Software Test Table 3-9 Software Testing Phase Table 3-10 Dynamic Testing Table3 -11 Software Module Testing Section 4.6... In PAGE 41: ...33 Table3 -5 Software Requirements Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 2.1 Preliminary Hazard Analysis (PHA) MMM 5.... In PAGE 42: ...34 Table3 -6 Software Architectural Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.2.... In PAGE 42: ....2.4.2 Independence Analysis HR M M Table3 -7 Software Detailed Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.3.... In PAGE 43: ...35 Table3 -8 Software Implementation Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.4.... In PAGE 43: ...4.9 Formal Methods NR HR HR Table3 -9 Software Testing Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Testing Defensive Programming NR HR M Boundary Value Tests R HR M Error Guessing NR NR R Test Coverage Analysis R HR M Functional Testing M M M Fagan Formal Inspections (Test Plans) HR HR M Reliability Modeling NR HR HR Checklists of Tests R HR... In PAGE 44: ...36 Table3 -10 Dynamic Testing TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Typical sets of sensor inputs HR M M Test specific functions HR M M Volumetric and statistical tests R HR HR Test extreme values of inputs R M M Test all modes of each sensor R M M Path testing R M M Every statement executed once HR M M Every branch tested at least once HR M M Every predicate term tested R HR M Every loop executed 0, 1, many times R M M Every path executed R HR M Every assignment to memory tested NR HR HR Every reference to memory tested NR HR HR All mappings from inputs checked NR HR HR All timing constraints verified R M M Test worst case interrupt sequences R R... In PAGE 45: ...37 Test significant chains of interrupts R R NR Test Positioning of data in I/O space HR M M Check accuracy of arithmetic NR HR M All modules executed at least once M M M All invocations of modules tested HR M M Table3 -11 Software Module Testing TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Simulation (Test Environment) R HR M Load Testing (Stress Testing) HR M M Boundary Value Tests R HR M Test Coverage Analysis R HR M Functional Testing M M M Performance Monitoring R HR M Formal Progress Reviews R M M Reliability Modeling NR HR HR Checklists of Tests R HR... ..."

"... In PAGE 8: ...able 2-3 Hazard Causes and Controls - Examples .........................................................16 Table3 -1 NASA Software Lifecycle - Reviews and Documents.... In PAGE 8: ...able 3-1 NASA Software Lifecycle - Reviews and Documents......................................20 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix.... In PAGE 8: ...able 3-2 MIL-STD-882C Software Hazard Criticality Matrix.......................................28 Table3 -3 Software Sub-system categories.... In PAGE 8: ...able 3-3 Software Sub-system categories........................................................................29 Table3 -4 Required Software Safety Effort .... In PAGE 8: ...able 3-4 Required Software Safety Effort .......................................................................30 Table3 -5 Software Requirements Phase.... In PAGE 8: ...able 3-5 Software Requirements Phase...........................................................................33 Table3 -6 Software Architectural Design Phase.... In PAGE 8: ...able 3-6 Software Architectural Design Phase................................................................34 Table3 -7 Software Detailed Design Phase .... In PAGE 8: ...able 3-7 Software Detailed Design Phase .......................................................................34 Table3 -8 Software Implementation Phase.... In PAGE 8: ...able 3-8 Software Implementation Phase........................................................................35 Table3 -9 Software Testing Phase .... In PAGE 8: ...able 3-9 Software Testing Phase .....................................................................................35 Table3 -10 Dynamic Testing .... In PAGE 8: ...able 3-10 Dynamic Testing .............................................................................................36 Table3 -11 Software Module Testing .... In PAGE 27: ...19 3.1 Software Development Lifecycle Approach Table3 -1 NASA Software Lifecycle - Reviews and Documents (page 20)shows the typical NASA software waterfall design lifecycle phases and lists the reviews and deliverable project documents required at each lifecycle phase. Each of these reviews and project documents should contain appropriate references and reports on software safety.... In PAGE 28: ...20 Table3 -1 NASA Software Lifecycle - Reviews and Documents LIFECYCLE PHASES MILESTONE REVIEWS SOFTWARE SAFETY TASKS DOCUMENTS Software Concept and Initiation (Project System and Subsystem Requirements and Design Development) SCR - Software Concept Review Software Management Plan Review Phase-0 Safety Review Scoping Safety Effort 2.1.... In PAGE 31: ... The system development phases are separated by system design reviews. Each system design review is conducted approximately in parallel with a corresponding system safety review as shown in Table3 -1 NASA Software Lifecycle - Reviews and Documents on page 20. The software development effort may or may not be synchronized with the system development effort.... In PAGE 35: ... 3.3 Scoping of Software Subsystem Safety Effort The level of required software safety effort for a system (shown in Table3 -3) is determined by its System Category, derived from Table 2-2 Hazard Prioritization - System Risk Index (Page 8), and the hazard severity level from Section 2.... In PAGE 36: ...28 Table3 -2 MIL-STD-882C Software Hazard Criticality Matrix HAZARD CATEGORY CONTROL CATEGORY CATASTRO- PHIC CRITICAL MODERATE NEGLIGIBLE / MARGINAL I1135 II 1 2 4 5 III 2 3 5 5 III 3 4 5 5 Software Hazard Risk Index Suggested Criteria 1 High Risk - significant analysis and testing resources 2 Medium risk - requirements and design analysis and in-depth testing required 3-4 Moderate risk - high level analysis and testing acceptable with management approval 5 Low Risk - Acceptable 3.3.... In PAGE 37: ...29 Table3 -3 Software Sub-system categories System Category Descriptions I Partial or total autonomous control of safety critical functions by software. (System Risk Index 2) Complex system with multiple subsystems, interacting parallel processors, or multiple interfaces.... In PAGE 38: ...30 Table3 -4 Required Software Safety Effort SYSTEM CATEGORY HAZARD SEVERITY LEVEL from Section 2.... In PAGE 39: ... Ultimately, the range of selected techniques must be negotiated and approved by project management, software development, software quality assurance, and software systems safety. Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing are modifications of tables that appear from an early International Electrotechnical Committee (IEC) draft standard IEC 1508, quot;Software For Computers In The Application Of Industrial Safety-Related Systems quot; [5]. This document is currently under review by national and international representatives on the IEC to determine its acceptability as an international standard on software safety for products which contain Programmable Electronic Systems (PESs).... In PAGE 39: ... These tables provide guidance on the types of assurance activities which may be performed during the lifecycle phases of safety-critical software development. For this guidebook, the Required Software Safety Efforts values displayed in Table3 -4 Required Software Safety Effort (page 30), will determine which development activities are required for each level of effort. Each of the following tables lists techniques and recommendations for use based on safety effort level for a specific software development phase or phases.... In PAGE 40: ... The final list of techniques to be used on any project should be developed jointly by negotiations between project management and safety assurance. All the following tables, Table3 -5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table 3-5 Software Requirements Phase Section 4.... In PAGE 40: ... All the following tables, Table 3-5 Software Requirements Phase through Table 3-11 Software Module Testing , list software development, safety and assurance activities which should be implemented in the stated phases of development. Life Cycle Phase Tasks and Priorities How To: Development Tasks How To: Analysis Tasks Concept Initiation Table3 -5 Software Requirements Phase Section 4.1 Section 5.... In PAGE 40: ...1 Section 5.1 Software Requirements Table3 -5 Software Requirements Phase Section 4.2 Section 5.... In PAGE 40: ...2 Section 5.1 Software Architectural Design Table3 -5 Software Requirements Phase Section 4.3 Section 5.... In PAGE 40: ...3 Section 5.1 Software Detailed Design Table3 -7 Software Detailed Design Phase Section 4.4 Section 5.... In PAGE 40: ... Table3 -9 Software Testing Phase Table 3-10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...Table 3-9 Software Testing Phase Table3 -10 Dynamic Testing Table 3-11 Software Module Testing Section 4.6... In PAGE 40: ...Table 3-9 Software Testing Phase Table 3-10 Dynamic Testing Table3 -11 Software Module Testing Section 4.6... In PAGE 41: ...33 Table3 -5 Software Requirements Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 2.1 Preliminary Hazard Analysis (PHA) MMM 5.... In PAGE 42: ...34 Table3 -6 Software Architectural Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.2.... In PAGE 42: ....2.4.2 Independence Analysis HR M M Table3 -7 Software Detailed Design Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.3.... In PAGE 43: ...35 Table3 -8 Software Implementation Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL 5.4.... In PAGE 43: ...4.9 Formal Methods NR HR HR Table3 -9 Software Testing Phase TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Testing Defensive Programming NR HR M Boundary Value Tests R HR M Error Guessing NR NR R Test Coverage Analysis R HR M Functional Testing M M M Fagan Formal Inspections (Test Plans) HR HR M Reliability Modeling NR HR HR Checklists of Tests R HR... In PAGE 44: ...36 Table3 -10 Dynamic Testing TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Typical sets of sensor inputs HR M M Test specific functions HR M M Volumetric and statistical tests R HR HR Test extreme values of inputs R M M Test all modes of each sensor R M M Path testing R M M Every statement executed once HR M M Every branch tested at least once HR M M Every predicate term tested R HR M Every loop executed 0, 1, many times R M M Every path executed R HR M Every assignment to memory tested NR HR HR Every reference to memory tested NR HR HR All mappings from inputs checked NR HR HR All timing constraints verified R M M Test worst case interrupt sequences R R... In PAGE 45: ...37 Test significant chains of interrupts R R NR Test Positioning of data in I/O space HR M M Check accuracy of arithmetic NR HR M All modules executed at least once M M M All invocations of modules tested HR M M Table3 -11 Software Module Testing TECHNIQUE SAFETY EFFORT LEVEL MIN MOD FULL Simulation (Test Environment) R HR M Load Testing (Stress Testing) HR M M Boundary Value Tests R HR M Test Coverage Analysis R HR M Functional Testing M M M Performance Monitoring R HR M Formal Progress Reviews R M M Reliability Modeling NR HR HR Checklists of Tests R HR... ..."

"... In PAGE 12: ... RTs to control and related trials were analysed for each participant according to their position in the experimental list such that the first three trials were labelled quot;time window 1 quot;, the second three quot;time window 2 quot;, the third three quot;time window 3 quot; and the last three quot;time window 4 quot;5 ( see Goldinger, 1999; Slowiaczek, McQueen, Soltano amp; Lynch, 2000, for similar analyses). As can be seen in Table2 , no significant inhibition was observed at the beginning of the experiment in the large set of competitors (F(1,40)=0.13) as would have been expected if a surprise on the first related trials was... In PAGE 13: ...F(3,120)=0.24). It should also be noted that RTs on related trials increased but did not decrease between the beginning and the end of the experiment, an observation that again suggests that the present inhibition was neither caused by a surprise thought to occur on the first related trials nor blocked by response biases that participants might develop in order to maximize response speed on related trials (Pitt amp; Shoaf, 2002). lt;Insert Table2 about here gt; A potentially important factor related to the competitor set size is phonotactic probability. Words phonologically similar to many other words generally include frequent components (e.... ..."

"... In PAGE 26: ... Calculations were carried out using a combination of Minitab and Fortran programs. The analysis of variance table is given in Table1 . Although the distributions of the F-statistics are only approximate, the results are clear-cut.... In PAGE 27: ... Table1 . Analysis of Variance Table for Violent Crimes Occurring in 1982 Based on the Model (16).... ..."