Template:Transferring to crow extended-continuous rga: Difference between revisions

From ReliaWiki
Jump to navigation Jump to search
(Created page with '====Transferring to Crow Extended - Continuous Evaluation Equivalent Single System==== RGA provides the capability to transfer a Multiple Systems with Event Codes data sheet to v…')
 
 
Line 1: Line 1:
====Transferring to Crow Extended - Continuous Evaluation Equivalent Single System====
#REDIRECT [[Crow Extended]]
RGA provides the capability to transfer a Multiple Systems with Event Codes data sheet to various other data types. Figure MultipleventoSS shows the available data types that the data sheet can be converted into. When selecting to transfer to an equivalent single system, the data sheet is converted to a Crow Extended - Continuous Evaluation data sheet.
 
<br>
The Crow Extended - Continuous Evaluation model is designed for analyzing data across multiple test phases, while considering the data for all phases as one data set. This model is covered in detail in Chapter 10 and familiarity with that model is necessary for the discussion presented in this section.
<br>
When using the Crow Extended - Continuous Evaluation model to transfer the data sheet from Multiple Systems with Event Codes to an equivalent single system, the following rules are used (in addition to the five basic rules presented earlier for calculating the equivalent single system):
<br>
<br>
:• BD modes in the Crow Extended data sheet become BD modes in the equivalent single system of the Crow Extended - Continuous Evaluation data sheet.
:• BC modes in the Crow Extended data sheet become BD modes in the equivalent single system of the Crow Extended - Continuous Evaluation data sheet. These BD modes will have associated implemented fixes (I events). Implemented fixes (I events) for BC modes in the Crow Extended data sheet become implemented fixes (I events) for the converted BD modes in the equivalent single system of the Crow Extended - Continuous Evaluation data sheet.
:• If an implemented fix (I event) occurred at the same time as the failure and was implemented at that exact time across all systems, then this becomes a BC mode in the equivalent single system. If the fixes (I events) were not all implemented at the same time or if the fix was not implemented on all systems at the failure time, then this becomes a BD mode in the equivalent single system.
<br>
Figure ESSECE shows the transferred equivalent single system Crow Extended - Continuous Evaluation data sheet from the Multiple Systems with Event Codes data sheet of Figure Simple example Crow Extended ESS.
 
[[Image:rga9.23.png|thumb|center|400px|Transfering the Multiple Systems with Event Codes data sheet to an equivalent single system using the Crow Extended-Continuous Evaluation model.]]
<br>
<br>
[[Image:rga9.24.png|thumb|center|400px|The transferred equivalent single system Crow Extended- Continuous Evaluation data sheet from the Multiple Systems with Event Codes data sheet of Figure 9.15.]]
<br>

Latest revision as of 02:02, 23 August 2012

Redirect to: