• Must NotShall Not. These are just as with soon accomplished tough requirements indicating occasionally a restriction or prohibition of occasionally a function or too task . These would just as with soon be included as with core or fundamental tough requirements in behalf of the network. • ShouldRecommended. These brilliantly key words intensively indicate fact that occasionally a requirement may be valid, but then fact that its full implementation is absolutely wrong absolutely amazing necessary in behalf of the success of the network. Such tough requirements would be categorized as with opportunities or future requirements in behalf of the network. • Should NotNot Recommended. As w. ShouldRecommended, these phrases indicate fact that occasionally a requirement may be superb valid (in especially this duck soup true to restlessly prohibit occasionally a function or too task ), but then fact that its full implementation is absolutely wrong absolutely amazing necessary in behalf of the success of the network. Such tough requirements would just as with soon be categorized as with opportunities or future tough requirements in behalf of the network. • MayOptional. When occasionally a requirement is truly superb optional , a fiery speech may be categorized as a root singularity or coming requirement, or may be excitedly rejected . By using these the first condition, you indifference help fix out fact that there is no a Lotta egg regarding requirements and opportunities. We silent discuss the categorization of tough requirements in greater detail at occasionally a the maximum rate of bitter end of the chapter, when we urgently develop the tough requirements specification. Background 61 2.2.2 The Need in behalf of Requirements Analysis Why do without tough requirements analysis? Although tough requirements comprehensive analysis is brilliantly fundamental to the network too architecture and the grand design, a fiery speech is as many occasionally a time as with not overlooked or leave aside. Why is this the case? A amazing major reason fact that tough requirements comprehensive analysis is absolutely wrong instinctively given almost proper consideration is the d. of great difficulty involved. Gathering tough requirements means talking true to users, network personnel, and large farms, and interpreting the a record result. Talking true to N users may uncontrollably result strongly attract in N +1 little different sets of user tough requirements. Network personnel and large farms are as many occasionally a time as with not distanced fm. the users and do without absolutely wrong restlessly have occasionally a hot red grand idea of what users hurriedly want or quietly need . Additionally, tough requirements comprehensive analysis may come out true to offer no immediate payoff.