Abstract is missing.
- A review of the state of the practice in requirements modelingMitchell D. Lubars, Colin Potts, Charles Richter. 2-14 [doi]
- Requirements engineering technologies at Rome LaboratoryWilliam E. Rzepka, James L. Sidoran, Douglas A. White. 15-18 [doi]
- Theories underlying requirements engineering: an overview of NATURE at GenesisMatthias Jarke, Janis A. Bubenko Jr., Colette Rolland, Alistair G. Sutcliffe, Yannis Vassiliou. 19-31 [doi]
- Modeling organizations for information systems requirements engineeringEric S. K. Yu. 34-41 [doi]
- Dealing with performance requirements during the development of information systemsBrian A. Nixon. 42-49 [doi]
- On defining requirements for interactionMichael D. Harrison, Philip J. Barnard. 50-54 [doi]
- Domain descriptionsMichael Jackson, Pamela Zave. 56-64 [doi]
- Domain modelling with hierarchies of alternative viewpointsSteve M. Easterbrook. 65-72 [doi]
- Requirements reconnoitring at the juncture of domain and instanceMartin S. Feather. 73-76 [doi]
- Should we specify systems or domain?D. Partridge, David Garlan, David R. Barstow, Jeff Kramer. 77-80 [doi]
- An incremental integration tool between requirements engineering and programming in the largeMartin Lefering. 82-89 [doi]
- CARD: a software requirements definition environmentAtsushi Ohnishi, Kiyoshi Agusa. 90-93 [doi]
- READS: a requirements engineering toolThomas J. Smith. 94-97 [doi]
- Requirement analysis by the KJ editorNaohiko Takeda, Akichika Shiomi, Kazuhisa Kawai, Hajime Ohiwa. 98-101 [doi]
- Requirements engineering by example: an empirical studyNeil A. M. Maiden, Alistair G. Sutcliffe. 104-111 [doi]
- Matching conceptual graphs as an aid to requirements re-useKevin Ryan, Brian Mathews. 112-120 [doi]
- Reuse of conceptual requirement specificationsSilvana Castano, Valeria De Antonellis. 121-124 [doi]
- Analyzing software requirements errors in safety-critical, embedded systemsRobyn R. Lutz. 126-133 [doi]
- Using scenarios in deficiency-driven requirements engineeringJohn S. Anderson, Brian Durney. 134-141 [doi]
- Defaults in specificationsMark Ryan. 142-149 [doi]
- Techniques for requirements elicitationJoseph A. Goguen, Charlotte Linde. 152-164 [doi]
- Integrating ethnography into the requirements engineering processIan Sommerville, Tom Rodden, Peter Sawyer, Richard Bentley, Michael Twidale. 165-173 [doi]
- Requirements capture as a cooperative activityLinda A. Macaulay. 174-181 [doi]
- The classification of requirements engineering methodsMatthew J. Bickerton, Jawed Siddiqi. 182-186 [doi]
- Tasks and social interaction: the relevance of naturalistic analyses of conduct for requirements engineeringPaul Luff, Marina Jirotka, Christian Heath, David Greatbatch. 187-190 [doi]
- Requirements engineering in systems engineering practiceStephanie M. White. 192-193 [doi]
- Social issues in requirements engineeringJoseph A. Goguen. 194-195 [doi]
- Documentation of requirements for computer systemsA. John van Schouwen, David Lorge Parnas, Jan Madey. 198-207 [doi]
- Formally specifying temporal constraints and error recoveryStuart Kent, T. S. E. Maibaum, William J. Quirk. 208-215 [doi]
- Description of specification developmentsJeanine Souquières, Nicole Lévy. 216-223 [doi]
- I never knew my requirements were object-oriented until I talked to my analystPericles Loucopoulos, Colin Potts, Stephen J. Mellor, John A. McDermid, Luqi, Lin Zucconi. 226-230 [doi]
- A translation method from natural language specifications into formal specifications using contextual dependenciesYasunori Ishihara, Hiroyuki Seki, Tadao Kasami. 232-239 [doi]
- The role of natural language in requirements engineeringKevin Ryan. 240-242 [doi]
- A strategy for conceptual model acquisitionJulio Cesar Sampaio do Prado Leite, Ana Paula M. Franco. 243-246 [doi]
- Process knowledge based rapid prototyping for requirements engineeringBalasubramaniam Ramesh, Luqi. 248-255 [doi]
- Issues in the development of a requirements traceability modelBalasubramaniam Ramesh, Michael Edwards. 256-259 [doi]
- Requirements engineering using the SOS paradigmSol J. Greenspan, Mark Feblowitz. 260-263 [doi]
- The change and evolution of requirements as a challenge to the practice of software engineeringSusan Harker, Ken D. Eason, John E. Dobson. 266-272 [doi]
- Representing knowledge in requirements engineering: an empirical study of what software engineers need to knowEiji Kuwana, James D. Herbsleb. 273-276 [doi]
- The role of policy in requirements definitionEdgar H. Sibley, Richard L. Wexelblat, J. Bret Michael, Michael C. Tanner, David C. Littman. 277-280 [doi]
- Recording requirements assumptions and rationaleLewis Johnson, Sol J. Greenspan, J. Lee, Gerhard Fischer, Colin Potts. 282-285 [doi]