This paper surveys and evaluates some techniques for eliciting requirements of computer-based systems, paying particular attention to how they deal with social issues. The methods surveyed include introspection, interviews, questionnaires, and protocol, conversation, interaction, and discourse analyses. Although they are relatively untried in Requirements Engineering, we believe there is much promise in the last three techniques, which grew out of ethnomethodology and sociolinguistics. In particular, they can elicit tacit knowledge by observing actual interactions in the workplace, and can also be applied to the system development process itself.

We seek to take some initial steps towards a theory of information that is adequate for understanding and designing systems that process information, i.e., information systems in a broad sense. Formal representations of information are needed in designing, using and maintaining such systems, especially when they are computer based. However, it is also necessary to take account of social context, including how information is produced and used, not merely how it is represented; that is, we need a social theory of information. Ideas from ethnomethodology and semiotics, as well as logic and the sociology of science, are used to explore the nature of information.

This note is intended to stimulate awareness and discussion of social issues in Requirements Engineering. It classifies issues according to what groups are involved, and sketches some issues in each class. 1 Introduction A computer-based system is built for people and by people. It is intended to serve some human purpose, and it exists in some human context, whether it is a university information system, jet fighter, heart pacemaker, or stock arbitrage system. The goal of Requirements Engineering is to determine what properties a system should have in order to succeed. Sometimes this is relatively straightforward; but often, it is not. Some of the most vexing difficulties are social, political and/or cultural. Many requirements engineers feel that such issues fall outside the scope of their profession, and instead fall under management, interpersonal skills, or ethical quibbles; some even argue that social issues should be ignored in the requirements process, in order to make it as c...

This paper surveys and evaluates some techniques for eliciting requirements of computer-based systems, paying particular attention to how they deal with social issues. The methods surveyed include introspection, interviews, questionnaires, and protocol, conversation, interaction, and discourse analyses. Although they are relatively untried in Requirements Engineering, we believe there is much promise in the last three techniques, which grew out of ethnomethodology and sociolinguistics. In particular, they can elicit tacit knowledge by observing actual interactions in the workplace, and can also be applied to the system development process itself.