Abstract is missing.
- How Creative Design HappensNigel Cross. 2-2 [doi]
- Requirements for Ubiquitous/Embedded Products - Digital TV, Mobile Phones and Consumer ProductsIkuo Minakata. 3-3 [doi]
- Goal-Oriented Requirements Enginering: A Roundtrip from Research to PracticeAxel van Lamsweerde. 4-7 [doi]
- Use Case Estimation - The Devil is in the DetailKevin Vinsen, Diane Jamieson, Guy Callender. 10-15 [doi]
- Precise Specification and Validation of Transactional Business SoftwareAlexandre L. Correa, Cláudia Maria Lima Werner. 16-25 [doi]
- Customer Experience Requirements for Multi-platform Service Interaction: Bringing Services Marketing to the Elicitation of User RequirementsLia Patrício, Raymond P. Fisk, João Falcão e Cunha, Nuno Jardim Nunes. 26-35 [doi]
- From Goals to Aspects: Discovering Aspects from Requirements Goal ModelsYijun Yu, Julio Cesar Sampaio do Prado Leite, John Mylopoulos. 38-47 [doi]
- From Aspectual Requirements to Proof Obligations for Aspect-Oriented SystemsShmuel Katz, Awais Rashid. 48-57 [doi]
- Modeling and Composing Scenario-Based Requirements with AspectsJoão Araújo, Jon Whittle, Dae-Kyoo Kim. 58-67 [doi]
- Requirements Engineering Process Improvement Based on an Information ModelJörg Dörr, Barbara Paech, Mathias Köhler. 70-79 [doi]
- Architecture-driven Problem DecompositionLucia Rapanotti, Jon G. Hall, Michael Jackson, Bashar Nuseibeh. 80-89 [doi]
- Patterns for the RE ProcessLars Hagge, Kathrin Lappe. 90-99 [doi]
- The Effect of Trust Assumptions on the Elaboration of Security RequirementsCharles B. Haley, Robin C. Laney, Jonathan D. Moffett, Bashar Nuseibeh. 102-111 [doi]
- Identifying Stakeholders and Their Preferences about NFR by Comparing Use Case Diagrams of Several Existing SystemsHaruhiko Kaiya, Akira Osada, Kenji Kaijiri. 112-121 [doi]
- Composing Requirements Using Problem FramesRobin C. Laney, Leonor Barroca, Michael Jackson, Bashar Nuseibeh. 122-131 [doi]
- Developing a Domain-Specific Cross-Organizational RE MethodJaap Gordijn, Vera Kartseva, Joost Schildwacht, Roel Wieringa, Hans Akkermans. 134-143 [doi]
- Defining Early IT System Requirements with Regulation Principles: The Lightswitch ApproachGil Regev, Alain Wegmann. 144-153 [doi]
- Human-Centred Requirements EngineeringAndreas Gregoriades, Jae Eun Shin, Alistair G. Sutcliffe. 154-163 [doi]
- COTS Tenders and Integration RequirementsSøren Lauesen. 166-175 [doi]
- Understanding Requirements in Enterprise Systems ProjectsJon Atle Gulla. 176-185 [doi]
- Expanding the Horizons of Requirements Engineering: Examining Requirements during Groupware Tool DiffusionGloria Mark, Mark Bergman, Steven E. Poltrock. 186-195 [doi]
- Visual Variability Analysis for Goal ModelsBruno González-Baixauli, Julio Cesar Sampaio do Prado Leite, John Mylopoulos. 198-207 [doi]
- Fluent-Based Animation: Exploiting the Relation between Goals and Scenarios for Requirements ValidationSebastián Uchitel, Robert Chatley, Jeff Kramer, Jeff Magee. 208-217 [doi]
- Goal-Oriented Requirements AnimationHung Tran Van, Axel van Lamsweerde, Philippe Massonet, Christophe Ponsard. 218-228 [doi]
- A Heterogeneous Solution for Improving the Return on Investment of Requirements TraceabilityJane Cleland-Huang, Grant Zemont, Wiktor Lukasik. 230-239 [doi]
- Using Card Sorting Technique to Classify Requirements ChangeNur Nurmuliani, Didar Zowghi, Susan P. Williams. 240-248 [doi]
- Helping Analysts Trace Requirements: An Objective LookJane Huffman Hayes, Alex Dekhtyar, Senthil Karthikeyan Sundaram, Sarah Howard. 249-259 [doi]
- RETNA: From Requirements to Testing in a Natural WayRavishankar Boddu, Lan Guo, Supratik Mukhopadhyay, Bojan Cukic. 262-271 [doi]
- OMML: A Behavioural Model Interchange FormatRobert J. Hall, Andrea Zisman. 272-282 [doi]
- Speeding up Requirements Management in a Product Software Company: Linking Customer Wishes to Product Requirements through Linguistic EngineeringJohan Natt och Dag, Vincenzo Gervasi, Sjaak Brinkkemper, Björn Regnell. 283-294 [doi]
- Requirements Engineering Process Selection at Hewlett-PackardAlan Padula. 296-300 [doi]
- Requirements for Requirements Management ToolsMatthias Hoffmann, Nikolaus Kühn, Matthias Weber, Margot Bittner. 301-308 [doi]
- The Conundrum of Categorising Requirements: Managing Requirements for Learning on the MoveDebra Trusso Haley, Bashar Nuseibeh, Helen C. Sharp, Josie Taylor. 309-314 [doi]
- Requirement-driven Approach to Interoperable Traveler Support System SpecificationRyuji Tsuchiya, Akihiko Matsuoka, Koichi Goto, Kiyotaka Seki, Takahiko Ogino. 316-321 [doi]
- Experiences in Managing an Automotive Requirements Engineering ProcessNadine Heumesser, Frank Houdek. 322-327 [doi]
- Requirements Engineering in the Development of Innovative Automotive Embedded Software SystemsAlexander Puschnig, Ramin Tavakoli Kolagari. 328-333 [doi]
- A Context-Driven Use Case Creation Process for Specifying Automotive Driver Assistance SystemsHannes Omasreiter, Eduard Metzker. 334-339 [doi]
- Developing A Requirements Specification For A Web Service ApplicationJ. Chris Gibson. 340-344 [doi]
- Defining Requirements at Different Levels of AbstractionStan Bühne, Günter Halmans, Klaus Pohl, Matthias Weber, Henning Kleinwechter, Thomas Wierczoch. 346-347 [doi]
- A Framework for the Definition of Metrics for Actor-Dependency ModelsXavier Franch, Gemma Grau, Carme Quer. 348-349 [doi]
- Improving the Separation of Non-Functional Concerns in Requirements ArtifactsGeórgia Maria C. de Sousa, Jaelson Castro. 350-351 [doi]
- Quantifying Non-Functional Requirements: A Process Oriented ApproachRaquel L. Hill, Jun Wang, Klara Nahrstedt. 352-353 [doi]
- Using Abuse Frames to Bound the Scope of Security ProblemsLuncheng Lin, Bashar Nuseibeh, Darrel C. Ince, Michael Jackson. 354-355 [doi]
- QM: A Tool for Building Software Quality ModelsJuan Pablo Carvallo, Xavier Franch, Gemma Grau, Carme Quer. 358-359 [doi]
- ART-SCENE: Enhancing Scenario Walkthroughs With Multi-Media ScenariosKonstantinos Zachos, Neil A. M. Maiden. 360-361 [doi]
- Active Tool Support for Requirements Engineering Through RETHHermann Kaindl. 362-363 [doi]
- An Environment for Use Cases based Requirements EngineeringStéphane S. Somé. 364-365 [doi]