Sub-practice 1 of Requirements Development SP 3.2 states " Analyze and quantify functionality required by end users". What does quantifying functionality mean? Does it refer to quality characteristics of functionality or does it refer to Function Point estimation?
What quantify means in this sub-practice is to spell out the required functionality requirements so everyone is in agreement, as well as state exactly how many functionality requirements there are. And since this is a sub-practice, this is an informative component of the model and it is supplied for clarification of the intent of the practice statement “Establish and maintain a definition of required functionality.” If you are implementing RD in your organization, you are not required to implement the sub-practices. You need to do what makes good business sense for your organization in order to determine the definition of the required functionality.
No comments:
Post a Comment