Classification of Research Efforts in Requirements Engineering PAMELA ZAVE AT&T Laboratories Research 1. PURPOSE OF THE CLASSIFICATION SCHEME be a great help in comparing, extending, and exploiting results). The great difficulty in constructing such a classification scheme is the heterogeneity of the topics usually considered part of requirements engineering. They include the following. Tasks that must be completed: elicitation of information from clients, validation, specification; Problems that must be solved: barriers to communication, incompleteness, inconsistency; Solutions to problems: formal languages and analysis algorithms, prototyping, metrics, traceability; Ways of contributing to knowledge: descriptions of current practice, case studies, controlled experiments; and Types of system: embedded systems, safety-critical systems, distributed systems. A typical list of research topics in requirements engineering contains all these entries and more. It is intended to be comprehensive, but it is also confusing. The obvious way out of this difficulty is a classification scheme with several orthogonal dimensions. The more dimensions the more precision, at the expense of making the scheme too complex to use. I have compromised by settling on two dimensions, which are presented separately in the next two sections. I have referenced a number of papers Requirements engineering is the branch of software
/lp/association-for-computing-machinery/classification-of-research-efforts-in-requirements-engineering-cmG9vu4kgY