Sometime in the future, Requirements Engineers (also known as Systems
Analysts) will replace their present manual methods by a computer
aided method (a Requirements Engineering System) just as programmers
have replaced manual by on-line programming. The Requirements Engineering
System will be part of the (logically) integrated Decision Support
System of the Systems Department. This paper briefly describes the
need for formal recorded requirements and analyzes the reasons why
organizations do not record and maintain requirements. The future
Requirement Engineering System is described and two issues concerned
with its usability are discussed. The first is concerned with the
language or representation method and the second with the facilities
that will aid the analyst. The final section summarizes the current
situation and outlines some reasons for believing that such a Requirements
Engineering System is technically feasible and can be cost effective.
%0 Conference Paper
%1 Teichroew1980
%A Teichroew, D.
%A Sayani, H.
%B ACM '80: Proceedings of the ACM 1980 annual conference
%C New York, NY, USA
%D 1980
%I ACM
%K NT2OD computer engineering linux requirements requirementsengineering toread
%P 369--381
%R http://doi.acm.org/10.1145/800176.809992
%T Computer-aided requirements engineering
%X Sometime in the future, Requirements Engineers (also known as Systems
Analysts) will replace their present manual methods by a computer
aided method (a Requirements Engineering System) just as programmers
have replaced manual by on-line programming. The Requirements Engineering
System will be part of the (logically) integrated Decision Support
System of the Systems Department. This paper briefly describes the
need for formal recorded requirements and analyzes the reasons why
organizations do not record and maintain requirements. The future
Requirement Engineering System is described and two issues concerned
with its usability are discussed. The first is concerned with the
language or representation method and the second with the facilities
that will aid the analyst. The final section summarizes the current
situation and outlines some reasons for believing that such a Requirements
Engineering System is technically feasible and can be cost effective.
%@ 0-89791-028-1
@inproceedings{Teichroew1980,
abstract = {Sometime in the future, Requirements Engineers (also known as Systems
Analysts) will replace their present manual methods by a computer
aided method (a Requirements Engineering System) just as programmers
have replaced manual by on-line programming. The Requirements Engineering
System will be part of the (logically) integrated Decision Support
System of the Systems Department. This paper briefly describes the
need for formal recorded requirements and analyzes the reasons why
organizations do not record and maintain requirements. The future
Requirement Engineering System is described and two issues concerned
with its usability are discussed. The first is concerned with the
language or representation method and the second with the facilities
that will aid the analyst. The final section summarizes the current
situation and outlines some reasons for believing that such a Requirements
Engineering System is technically feasible and can be cost effective.},
added-at = {2009-11-19T17:34:35.000+0100},
address = {New York, NY, USA},
author = {Teichroew, D. and Sayani, H.},
biburl = {https://www.bibsonomy.org/bibtex/2a3fc5b82cfa7d3493a129c7a5ae05f0b/butonic},
booktitle = {ACM '80: Proceedings of the ACM 1980 annual conference},
doi = {http://doi.acm.org/10.1145/800176.809992},
file = {:C\:\\Users\\Bugra\\Documents\\Studium\\DA\\Literatur\\Teichroew1980.pdf:PDF},
interhash = {bb432972a2c9557ae937300f1d361417},
intrahash = {a3fc5b82cfa7d3493a129c7a5ae05f0b},
isbn = {0-89791-028-1},
keywords = {NT2OD computer engineering linux requirements requirementsengineering toread},
owner = {Tom},
pages = {369--381},
publisher = {ACM},
timestamp = {2009-11-19T17:34:35.000+0100},
title = {Computer-aided requirements engineering},
year = 1980
}