default search action
Google
Google Scholar
Semantic Scholar
Internet Archive Scholar
CiteSeerX
ORCIDRE 1993: San Diego, California, USA
- Proceedings of IEEE International Symposium on Requirements Engineering, RE 1993, San Diego, California, USA, January 4-6, 1993. IEEE Computer Society 1993, ISBN 0-8186-3120-1
- Mitchell D. Lubars, Colin Potts, Charles Richter:
A review of the state of the practice in requirements modeling. 2-14 - William E. Rzepka, James L. Sidoran, Douglas A. White:
Requirements engineering technologies at Rome Laboratory. 15-18 - Matthias Jarke, Janis A. Bubenko Jr., Colette Rolland, Alistair G. Sutcliffe, Yannis Vassiliou:
Theories underlying requirements engineering: an overview of NATURE at Genesis. 19-31 - Eric S. K. Yu:
Modeling organizations for information systems requirements engineering. 34-41 - Brian A. Nixon:
Dealing with performance requirements during the development of information systems. 42-49 - Michael D. Harrison, Philip J. Barnard:
On defining requirements for interaction. 50-54 - Michael Jackson, Pamela Zave:
Domain descriptions. 56-64 - Steve M. Easterbrook:
Domain modelling with hierarchies of alternative viewpoints. 65-72 - Martin S. Feather:
Requirements reconnoitring at the juncture of domain and instance. 73-76 - D. Partridge, David Garlan, David R. Barstow, Jeff Kramer:
Should we specify systems or domain? 77-80 - Martin Lefering:
An incremental integration tool between requirements engineering and programming in the large. 82-89 - Atsushi Ohnishi, Kiyoshi Agusa:
CARD: a software requirements definition environment. 90-93 - Thomas J. Smith:
READS: a requirements engineering tool. 94-97 - Naohiko Takeda, Akichika Shiomi, Kazuhisa Kawai, Hajime Ohiwa:
Requirement analysis by the KJ editor. 98-101 - Neil A. M. Maiden, Alistair G. Sutcliffe:
Requirements engineering by example: an empirical study. 104-111 - Kevin Ryan, Brian Mathews:
Matching conceptual graphs as an aid to requirements re-use. 112-120 - Silvana Castano, Valeria De Antonellis:
Reuse of conceptual requirement specifications. 121-124 - Robyn R. Lutz
:
Analyzing software requirements errors in safety-critical, embedded systems. 126-133 - John S. Anderson, Brian Durney:
Using scenarios in deficiency-driven requirements engineering. 134-141 - Mark Ryan:
Defaults in specifications. 142-149 - Joseph A. Goguen, Charlotte Linde:
Techniques for requirements elicitation. 152-164 - Ian Sommerville, Tom Rodden, Peter Sawyer, Richard Bentley, Michael B. Twidale:
Integrating ethnography into the requirements engineering process. 165-173 - Linda A. Macaulay:
Requirements capture as a cooperative activity. 174-181 - Matthew J. Bickerton, Jawed Siddiqi:
The classification of requirements engineering methods. 182-186 - Paul Luff, Marina Jirotka, Christian Heath, David Greatbatch:
Tasks and social interaction: the relevance of naturalistic analyses of conduct for requirements engineering. 187-190 - Stephanie M. White:
Requirements engineering in systems engineering practice. 192-193 - Joseph A. Goguen:
Social issues in requirements engineering. 194-195 - A. John van Schouwen, David Lorge Parnas, Jan Madey:
Documentation of requirements for computer systems. 198-207 - Stuart Kent, T. S. E. Maibaum, William J. Quirk:
Formally specifying temporal constraints and error recovery. 208-215 - Jeanine Souquières, Nicole Lévy:
Description of specification developments. 216-223 - Colin Potts:
Panel: 'I never knew my requirements were object-oriented until I talked to my analyst'. 226-230 - Yasunori Ishihara, Hiroyuki Seki, Tadao Kasami:
A translation method from natural language specifications into formal specifications using contextual dependencies. 232-239 - Kevin Ryan:
The role of natural language in requirements engineering. 240-242 - Julio César Sampaio do Prado Leite, Ana Paula M. Franco:
A strategy for conceptual model acquisition. 243-246 - Balasubramaniam Ramesh, Luqi:
Process knowledge based rapid prototyping for requirements engineering. 248-255 - Balasubramaniam Ramesh, Michael Edwards:
Issues in the development of a requirements traceability model. 256-259 - Sol J. Greenspan, Mark Feblowitz:
Requirements engineering using the SOS paradigm. 260-263 - Susan Harker, Ken D. Eason, John E. Dobson:
The change and evolution of requirements as a challenge to the practice of software engineering. 266-272 - Eiji Kuwana, James D. Herbsleb:
Representing knowledge in requirements engineering: an empirical study of what software engineers need to know. 273-276 - Edgar H. Sibley, Richard L. Wexelblat, J. Bret Michael, Michael C. Tanner, David C. Littman:
The role of policy in requirements definition. 277-280 - Lewis Johnson, Sol J. Greenspan, J. Lee, Gerhard Fischer, Colin Potts:
Recording requirements assumptions and rationale. 282-285
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
last updated on 2024-11-19 20:52 CET by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint
dblp was originally created in 1993 at:
since 2018, dblp has been operated and maintained by:
the dblp computer science bibliography is funded and supported by:
