{"title":"A customer-oriented approach to optimizing reliability-allocation within a set of weapon-system requirements","authors":"J.J. Hadel, P. Lakey","doi":"10.1109/RAMS.1995.513229","DOIUrl":null,"url":null,"abstract":"A systems engineering approach to weapon system requirements allocation demands that all system level performance requirements, including reliability, be flowed down and allocated to lower-level sub functions using a logical, structured methodology. Normally it is not in the customer's best interest to contractually specify MTBF design parameters developed from system requirements because such action borders on dictating hardware design solutions instead of focusing on communicating customer overall needs and desires to the development agency. Because of this, the requirements flowdown process appears to offer opportunities for multiple feasible solutions, all of which are capable of meeting the customer's top level requirements.","PeriodicalId":143102,"journal":{"name":"Annual Reliability and Maintainability Symposium 1995 Proceedings","volume":"313 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1995-01-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"6","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Annual Reliability and Maintainability Symposium 1995 Proceedings","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/RAMS.1995.513229","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 6
Abstract
A systems engineering approach to weapon system requirements allocation demands that all system level performance requirements, including reliability, be flowed down and allocated to lower-level sub functions using a logical, structured methodology. Normally it is not in the customer's best interest to contractually specify MTBF design parameters developed from system requirements because such action borders on dictating hardware design solutions instead of focusing on communicating customer overall needs and desires to the development agency. Because of this, the requirements flowdown process appears to offer opportunities for multiple feasible solutions, all of which are capable of meeting the customer's top level requirements.