Table of Contents

• Requirements for Evolving Systems: A Telecommunications PerspectivePamela Zave. 2-9 [doi]
• The Hidden Meta-Requirements of Security and PrivacyEugene H. Spafford. 10 [doi]
• Practice-Based DesignLucy A. Suchman. 11 [doi]
• Requirements Engineering and Program Synthesis: Mutually Exclusive or Synergistic?Michael R. Lowry. 12-13 [doi]
• Events and Constraints: A Graphical Editor for Capturing Logic Requirements of ProgramsMargaret H. Smith, Gerard J. Holzmann, Kousha Etessami. 14-22 [doi]
• Virtual Environment Modeling for Requirements Validation of High Consequence SystemsVictor L. Winter, Dejan Desovski, Bojan Cukic. 23-30 [doi]
• Metaphors of IntentColin Potts. 31-39 [doi]
• Consistency Management of Product Line RequirementsJuha Savolainen, Juha Kuusela. 40-47 [doi]
• Product-Line Requirements Specification (PRS): An Approach and Case StudyStuart R. Faulk. 48-55 [doi]
• Extending the Product Family Approach to Support n-Dimensional and Hierarchical Product LinesJeffrey M. Thompson, Mats Per Erik Heimdahl. 56-65 [doi]
• Matching ERP System Functionality to Customer RequirementsColette Rolland, Naveen Prakash. 66-75 [doi]
• Software Acquisition: A Business Strategy AnalysisBarbara Farbey, Anthony Finkelstein. 76-83 [doi]
• An Industrial Survey of Requirements Interdependencies in Software Product Release PlanninPär Carlshamre, Kristian Sandahl, Mikael Lindvall, Björn Regnell, Johan Natt och Dag. 84-93 [doi]
• Evolving Beyond Requirements Creep: A Risk-Based Evolutionary Prototyping ModelRyan A. Carter, Annie I. Antón, Laurie A. Williams, Aldo Dagnino. 94-101 [doi]
• Will It Work?Jonathan Hammond, Rosamund Rawlings, Anthony Hall. 102-109 [doi]
• Requirements Engineering for Complex Collaborative SystemsAlistair G. Sutcliffe. 110-119 [doi]
• Domain Independent Regularities in ScenariosMarcela Ridao, Jorge Horacio Doorn, Julio Cesar Sampaio do Prado Leite. 120-127 [doi]
• An Empirical Study of Facilitation of Computer-Mediated Distributed Requirements NegotiationsDaniela E. Damian, Mildred L. G. Shaw, Armin Eberlein, Brian R. Gaines, J. Brian Woodward. 128-137 [doi]
• The Role of Policy and Stakeholder Privacy Values in Requirements EngineeringAnnie I. Antón, Julia Brande Earp, Thomas A. Alspaugh, Colin Potts. 138-145 [doi]
• Integrating Organizational Requirements and Object Oriented ModelingJaelson Castro, John Mylopoulos, Fernanda M. R. Alencar, Gilberto A. Cysneiros Filho. 146-153 [doi]
• Requirements Modeling for Organization Networks: A (Dis-)Trust-Based ApproachGünter Gans, Matthias Jarke, Stefanie Kethers, Gerhard Lakemeyer, Lutz Ellrich, Christiane Funken, Martin Meister. 154-165 [doi]
• XML-Based Method and Tool for Handling Variant Requirements in Domain ModelsStan Jarzabek, Hongyu Zhang. 166-173 [doi]
• Model Checking Early Requirements Specifications in TroposAriel Fuxman, John Mylopoulos, Marco Pistore, Paolo Traverso. 174-181 [doi]
• An Algorithm for Strengthening State Invariants Generated from Requirements SpecificationsRalph D. Jeffords, Constance L. Heitmeyer. 182-193 [doi]
• Residual Requirements and Architectural ResidueDavid S. Wile. 194-201 [doi]
• Reconciling Software Requirements and Architectures: The CBSP ApproachPaul Grünbacher, Alexander Egyed, Nenad Medvidovic. 202-211 [doi]
• Requirements-Based Dynamic Metrics In Object-Oriented SystemsJane Cleland-Huang, Carl K. Chang, Hosung Kim, Arun Balakrishnan. 212-221 [doi]
• Evolution of Safety-Critical Requirements Post-LaunchRobyn R. Lutz, Ines Carmen Mikulski. 222-227 [doi]
• Deriving Safety Requirements Using ScenariosKaren Allenby, Tim Kelly. 228-235 [doi]
• Re-Engineering Fault Tolerance Requirements: A Case Study in Specifying Fault Tolerant Flight Control SystemsDiego Del Gobbo, Ali Mili. 236-247 [doi]
• Systematic Documentation of RequirementsDavid Lorge Parnas. 248 [doi]
• Goal-Oriented Requirements Engineering: A Guided TourAxel van Lamsweerde. 249 [doi]
• Capturing Use Cases with DOORSIan F. Alexander. 264 [doi]
• Early Experience with Requirements Traceability in an Industrial EnvironmentMerlin Dorfman, Roy Chardon. 265 [doi]
• Where Are We on the Fend off the Alligators - Drain the Swamp Continuum?Donald C. Gause, Savile Row. 266 [doi]
• A Unified Approach to Systems and Software RequirementsAnthony Hall. 267 [doi]
• What Happens With Good Requirements PracticesIvy Hooks. 268 [doi]
• Formalism and Informality in REMichael Jackson. 269 [doi]
• Adoption of Requirements Engineering: Conditions for SuccessHermann Kaindl. 270 [doi]
• Changes in the Requirements Engineering Processes for COTS-Based SystemsRon Kohl. 271 [doi]
• Is Backtracking so Bad? The Role of Learning in Software DevelopmentBen Kovitz. 272 [doi]
• Rethinking RequirementsBrian Lawrence. 273 [doi]
• Business Implications on the Requirements ProcessBrian Miller. 274 [doi]
• Requirements Management at NASALinda Rosenburg. 275 [doi]
• Systems Engineering at the Enterprise LevelRichard Stevens. 276 [doi]
• Discovering Unanticipated Software Output ModesJeffrey M. Voas. 277 [doi]
• Designing for the UserMonica M. C. Schraefel. 280 [doi]
• Systems or Software: What Should the S in SRE Stand for?Regina Gonzales. 281 [doi]
• Extreme RE: What If There Is No Time for Requirements Engineering?Sol J. Greenspan. 282-285 [doi]
• Ask Pete, Software Planning and Estimation through Project CharacterizationTim Kurtz. 286 [doi]
• An Integrated V&V Environment for Critical Systems DevelopmentIssa Traoré. 287 [doi]
• Risk Reduction Using DDP (Defect Detection and Prevention): Software Support and Software ApplicationsMartin S. Feather. 288 [doi]
• Specification Modeling and Validation Applied to Network Security GatewaysRobert J. Hall. 289-291 [doi]
• The Single Model PrincipleRichard F. Paige, Jonathan S. Ostroff. 292-293 [doi]
• Integrating Informal and Formal Approaches to Requirements Modeling and AnalysisBetty H. C. Cheng, Laura A. Campbell. 294-295 [doi]
• Acquiring Software Requirements As Conceptual GraphsHarry S. Delugach, Brian E. Lampkin. 296-297 [doi]
• What Happens before Requirements Engineering?Bridgette Wessels, John E. Dobson. 298-299 [doi]
• Scenario Patterns Based on Case Grammar ApproachKenji Watahiki, Motoshi Saeki. 300-301 [doi]
• Empowering Requirements for a Product FamilyElena Pérez-Miñana, Paul Krause, Pierre America. 302-303 [doi]
• Requirements Archaeology: From Unstructured Information to High Quality SpecificationsFriedemann Kiedaisch, Martin Pohl, Joachim Weisbrod, Siegfried Bauer, Stefan Ortmanns. 304-305 [doi]
• Geographic Problem FramesMaria Augusta V. Nelson, Donald D. Cowan, Paulo S. C. Alencar. 306-307 [doi]
• Requirements Elicitation Using Visual and Textual InformationJ. Michael Moore, Frank M. Shipman III. 308-309 [doi]
• Process-Oriented Metrics for Software Architecture AdaptabilitLawrence Chung, Nary Subramanian. 310-311 [doi]
• A Requirements Negotiation Model Based on Multi-Criteria AnalysisHoh In, David Olson, Tom Rodgers. 312-313 [doi]
• Issues of Visualized Conflict ResolutionHoh In, Siddhartha Roy. 314-315 [doi]
• Evolving System Architecture to Meet Changing Business Goals: An Agent and Goal-Oriented ApproachDaniel Gross, Eric S. K. Yu. 316-317 [doi]
• Scenario-Based Systems ArchitectingGalal Hassan Galal. 318-319 [doi]