Template:WebNotes/RGAMission Profile: Difference between revisions
No edit summary |
No edit summary |
||
| (3 intermediate revisions by 3 users not shown) | |||
| 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 | It is common practice for systems to be subjected to operational testing during a development program, often under stated mission profile conditions. This stated mission profile attempts to mimic real conditions while taking into account budget, resources, schedule and other considerations. 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 8: | Line 8: | ||
|- | |- | ||
| [[Image:Helpblue.png]] | | [[Image:Helpblue.png]] | ||
| [http://help.synthesisplatform.net/rga9/mission_profiles.htm | | [http://help.synthesisplatform.net/rga9/index.htm#mission_profiles.htm V9 Help] or [http://help.synthesisplatform.net/rga10/index.htm#mission_profiles.htm V10 Help] | ||
|- | |- | ||
| [[Image:Book blue.png]] | | [[Image:Book blue.png]] | ||
| Line 17: | Line 17: | ||
|- | |- | ||
| [[Image:Bulbblue.png]] | | [[Image:Bulbblue.png]] | ||
| [ application example(s)...] | | [http://www.reliasoft.com/rga/examples/rgex7/index.htm application example(s)...] | ||
|} | |} | ||
Latest revision as of 22:07, 23 April 2015
 |
| Mission Profile Folio
It is common practice for systems to be subjected to operational testing during a development program, often under stated mission profile conditions. This stated mission profile attempts to mimic real conditions while taking into account budget, resources, schedule and other considerations. 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...
|
V9 Help or V10 Help |
|
the theory textbook... |
|
related article(s)... |
|
application example(s)... |
