RE 2010: Sydney, New South Wales, Australia

• Ricardo Gacitua, Peter Sawyer, Vincenzo Gervasi:
  On the Effectiveness of Abstraction Identification in Requirements Engineering. 5-14
  
• Igor Menzel, Mark Mueller, Anne Gross, Jörg Dörr:
  An Experimental Comparison Regarding the Completeness of Functional Requirements Specifications. 15-24
  
• Hui Yang, Anne N. De Roeck, Vincenzo Gervasi, Alistair Willis, Bashar Nuseibeh:
  Extending Nocuous Ambiguity Analysis for Anaphora in Natural Language Requirements. 25-34
  
• Norbert Seyff, Florian Graf, Neil A. M. Maiden:
  Using Mobile RE Tools to Give End-Users Their Own Voice. 37-46
  
• Jessica D. Young, Annie I. Antón:
  A Method for Identifying Software Requirements Based on Policy Commitments. 47-56
  
• Neil A. M. Maiden, Sara Jones, Inger Kristine Karlsen, Roger Neill, Konstantinos Zachos, Alastair Milne:
  Requirements Engineering as Creative Problem Solving: A Research Agenda for Idea Finding. 57-66
  
• Paul C. Clements, Len Bass:
  Using Business Goals to Inform a Software Architecture. 69-78
  
• Remo Ferrari, Nazim H. Madhavji, Oliver Sudmann, Christian Henke, Jens Geisler, Wilhelm Schäfer:
  Requirements Engineering Decisions in the Context of an Existing Architecture: A Case Study of a Prototypical Project. 79-88
  
• Sami Jantunen, Donald C. Gause, Ragnar Wessman:
  Making Sense of Product Requirements. 89-92
  
• Peter Sawyer, Nelly Bencomo, Jon Whittle, Emmanuel Letier, Anthony Finkelstein:
  Requirements-Aware Systems: A Research Agenda for RE for Self-adaptive Systems. 95-103
  
• Xin Peng, Bihuan Chen, Yijun Yu, Wenyun Zhao:
  Self-Tuning of Software Systems Through Goal-based Feedback Loop Control. 104-107
  
• Nauman A. Qureshi, Anna Perini:
  Requirements Engineering for Adaptive Service Based Applications. 108-111
  
• Ivan Jureta, Alexander Borgida, Neil A. Ernst, John Mylopoulos:
  Techne: Towards a New Generation of Requirements Modeling Languages with Goals, Preferences, and Inconsistency Handling. 115-124
  
• Luciano Baresi, Liliana Pasquale, Paola Spoletini:
  Fuzzy Goals for Requirements-Driven Adaptation. 125-134
  
• Sotirios Liaskos, Sheila A. McIlraith, Shirin Sohrabi, John Mylopoulos:
  Integrating Preferences into Goal Models for Requirements Engineering. 135-144
  
• Zornitza Racheva, Maya Daneva, Klaas Sikkel, Andrea Herrmann, Roel Wieringa:
  Do We Know Enough about Requirements Prioritization in Agile Projects: Insights from a Case Study. 147-156
  
• Ahmed Al-Emran, Dietmar Pfahl, Günther Ruhe:
  Decision Support for Product Release Planning Based on Robustness Analysis. 157-166
  
• Samuel Fricker, Martin Glinz:
  Comparison of Requirements Hand-off, Analysis, and Negotiation: Case Study. 167-176
  
• Sam Supakkul, Tom Hill, Lawrence Chung, Thein Than Tun, Julio Cesar Sampaio do Prado Leite:
  An NFR Pattern Approach to Dealing with NFRs. 179-188
  
• David Ameller, Xavier Franch, Jordi Cabot:
  Dealing with Non-Functional Requirements in Model-Driven Development. 189-198
  
• Ayse Morali, Roel Wieringa:
  Risk-based Confidentiality Requirements Specification for Outsourced IT Systems. 199-208
  
• Hakim Sultanov, Jane Huffman Hayes:
  Application of Swarm Techniques to Requirements Engineering: Requirements Tracing. 211-220
  
• Alexander Egyed, Florian Graf, Paul Grünbacher:
  Effort and Quality of Recovering Requirements-to-Code Traces: Two Exploratory Experiments. 221-230
  
• David Cuddeback, Alex Dekhtyar, Jane Huffman Hayes:
  Automated Requirements Traceability: The Study of Human Analysts. 231-240
  
• Camille Salinesi, Raúl Mazo, Daniel Diaz, Olfa Djebbi:
  Using Integer Constraint Solving in Reuse Based Requirements Engineering. 243-251
  
• Atif Mashkoor, Jean-Pierre Jacquot:
  Domain Engineering with Event-B: Some Lessons We Learned. 252-261
  
• Eunsuk Kang, Daniel Jackson:
  Dependability Arguments with Trusted Bases. 262-271
  
• Alistair Mavin, Philip Wilkinson:
  Big Ears (The Return of "Easy Approach to Requirements Engineering"). 277-282
  
• Marko Komssi, Marjo Kauppinen, Maaret Pyhäjärvi, Jukka Talvio, Tomi Männistö:
  Persuading Software Development Teams to Document Inspections: Success Factors and Challenges in Practice. 283-288
  
