-These issues and difficulties can result in requirements - -2
-that show various problems. Two particularly relevant and - -3
-common problems are completeness and pertinence. Or better, - -4
-the lack of completeness and pertinence. Completeness refers to - -5
-the fact that it is often extremely difficult - -6
-to identify all of the requirements. That is it - -7
-is very difficult to have a complete picture - -8
-of the purpose of the software. So what happens - -9
-is that incomplete requirements are collected and the software - -10
-is missing functionality that is important for the user. Pertinence - -11
-conversely has to do with the relevance of the - -12
-requirements. To avoid completeness problems developers often end up collecting - -13
-a lot of irrelevant when not conflicting requirements. In - -14
-these cases what can happen is that the software could - -15
-either end up being bloated that is it might - -16
-contain a needed functionality. The functionality represented by these extra - -17
-requirements or it might even be impossible to build the - -18
-software due to the conflicting additional requirements. And to make - -19
-things even worse collecting all of these requirements sometimes doesn't - -20
-even solve the completeness issue. So you might end up - -21
-with a set of requirements that is not only incomplete - -22
-but it also contains extra information that can be harmful - -23
-to the system. So again the bottom line is that - -24
-gathering an adequate, accurate, complete, - -25
-and pertinent set of requirements that - -26
-identify the purpose of a software system is an arduous task. -- cgit 1.4.1