In many organizations, there has been a move toward the use of object-oriented
methods for the development of information systems. Little is understood,
or reported on the basis of research, of the use of object-oriented
methods by practicing professionals in the production of requirements
specifications for commercial or industrial sized projects. In this
paper, we outline a conceptual framework of �what might be happening�
in professional object-oriented requirements engineering based on
the common characteristics of published, well known object-oriented
methods. We then describe a research project and the findings from
a set of six case studies that have been undertaken that examine
professional practice from the standpoint of the epistemology contained
in the conceptual model. In these studies, it was found that the
more formal models of objectorientation were rarely used to validate,
or even clarify, the specification with clients or users. Rather,
analysts tended to use informal models, such as use cases or ad hoc
diagrams, to communicate the specification to users. Formal models
are more often used internally within the analysis team and for communicating
the specification to the design team.
%0 Conference Paper
%1 Dawson1999
%A Dawson, Linda
%A Swatman, Paul
%B ICIS '99: Proceeding of the 20th international conference on Information Systems
%C Atlanta, GA, USA
%D 1999
%I Association for Information Systems
%K NT2OD engineering linux requirements requirementsengineering toread ubuntu
%P 260--273
%R http://doi.acm.org/10.1145/352925.352949
%T The use of object-oriented models in requirements engineering: a
field study
%X In many organizations, there has been a move toward the use of object-oriented
methods for the development of information systems. Little is understood,
or reported on the basis of research, of the use of object-oriented
methods by practicing professionals in the production of requirements
specifications for commercial or industrial sized projects. In this
paper, we outline a conceptual framework of �what might be happening�
in professional object-oriented requirements engineering based on
the common characteristics of published, well known object-oriented
methods. We then describe a research project and the findings from
a set of six case studies that have been undertaken that examine
professional practice from the standpoint of the epistemology contained
in the conceptual model. In these studies, it was found that the
more formal models of objectorientation were rarely used to validate,
or even clarify, the specification with clients or users. Rather,
analysts tended to use informal models, such as use cases or ad hoc
diagrams, to communicate the specification to users. Formal models
are more often used internally within the analysis team and for communicating
the specification to the design team.
%@ ICIS1999-X
@inproceedings{Dawson1999,
abstract = {In many organizations, there has been a move toward the use of object-oriented
methods for the development of information systems. Little is understood,
or reported on the basis of research, of the use of object-oriented
methods by practicing professionals in the production of requirements
specifications for commercial or industrial sized projects. In this
paper, we outline a conceptual framework of �what might be happening�
in professional object-oriented requirements engineering based on
the common characteristics of published, well known object-oriented
methods. We then describe a research project and the findings from
a set of six case studies that have been undertaken that examine
professional practice from the standpoint of the epistemology contained
in the conceptual model. In these studies, it was found that the
more formal models of objectorientation were rarely used to validate,
or even clarify, the specification with clients or users. Rather,
analysts tended to use informal models, such as use cases or ad hoc
diagrams, to communicate the specification to users. Formal models
are more often used internally within the analysis team and for communicating
the specification to the design team.},
added-at = {2009-11-19T17:31:26.000+0100},
address = {Atlanta, GA, USA},
author = {Dawson, Linda and Swatman, Paul},
biburl = {https://www.bibsonomy.org/bibtex/2002a9f03ac46ea786c0b655304faff74/butonic},
booktitle = {ICIS '99: Proceeding of the 20th international conference on Information Systems},
doi = {http://doi.acm.org/10.1145/352925.352949},
file = {:C\:\\Users\\Bugra\\Documents\\Studium\\DA\\Literatur\\Dawson1999.PDF:PDF},
interhash = {4d6d87f1250c7ba82032aa5632f6d929},
intrahash = {002a9f03ac46ea786c0b655304faff74},
isbn = {ICIS1999-X},
keywords = {NT2OD engineering linux requirements requirementsengineering toread ubuntu},
location = {Charlotte, North Carolina, United States},
owner = {Tom},
pages = {260--273},
publisher = {Association for Information Systems},
timestamp = {2009-11-19T17:31:26.000+0100},
title = {The use of object-oriented models in requirements engineering: a
field study},
year = 1999
}