%0 Journal Article %1 Zave1997 %A Zave, Pamela %A Jackson, Michael %D 1997 %J ACM Transactions on Software Engineering and Methodology %K dark engineering ontology requirements requirementsengineering %N 1 %P 1--30 %T Four Dark Corners of Requirements Engineering %U http://www.cs.toronto.edu/~nernst/papers/zave97req.pdf %V 6 %X Research in requirements engineering has produced an extensive body of knowledge, but there are four areas in which the foundation of the discipline seems weak or obscure. This article shines some light in the four dark corners, exposing problems and proposing solutions. We show that all descriptions involved in requirements engineering should be descriptions of the environment. We show that certain control information is necessary for sound requirements engineering, and we explain the close association between domain knowledge and refinement of requirements. Together these conclusions explain the precise nature of requirements, specifications, and domain knowledge, as well as the precise nature of the relationships among them. They establish minimum standards for what information should be represented in a requirements language. They also make it possible to determine exactly what it means for requirements engineering to be successfully completed.

@article{Zave1997, abstract = {Research in requirements engineering has produced an extensive body of knowledge, but there are four areas in which the foundation of the discipline seems weak or obscure. This article shines some light in the four dark corners, exposing problems and proposing solutions. We show that all descriptions involved in requirements engineering should be descriptions of the environment. We show that certain control information is necessary for sound requirements engineering, and we explain the close association between domain knowledge and refinement of requirements. Together these conclusions explain the precise nature of requirements, specifications, and domain knowledge, as well as the precise nature of the relationships among them. They establish minimum standards for what information should be represented in a requirements language. They also make it possible to determine exactly what it means for requirements engineering to be successfully completed.}, added-at = {2009-10-19T13:28:17.000+0200}, author = {Zave, Pamela and Jackson, Michael}, biburl = {https://www.bibsonomy.org/bibtex/29068fd52b756e98c6dcb23ff95247907/lama}, citeulike-article-id = {120111}, description = {sdasda}, file = {:10.1.1.26.4161.pdf:PDF}, interhash = {b86b10370cf3feded361cf7955bc3be6}, intrahash = {9068fd52b756e98c6dcb23ff95247907}, journal = {ACM Transactions on Software Engineering and Methodology}, keywords = {dark engineering ontology requirements requirementsengineering}, number = 1, pages = {1--30}, priority = {0}, timestamp = {2009-10-19T13:28:17.000+0200}, title = {Four Dark Corners of Requirements Engineering}, url = {http://www.cs.toronto.edu/~nernst/papers/zave97req.pdf}, volume = 6, year = 1997 }