A Systems Engineering Approach to Trading Conflicting Requirements

Development programs are often faced with dealing with requirements that conflict with each other. Given these conflicting requirements, an approach is required to tackle the problem and present the customer with a best value solution. Background causes for the conflicting requirements are explained based on users and subject matter specialists. Examples relevant to the rotorcraft industry of requirements that conflict in relationship to cost, performance, risk and growth are presented. This paper will discuss a systematic approach for prioritizing conflicting requirements and trading off those requirements. The approach will suggest systems engineering techniques and tools employing quantitative and qualitative measures to develop a system architecture that provides the best customer value while trying to satisfice if not resolve those requirement conflicts. Lessons learned and future thoughts for the systems engineering professionals are proposed.