Requirements Bibliography
 Press here to go to Al Davis’s home page

© 1996 - 2008, Alan M. Davis

You are visitor number Hit Counter since July 21, 2003.
(The site was available online between March 1996 and July 2003 without a hit counter)

This site provides free access to a large (over 4600 entries) bibliography of requirements-related papers and books (click on a letter below).
(Warning: If you are using a "search" or "find" to locate something of interest in this list, be aware that this bibliography resides in six files. You'll need to search in the files with bibliographic entries for A-D, E-H, I-L, M-P, Q-T and U-Z separately)

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z     Demographics

    Q

    A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z     Demographics

  1. [Qian and Xu 2005].
    Qian, J., and B. Xu, "Model Checking for Statecharts," IASTED International Conference on Software Engineering and Applications (SEA), 2005.
  2. [Quer and Olive 1993].
    Quer, C., and A. Olive, "Object Interaction in Object-Oriented Deductive Conceptual Models," Fifth Conference on Advanced Information Systems Engineering, Paris, France, June 1993.
  3. [Quer, et al. 2005].
    Quer, C.,  et al., "DesCOTS-EV: A Tool for the Evaluation of COTS Components," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 457-460.
  4. [Quirk 1990].
    Quirk, W., "Automated support for marrying requirements to programs," Managing complexity in software engineering, London: Peregrinus, 1990, pp. 239-246.

 

R

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z     Demographics

  1. [Raadt, et al. 2005].
    van der Raadt, B., et al., "Exploring Web Services from a Business Value Perspective," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 53-62.
  2. [Rabiser, et al. 2006].
    Rabiser, R., et al., "Capturing Multimedia Requirements Descriptions with Mobile RE Tools," IEEE International Workshop on Multimedia Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006, p. 2.
  3. [Rabiser, et al. 2007].
    Rabiser, R., et al., "Involving Non-Technicians in Product Derivation and Requirements Engineering: A Tool Suite for Product Line Engineering,"     IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  4. [Rader 1996].
    Rader, J., "Successful Vendor Collaboration Deploying A Requirements Management Tool," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  5. [Rafla, et al. 2007].
    Rafla, T., et al., "A method to elicit architecturally sensitive usability requirements: its integration into a software development process," Software Quality Journal, 15, 2 (June 2007), pp. 117-133.
  6. [Raghaven 1990].
    Raghaven S., "Towards automated requirements analysis," International Workshop on Computer-Aided Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1990, pp. 269-278.
  7. [Rahman, et al. 2005].
    Rahman, S., et al., "Query-by-object interface for information requirement elicitation in m-commerce," IEEE International Conference on E-Commerce Technology, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 143-150.
  8. [Rahman, et al. 2005a].
    Rahman, S., et al., "Query-by-object interface for dynamic access and information requirement elicitation," IEEE International Conference on Mobile Business, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 667-670.
  9. [Rahwan, et al. 2006].
    Rahwan, I., et al., "Integrating social modelling and agent interaction through goal-oriented analysis," Computer Systems Science and Engineering, 21, 2 (March 2006), pp. 87-98.
  10. [Raiman and Zukernine 2007].
    Raiman, M., and M. Zukernine, "AsmLSec: An Extension of Abstract State Machine Language for Attack Scenario Specification," IEEE International Conference on Availability, Reliability and Security (ARES), Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 775-782.
  11. [Rajagopal, et al. 2005].
    Rajagopal, S., et al., "A New Approach to Software Requirements Elicitation," Sixth International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing and First ACIS International Workshop on Self-Assembling Wireless Networks (SNPD/SAWN'05), Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 32-42.
  12. [Rajasree, et al. 2003].
    Rajasree, M., et al., "Pattern Oriented Software Development: Moving Seamlessly from Requirements to Architecture," Workshop on From Requirements to Architectural Design (STRAW), 2003.
  13. [Rajlich 2006].
    Rajlich, V., "Changing the Paradigm for Software Engineering," Communications of the ACM, 49, 8 (August 2006), pp. 67-71.
  14. [Ralyté 1999].
    Ralyté, J., "Reusing Scenario Based Approaches in Requirements Engineering Methods: CREWS Method Base," Tenth International Workshop on Database and Expert Systems Applications, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 305-309.
  15. [Ralyté, et al. 2005].
    Ralyté, J., et al., "Applying Modular Method Engineering to Validate and Extend the RESCUE Requirements Process," International Conference on Conceptual Modeling, Lecture Notes in Computer Science 3716, Berlin: Springer, 2005, pp. 209-224.

  16. [Ramamoorthy and So 1977].
    Ramamoorthy, C., and H. So, "Survey of principles and techniques of software requirements and specifications," Software engineering techniques, state of the art report, Maidenhead, UK: Infotech International, 1977, pp. 265-318.

  17. [Ramamoorthy, et al. 1986].
    Ramamoorthy, C., et al., "Application of Metrics to Requirement Specification Based on the State Transition Model," Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 1986.

  18. [Ramamoorthy, et al. 1986a].
    Ramamoorthy, C., et al., "Software Quality and Requirement Specification," International Conference on Computer Languages, 1986.
  19. [Ramasubramaniam and Venkatachar 2007].
    Ramasubramaniam, K., and R. Venkatachar, "Goal-Aligned Requirements Generation," Advances in Conceptual Modeling - Theory and Practice, Berlin: Springer, 2007.
  20. [Ramesh and Dhar 1992].
    Ramesh, B., and V. Dhar, "Supporting Systems Development by Capturing Deliberations During Requirements Engineering," (see abstract) IEEE Transactions on Software Engineering, 18, 6 (June 1992), pp. 498-510.
  21. [Ramesh and Edwards 1993].
    Ramesh, B., and M. Edwards, "Issues in the Development of a Requirements Traceability Model," International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 256-259.
  22. [Ramesh and Luqi 1993].
    Ramesh, B., and Luqi, "Process Knowledge Based Rapid Prototyping for Requirements Engineering," International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 248-255.
  23. [Ramesh and Luqi 1995].
    Ramesh, B., and Luqi, "An Intelligent Assistant for Requirements Validation," Journal of Systems Integration, 5, 2 (June 1995), pp. 157-177.
  24. [Ramesh, et al. 1995].
    Ramesh, B., et al., "Implementing Requirements Traceability: A Case Study," (see abstract) Second International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
  25. [Ramesh, et al. 1995a].
    Ramesh, B., et al., "Lessons Learned from Implementing Requirements Traceability," CrossTalk, 8, 4 (April 1995), pp. 11-20.
  26. [Ramesh, et al. 1995b].
    Ramesh, B. et al., "Towards Requirements Traceability Models," Conference and Workshop on Systems Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 1995..
  27. [Ramesh, et al. 1997].
    Ramesh, B., et al., "Requirements Traceability: Theory and Practice," Annals of Software Engineering, 3 (January 1997), pp. 397-415.
  28. [Ramesh 1998].
    Ramesh, B., "Factors Influencing Requirements Traceability Practice," Communications of the ACM, 41, 12 (December 1998), pp. 37-44.
  29. [Ramesh and Bui 1999].
    Ramesh, B. and T. Bui, "Negotiation in Network Based Requirements Analysis," 32nd Annual Hawaii International Conference on Systems Sciences, Los Alamitos, California: IEEE Computer Society Press, 1999.
  30. [Ramesh 2000].
    Ramesh, B., "Implementing Requirements Traceability," Cutter IT Journal, 13, 5 (May 2000).
  31. [Ramesh and Jarke 2001].
    Ramesh, B., and M. Jarke, "Toward a Reference Model for Requirements Traceability," IEEE Transactions on Software Engineering, 27, 1 (January 2001), pp. 58-93.
  32. [Ramesh, et al. 2005].
    Ramesh, B., et al., "Managing Context in Business Process Management Systems," Requirements Engineering, 10, 3 (November 2005), pp. 223-237.
  33. [Ramires, et al. 2005].
    Ramires, J., et al., "Software Requirements Negotiation Using Software Quality Function Deployment," International Workshop on Groupware, Lecture Notes in Computer Science 3706, Berlin: Springer, 2005, pp. 308-324.

    Ramly, see El-Ramly
     
  34. [Ramos and Carvalho 2002].
    Ramos, I., and J. Carvalho, "Creating Work Realities Supported by Computer-Based Systems," International Workshop on Requirements Engineering: Foundations for Software Quality, Essen, Germany: Essener Informatik Beitiage, 2002, pp. 84-101.
  35. [Ramos, et al. 2005].
    Ramos, I., et al., "Requirements engineering for organizational transformation," Information and Software Technology, 47, 7 (May 2005), pp. 279-495.
  36. [Ramos and Berry 2005]
    Ramos, I., and D. Berry, "Is Emotion Relevant to Requirements," Requirements Engineering, 10, 3 (November 2005), pp. 238-242.
  37. [Ramzan, et al. 2006].
    Ramzan, S., et al., "Evaluation of the Requirements Change Management Models on the Basis of Process Model Elements and their Representation," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
  38. [Ramzan and Ikram 2007].
    Ramzan, S., and N. Ikram, "Requirement change management process models: activities, artifacts and roles," International MultiTopic Conference, Los Alamitos, California: IEEE Computer Society Press, 2007.
  39. [Randall, et al. 1994].
    Randall, D., et al., "Steps Toward a Partnership: Ethnography and System Design," in Requirements Engineering Social and Technical Issues, M. Jirotka, and J. Goguen, eds., London: Academic Press, 1994.
  40. [Ranjan and Misra 2006].
    Ranjan, P. and A. Misra, "A hybrid model for agent based system requirements analysis," ACM Software Engineering Notes, 31, 3 (May 2006), pp. 1-7.
  41. [Ranjan and Misra 2006a].
    Ranjan, P. and A. Misra, "A Novel Approach of Requirements Analysis for Agent Based System," ACIS International Conference on Software Engineering, Artificial Intelligence, Networking, and Parallel/Distributed Computing (SNPD'06), New York: ACM Press, 2006, pp. 299-304.
  42. [Rapanotti, et al. 2004].
    Rapanotti, L., et al., "Architecture-Driven Problem Decomposition," (see abstract) International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 80-89.
  43. [Rapanotti, et al. 2006].
    Rapanotti, L., et al., "Deriving specifications from requirements through problem reduction," IEE Proceedings on Software, 153, 5 (October 2006), pp. 183-198.
  44. [Rash 1999].
    Rash, W., "O Come All Ye Faithful: Analyze Your Requirements," InterNet Week, 771, (June 28, 1999), pp. 2-3.
  45. [Rash, et al. 2007].
    Rash, J., et al., "A requirements-based programming approach to developing a NASA autonomous ground control system," Artificial Intelligence Review, (2007).
  46. [Rashid, et al. 2002].
    Rashid, A., et al., "Early Aspects: a Model for Aspect-Oriented Requirements Engineering," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  47. [Rashid, et al. 2003].
    Rashid, A., et al., "Modularisation and Composition of Aspectual Requirements,"  Second International Conference on Aspect-Oriented Software Development, New York: ACM Press, March 2003, pp. 11-20.
  48. [Rashid, et al. 2004].
    Rashid, A., et al., "Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design,"  IEE Proceedings on Software, 151, 4 (August 2004), pp. 153-155.
  49. [Rashid, et al. 2006].
    Rashid, A., et al., "Visual Requirements Specification in End-User Participation," IEEE International Workshop on Multimedia Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006, p. 6.
  50. [Rashid 2007].
    Rashid, A., "OpenProposal: Towards Collaborative End-User Participation in Requirements Management By Usage of Visual Requirement Specifications,"     IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  51. [Ratchev, et al. 2003].
    Ratchev, S., et al., "Knowledge Based Requirement Engineering for One-of-a-Kind Complex Systems,"  Knowledge Based Systems, (2003); also appears in Concurrent Engineering, 13, 3 (2005), pp. 171-183.
  52. [Ratcliff 1988].
    Ratcliff, B., "Early and Not-So-Early Prototyping -- Rationale and Tool Support," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1988, pp. 127-134.
  53. [Ratcliffea and Budgen 2005].
    Ratcliffea, M., and D. Budgen, "The application of use cases in systems analysis and design specification,"  Information and Software Technology, 47, 9 (June 2005), pp. 623-641.
  54. [Rausch 2000].
    Rausch, A., "Software Evolution in Componentware Using Requirements/Assurances Contracts," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 147-156.
  55. [Rauterberg and Strom 1994].
    Rauterberg, M., and O. Strom, "About the Benefits of User-Oriented Requirements Engineering," International Workshop on Requirements Engineering: Foundations of Software Quality, June 1994.
  56. [Ravichandan, et al. 2007].
    Ravichandan, R., et al., "Reconciling Synthesis and Decomposition: A Composite Approach to Capability Identification," IEEE Conference and Workshop on Systems Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 287-298.
  57. [Ravichandan, et al. 2007a].
    Ravichandan, R., et al., "Capabilities Engineering: Constructing Change-Tolerant Systems," Hawaii International Conference on System Sciences (HICSS), Los Alamitos, California: IEEE Computer Society Press, 2007.
  58. [Ravid and Berry 2000].
    Ravid, A., and D. Berry, "A Method for Extracting and Stating Software Requirements that a User Interface Contains," Requirements Engineering Journal, 5, 4 (2000), pp. 225-241.
  59. [Ravn, et al. 1993].
    Ravn, A., et al., "Specifying and Verifying Requirements of Real-Time Systems," (see abstract) IEEE Transactions on Software Engineering, 19, 1 (January 1993), pp. 41-55.
  60. [Rawsthorne 1996].
    Rawsthorne, D., "Capturing Functional Requirements Through Object Interactions," (see abstract) Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 60-67.
  61. [Ray, et al. 2004].
    Ray, A., et al., "Secure Requirements Elicitation Through Triggered Message Sequence Charts," Lecture Notes in Computer Science, Volume 3347, Berlin: Springer, 2004, pp. 273-282. 
  62. [Raymond 2002]
    Raymond, D., "Authorisation Requirements on a Budget," Requirements Engineering, 7, 4 (2002), pp. 179-191.
  63. [Rayson, et al. 1999].
    Rayson, P., et al., "Recovering Legacy Requirements," Fifth International Workshop on Requirements Engineering: Foundations for Software Quality, Heidelberg, Germany, June 1999.
  64. [Reddy, et al. 2003].
    Reddy, M., et al., "Sociotechnical Requirements Analysis for Clinical Systems," Methods of Information in Medicine, 42, 4 (2003), pp. 437-444.

    Redondo, see also Diaz-Redondo
     
  65. [Reed 1993].
    Reed, M., "Requirements Traceability on the F-22," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1993.
  66. [Reed 1995].
    Reed, M., "Requirements Traceability on the F-22," Fifth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
  67. [Reed 1995a].
    Reed, M., "Requirements Management and Databases: The F-22 Program Solution," Fifth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
  68. [Refsdal, et al. 2006].
    Refsdal, A., et al., "Specification and Refinement of Soft Real-Time Requirements Using Sequence Diagrams," International Conference on Formal Modeling and Analysis of Timed Systems, Lecture Notes in Computer Science 3829, Berlin: Springer Verlag, 2006, pp. 32-48.
  69. [Regev and Wegmann 2004].
    Regev, G., and A.Wegmann, "Defining Early IT System Requirements with Regulation Principles: The Lightswitch Approach," (see abstract) International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 144-153.
  70. [Regev and Wegmann 2005].
    Regev, G., and A.Wegmann, "Where Do Goals Come From: The Underlying Principles of Goal-Oriented Requirements Engineering," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 253-262.
  71. [Regev, et al. 2005].
    Regev, G., et al., "Editorial: Coordinated Development of Business Processes and Their Support Systems," Requirements Engineering, 10, 3 (November 2005), pp. 173-174.
  72. [Regev, et al.  2006].
    Regev, G., et al., "Creativity and the Age-Old Resistance to Change Problem in RE," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  73. [Regnell, et al. 1995].
    Regnell, B., et al., "Improving the Use Case Driven Approach to Requirements Engineering," Second IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1995.
  74. [Regnell and Davidson 1997].
    Regnell, B., and A. Davidson, "From Requirements to Design with Use Cases - Experiences from Industrial Pilot Projects," Third International Workshop on Requirements Engineering: Foundations for Software Quality, Namur, Belgium: Presses Universitaires de Namur, 1997, pp. 205-222..
  75. [Regnell, et al. 1998].
    Regnell, B., et al., "A Market-Driven Requirements Engineering Process," Requirements Engineering, 3, 2 (February 1998), pp. 121-129.
  76. [Regnell and Runeson 1998].
    Regnell, B., and P. Runeson, "Combining Scenario-Based Requirements with Static Verification and Dynamic Testing," Fourth International Workshop on Requirements Engineering: Foundations of Software Quality, June 1998.
  77. [Regnell, et al. 2000].
    Regnell, B., et al., "Visualization of Agreement and Satisfaction in Distributed Prioritization of Market Requirements," Sixth International Workshop on Requirements Engineering: Foundations for Software Quality, Stockholm, Sweden, June 2000.
  78. [Regnell, et al. 2000a].
    Regnell, B., et al., "Are the Perspectives Really Different? Further Experimentation on Scenario-Based Reading of Requirements," Empirical Software Engineering, 5 (2000), pp. 331-356.
  79. [Regnell, et al. 2001].
    Regnell, B., et al., "An Industrial Case Study on Distributed Prioritization of Market-Driven Requirements Engineering for Packaged Software," Requirements Engineering Journal, 6, 1 (2001), pp. 51-62.
  80. [Regnell, et al. 2003].
    Regnell, B., et al., "An Analytical Model for Requirements Selection Quality Evaluation in Product Software Development," International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 254-263.
  81. [Regnell and Brinkkemper 2005].
    Regnell, B. and S. Brinkkemper, "Market-Driven Requirements Engineering for Software Products," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 287-308.
  82. [Regnell, et al. 2005].
    Regnell, B., et al., "Guest editorial: 10th anniversary workshop on Requirements Engineering: Foundation for Software Quality (REFSQ’2004)," Requirements Engineering, Requirements Engineering, 10, 4 (December 2005), pp. 243-246.
  83. [Regnell, et al. 2006].
    Regnell, B., et al., "Assessing Requirements Compliance Scenarios in System Platform Subcontracting," Product-Focused Software Process Improvement, Lecture Notes in Computer Science 4034, Berlin: Springer, 2006.
  84. [Regnell, et al. 2007].
    Regnell, B., et al., "A Quality Performance Model for Cost-Benefit Analysis of Non-Functional Requirements Applied to the Mobile Handset Domain," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ' 07), Berlin: Springer, 2007.
  85. [Reid 1990].
    Reid, T., "Object-oriented requirements analysis: a tool vision," Washington Ada Symposium, New York: ACM Press, 1990, pp. 227-230.
  86. [Reifer and Trattner 1976].
    Reifer, D., and S. Trattner, "Software Specification Techniques: A Tutorial," IEEE COMPCON, Los Alamitos, California: IEEE Computer Society Press, 1976.
  87. [Reifer 2002].
    Reifer, D., Making the Software Business Case, New York: Addison Wesley, 2002.
  88. [Reinertsen 1997].
    Reinertsen, D.,     Managing the Design Factory, New York: Free Press, 1997.
  89. [Reiser and Weber 2006].
    Reiser, M.-O., and M. Weber, "Managing Highly Complex Product Families With Multi-Level Feature Trees," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  90. [Reiser and Weber 2007]
    Reiser, M.-O., and M. Weber, "A domain model of Web recommender systems based on usage mining and collaborative filtering," Requirements Engineering, 12, 2 (April 2007), pp. 57-75.
  91. [Reizer, et al. 1994].
    Reizer, N., et al., "Using Formal Methods for Requirements Specification of a Proposed POSIX Standard," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 118-125.

  92. [Reubenstein and Waters 1989].
    Reubenstein, H., and R. Waters, "Requirements Apprentice: An Initial Scenario," International Workshop on Software Specification & Design, Los Alamitos, California: IEEE Computer Society Press, 1989.

  93. [Reubenstein and Waters 1991].
    Reubenstein, H., and R. Waters, "Requirements Apprentice: Automated Assistant for Requirements Acquisition," IEEE Transactions on Software Engineering, 17, 3 (March 1991), pp. 226-240.
  94. [Reubenstein 1994].
    Reubenstein, H., "The Role of Software Architecture in Software Requirements Engineering," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 244.
  95. [Revelle, et al. 1997].
    Revelle, J., et al., The QFD Handbook, New York: John Wiley, 1997.
  96. [Rexfelt and Rosenblad 2006].
    Rexfelt, O., and E. Rosenblad, "A Practical Framework for Eliciting and Modeling System Dependability Requirements: Experience from the NASA High Dependability Computing Project," International Journal of Industrial Ergonomics, 36, 1 (January 2006), pp. 73-81.
  97. [Reynolds 2007].
    Reynolds, P., "Managing requirements for a US$1bn IT-based business transformation: New approaches and challenges," The Journal of Systems and Software, 80, 3 (March 2007), pp. 285-293.
  98. [Rhodes 1996].
    Rhodes, R., "Objects, Actors and Roles: An Identity Triad For Requirements," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.

    Ribeiro, see Blois Ribeiro
     
  99. [Ricca, et al. 2007].
    Ricca, F., et al., "Talking tests: an empirical assessment of the role of fit acceptance tests in clarifying requirements," International Workshop on Principles of Software Evolution, Berlin: Springer, 2007.
  100. [Rice, et al. 2007].
    Rice, M., "Forum Theatre as a requirements gathering methodology in the design of a home telecommunication system for older adults," Behavior and Information Technology (2007). 
  101. [Rich, et al. 1987].
    Rich, C., et al., "Towards a Requirements Apprentice," 4th International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1987, pp. 79-86.
  102. [Richards 2003].
    Richards, D., "Merging Individual Conceptual Models of Requirements," Requirements Engineering Journal, 8, 4 (2003), pp. 195-205.
  103. [Richards 2003a].
    Richards, D., "Requirements Reconciliation using a Computer Supported Collaborative Approach," Journal of Integrated Design and Process Science, 7, 2 (June 2003), pp. 113-129.
  104. [Richards, et al.  2003].
    Richards, D., et al., "An Approach to Visualise and Reconcile Use Case Descriptions from Multiple Viewpoints," 11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 373-374.
  105. [Richards 2004].
    Richards, J., "Discovering Real Business Requirements," Quality Progress, 27, 11 (November 2004), pp. 97-100.
  106. [Richards 2004].
    Richards, D., "Using Concept Lattices for Requirements Reconciliation," Lecture Notes in Computer Science, Volume 2961, Berlin: Springer, 2004, pp. 402-409. 
  107. [Richter 1986].
    Richter, C., "An Assessment of Structured Analysis and Structured Design," ACM Software Engineering Notes, 11, 4 (August 1986), pp. 75-83.
  108. [Richter and Maffeo 1993].
    Richter, G., and B. Maffeo, "Toward a Rigorous Interpretation of ESML -- Extended Systems Modeling Language," (see abstract) IEEE Transactions on Software Engineering, 19, 2 (February 1993), pp. 165-180.
  109. [Richter, et al. 2005].
    Richter, H., et al., "An empirical investigation of capture and access for software requirements activities," IEEE Conference on Graphic Interface (GI), Los Alamitos, California: IEEE Computer Society Press, 2005.
  110. [Rickman 2001].
    Rickman, D., "A New Process for Requirements Understanding," 20th Digital Avionics Systems Conference, 2001, p. 4-D-4ff.
  111. [Riddle and Saeed 1999].
    Riddle, S., and A. Saeed, "Tool Support for Implementation and Analysis of Traceability," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1999.
  112. [Rifaut 2005].
    Rifaut, A., "Goal-Driven Requirements Engineering for Supporting the ISO 15504 Assessment Process," European Conference on Software Process Improvement (EuroSPI), Lecture Notes in Computer Science, Volume 3792, Berlin: Springer, 2005, pp. 151-162. 

  113. [Rindskopf 1996].
    Rindskopf, M., "Evolution of the Technical Requirements Baseline with Design Phases of a Program or Project," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.

  114. [Rinke and Weyer 2007].
    Rinke, T., and T. Weyer, "Defining Reference Models for Modelling Qualities: How Requirements Engineering Techniques can Help," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ' 07), Berlin: Springer, 2007.
  115. [Ripps 1990].
    Ripps, D., "Developing Real-Time Requirements," EDN, 35 (October 11, 1990), pp. 223ff.
  116. [Rittel 1972].
    Rittel, H., "On the Planning Crisis: Systems Analysis of the First and Second Generations," Bedriftokonomen, 8 (1972), pp. 390-396.
  117. [Ritzman and Gierszal 1990].
    Ritzman, P., and H. Gierszal, Study on Requirements Engineering, Freiburg, Germany: 2i Industrial Informatics, 1990.
  118. [Roast and Siddiqi 1997].
    Roast, C., and J. Siddiqi, "Usability Requirements as Specification Constraints: An Example of WYSIWYG," IEE Proceedings on Software Engineering, 144, 2 (April 1997), pp. 101-110.
  119. [Robben, et al. 1998].
    Robben, B., et al., "Components for Non-Functional Requirements," European Conference on Object-Oriented Technology (ECOOP), Lecture Notes in Computer Science 1543, Berlin: Springer, 1998, pp. 151ff.

  120. [Roberts and Renfro 1989].
    Roberts, L., and J. Renfro, "Software Requirements Engineering in IBM Systems Integration Division," AIAA Computers in Aerospace Conference, Los Alamitos, California: IEEE Computer Society Press, 1989.

  121. [Robertson and Robertson 1994].
    Robertson, J., and S. Robertson, Mastering the Requirements Process, New York: Addison Wesley, 1999.
  122. [Robertson and Robertson 1997].
    Robertson, J., and S. Robertson, "Requirements Made to Measure," American Programmer, 10, 8 (August 1997), pp. 27-32.
  123. [Robertson and Robertson 1999].
    Robertson, J., and S. Robertson, Complete Systems Analysis, Vols. 1 and 2, Upper Saddle River, New Jersey: Prentice Hall, 1994.
  124. [Robertson and Robertson 1999a].
    Robertson, J., and S. Robertson, "Reliable Requirements through the Quality Gateway," (see abstract) Tenth International Workshop on Database and Expert Systems Applications, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 357-363.
  125. [Robertson and Robertson 2000].
    Robertson, J., and S. Robertson, "Requirements Management: A Cinderella Story," Requirements Engineering Journal, 5, 2 (March 2000), pp. 134-136.
  126. [Robertson 2001].
    Robertson, S., "Who's Afraid of the Dark?" IEEE Software, 18, 4 (July/August 2001), pp. 12-15.
  127. [Robertson 2001a].
    Robertson, S., "Requirements Trawling: Techniques for Discovering Requirements," International Journal of Human-Computer Studies, 55, 4 (October 2001), pp. 405-421.
  128. [Robertson 2002].
    Robertson, J., "Eureka! Why Analysts Should Invent Requirements," IEEE Software, 19, 4 (July/August 2002), pp. 20-22.
  129. [Robertson 2004a].
    Robertson, S., "Requirements and the Business Case," IEEE Software, 21, 5 (September/October 2004), pp. 93-95.
  130. [Robertson and Robertson 2004].
    Robertson, J., and S. Robertson, Requirements-Led Project Management, Reading, Massachusetts: Addison-Wesley, 2004.
  131. [Robertson 2005].
    Robertson, J., "Requirements Analysts Must Also Be Inventors," IEEE Software, 22, 1 (January/February 2005), pp. 48, 50.

  132. [Robertson 2005a].
    Robertson, S., "Keynote: Exemplars for Better Requirements - Tales from the Trenches," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, p. 5.

  133. [Robertson 2006].
    Robertson, J. "Do Agilists Understand Requirements," Cutter IT Journal, 19, 7 (July 2006).
  134. [Robillard and Krutchen 2003].
    Robillard, P., and P. Krutchen, Software Engineering Processes: With the UPEDU, Boston, Massachusetts: Addison Wesley, 2003, Chapter 4.
  135. [Robinson 1988].
    Robinson, W., "Integrating Multiple Specifications Using Domain Goals," (see abstract) Fifth International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1988, pp. 216-226.
  136. [Robinson 1990].
    Robinson, W., "A Multi-Agent View of Requirements," 12th International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1990.
  137. [Robinson 1990a].
    Robinson, W., "Negotiation Behavior During Specification -- The Need for Formal Requirements," 12th International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1990.
  138. [Robinson and Fickas 1994].
    Robinson, W., and S. Fickas, "Supporting Multi-Perspective Requirements Engineering," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 206-215.
  139. [Robinson and Volkov 1997].
    Robinson, W., and S. Volkov, "A Meta-Model for Restructuring Stakeholder Requirements," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1997.
  140. [Robinson and Pawlowsky 1998].
    Robinson, W., and D. Pawlowsky, "Surfacing Root Requirements Interactions from Inquiry Cycle Requirements Documents," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 82-89.
  141. [Robinson and Volkov 1998].
    Robinson, W., and S. Volkov, "Supporting the Negotiation Life Cycle," (see abstract) Communications of the ACM, 41, 5 (May 1998), pp. 95-102.
  142. [Robinson and Pawlowsky 1999].
    Robinson, W., and D. Pawlowsky, "Managing Requirements Inconsistency with Development Goal Monitors," IEEE Transactions on Software Engineering, 25, 6 (June 1999), pp. 816-835.
  143. [Robinson 2001].
    Robinson, W., "Monitoring Software Requirements using Instrumented Code," 35th Hawaii Conference on Systems Sciences, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 3600-3609.
  144. [Robinson 2003].
    Robinson, W., "Run-Time Monitoring of Web Service Requirements," International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 65-74.
  145. [Robinson 2003a].
    Robinson, W., "Surfacing Requirements Interactions," in Perspectives on Software Requirements, Leite, J., and J. Doorn, eds., Berlin: Springer, 2003.
  146. [Robinson, et al. 2003].
    Robinson, W., et al., "Requirements Interaction Management," (see abstract) ACM Computing Surveys, 35, 2 (June 2003), pp. 132-191.
  147. [Robinson 2005].
    Robinson, W., "Implementing Rule-Based Monitors within a Framework for Continuous Requirements Monitoring," 38th Hawaii Conference on Systems Sciences, Los Alamitos, California: IEEE Computer Society Press, 2005, p. 188a.
  148. [Robinson, et al. 2005].
    Robinson, M., et al., "Risk Mitigation of Design Requirements Using a Probabilistic Analysis," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 231-239.
  149. [Robinson 2006].
    Robinson, W., "A requirements monitoring framework for enterprise systems," Requirements Engineering, 11, 1 (March 2006), pp. 17-41.
  150. [Rockart 1970].
    Rockart, J., "Model-Based Systems Analysis: A Methodology and Case Study," Industrial Management Review, 11, 2 (Winter 1970), pp. 1-14.
  151. [Rockstrom and Saracco 1982].
    Rockstrom, A., and B. Saracco, "SDL -- CCITT Specification and Description Language," IEEE Transactions on Communications, 30, 6 (June 1982), pp. 1310-1317.
  152. [Rodriguez-Dapena 2001].
    Rodriguez-Dapena, P., "Non-Functional Requirements as a Driving Force of Software Development," Software Quality Professional, 3, 4 (September 2001), pp. 12-22.
  153. [Rodriguez, et al. 2004].
    Rodriguez, O., et al., "Reasoning About Requirements Evolution Using Clustered Belief Revision," Lecture Notes in Computer Science, Volume 3171, Berlin: Springer, 2004, pp. 41-51. 
  154. [Rodríguez, et al. 2006].
    Rodríguez, A., et al., "Capturing Security Requirements in Business Processes Through a UML 2.0 Activity Diagrams Profile," Advances in Conceptual Modeling - Theory and Practice, Lecture Notes in Computer Science, Volume 4231, Berlin: Springer, 2006, pp. 32-42. 
  155. [Rodríguez, et al. 2006a].
    Rodríguez, A., et al., "Towards a UML 2.0 Extension for the Modeling of Security Requirements in Business Processes," Trust and Privacy in Digital Business, Lecture Notes in Computer Science, Volume 4083, Berlin: Springer, 2006, pp. 51-61. 
  156. [Rodríguez, et al. 2007].
    Rodríguez, A., et al., "M-BPSec: A Method for Security Requirement Elicitation from a UML 2.0 Business Process Specification," Advances in Conceptual Modeling - Theory and Practice, Berlin: Springer, 2007.
  157. [Rogers 2000].
    Rogers, W., "A Best Practices Approach to Software Requirements," (book reviews) IEEE Software, 17, 2 (March/April 2000), pp. 101-102.
  158. [Rolland and Proix 1992].
    Rolland, C., and C. Proix, "A Natural Language Approach to Requirements Engineering," (see abstract) 4th International CAiSE Conference, Manchester, UK, 1992.
  159. [Rolland 1994].
    Rolland, C., "Modeling and Evolution of Artifacts," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 216-219.
  160. [Rolland 1994a].
    Rolland, C., "A Contextual Approach for the Requirements Engineering Process," (see abstract) 6th International Conference on Software Engineering and Knowledge Engineering, June 1994.
  161. [Rolland and Prakash 1994].
    Rolland, C., and N. Prakash, "Guiding the Requirements Engineering Process," First Asia-Pacific Conference on Software Engineering, December 1994.
  162. [Rolland and Plihon 1996].
    Rolland, C., and V. Plihon, "Using Generic Method Chunks to Generate Process Models Fragments," (see abstract) Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 173-180.
  163. [Rolland, et al. 1998].
    Rolland, C., et al., "Guiding Goal Modeling Using Scenarios," (see abstract) IEEE Transactions on Software Engineering 24, 12 (December 1998), pp. 1055-1071.
  164. [Rolland, et al. 1998a].
    Rolland, C., et al., "A Proposal for a Scenario Classification Framework," Requirements Engineering Journal 3, 1 (1998), pp. 23-47.
  165. [Rolland and Ben Achour 1998].
    Rolland, C., and C. Ben Achour, "Guiding the Construction of Textual Use Case Specifications," Data and Knowledge Engineering 25, 1-2 (January 1998).
  166. [Rolland 1999].
    Rolland, C., "Requirements Engineering for COTS Based Systems," Information and Software Technology, 41, 14 (November 1999), pp. 985-990.
  167. [Rolland, et al. 1999].
    Rolland, C., et al., "Experience with goal-scenario coupling in requirements engineering," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999.
  168. [Rolland and Prakash 2000].
     Rolland, C., and N. Prakash, "From Conceptual Modelling to Requirements Engineering," Annals of Software Engineering, 10, 1 (January 2000), pp. 151-176.
  169. [Rolland, et al. 2003].
     Rolland, C., et al., "Guiding Lyee User Requirements Capture," Knowledge Based Systems, 16, 7-8 (November 2003), pp. 351-359.
  170. [Rolland, et al. 2004].
    Rolland, C., et al., "Eliciting Gaps in Requirements Change," Requirements Engineering, 9, 1 (February 2004), pp. 1-15.
  171. [Rolland and Salinesi 2005].
    Rolland, C., and C. Salinesi, "Modeling Goals and Reasoning with Them," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 189-217.
  172. [Rolland 2006].
     Rolland, C., "From Conceptual Modeling to Requirements Engineering," Conceptual Modeling - ER 2006, Lecture Notes in Computer Science, Volume 4215, Berlin: Springer, 2006, pp. 5-11. 
  173. [Rolland and Kaabi 2007].
    Rolland, C., and R.-S. Kaabi, "An Intentional Perspective to Service Modeling and Discovery," IEEE International Workshop on Requirements Engineering for Services, IEEE International Computer Software and Applications Conference (COMPSAC), Volume 2, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 455-460.
  174. [Roman 1982].
    Roman, G., "A Rigorous Approach to Building Formal System Requirements," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1982, pp. 417-423.
  175. [Roman 1985].
    Roman, G., "A Taxonomy of Current Issues in Requirements Engineering," IEEE Computer, 18, 4 (April 1985), pp. 14-23..
  176. [Romanchik 2003].
     Romanchik, D., "A Use Case Approach to Defining Software Requirements," Application Development Trends, 10, 9 (September 1, 2003), p. 61.
  177. [Romano and Palmer 1998].
    Romano, J., and J. Palmer, "TBRIM: Decision Support for Validation/Verification of Requirements," IEEE International Conference on Systems, Man, and Cybernetics, Volume 3, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 2489-2494.
  178. [Romanski 2003].
    Romanski, G.,  "Requirements, Configuration Management and Traceability for Safety Critical Software," 11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 304.
  179. [Rooksby, et al. 2007].
    Rooksby, J., "A Hybrid Approach to Upstream Requirements: IBIS and Cognitive Mapping," International Symposium on Software Metrics, Berlin: Springer, 2007.
  180. [Rosa, et al. 2000].
    Rosa, N., et al., "Incorporating Non-Functional Requirements into Software Architectures," Workshop on Parallel and Distributed Processing (IPDPS), Lecture Notes in Computer Science 1800, Berlin: Springer, 2000, pp. 1009ff.
  181. [Rosa, et al. 2002].
    Rosa, N., et al., "NFL: A Language for Describing Non-Functional Properties," 35th Hawaii International Conference on System Science, Los Alamitos, California: IEEE Computer Society Press, 2002.
  182. [Rosca 2000].
    Rosca, D., "An Active/Collaborative Approach in Teaching Requirements Engineering," 30th Annual Frontiers in Education Conference, Volume 1, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 9-12.

  183. [Rosca and Wild 2001].
    Rosca, D., and C. Wild, "Towards a Flexible Deployment of Business Rules," International Conference on Software Engineering and Knowledge Engineering, 2001.

  184. [Rosca, et al. 2002].
    Rosca, D., et al., "Enterprise Modeling and Decision-Support for Automating the Business Rules Lifecycle," Automated Software Engineering, 9, 4 (October 2002), pp. 9-12.
  185. [Rosca 2005].
    Rosca, D., "Multidisciplinary and Active/Collaborative Approaches in Teaching Requirements Engineering," European Journal of Engineering Education, 30, 1 (March 2005), pp. 121-128.
  186. [Rose, et al. 1992].
    Rose, T., et al., "Organizing Software Repositories Modeling Requirements and Implementation Experiences," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1992.
  187. [Rosenbaum and hackler 1981].
    Rosenbaum, J., and W. Hackler, "REQUIREMENTS SPECIFICATIONS FOR EMBEDDED ASTRONAUTIC SYSTEMS - AN INNOVATIVE METHODOLOGY," Advances in the Astronautical Sciences, 44, (1981), pp. 495ff.
  188. [Rosenberg, et al. 1998].
    Rosenberg, L., et al., "Requirements: Testing and Metrics," Fifteenth Annual Northwest Software Quality Conference, 1998.
  189. [Rosenberg, et al. 1998a].
    Rosenberg, L., et al., "Testing Metrics for Requirements Quality," Software Quality Week, 1998.
  190. [Rosenberg and Scott 2001].
    Rosenberg, D., and K. Scott, "Give Them What They Want," Software Development, 9, 6 (June 2001), pp. 54-56.

  191. [Rosenberg and Scott 2001a].
    Rosenberg, D., and K. Scott, "Driving Design: The Problem Domain," Software Development, 2001.

  192. [Ross 1977].
    Ross, D., "Guest Editorial: Reflections on Requirements," IEEE Transactions on Software Engineering, 3, 1 (January 1977), pp. 2-5.
  193. [Ross 1977a].
    Ross, D., "Structured Analysis: A Language for Communicating Ideas," IEEE Transactions on Software Engineering, 3, 1 (January 1977), pp. 16-34.
  194. [Ross and Schoman 1977].
    Ross, D., and K. Schoman, "Structured Analysis for Requirements Definition," IEEE Transactions on Software Engineering, 3, 1 (January 1977), pp. 6-15.
  195. [Ross 1978].
    Ross, D., "Quality starts with requirements definition," Constructing Quality Software, Amsterdam: North Holland, 1978, pp. 397-406.
  196. [Ross 1985].
    Ross, D., "Applications and Extensions to SADT," IEEE Computer, 18, 4 (April 1985), pp. 25-34.
  197. [Rossi and Tuunanen 2003].
    Rossi, M., and T. Tuunanen, "Marketing Meets Requirements Engineering," 11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 341.
  198. [Rossi and Tuunanen 2004].
    Rossi, M., and T. Tuunanen, "A Method and Tool for Wide Audience Requirements Elicitation and rapid Prototyping for Mobile Systems," Lecture Notes in Computer Science, Volume 3289, Berlin: Springer, 2004, pp. 629-640. 
  199. [Rost 2006].
    Rost, J.,  "Are "Best Practices" Requirements Documents a Myth?," IEEE Software, 23, 3 (May/June 2006), pp. 103-104.
  200. [Røstad 2006].
    Røstad, I., "An Extended Misuse Case Notation: Including Vulnerabilities and the Insider Threat," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
  201. [Roudies and Fredj 1999].
    Roudies, O., and M. Fredj, "A Reuse Based Approach for Requirements Engineering," ACS/IEEE International Conference on Computer Systems and Applications, Los Alamitos, California: IEEE Computer Society Press, 1999.
  202. [Rowatt, et al. 1997].
    Rowatt, W., et al., "Perceptions of Brainstorming in Groups: The Quality over Quantity Hypothesis," Journal of Creative Behavior, 31, pp. 131-150.
  203. [Roy 1983].
    Roy, D., "A Methodology for Expressing the System Requirements of a Switching System," Second Phoenix Conference on Computers and Communications, Los Alamitos, California: IEEE Computer Society Press, 1983, pp. 368-374.
  204. [Roy, et al. 2006].
    Roy, J.-F., et al., "Towards Integrated Tool Support for the User Requirements Notation," System Analysis and Modeling: Language Profiles, Lecture Notes in Computer Science Volume 4320, Berlin, Germany: Springer, 2006, pp. 198-215.
  205. [Rubens 2007]
    Rubens, J., "Business analysis and requirements engineering: the same, only different?," Requirements Engineering, 12, 2 (April 2007), pp. 121-123.
  206. [Rugg, et al. 2007].
    Rugg, G., et al., "Eliciting information about organizational culture via laddering," Information Systems (2007). 
  207. [Ruhe, et al. 2002].
    Ruhe, G., et al., "Quantitative WinWin: A New Method for Decision Support in Requirements Negotiation," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2002, pp. 167-174.
  208. [Ruhe, et al. 2003].
    Ruhe, G., et al., "Trade-Off Analysis for Requirements Selection," International Journal on Software Engineering and Knowledge Engineering, 13, 4 (August 2003), pp. 345-366.
  209. [Ruhe and Saliu 2005].
    Ruhe, G., and M. Saliu, "The Art and Science of Software Release Planning," IEEE Software, 22, 6 (November/December 2005), pp. 47-53.
  210. [Ruiz, et al. 2006].
    Ruiz, N., et al., "Early Requirement Guidelines for Multiagent System Modeling," IEEE Workshop on Distributed Intelligent Systems: Collective Intelligence and Its Applications (DIS'06), Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 183-188.
  211. [Ruiz-Cortéz, et al. 2001].
    Ruiz-Cortéz, A., et al., "Automated Support for Quality Requirements in Web Services Based Systems," Eighth IEEE Workshop on Future Trends in Distributed Computing Systems, Los Alamitos, California: IEEE Computer Society Press, 2001.
  212. [Ruiz-Cortéz, et al. 2002].
    Ruiz-Cortéz, A., et al., "Enhancing Win-Win to Automate the Detection of Conflicts in Quality Requirements," VII Jornadas del Software y Bases de Datos (JISBD '02), ISBN 84-688-0206-9, El Escorial (Madrid): Facultad de Informatica, Universitad Politechnica de Madrid, 2002, pp. 117-126.
  213. [Ruiz-Cortéz, et al. 2002a].
    Ruiz-Cortéz, J., et al., "Automatic Detection of Conflicts in Quality Requirements Models," in Applying Requirements Engineering, Durán, A., and M. Toro, eds., Salamanca, Spain: Catedral Publ., 2002, pp. 121-130.
  214. [Rundlet and Miller 1994].
    Rundlet, N., and W. Miller, "Requirements Management: DOORS to the Battlefield of the Future," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 65-72.
  215. [Rundlet and Miller 1995].
    Rundlet, N., and W. Miller, "Not Invented Here: The Movement from Internally Developed Tools to Doors for Requirements Management," Fifth International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
  216. [Runeson, et al. 1999].
    Runeson, P., et al., "Experimental and Simulation Analysis of Perspective Difference in Scenario-Based Requirements Inspection," Fifth International Workshop on Requirements Engineering: Foundations for Software Quality, Heidelberg, Germany, June 1999.
  217. [Rupp 2002].
    Rupp, C., "Requirements and Psychology," (see abstract) IEEE Software, 19, 3 (May/June 2002), pp. 16-18.
  218. [Rushby 1997].
    Rushby, J., "Calculating with Requirements," Third International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1997, pp. 144-146.

  219. [Rushton, et al. 2004].
    Rushton, G., et al., "Control Software Interface for Managing System Requirements," Society of Automotive Engineers World Congress, 2004.

  220. [Russell 2000].
    Russell, L., "Disaster Looks Good to Me," Cutter IT Journal, 13, 5 (May 2000).
  221. [Russell 2004].
    Russell, M., "Assessing the Impact of Requirements Volatility on the SE Process Using Bayesian Analysis," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  222. [Russo, et al. 1998].
    Russo, A., et al., "Restructuring Requirements Specifications for Managing Inconsistency and Change: A Case Study," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 51-60.
  223. [Russo, et al. 1999].
    Russo, A., et al., "Restructuring Requirements Specification," IEE Proceedings on Software, 146, 1 (February 1999), pp. 44-53.
  224. [Russo, et al. 2002].
    Russo, A., et al., "An Abductive Approach for Analysing Event-Based Requirements Specifications," Eighteenth International Conference on Logic Programming, Berlin: Springer, 2002.
  225. [Rutherford 1988].
    Rutherford, D., "Software requirements for for high integrity avionic systems," IEE Colloquium on High Integrity Systems, Los Alamitos, California: IEEE Computer Society Press, 1988. 
  226. [Ryan and Matthews 1993].
    Ryan, M., and B. Matthews, "Matching Conceptual Graphs to Requirements Re-use," International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 112-120.
  227. [Ryan 1993].
    Ryan, K., "The Role of Natural Language in Requirements Engineering," (see abstract) International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 240-242.
  228. [Ryan and O'Beirne 1994].
    Ryan, K., and A. O'Beirne, "An Experiment in Requirements Engineering Using Conceptual Graphs," Conference on Requirements Elicitation for Software-Based Systems, July 1994.
  229. [Ryan 1997].
    Ryan, K., "Commentary on AbstFinder: A Prototype Natural Language Text Abstraction Finder for Use in Requirements Elicitation," Automated Software Engineering, 4, 4 (October 1997), p. 415.
  230. [Ryan and Karlsson 1997].
    Ryan, K., and J. Karlsson, "Prioritizing Software Requirements in an Industrial Setting," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1997.
  231. [Rzepka 1983].
    Rzepka, W., "RADC SREM Evaluation Program -- A Status Report," ACM Software Engineering Notes, 8, 1 (January 1983), pp. 20-22.
  232. [Rzepka 1983a].
    Rzepka, W., "RADC SREM Evaluation Program -- Interim Results," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1983, pp. 644-645.
  233. [Rzepka 1985].
    Rzepka, W., "A Requirements Engineering Testbed," Third International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1985, pp. 205-206.
  234. [Rzepka and Ohno 1985].
    Rzepka, W., and Y. Ohno, "Guest Editors' Introduction: Requirements Engineering Environments,"  IEEE Computer, 18, 4 (April 1985), pp. 9-12.
  235. [Rzepka and Daley 1986].
    Rzepka, W., and P. Daley, "A Prototyping Tool to Assist in Requirements Engineering," 19th Hawaii International Conference on Systems Science, Los Alamitos, California: IEEE Computer Society Press, January 1986.

  236. [Rzepka 1989].
    Rzepka, W., "Requirements Engineering Testbed: Concept, Status and First Results," Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 1989.

  237. [Rzepka 1992].
    Rzepka, W., "A Requirements Engineering Testbed: Concept and Status," 2nd IEEE International Conference on Systems Integration, Los Alamitos, California: IEEE Computer Society Press, June 1992, pp. 118-126.
  238. [Rzepka, et al. 1993].
    Rzepka, W., et al., "Requirements Engineering Technologies at Rome Laboratory," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 15-18.
  239. [Rzepka 1994].
    Rzepka, W., "Technology Transfer at Rome Laboratory," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 148.

    S

    A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z     Demographics

          Saadoon, see Al-Saadoon
  1. [Sabetzadeh and Easterbrook 2005].
    Sabetzadeh, M., and S. Easterbrook, "iVuBlender: A Tool for Merging Incomplete and Inconsistent Views," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 453-454.
  2. [Sabetzadeh and Easterbrook 2005a].
    Sabetzadeh, M., and S. Easterbrook, "An Algebraic Framework for Merging Incomplete and Inconsistent Views," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 306-318.
  3. [Sabetzadeh and Easterbrook 2006a].
    Sabetzadeh, M., and S. Easterbrook, "View merging in the presence of incompleteness and inconsistency," Requirements Engineering, 11, 3 (June 2006), pp. 174-193.
  4. [Sabetzadeh, et al. 2007].
    Sabetzadeh, M., et al., "Consistency Checking of Conceptual Models via Model Merging," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  5. [Sadana and Liu 2007].
    Sadana, V., and X. Liu, "Analysis of Conflicts among Non-Functional Requirements Using Integrated Analysis," IEEE International Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 215-218.
  6. [Saeed, et al. 1991].
    Saeed, A., et al., "The Role of Formal Methods in the Requirements Analysis for Safety-Critical Systems: a Train Set Example," 21st Symposium on Fault-Tolerant Computing, June 1991, pp. 478-485.
  7. [Saeed, et al. 1992].
    Saeed, A., et al., An Approach to the Assessment of Requirements Specifications for Safety-Critical Systems, Technical Report 381, Computing Laboratory, University of Newcastle on Tyne, 1992.
  8. [Saeki, et al. 1996].
    Saeki, M., et al., "Structuring Utterance Records of Requirements Elicitation Meetings Based on Speech Act Theory," (see abstract) Second IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1996, pp. 21-30.
  9. [Saeki 1999].
    Saeki, M., "Reusing Use Case Descriptions for Requirements Specification: Towards Use Case Patterns," (see abstract) Sixth Asia Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 309-316.
  10. [Sagheb-Tehrani and Ghazarian 2002].
    Sagheb-Tehrani, M., and A. Ghazarian, "Software Development Process: Strategies for Handling Business Rules and Requirements," ACM Software Engineering Notes, 27, 2 (March 2002), pp. 58-62.
  11. [Sahraoui and Dhalgren 2001].
    Sahraoui, A., and J. Dhalgren, "Towards a System Engineering, Micro-Simulation Based Approach for Assessing Requirement For Transport Projects," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2001.
  12. [Saiedian and Dale 2000].
    Saiedian, H., and R. Dale, "Requirements Engineering: Making the Connection Between the Software Developer and Customer," Information and Software Technology, 42, 6 (April 2000), pp. 419-428.
  13. [Saiedian, et al. 2004].
    Saiedian, H., et al., "Scenario-Based Requirements Analysis Techniques for Real-Time Software Systems: A Comparative Analysis," Requirements Engineering, (accepted for publication 2004).
  14. [Sailor 1992].
    Sailor, J., "Building and Managing the Requirements/Verification Database," Second Annual International Symposium on Requirements Engineering, Seattle, Washington: International Council on Systems Engineering, July 1992.
  15. [Sakthivel and Moily 1993].
    Sakthivel, S., and J. Moily, "Analytic Verification of Information System Requirements using Petri Net Properties," Information and Software Technology, 35 (February 1993), pp. 89-100.
  16. [Saleh and El-Morr 2004].
    Saleh, K., and C. El-Morr, "M-UML: An Extension to UML for the Modeling of Mobile Agent-Based Software Systems," Information and Software Technology, 46, 4 (March 2004), pp. 219-227.

    Salem, see Al-Salem
     
  17. [Salifu, et al. 2007].
    Salifu, M., et al., "Specifying Monitoring and Switching Problems in Context," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  18. [Salinesi and Etien 2003].
    Salinesi, C., and A. Etien, "Compliance Gaps: A Requirements Elicitation Approach in the Context of System Evolution," Lecture Notes in Computer Science, Volume 2817, Berlin: Springer, 2003, pp. 71-82. 
  19. [Salinesi, et al. 2004].
    Salinesi, C., et al., "Goal/Strategy Maps: Methods, Techniques and Tools to Specify Requirements in Different Evolutionary Concepts," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  20. [Salinesi, et al.  2004a].
    Salinesi, C., et al., "A Systematic Approach to Express IS Evolution Requirements Using Gap Modelling and Similarity Modelling Techniques," Lecture Notes in Computer Science, Volume 3084, Berlin: Springer, 2004, pp. 338-352. 
  21. [Salit 2003]
    Salit, R., "Requirements Are Corporate Assets," IEEE Software, 20, 3 (May/June 2003), pp. 87-88.
  22. [Saliu and Ruhe 2005].
    Saliu, O., and G. Ruhe, "Software Release Planning for Evolving Systems," Innovations in Systems and Software Engineering, 1, 2 (September 2005), pp. 189-204.
  23. [Salo 1998].
    Salo, A., "Requirements for Groupware-Supported Requirements Process in New Product Development," Fourth International Workshop on Requirements Engineering: Foundations for Software Quality, Pisa, Italy, June 1998.
  24. [Salter 1976].
    Salter, K., "A Methodology for Decomposing System Requirements into Data Processing Requirements," 2nd International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1976, pp. 91-101.
  25. [Salvaneschi 1990].
    Salvaneschi, P., "User requirements quality," European Conference on Software Quality Assurance, Oslo, Norway: Norwegian Computer Society, 1990, pp. 14ff.
  26. [Salvatore and Alameda 2003].
    Salvatore, F., and T. Alameda,  "Daily Challenges in Requirements Engineering," 11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 297.
  27. [Salzer and Levin 2004].
    Salzer, H., and I. Levin, "Spreadsheet-Based Logic Controller for Teaching Fundamentals of Requirements Engineering," International Journal of Engineering Education, 20, 6 (2004).

  28. [Sampaio, et al. 2005].
    Sampaio, A., et al.,  "Early-AIM: An Approach for Identifying Aspects in Requirements," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 487-488.

  29. [Sampaio, et al. 2005a].
    Sampaio, A., et al.,  "EA-Miner: a tool for automating aspect-oriented requirements identification," IEEE/ACM international Conference on Automated software engineering, New York: ACM Press, 2005, pp. 352-355.

  30. [Sampaio, et al. 2007].
    Sampaio, A., et al., "EA-Miner: Towards Automation in Aspect-Oriented Requirements Engineering," Transactions on Aspect-Oriented Software Development, Berlin: Springer, 2007.

    Sampaio do Prado Leite, see Leite

  31. [Sampson 1997].
    Sampson, M., "Driving Test and Verification from SLATE," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1997.
  32. [Sampson 1998].
    Sampson, M., "Web-based Requirement Management and Regulatory Tracking," Eighth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1998.
  33. [Sampson 2003].
    Sampson, M., "Connected Requirements...Liberating Requirements So They Can Influence Design," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2003.

  34. [Samson 1987].
    Samson, D., "Object-Oriented Requirements Definition: Closing the Disconnect," International Conference on Systems Man and Cybernetics, 1987.

  35. [Samson 1990].
    Samson, D., "REQSPERT: automated test planning from requirements," International Conference on Systems Integration, Los Alamitos, California: IEEE Computer Society Press, 1990, pp. 702-708.

  36. [Samson 1993].
    Samson, D., "Knowledge-Based Test Planning: Framework for a Knowledge-Based System to Prepare a System Test Plan From System Requirements," The Journal of Systems and Software, 20, 2 (February 1993), pp. 115-124.
  37. [Sanchez 1996].
    Sanchez, J., "System Requirements Analysis," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  38. [Sanchez 1996a].
    Sanchez, J., "Application of Statistical Processes on a Set Theory Model for Anomaly Handling in System Requirements Analysis," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  39. [Sanchez 1996b].
    Sanchez, J., "Software Design of System Requirements Utilizing Set Theory Model for Anomaly Handling," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  40. [Sánchez-Díaz, et al. 2001].
    Sánchez-Díaz, J., et al., "From User Requirements to User Interfaces: A Methodological Approach," Lecture Notes in Computer Science, Volume 2068, Berlin: Springer, 2001, pp. 60ff. 
  41. [Sánchez-Díaz, et al. 2002].
    Sánchez-Díaz, J., et al., "Automatic Generation of User Interface Prototypes from Requirements Models," in Applying Requirements Engineering, Durán, A., and M. Toro, eds., Salamanca, Spain: Catedral Publ., 2002, pp. 101-119.
  42. [Sánchez-Díaz, et al.  2003].
    Sánchez-Díaz, J., et al., "Semi Automatic Generation of User Interface Prototypes from Early Requirement Models," in Perspectives on Software Requirements, Leite, J., and J. Doorn, eds., Berlin: Springer, 2003.
  43. [Sánchez-Alonso, et al. 2004].
    Sánchez-Alonso, M., et al., "COFRE: Environment for Specifying Coordination Requirements Using Formal and Graphical Techniques," Journal of Research and Practice in Information Technology, 36, 4 (November 2004). pp. 231-246.
  44. [Sánchez, et al. 2006].
    Sánchez, P., et al., "Towards MDD Transformations from AO Requirements into AO Architecture," Software Architecture, Lecture Notes in Computer Science Volume 4344, Berlin, Germany: Springer, 2006, pp. 159-174.
  45. [Sandahl, et al., 1998].
    Sandahl, K., et al., "An Extended Replication of an Experiment for Assessing Methods for Software Requirements Inspections," Empirical Software Engineering, 3, 4 (December 1998), pp. 327-354.
  46. [Sandahl, et al. 2002a].
    Sandahl, K., et al., "Requirements Engineering for Integrational Software Development," International Workshop on Requirements Engineering: Foundations for Software Quality, Essen, Germany: Essener Informatik Beitiage, 2002, pp. 172-177.
  47. [Santana-Filho and Kochan 2001].
    Santana-Filho, O., and K. Kochan, "The Importance of Requirements Engineering for Software Quality," International Conference on Information Systems, Analysis and Synthesis, Volume I, 2001.
  48. [Santander and Castro 2002].
    Santander, V., and J. Castro, "Deriving Use Cases from Organizational Modeling," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  49. [Santos and Carvalho 1996].
    Osborne, I., and J. Carvalho, "An Assessment of the Applicability of Object-Oriented Analysis to the Development of Information Systems," (see abstract) Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 238-244.
  50. [Santos and Carvalho 1998].
    Santos, I., and J. Carvalho, "The Structural, Social, Political and Symbolic Dimensions of Computer-Based Systems Requirements," Fourth International Workshop on Requirements Engineering: Foundations for Software Quality, Pisa, Italy, June 1998.
  51. [Sateesh 1995].
    Sateesh, T., "Making the Requirements of Process Controlled Systems," (see abstract) 28th Annual IEEE International Conference on System Sciences, Los Alamitos, CA: IEEE Computer Society Press, 1995.
  52. [Sateesh 1995a].
    Sateesh, T., "Conceptual model of real-time systems: a perspective," ACM Symposium on Applied Computing, New York: ACM Press, 1995, pp. 206-209.
  53. [Sato 1995].
    Sato, Y., "Requirements Acquisition in Systems Development: A Human-Centered Perspective of the Tacit Requirements," AI and Society, 9, 2-3 (June 1995), pp. 208-217.
  54. [Sato, et al. 2006].
    Sato, M., et al., "A Proposal of Requirement Definition Method with Patterns for Element / Network Management," Management of Convergence Networks and Services, Lecture Notes in Computer Science 4238, Berlin: Springer, 2006.
  55. [Saunders 1991].
    Saunders, P., "Effective Interviewing Tips for Information Systems Professionals," Journal of Systems Management, 42 (March 1991), pp. 28-31.
  56. [Savolainen and Kuusela 2001].
    Savolainen, J., and J. Kuusela, "Consistency Management of Product Line Requirements," (see abstract) Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 40-47.
  57. [Savolainen, et al. 2005a].
    Savolainen, J., et al., "Transitioning from product line requirements to product line architecture," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 186-195.
  58. [Savolainen, et al. 2007].
    Savolainen, J., et al., <