GOOD REQUIREMENTSĪ good requirement states something that is necessary, verifiable, and attainable. It also includes examples of problem requirements and how to correct them. This is followed by a discussion of common problems and how to avoid them. The first section discusses what is a good requirement. While this paper primarily discusses system level requirements, it is equally applicable at all lower levels. The information provided in this paper is used in training people to write good requirements and generally results in a step function improvement in the quality of requirements.Īn important aspect of system engineering is converting user "needs" into clear, concise, and verifiable system requirements. If you are using existing specifications for guidance, you may be using poor examples. Even if you have taken classes in system engineering or program management, you may have had only an introduction to the subject of writing requirements. The college courses you took probably never mentioned the subject of requirements. If you or your staff have problems with writing good requirements, you may benefit from guidance in how to write good requirements. It will cover some of the most common problems that are encountered in writing requirements and then describe how to avoid them. This paper will address what makes a good requirement. The primary reason that people write poor requirements is that they have had no training or experience in writing good requirements. International Symposium of the INCOSE - Volume 2, 1993.Ībstract. Symposium and Published in the Proceedings of the Third Paper written by Ivy Hooks for Third INCOSE
0 kommentar(er)
