Template:WebNotes/RGAMission Profile: Difference between revisions
(Created page with '{{Template:NoSkin}} {{Template: WebNotesRGABanner}} |{{Font|Mission Profile Folio|11|tahoma|bold|gray}} Short description of the situations when you might use this model. |} {{F…') |
No edit summary |
||
| Line 2: | Line 2: | ||
{{Template: WebNotesRGABanner}} | {{Template: WebNotesRGABanner}} | ||
|{{Font|Mission Profile Folio|11|tahoma|bold|gray}} | |{{Font|Mission Profile Folio|11|tahoma|bold|gray}} | ||
It is common practice for systems to be subjected to operational testing during a development program, often times under stated mission profile conditions. This stated mission profile attempts to mimic real conditions while taking into account budge, resources, schedule and other consideration.s Because of a lack of structure for managing the elements that make up the mission profile, it is difficult to have an agreed upon methodology for estimating the system's reliability. Many systems fail operational testing because key assessments such as growth potential and projections cannot be made in a straightforward manner so that management can take appropriate action. The Mission Profile folio addresses this issue by incorporating a systematic mission profile methodology for operational reliability testing and reliability growth assessments. | |||
|} | |} | ||
{{Font|Learn more from...|11|tahoma|bold|gray}} | {{Font|Learn more from...|11|tahoma|bold|gray}} | ||
| Line 11: | Line 11: | ||
|- | |- | ||
| [[Image:Book blue.png]] | | [[Image:Book blue.png]] | ||
| [http://reliawiki. | | [http://reliawiki.org/index.php/Operational_Mission_Profile_Testing the theory textbook...] | ||
|- | |- | ||
| [[Image:Articleblue.png]] | | [[Image:Articleblue.png]] | ||
| [ related article(s)...] | | [http://reliawiki.com/index.php/Mission_Profile_Testing_Articles related article(s)...] | ||
|- | |- | ||
| [[Image:Bulbblue.png]] | | [[Image:Bulbblue.png]] | ||
Revision as of 00:10, 11 July 2013
 |
| Mission Profile Folio
It is common practice for systems to be subjected to operational testing during a development program, often times under stated mission profile conditions. This stated mission profile attempts to mimic real conditions while taking into account budge, resources, schedule and other consideration.s Because of a lack of structure for managing the elements that make up the mission profile, it is difficult to have an agreed upon methodology for estimating the system's reliability. Many systems fail operational testing because key assessments such as growth potential and projections cannot be made in a straightforward manner so that management can take appropriate action. The Mission Profile folio addresses this issue by incorporating a systematic mission profile methodology for operational reliability testing and reliability growth assessments. |
Learn more from...
|
the help file... |
|
the theory textbook... |
|
related article(s)... |
|
[ application example(s)...] |
