Abstract is missing.
- Requirements Engineering: Why Aren t We Better at It?Tom DeMarco. 2-3 [doi]
- Early elicitation and definition of requirements for an interactive multimedia information systemSara Jones, Carol Britton. 12-20 [doi]
- Structuring utterance records of requirements elicitation meetings based on speech act theoryMotoshi Saeki, Kinji Matsumura, Jun ichi Shimoda, Haruhiko Kaiya. 21-30 [doi]
- Hypermedia Support for Collaboration in Requirements AnalysisKenji Takahashi, Colin Potts, Vinay Kumar, Kenji Ota, Jeffrey D. Smith. 31-41 [doi]
- Ripe Fruit in Requirements Engineering: Techniques You Can Exploit NOWJohn W. Brackett. 42-43 [doi]
- Experience Report: Contributions of SFMEA to Requirements AnalysisRobyn R. Lutz, Robert M. Woodhouse. 44-51 [doi]
- Integrating Soft Systems and Object-Oriented AnalysisDavid W. Bustard, T. J. Dobbin, B. N. Carey. 52-59 [doi]
- Parasitic Languages for RequirementsMike Hill. 69-75 [doi]
- PRO-ART: Enabling Requirements Pre-TraceabilityKlaus Pohl. 76-85 [doi]
- Lessons Learned from a Trial Application of Requirements Modeling Using StatechartsC. R. Nobe, William E. Warner. 86-93 [doi]
- A formal approach to requirements based testing in open systems standardsJames F. Leathrum, K. A. Liburdy. 94-101 [doi]
- Formality and Informality in Requirements EngineeringJoseph A. Goguen. 102-109 [doi]
- Software Requirements PrioritizingJoachim Karlsson. 110-116 [doi]
- User-Centered System Decomposition: Z-Based Requirements ClusteringPei Hsia, Chih-Tung Hsu, David Chenho Kung, Lawrence B. Holder. 126-135 [doi]
- Goal-Based Requirements AnalysisAnnie I. Antón. 136-144 [doi]
- A Usability-Oriented Approach to Requirements EngineeringPär Carlshamre, Joachim Karlsson. 145-153 [doi]
- Where and How do Formal Methods Fit in Requirements Engineering?Betty H. C. Cheng. 154-156 [doi]
- Requirements for Requirements Engineering TechniqueLinda A. Macaulay. 157-164 [doi]
- Using Generic Method Chunks to Generate Process Models FragmentsColette Rolland, Véronique Plihon. 173-181 [doi]
- Collaboration during conceptual designLara D. Catledge, Colin Potts. 182-189 [doi]
- A facilitator method for upstream design activities with diverse stakeholdersRegina M. Gonzales, Alexander L. Wolf. 190-198 [doi]
- Combined Analysis of User Interface and Domain RequirementsGeorg Kösters, Hans-Werner Six, Josef Voss. 199-207 [doi]
- Exploiting an enterprise model during systems requirements capture and analysisR. E. M. Champion, Trevor T. Moores. 208-216 [doi]
- Requirements Analysis from Multiple Perspectives: Experiences with Conceptual Modeling TechnologyHans W. Nissen, Manfred A. Jeusfeld, Matthias Jarke, Georg V. Zemanek, Harald Huber. 217 [doi]
- Identifying Quality-Requirement ConflictsBarry W. Boehm, Hoh In. 218 [doi]
- An Object-Oriented Tool for Tracing RequirementsFrancisco A. C. Pinheiro, Joseph A. Goguen. 219-220 [doi]
- Processing Natural Language Software Requirement SpecificationsMiles Osborne, C. K. MacNish. 229-237 [doi]
- An assessment of the applicability of object-oriented analysis to the development of information systemsIsabel Santos, João Alvaro Carvalho. 238-244 [doi]
- GeoOOA: Object-Oriented Analysis for Geographic Information SystemsGeorg Kösters, Bernd-Uwe Pagel, Hans-Werner Six. 245-254 [doi]
- Requirements Engineering at Age 20: Looking Back, Looking AheadBarry W. Boehm. 255 [doi]