If you are going to have a Requirements design phase, it makes more sense to do it right the first time, rather than saving it for a later phase. If a design is bad, then the problems encountered in implementing and test¬ing are increased and the chances of obtaining a reliable flight software system are minimized.nIn general, the responsibility of the Requirements is to concern itself with the first phase of program structuring (that is, the determination of valid functions). The responsibility of the Specifications level is to concern itself with phase 2 of program structuring (that is, the architec¬tural mapping of the design). In some cases, the Requirements will not complete the first phase. In some cases, it will go further. An im-portant interface function between Requirements and Specification is knowing to what extent the Requirements have been defined and there¬fore relaying this information to the Specifications people.
展开▼