• Juha Savolainen, Juha Kuusela, Asko Vilavaara:
  Transition to Agile Development - Rediscovery of Important Requirements Engineering Practices. 289-294
  
• Janice Hill, Scott R. Tilley:
  Creating Safety Requirements Traceability for Assuring and Recertifying Legacy Safety-Critical Systems. 297-302
  
• Michael C. Panis:
  Successful Deployment of Requirements Traceability in a Commercial Engineering Organization...Really. 303-307
  
• Daniel M. Berry, Krzysztof Czarnecki, Michal Antkiewicz, Mohamed AbdelRazik:
  Requirements Determination is Unstoppable: An Experience Report. 311-316
  
• Lin Liu, Tong Li, Fei Peng:
  Why Requirements Engineering Fails: A Survey Report from China. 317-322
  
• Margot Bittner, Mark-Oliver Reiser, Helko Glathe, Matthias Weber:
  Manufacturer-Supplier Requirements Synchronization Using Exchange Containers and Multi-Level Systems. 325-330
  
• Matt C. Primrose:
  User Experience Grading Via Kano Categories. 331-336
  
• Deepa K. Vijayamma, Nora Yamini David:
  Enhancing Customer Partnership Through Requirements Framework. 337-342
  
• Sebastian Siegl, Kai-Steffen Jens Hielscher, Reinhard German:
  Model Based Requirements Analysis and Testing of Automotive Systems with Timed Usage Models. 345-350
  
• James Lockerbie, David Bush, Neil A. M. Maiden, Henk A. P. Blom, Mariken H. C. Everdij:
  Using i* Modelling as a Bridge between Air Traffic Management Operational Concepts and Agent-based Simulation Analysis. 351-356
  
• Sondoss El Sawah, Alan McLucas, Mike Ryan:
  Using Cognitive Mapping to Elicit Modelling Requirements: An Overview. 357-363
  
• Avik Sinha, Amit M. Paradkar, Hironori Takeuchi, Taiga Nakamura:
  Extending Automated Analysis of Natural Language Use Cases to Other Languages. 364-369
  
• Brian Berenbach:
  Requirements Engineering for Industrial Systems: No Easy Answers. 373-374
  
• Martin Mahaux, Patrick Heymans, Neil A. M. Maiden:
  Making It all Up: Getting in on the Act to Improvise Creative Requirements. 375-376
  
• Vincenzo Gervasi:
  Who Framed Roger User? Problem Frames as a User Interaction Design Tool. 377-378
  
• Mamoun Hirzalla:
  Realizing Business Agility Requirements through SOA and Cloud Computing. 379-380
  
• Mikio Aoyama, Takako Nakatani, Shinobu Saito:
  REBOK Manifest: Towards a Requirements Engineering Body of Knowledge. 383-384
  
• Martin Glinz:
  Very Lightweight Requirements Modeling. 385-386
  
• Joy Beatty:
  My Company Can't Afford RE Training Right Now, What Do We Do?. 387
  
• Kevin Ryan, Neil A. M. Maiden, Martin Glinz:
  If You Want Innovative RE, Never Ask the Users; A Formal Debate. 388
  
• Leonid Kof:
  From Requirements Documents to System Models: A Tool for Interactive Semi-Automatic Translation. 391-392
  
• Massila Kamalrudin, John G. Hosking, John C. Grundy:
  MaramaAI: Automated and Visual Approach for Inconsistency Checking of Requirements. 393-394
  
• David Callele, Eric Neufeld, Kevin Schneider:
  An Introduction to Experience Requirements. 395-396
  
• Norbert Seyff, Florian Graf, Paul Grünbacher:
  Using Contextual Information to Guide on-site Analysts. 397-398
  
• Hermann Kaindl, Michal Smialek, Wiktor Nowakowski:
  Case-based Reuse with Partial Requirements Specifications. 399-400
  
• Xiaohong Chen, Bin Yin, Zhi Jin:
  Dptool: A Tool for Supporting the Problem Description and Projection. 401-402
  
• Reinhard Stoiber, Samuel Fricker, Michael Jehle, Martin Glinz:
  Feature Unweaving: Refactoring Software Requirements Specifications into Software Product Lines. 403-404
  
• Rui Monteiro, João Araújo, Vasco Amaral, Pedro Patrício:
  Mdgore: Towards Model-Driven and Goal-Oriented Requirements Engineering. 405-406
  
• Chun Liu, Yue Wang, Wei Zhang, Zhi Jin:
  Elicitation of Dependability Requirements: A HAZOP-based Approach. 407-408
  
• Krzysztof Wnuk, David Callele, Björn Regnell:
  Guiding Requirements Scoping Using ROI: Towards Agility, Openness and Waste Reduction. 409-410
  
• Christopher Stanbridge:
  Retrospective Requirement Analysis Using Code Coverage of GUI Driven System Tests. 411-412
  
• Joy Beatty:
  If You Build It, Will They Use It? Leveraging Business Objectives to Deliver Successful Projects. 413-414
  

Last update Tue May 21 17:53:37 2013 CET by the DBLP Team — Data released under the ODC-BY 1.0 license — See also our legal information page