| K. Pohl. Requirements engineering: An overview. In A. Kent and J. Williams, editors, Encyclopedia of Computer Science and Technology, Vol. 36. Supplement 21. Marcel Deccer Inc, 1996. |
....customer. The problem statement can be reviewed by the customer, and misunderstandings concerning the overall goal can be detected and resolved. Therefore, producing this document can be seen as a first step in achieving an agreement on the problem between customer and developer in the sense of [Poh96]. This agreement must be reflected in at least one of these documents such that it can serve as the starting point of the further development. 23 7.2 Domain analysis At the beginning of this study it was not clear to which extent concepts of the problem domain have to be included explicitly ....
K. Pohl. Requirements Engineering: An overview. Aachener Informatik-Berichte 96-05, RWTH Aachen, Fachbereich Informatik, 1996.
No context found.
K. Pohl. Requirements engineering: An overview. In A. Kent and J. Williams, editors, Encyclopedia of Computer Science and Technology, Vol. 36. Supplement 21. Marcel Deccer Inc, 1996.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC