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


© 1996 - 2010, Alan M. Davis

This site provides a bibliography of over 5200 requirements-related papers and books organized by author's last name (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


A

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. [Aaist 2005].
    van der Aaist, W., "Business Alignment: Using Process Mining as a Tool for Delta Analysis and Conformance Testing," Requirements Engineering, 10, 3 (November 2005), pp. 198-211.
  2. [Aaist, et al. 2005].
    van der Aaist, W., et al., "Let's Go All the Way: From Requirements Via Colored Workflow Nets to a BREL Implementation of a New Bank System," On the Move to Meaningful Internet Systems Conference, Lecture Notes in Computer Science 3760, Berlin: Springer, 2005, pp. 22-39.
  3. [Abadi and Bahill 2002].
    Abadi, C., and A. Bahill, "Separating Product and Process Requirements," (see abstract) International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2002.
  4. [Abbott and Moorhead 1981].
    Abbott, R., and D. Moorhead, "Software Requirements and Specifications," Journal of Systems and Software, 2 (1981), pp. 297-316.
  5. [Abbott 1986].
    Abbott, R., An Integrated Approach to Software Development, New York: John Wiley, 1986, Chapters 2-5.
  6. [Abbott 2001].
    Abbott, B., "Requirements Set the Mark," InfoWorld, 23, 10 (March 5, 2001), pp. 45-46.

    Abdallah, see Ben-Abdallah
     
  7. [Abie, et al. 2004].
    Abie, H., et al., "Integrating a Security Requirement Language with UML," Lecture Notes in Computer Science, Volume 3273, Berlin: Springer, 2004, pp. 350-364. 
  8. [Abran and Robillard 1994].
    Abran, A., and P. Robillard, "Function Points: A Study of Their Measurement Processes and Scale Transformations," Journal of Systems and Software, 25 (1994), pp. 171-184.
  9. [Aburub, et al. 2007].
    Aburub, F., et al., "Modelling non-functional requirements of business processes," Information and Software Technology, 49, 11-12 (2007), pp. 1162-1171.
  10. [Acaba 1996].
    Acaba, R., "Lessons Learned in the Selection of a Company Standard Requirements Management Tool," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  11. [Achour, et al. 1999].
    ben Achour, C.,
    et al., "Guiding use case authoring: results of an empirical study," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999.
  12. [Ägerfolk and Ralyté 2006].
    Ägerfolk, P., and J. Ralyté, "Situational Requirements Engineering Processes: reflecting on method engineering and requirements practice," Software Process: Improvement and Practice (accepted 2006).
  13. [Acaba and Bostic 1996].
    Acaba, R., and K. Bostic, "A Simplified Method for Requirements Flowdown and Test Limit Definition," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  14. [Acharya, et al. 2005].
    Acharya, S., et al., "Domain consistency in requirements specification," Fifth International Conference on Quality Software, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 231-238.
  15. [Acosta, et al. 1999].
    Acosta, A., et al., "Prototypes Generator: Its User Interface and its Development Method," World Multi-Conference on Systemics, Cybernetics and Informatics, 1999, Volume 2.
  16. [Acosta, et al. 1994].
    Acosta, R., et al., "A Case Study of Applying Rapid Prototyping Techniques in the Requirements Engineering Environment," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 66-73.
  17. [Adam and Doerr 2008].
    Adam, S., and J. Doerr, "The role of service abstraction and service variability and its impact on requirements engineering for service-oriented systems," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 2008. 
  18. [Adams, et al. 1992].
    Adams, T., et al., "Utilization of Quality Function Deployment as a Tool for the Systems Engineer," Second Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, July 1992.
  19. [Adeel, et al. 2007].
    Adeel, K., "Defect Prevention Techniques and its Usage in Requirements Gathering - Industry Practices," Student Conference on Engineering Sciences and Technology (SCONEST), 2007.
  20. [Adhami, et al. 1989].
    Adhami, E., et al., "A knowledge-based approach to computer aided requirements engineering," Software Engineering Environments: Research and Practice, Chichester, UK: Ellis Horwood, 1989, pp. 187-202.
  21. [Adhikari 1994].
    Adhikari, S., "SysEn: An Integrated Approach to Specification, Modeling, Rapid Prototyping, Simulation and Documentation," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1994.
  22. [Adikari, et al. 2007].
    Adikari, S., et al., "Design Science-Oriented Usability Modelling for Software Requirements," International Conference on Human-Computer Interaction, Berlin: Springer, 2007.
  23. [Adler 1988].
    Adler, M., "An Algebra for Data Flow Diagram Process Decomposition," (see abstract) IEEE Transactions on Software Engineering, 14, 2 (February 1988), pp. 169-183.
  24. [Adolph, et al. 2003].
    Adolph, S., et al., Patterns for Effective Use Cases, Boston, Massachusetts: Addison Wesley, 2003.
  25. [Agarwal and Tanniru 1990].
    Agarwal, R., and M. Tanniru, "Knowledge acquisition using structured interviewing: an empirical investigation," Journal of Management Information Systems, 7, 1 (1990), pp. 123-140.
  26. [Agarwal and Jones 1994].
    Agarwal, N., and J. Jones, "Advancing System Engineering with a Requirements Problem Reporting Process," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 959-964.
  27. [Agarwal, et al. 1996].
    Agarwal, R., et al., "Cognitive Fit in Requirements Modeling: A Study of Object and Process Methodologies," (see abstract) Journal of Management Information Systems, 13, 2 (Fall 1996), pp. 137-162.
  28. [Agarwal and Ghosh 1999].
    Agarwal, R., and B. Ghosh, "Requirements Engineering for Enhancement Projects," 28th Argentine Meeting on Informatics and Operations Research, Workshop on Requirements Engineering (WER’99), Buenos Aires, Argentina, 1999.
  29. [Agarwal and Ghosh 2000].
    Agarwal, R., and B. Ghosh, "A Practical Approach for Iterative Re-Engineering of User Requirements," Sixth International Workshop on Requirements Engineering: Foundations for Software Quality, Stockholm, Sweden, June 2000.
  30. [Agarwal and Gupta 2008].
    Agarwal, A., and D. Gupta, "Security Requirements Elicitation Using View Points for Online System," International Conference on Emerging Trends in Engineering and Technology, Los Alamitos, California: IEEE Computer Society Press, 2008.
  31. [Ĺgerfalk and Ralyté 2006].
    Ĺgerfalk, P., and J. Ralyté, "Situational Requirements Engineering Processes: reflecting on method engineering and requirements practice," Software Process: Improvement and Practice, 11, 5 (September/October 2006), pp. 447-450.
  32. [Aggarwal 2002].
    Aggarwal, V., "The Application of the Unified Modeling Language in Object-Oriented Analysis of Healthcare Information Systems," (see abstract) Journal of Medical Systems, 26, 5 (October 2002), pp. 383-397.
  33. [Agouridas and Kossmann 2007].
    Agouridas, V., and M. Kossmann, "Combined Requirements Engineering: The Quest for Widening the Applicability of Requirements Engineering Practices," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2007.
  34. [Agouridas, et al. 2008].
    Agouridas, V., et al., "Advanced product planning: a comprehensive process for systemic definition of new product requirements," Requirements Engineering Journal, 13, 1 (January 2008), pp. 19-48.
  35. [Aguilar and Berry 1990].
    Aguilar, C., and D. Berry, "The Use of a Repeated Phrase Finder in Requirements Extraction," (see abstract) Journal of Systems and Software, 13, 3 (November 1990), pp. 209-230.
  36. [Agusa, et al. 1979].
    Agusa, K., et al., "Verification of Requirements Description," Twelfth Hawaii International Conference on System Science, Los Alamitos, California: IEEE Computer Society Press, 1979.
  37. [Agusa, et al. 1982].
    Agusa, K., et al., "Verification System for Formal Requirements Description," Sixth International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1982, pp. 120-126.
  38. [Agusa, et al. 1984].
    Agusa, K., et al., "A Verification Method for Formal Requirements Descriptions," Journal of Information Processing, 7, 4 (1984), pp. 223-229.
  39. [Agusa and Ohno 1985].
    Agusa, K., and Y. Ohno, "Supporting System for Software Maintenance - Ripple Effect Analysis of Requirements Description Modification," Journal of Information Processing, 8, 3 (1985), pp. 179-189.
  40. [Ahmad 2008].
    Ahmad, S., “Negotiation in the Requirements Elicitation and Analysis Process," IEEE Australian Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2008, pp. 683-689.
  41. [Ahmed, et al. 2007].
    Ahmed, F., et al., "Exploring Traceability-based Requirements Inspection," IASTED International Conference on Software Engineering and Applications (SEA), 2007.
  42. [Ahn and Chong 2006].
    Ahn, S., and K. Chong, "Eliciting potential requirements with feature-oriented gap analysis," 9th International Conference on Software Reuse (ICSR 2006), Lecture Notes in Computer Science 4039, Berlin: Springer, 2006, p 427-431.
  43. [Ahn and Chong 2006a].
    Ahn, S., and K. Chong, "A Feature-Oriented Requirements Tracing Method: A Study of Cost-Benefit Analysis," IEEE International Conference on Hybrid Information Technology (ICHIT), Los Alamitos, California: IEEE Computer Society Press, 2006, Volume 2, pp. 611-616.
  44. [Ahn and Chong 2007].
    Ahn, S., and K. Chong, "Requirements Change Management on Feature-Oriented Requirements Tracing," International Conference on Computational Science and Its Applications (ICCSA), Berlin: Springer, 2007.
  45. [Aiken 1990].
    Aiken, P., "Hypermedia-Based Requirements Engineering," in Advanced Technology for Command and Control System Engineering, S. Andriole, ed., Fairfax, Virginia: AFCEA International Press, 1990, pp. 48-65.
  46. [Aizenbud-Reshef, et al. 2006].
    Aizenbud-Reshef, N., et al., "Model Traceability," IBM Systems Journal, 45, 3 (2006), pp. 515-526.
  47. [van der Akker, et al., 2008].
    Akker, M. van der, et al., "Software product release planning through optimization and what-if analysis," Information and Software Technology, 50, 1-2 (January 2008), pp. 101-111 (5-7?).
  48. [Akkermans and Gordijn 2006].
    Akkermans, H., and J. Gordijn, "What is this Science called Requirements Engineering?," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  49. [Akoumianakis and Stephanidis 2005].
    Akoumianakis, D., and C. Stephanidis, "Chapter 13: Using Non-Functional Requirements as Design Drivers for Universal Access," in Universal Access in Health Telematics, Lecture Notes in Computer Science 3041, Berlin: Springer, 2005, pp. 141-155.
  50. [Akoumianakis, et al. 2007].
    Akoumianakis, D., et al., "Non-functional User Interface Requirements Notation (NfRn) for Modeling the Global Execution Context of Tasks," International Workshop on Task Models and Diagrams for Users Interface Design, Berlin: Springer, 2007.
  51. [Alaa and Fitzgerald 2004].
    Alaa, G., and G. Fitzgerald, "A Proposal for an Upfront Modeling and Design Practice for eCommerce Applications," Thirty-Seventh Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 174-183.
  52. [Al-Ani 2003].
    Al-Ani, B., "A Framework to Validate Requirements Engineering Research Artifacts," 1st International Workshop on Comparative Evaluation in Requirements Engineering, Sydney, Australia: Faculty of Information Technology, University of Technology, Sydney, 2003, pp. 27-33.
  53. [Al-Ani and Edwards 2004].
    Al-Ani, B., and K. Edwards, "An Empirical Study of a Qualitative Systematic Approach to Requirements Analysis (QSARA)," International Symposium on Empirical Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 177-186.
  54. [Al-Ani and Yusop 2004].
    Al-Ani, B., and N. Yusop, "Role-Playing, Groupwork, and Other Ambitious Teaching Methods in a Large Requirements Engineering Course," IEEE Conference and Workshop on Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 299-306.
  55. [Al-Ani and Sim 2006].
    Al-Ani, B., and S. Sim, "So, You Think You Are a Requirements Engineer? (poster)," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  56. [Al-Ani and Sim 2006a].
    Al-Ani, B., and S. Sim, "Using Examples as a Framework for Evaluating Requirements Terminology," IEEE International Workshop on Comparative Evaluation in Requirements Engineering (CERE), Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 3-7.
  57. [Al-Ani 2002].
    Al-Ani, B., "Systems' Requirements: Once Captured, are Slaughtered," Australian Workshop on Requirements Engineering, 2002.
  58. [Alarcon and Garbajosa 2007].
    Alarcon, P., and J. Garbajosa, "Identifying Application Key Knowledge through System Operations Modeling," International Conference on Cognitive Informatics, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 246-254.
  59. [Alavi and Wetherbe 1982].
    Alavi, M., and J. Wetherbe, "Reducing Complexity in Information Requirements Planning," Systems, Objectives, and Solutions, 2, 3 (August 1982), pp. 143-158.

    al Balushi, see Balushi
     
  60. [AlBourae, et al. 2006].
    AlBourae, T., et al., "
    Lightweight Replanning of Software Product Releases," IEEE International Workshop on Software Product Management, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 27-34.

    Alcazar, see Garcia-Alcazar
     
  61. [Aldaijy 2004].
    Aldaijy, A., " Empirical Assessment of the Impact of Requirements Uncertainty on Development Quality Performance," Command and Control Research and Technology Symposium 2004, Command and Control Research Program, 2004.
  62. [Aldaijy, et al. 2006].
    Aldaijy, A., et al., "The effects of requirements and task uncertainty on software product quality," 15th International Conference on Software Engineering and Data Engineering, Cary, NC: International Society for Computers and Their Applications, 2006, pp. 8ff.
  63. [Alderson 1999].
    Alderson, A., "False Requirements Express Real Needs," (see abstract) Requirements Engineering Journal, 4, 1 (1999), pp. 60-61.
  64. [Alencar, et al. 2006].
    Alencar, F., et al., "Using Aspects to Simplify i*Models (poster)," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  65. [Alenljung and Persson 2005].
    Alenljung, B., and A. Persson, "Factors that Affect Requirements Engineers in Their Decision Situations: A Case Study", 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
  66. [Alenljung and Persson 2008].
    Alenljung, B., and A. Persson, "DESCRY: A Method for Evaluating Decision-Supporting Capabilities of Requirements Engineering Tools," International Working Conference on Requirements Engineering: Foundations for Software Quality, Berlin: Springer, 2008.
  67. [Alencar, et al. 2008].
    Alencar, F., et al., "Integration of Aspects with i* Models," International Bi-Conference Workshop on Agent-Oriented Information Systems, Berlin: Springer, 2008.
  68. [Alenljung and Persson 2008].
    Alenljung, B. and A. Persson, "Portraying the Practice of Decision-Making in Requirements Engineering: A Case of Large Scale Bespoke Development," Requirements Engineering, 13, 4 (October 2008), pp. 257-279.
  69. [Alexander and Potter 1987].
    Alexander, H., and B. Potter, "Case Study: The Use of Formal Specification and Rapid Prototyping to Establish Product Feasibility," Information and Software Technology, 29, 7 (September 1987), pp. 388-394.
  70. [Alexander 1997].
    Alexander, I., "A Historical Perspective on Requirements," Requirenautics Quarterly, 12 (October 1997), pp. 13-20.
  71. [Alexander 1998].
    Alexander, I., "Why You Need Requirements Engineering," Requirenautics Quarterly, 15 (October 1998), pp. 9-10.
  72. [Alexander 1999].
    Alexander, I., "Extreme Programming: Rapid Requirements," Requirenautics Quarterly, 14 (1999).
  73. [Alexander 1999a].
    Alexander, I., "Do User Requirements Exist?" Requirenautics Quarterly, 14 (1999).
  74. [Alexander 1999b].
    Alexander, I., "Is There Such a Thing as a User Requirements?" (see abstract) Requirements Engineering Journal, 4, 4 (1999), pp. 221-223.
  75. [Alexander 1999c].
    Alexander, I., "Migrating Towards Cooperative Requirements Engineering," Computing and Control Engineering Journal, 10, 1 (February 1999), pp. 17-22.
  76. [Alexander 1999d].
    Alexander, I., "Supporting a Co-Operative Requirements Engineering Process," International Workshop on Database and Expert System Applications, Los Alamitos, California: IEEE Computer Society Press, 1999.
  77. [Alexander 2001].
    Alexander, I., "What is Requirements Engineering Anyway?" Requirenautics Quarterly, 16 (1999).
  78. [Alexander 2001a].
    Alexander, I., "Requirements Are Either Needs or Specifications," Requirenautics Quarterly, 16 (1999).
  79. [Alexander 2001b].
    Alexander, I., "On Abstraction in Scenarios," Requirements Engineering Journal, 6, 4 (2001), pp. 252-255.
  80. [Alexander 2001c].
    Alexander, I., "Toward Automatic Traceability in Industrial Practice," International workshop on Traceability in emerging forms of software engineering, New York: ACM Press, 2001.
  81. [Alexander 2002].
    Alexander, I., "Initial Industrial Experience of Misuse Cases in Trade-Off Analysis," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  82. [Alexander and Kiedaisch 2002].
    Alexander, I., and F. Kiedaisch, "Towards Recyclable System Requirements," 9th Annual IEEE International Conference on the Engineering of Computer Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2002, pp. 9-16.
  83. [Alexander and Stevens 2002].
    Alexander, I., and R. Stevens, Writing Better Requirements, London, UK: Addison-Wesley, 2002.
  84. [Alexander and Zink 2002].
    Alexander, I., and T. Zink, "Introduction to Systems Engineering with Use Cases," Computing and Control Engineering 13, 6 (December 2002), pp. 289-297.
  85. [Alexander 2003].
    Alexander, I., "Misuse Cases: Use Cases with Hostile Intent," IEEE Software, 20, 1 (January-February 2003), pp. 58-66.
  86. [Alexander 2003a].
    Alexander, I., "Misuse Cases Help to Elicit Non-Functional Requirements," Computing and Control Engineering, 14, 1 (February 2003), pp. 40-45.
  87. [Alexander 2003b].
    Alexander, I., "Stakeholders: Who Is Your System For?," (see abstract) Computing and Control Engineering, 14, 2 (March 2003).
  88. [Alexander 2003c].
    Alexander, I., "Book Review: Designing Collaborative Systems. A Practical Guide to Ethnography by A. Crabtree," European Journal of Information Systems, 12, (2003), pp. 247-248.
  89. [Alexander and Robertson 2004].
    Alexander, I., and S. Robertson, "Understanding Project Sociology by Modeling Stakeholders," IEEE Software, 21, 1 (January-February 2004), pp. 23-27.
  90. [Alexander and Maiden 2004].
    Alexander, I., and N. Maiden, eds., Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle, New York: John Wiley and Sons, 2004.
  91. [Alexander, et al. 2005].
    Alexander, I., et al., "What Influences the Requirements Practice in Industry: A Report on Industrial Practice," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 411-415.
  92. [Alexander 2005].
    Alexander, I., "Book Review: Agile or Analytic: Cohn vs. Lavi and Kudish," Requirements Engineering, 10, 4 (December 2005), pp. 307-308.
  93. [Alexander 2006].
    Alexander, I., "10 Small Steps to Better Requirements" IEEE Software, 23, 2 (March-April 2006), pp. 19-21.
  94. [Alexander 2006a].
    Alexander, I., "Identifying Dissonance and Other Dangers from Requirements," IEE Institution of Engineering and Technology International Conference on System Safety,
    Stevenage, UK: Institute of Engineering Technology, 2006.
  95. [Alexander 2007].
    Alexander, I., "Building What Stakeholders Desire (Point Counterpoint)," IEEE Software, 24, 2 (March-April 2007), pp. 62-65.
  96. [Alexander 2007a].
    Alexander, I., "Choosing a Tram Route: An Experience in Trading-Off Constraints,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  97. [Alexander 2008].
    Alexander, I., "Evaluating the Options Against Requirements: How Far Can Statistics Go?," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2008.
  98. [Alferez, et al. 2007].
    Alferez, M., "Toward Volatility Analysis in Software Product Line Engineering," Workshop on Aspect-Oriented Product Line Engineering (AOPLE), 2007.
  99. [Alferez, et al. 2008].
    Alferez, M., et al., "A Model-Driven Approach for Software Product Lines Requirements Engineering," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2008.
  100. [Alfonso, et al. 2004].
    Alfonso, A., et al., "Visual Timed Event Scenarios," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004.
  101. [Alford and Burns 1976].
    Alford, M., and I. Burns, "R-Nets: A Graph Model for Real-Time Software Requirements," Symposium on Computer Software Engineering, New York: Polytechnic Press, 1976, pp. 97-108.
  102. [Alford 1977].
    Alford, M., "A Requirements Engineering Methodology for Real-Time Processing Requirements," IEEE Transactions on Software Engineering, 3, 1 (January 1977), pp. 60-69.
  103. [Alford 1978].
    Alford, M., "Software Requirements Engineering Methodology at the Age of Two," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1978, pp. 332-339. 
  104. [Alford 1979].
    Alford, M., "Requirements for Distributed Data Processing Design," First International Conference on Distributed Computer Systems, Los Alamitos, California: IEEE Computer Society Press, 1979, pp. 1-14. 
  105. [Alford 1980].
    Alford, M., "Software Requirements Engineering Methodology at the Age of Four," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1980, pp. 866-874. 
  106. [Alford 1980a].
    Alford, M., "Software Requirements in the 80s: From Alchemy to Science," ACM '80 Conference, New York: ACM Press Press, 1980, pp. 342-349.
  107. [Alford 1984].
    Alford, M., "Derivation of Database Management Design from System Requirements," IEEE International Conference on Data Engineering, Los Alamitos, California: IEEE Computer Society Press, 1984.   
  108. [Alford 1985].
    Alford, M., "SREM at the Age of Eight: the Distributed Computing Design System," IEEE Computer, 18, 4 (April 1984), pp. 36-46.   
  109. [Alford 1991].
    Alford, M., "Strengthening the Systems Engineering Process," International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 1991.
  110. [Alford 1993].
    Alford, M., "Behavior Based System Test Planning," International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 1993.
  111. [Alford 1994].
    Alford, M., "Attacking Requirements Complexity Using a Separation of Concerns," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 2-5.
  112. [Alford 1994a].
    Alford, M., "Panel Session: Issues in Requirements Engineering Technology Transfer: From Researcher to Entrepreneur," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 144.
  113. [Alford 1995].
    Alford, M., "Taming the Software Monster with Threads," International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 1995.
  114. [Alghathbar 2007].
    Alghathbar, K., "Validating the enforcement of access control policies and separation of duty principle in requirement engineering," Information and Software Technology, to appear, 2007.
  115. [Ali and Hall 2008].
    Ali, S., and J. Hall, "Introducing Regulatory Compliance Requirements Engineering," Information Security Solutions Europe Conference, Berlin: Springer, 2008.
  116. [Alipour and Isazadeh 2008].
    Alipour, H., and A. Isazadeh, "Software reliability assessment based on a formal requirements specification," International Conference on Human Systems Interaction (HSI), 2008.
  117. [Al-Karaghouli, et al. 2000].
    Al-Karaghouli, W., et al., "Negotiating and Understanding Information Systems Requirements: The Use of Set Diagrams," (see abstract) Requirements Engineering Journal, 5, 2 (2000), pp. 93-102.
  118. [Al-Karaghouli, et al. 2005].
    Al-Karaghouli, W., et al., "Negotiating and Understanding Information Systems Requirements: The Use of Set Diagrams," Journal of Enterprise Information Management  (2005).
  119. [Alkkiomaki and Smolander 2007].
    Alkkiomaki, V., and K. Smolander, "Integration Use Cases - An Applied UML Technique for Modeling Functional Requirements in Service Oriented Architecture," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ' 07), Berlin: Springer, 2007.
  120. [Allenby and Kelly 2001].
    Allenby, K., and T. Kelly, "Deriving Safety Requirements Using Scenarios," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 228-235.
  121. [Almefelt, et al. 2006].
    Almefelt, L., et al., "Requirements management in practice: findings from an empirical study in the automotive industry," Research in Engineering Design, (2006).
  122. [Almendros-Jimenez and Gonzalez-Jimenez 2002].
    Almendros-Jimenez, J., and L. Gonzalez-Jimenez, "Bases for the Development of LAST: a Formal Method for Business Software Requirements Specification," Information and Software Technology, 44, 2 (February 2002), pp. 65-75.

    Alonso, see also Sánchez-Alonso
     
  123. [Alonso Amo, et al. 1999].
    Alonso Amo, F., et al., "An Incremental Prototyping Approach to Software Development in Knowledge Engineering," World Multi-Conference on Systemics, Cybernetics and Informatics, 1999, Volume 2.
  124. [Al-Otaiby, et al. 2004].
    Al-Otaiby, T., et al., "Software Modularization Using Requirements Attributes," 42nd Annual ACM Southeast Conference, New York: ACM Press, 2004, pp. 104-109.
  125. [Al-Otaiby and AlSharif 2007].
    Al-Otaiby, T., and F. AlSharif, "Software requirements modularization using partitioning clustering technique," ACM Southeastern Conference (SOUTHEASTCON), New York: ACM Press, 2007, pp. 65-69.
  126. [Alrajeh, et al. 2007]
    Alrajeh, D., et al., "Extracting Requirements from Scenarios with ILP," in Inductive Logic Programming, Lecture Notes in Computer Science, Volume 4455, Berlin: Springer, 2007, pp. 64-78.
  127. [Al-Rawas and Easterbrook 1996].
    Al-Rawas, A., and S. Easterbrook, "Communication Problems in Requirements Engineering: A Field Study," First Westminster Conference on Professional Awareness in Software Engineering, University of Westminster, Westminster, London, UK, 1996, pp. 47-60.
  128. [Al-Saadoon, et al. 1995].
    Al-Saadoon, O., et al., "AURA-CFG/E: An Object-Oriented Approach for Acquisition and Decomposition of DFDs from End Users," Seventh International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, June 1995, pp. 1-7.
  129. [Al-Salem and Samaha 2007].
    Al-Salem, L., and A. Samaha, "Eliciting Web application requirements - an industrial case study," Journal of Systems and Software, 80, 3 (March 2007), pp. 294-313.
  130. [Al-Salem and Samaha 2007a].
    Al-Salem, L., and A. Samaha,
    "Strategy-focused requirements engineering method for web applications," International Journal of Web Engineering and Technology, (2007).
  131. [Alshawi and Al-Karaghouli2003].
    Alshawi, S., and W. Al-Karaghouli, "Managing knowledge in business requirements identification," Logistics Information Management (2003).
  132. [Alspaugh, et al. 1999].
    Alspaugh, T.,
    et al., "An integrated scenario management strategy," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999.
  133. [Alspaugh and Antón 2001].
    Alspaugh, T., and A. Antón, "Scenario Networks: A Case Study of the Enhanced Messaging System," Seventh International Workshop on Requirements Engineering: Foundations for Software Quality, Interlocken, Switzerland, June 2001.
  134. [Alspaugh 2002].
    Alspaugh, T., Scenario Networks and Formalization for Scenario Management, Ph.D. dissertation, North Carolina State University, Raleigh, North Carolina, September 2002.
  135. [Alspaugh and Antón 2003].
    Alspaugh, T., and A. Antón,  "Contrasting Use Case, Goal, and Scenario Analysis of the Euronet System,"
    11th IEEE International Conference on Requirements Engineering
    , Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 355-356.
  136. [Alspaugh, et al. 2005].
    Alspaugh, T., et al., "Scenario-Driven Specification-Based Testing Against Goals and Requirements," 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
  137. [Alspaugh and Antón 2008].
    Alspaugh, T., and A. Antón,  "Scenario support for effective requirements," Information and Software Technology (2008).
  138. [Al-Subaie and Maibaum 2006].
    Al-Subaie, H., and T. Maibaum, "Evaluating the Effectiveness of a Goal-Oriented Requirements Engineering Methodology," IEEE International Workshop on Comparative Evaluation in Requirements Engineering (CERE), Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 8-19.
  139. [Alter 2004].
    Alter, S., "Possibilities for cross-fertilization between interpretive approaches and other methods for analyzing information systems," European Journal of Information Systems, 13, 3 (September 2004), pp. 173-185.
  140. [Alur and Weiss 2008].
    Alur, R., and G. Weiss, "Regular specifications of resource requirements for embedded control software," IEEE Symposium on Real-Time and Embedded Technology and Applications, Los Alamitos, California: IEEE Computer Society Press, 2008.
  141. [Alur, et al. 2008].
    Alur, R., et al., "Ranking automata and games for prioritized requirements," International Conference on Computer Aided Verification (CAV), Berlin: Springer, 2008.

    Alvarez, see also Granja-Alvarez
     
  142. [Alvarez 2001].
    Alvarez, R., "There's More to the Story: Using Narrative Analysis to Examine Requirements Engineering as a Social Process," Seventh International Workshop on Requirements Engineering: Foundations for Software Quality, Interlocken, Switzerland, June 2001.
  143. [Alvarez 2002].
    Alvarez, R., "Discourse Analysis of Requirements and Knowledge Elicitation Interviews," 35th Hawaii International Conference on System Science, Los Alamitos, California: IEEE Computer Society Press, 2002.
  144. [Alvarez and Urla 2002].
    Alvarez, R., and J. Urla, "Tell Me a Good Story: Using Narrative Analysis to Examine Information Requirements Interviews during an ERP Implementation," ACM SIGMIS Database, 33, 1 (Winter 2002), pp. 38-52.
  145. [Alves and Finkelstein 2002].
    Alves, C., and A. Finkelstein, "Challenges in COTS Decision-Making: A Goal-Driven Requirements Engineering Perspective," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2002, pp. 789-794.
  146. [Alves and Finkelstein 2002a].
    Alves, C., and A. Finkelstein, "Negotiating Requirements for COTS-Based Systems," International Workshop on Requirements Engineering: Foundations for Software Quality, 2002.
  147. [Alves 2003].
    Alves, C., "COTS-Based Requirements Engineering,"Conference on Component-Based Software Quality-Methods and Techniques, Lecture Notes in Computer Science, Volume 2693, Berlin: Springer, 2003, pp. 21-39. 
  148. [Alves, et al. 2007].
    Alves, C., et al., "Challenges in Requirements Engineering for Mobile Games Development: The Meantime Case Study,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  149. [Alves, et al. 2008].
    Alves, C., et al., "Requirements engineering process improvement: a knowledge transfer experience," Symposium on Applied Computing, New York: ACM Press, 2008, pp. 619-623.
  150. [Alves, et al. 2008].
    Alves
    , C., et al., "Early Aspects: Aspect-Oriented Requirements and Architecture for Product Lines," International Conference on Software Product Lines, Los Alamitos, California: IEEE Computer Society Press, 2008.
  151. [Amaya, et al. 2006].
    Amaya, P., et al., "Towards a Subject-Oriented Model-Driven Framework,"
    Electronic Notes in Theoretical Computer Science, 193, 1 (September 2006), pp. 31-44.
  152. [Ambler 1994].
    Ambler, C., "Technology Transfer From the University Laboratory Point of View," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 146.
  153. [Ambler 2002].
    Ambler, S., Agile Modeling, New York: John Wiley, 2002, Chapters 24-25.
  154. [Ambler 2004].
    Ambler, S., "Come In Out of the Requirements Cold," Computing Canada, 30, 17 (November 2004), p. 11.
  155. [Ambriola and Gervasi 1997].
    Ambriola, V., and V. Gervasi, "Processing Natural Language Requirements," Twelfth Annual International Conference on Automated Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1997, pp. 36-45.
  156. [Ambriola and Gervasi 1997a].
    Ambriola, V., and V. Gervasi, "An Environment for Cooperative Construction of Natural Language Requirements Bases," Eighth Conference on Software Engineering Environments, Los Alamitos, California: IEEE Computer Society Press, 1997, pp. 124-130.
  157. [Ambriola and Gervasi 1998].
    Ambriola, V., and V. Gervasi, "Representing Structural Requirements in Software Architecture," (see abstract) International Conference on Systems Implementation 2000: Languages, Methods and Tools, London: Chapman and Hall, 1998, pp. 114-127.
  158. [Ambriola and Gervasi 1998a].
    Ambriola, V., and V. Gervasi, "The Case for Cooperative Requirements Writing," European Conference on Object-Oriented Technology (ECOOP), Lecture Notes in Computer Science 1543, Berlin: Springer, 1998, pp. 477ff.
  159. [Ambriola and Gervasi 2000].
    Ambriola, V., and V. Gervasi, "Process Metrics for Requirements Analysis," Seventh International  Workshop on Software Process Technology, Lecture Notes on Computer Science, 1780, Springer-Verlag, 2000, pp. 90-95.
  160. [Ambriola and Gervasi 2006].
    Ambriola, V., and V. Gervasi, "On the systematic analysis of natural language requirements with CIRCE," Automated Software Engineering, 13, 1 (January 2006), pp. 107-167.
  161. [America and van Wijgerden 2000].
    America, P., and J. Van Wijgerden, "Requirements Modeling for Families of Complex Systems," inSoftware Architectures for Product Families, Lecture Notes in Computer Science 1951, Berlin: Springer, 2000, pp. 199-209.
  162. [Amirat 2007].
    Amirat, A., "Towards a requirements model for crosscutting concerns," Information Technology Journal, 6, 3 (April 2007), pp. 332-337. 
  163. [Ampo and Lutz 1994].
    Ampo, Y., and
     R. Lutz, Initiating Formal Requirements Specifications with Object-Oriented Models, NASA Jet Propulsion Lab Technical Report 94-0847, 1994.
  164. [Amyot, et al. 1999].
    Amyot, D.,
    et al., "Use case maps for the capture and validation of distributed systems requirements," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999.
  165. [Amyot and Eberlein 2001].
    Amyot, D., and A. Eberlein, "An Evaluation of Scenario Notations for Telecommunication Systems Development," 9th International Conference on Telecommunication Systems (ICTS2001), Dallas, Texas, 2001.
  166. [Amyot 2003].
    Amyot, D., "Introduction to the User Requirements Notation: Learning by Example," Computer Networks, 42, 3 (June 2003), pp. 285-301.
  167. [Amyot and Mussmacher 2003].
    Amyot, D., and G. Mussbacher, "URN: Towards a New Standard for the Visual Description of Requirements," Lecture Notes in Computer Science, Volume 2599, Berlin: Springer, 2003, pp. 21-37. 
  168. [Anda and Sjřberg 2002].
    Anda, B., and D. Sjřberg, "Toward an Inspection Technique for Use Case Models," Fourteenth International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, July 2002.
  169. [Anderegg 1996].
    Anderegg, A., "A Concurrent Process for Development and Validation of Operational Requirements," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  170. [Anderson 1985].
    Anderson, T., Software Requirements: Specification and Testing, Oxford, UK: Blackwell Publishing, 1985.
  171. [Anderson 1989].
    Anderson, L., "Supporting Traceability Requirements with CASE," Defense Computing, 1989.
  172. [Anderson and Durney 1993].
    Anderson, J., and B. Durney, "Using Scenarios in Deficiency-Driven Requirements Engineering," (see abstract) International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 134-141.
  173. [Anderson and Shaw 1997].
    Anderson, A., and G. Shaw, "Executable Requirements and Specifications," Journal of VLSI Signal Processing, 1997.
  174. [Anderson and Felici 2000].
    Anderson, R., and M. Felici, "Controlling Requirements Evolution: An Avionics Case Study," International Conference on Computer Safety, Reliability, and Security (SAFECOMP), Lecture Notes in Computer Science 1943, Berlin: Springer, 2000, pp. 361ff.
  175. [Anderson, et al. 2000].
    Anderson, S., et al., "
    Experiences with the Application of Symbolic Model Checking to the Analysis of Software Specifications," Lecture Notes in Computer Science 1755, Berlin: Springer, 2000, pp. 460ff.
  176. [Anderson and Felici 2001].
    Anderson, S., and M. Felici, "Requirements Evolution: From Process to Product Oriented Management," Lecture Notes in Computer Science, 2188 (2001), pp. 27-41. 
  177. [Anderson, et al. 2005].
    Anderson, E., et al., "
    An Enterprise Level Security Requirements Specification Model," 38th Hawaii Conference on Systems Sciences, Los Alamitos, California: IEEE Computer Society Press, 2005, p. 186c.
  178. [Andersson, et al. 2008].
    Andersson, B., et al., "Aligning goals and services through goal and business modelling," Information Systems and E-Business Management, Berlin: Springer, 2008.
  179. [Andrade, et al. 1999].
    Andrade, J., et al., "Creation of an Automated Management Software Requirements Environment: A Practical Experience," (see abstract) Tenth International Workshop on Database and Expert Systems Applications, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 328-335.
  180. [Andrade, et al. 2004].
    Andrade, J., et al., "Computer-Assisted Discrepancy Management -- A Case Study in Research Transfer to Industry," Journal of Research and Practice in Information Technology, 36, 4 (November 2004), pp. 295-315.
  181. [Andrade, et al. 2004a].
    Andrade, J., et al., "A methodological framework for viewpoint-oriented conceptual modeling," IEEE Transactions on Software Engineering, 30, 5 (May 2004), pp. 282-294.
  182. [Andrea and Meszaros 2004].
    Andrea J, and G. Meszaros, "Agile Requirements: Tailoring the Functional Requirements Specification Process to Improve Agility," Lecture Notes in Computer Science, Volume 3134, Berlin: Springer, 2004, pp. 205ff. 
  183. [Andreou 2003].
    Andreou, A., "Promoting Software Quality Through a Human, Social, and Organizational Requirements Elicitation Process," Requirements Engineering, 8, 2 (July 2003), pp. 85-101.
  184. [Andrews 1991].
    Andrews, D., "JAD: A Crucial Dimension for Rapid Application Development," Journal of Systems Management, (March 1991), pp. 23-31.
  185. [Andrews and Goeddel 1994].
    Andrews, B., and W. Goeddel, Jr., "Using Rapid Prototyping for Early Requirements Validation," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994.
  186. [Andrews, et al. 2004].
    Andrews, A., et al., "Requirements Trade-offs During UML Design," IEEE Conference and Workshop on Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 282-291.
  187. [Andriole 1987].
    Andriole, S., "Storyboard Prototyping For Requirements Verification," Large Scale Systems, 12 (1987), pp. 231-247.
  188. [Andriole 1989].
    Andriole, S., Storyboard Prototyping: A New Approach to User Requirements Analysis, Wellesley, Massachusetts: QED, 1989.
  189. [Andriole 1992].
    Andriole, S., Rapid Application Prototyping, Wellesley, Massachusetts: QED, 1992.
  190. [Andriole 1994].
    Andriole, S., "Fast, Cheap Requirements: Prototype, or Else!" (see abstract) Manager Column, IEEE Software, 11, 2 (March 1994), pp. 85-87.
  191. [Andriole 1994a].
    Andriole, S., "Requirements Analysis & Prototyping: Fast, Cheap & Robust," Software Development, 2, 5 (May 1994).
  192. [Andriole 1998].
    Andriole, S., "The Politics of Requirements Management," IEEE Software, 15, 6 (November/December 1998), pp. 82-84.
  193. [Andriole and Monsanto 1995].
    Andriole, S., and C. Monsanto, "Tracking Requirements: Interactive Collaborative Requirements Management," Software Development, 3, 9 (September 1995), pp. 34-40.
  194. [Ang 2007].
    Ang, A., "Improving the Quality of Requirements Engineering Knowledge Representation Through Natural Language Requirements Patterns," IASTED International Conference on Software Engineering and Applications (SEA), 2007.

    Ani, see Al-Ani
     
  195. [Annoni, et al. 2007].
    Annoni, E., et al., "Data and Process Analysis of Data Warehouse Requirements," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2007.

    Ansary, see El-Ansary
     
  196. [ANSI 1977].
    American National Standards Institute, Standard Guidelines for Developing Functional Requirements for Computerized Laboratory Systems, 1977.
  197. [Anthes 1994].
    Anthes, G., "No More Creeps! Are You a Victim of Creeping User Requirements?" Computerworld, 28, 18 (May 2, 1994), pp. 107-110.
  198. [Antón, et al. 1993].
    Antón, A., et al., "Object-Based Requirements Modeling for Process Continuity," Twenty-Sixth Hawaii International Conference on Systems Sciences, Volume 3, Los Alamitos, California: IEEE Computer Society Press, 1993, pp. 191-202.
  199. [Antón 1996].
    Antón, A.
    , "Goal-Based Requirements Analysis," Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 136-144.
  200. [Antón 1997].
    Antón, A., Goal Identification and Refinement in the Specification of Software-Based Information Systems, Ph.D. Thesis, Georgia Institute of Technology, Atlanta, Georgia June 1997.
  201. [Ann and Potts 1998].
    Antón, A., and C. Potts, "The Use of Goals to Surface Requirements for Evolving Systems," Twentieth International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society, 1998, pp. 157-166.
  202. [Antón and Atlee 2000].
    Antón, A., and J. Atlee, "What do you mean I've been practicing without a license? Certification & licensing of requirements engineering professionals," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2000.
  203. [Antón, et al. 2000].
    Antón, A., et al., "Deriving Goals from a Use Case Based Requirements Specification for an Electronic Commerce System," Sixth International Workshop on Requirements Engineering: Foundations for Software Quality, Stockholm, Sweden, June 2000.
  204. [Antón, et al. 2001].
    Antón, A., et al., "The Role of Policy and Privacy Values in Requirements Engineering," International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp.138-145.
  205. [Antón, et al. 2001a].
    Antón, A., et al., "Deriving Goals from a Use Case Based Requirements Specification," Requirements Engineering Journal, 6, 1 (2001), pp. 63-73.
  206. [Antón and Earp 2001].
    Antón, A., and J. Earp, "Strategies for Developing Policies and Requirements for Secure E-Commerce Systems," in Recent Advances in E-Commerce Security and Privacy, A. Ghosh,  ed., Kluwer Academic Publishers, pp. 29-46.
  207. [Antón, et al. 2002].
    Antón, A., et al., "Analyzing Web Site Privacy Requirements Using a Privacy Goal Taxonomy," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  208. [Antón 2002]
    Antón, A., "Guest Editorial: Requirements Engineering for Information Security," Requirements Engineering, 7, 4 (2002), pp. 177-178.
  209. [Antón 2003]
    Antón, A., "Successful Software Projects Need Requirements Planning," IEEE Software, 20, 3 (May/June 2003), pp. 44-47.
  210. [Antón and Potts 2003]
    Antón, A., and C. Potts, "Functional Paleontology: The Evolution of User-Visible System Services," (see abstract) IEEE Transactions of Software Engineering, 29, 2 (February 2003), pp. 151-166.
  211. [Antón and Earp 2003]
    Antón, A., and J. Earp, "A Requirements Taxonomy for Reducing Website Privacy Vulnerabilities," Requirements Engineering, 29 (2003).
  212. [Antón, et al. 2003]
    Antón, A., et al., "Precluding Incongruous Behavior by Aligning Software Requirements with Security and  Privacy Policies," Information and Software Technology, 45, 14 (November 2003), pp. 967-977.
  213. [Antonellis and Vandoni 1993].
    de Antonellis, V., and L. Vandoni, "Temporal Aspects in Reuse of Requirements Specifications," Fifth Conference on Advanced Information Systems Engineering, Paris, France, June 1993.
  214. [Antoniou 1998].
    Antoniou, G., "The Role of Nonmonotonic Representations in Requirements Engineering," International Journal on Software Engineering and Knowledge Engineering, 8, 3 (1998), pp. 385-399.
  215. [Aoumeur and Saake 1999].
    Aoumeur, N., and G. Saake, "Operational Interpretation of the Requirements Specification Language ALBERT Using Timed Rewriting Logic," Fifth International Workshop on Requirements Engineering: Foundations for Software Quality, Heidelberg, Germany, June 1999.
  216. [Aoyama 2001].
    Aoyama, M., "Continuous and Discontinuous Software Evolution: Aspects of Software Evolution Across Multiple Product Lines," International Workshop on Principles of Software Evolution (IWPSE), New York: ACM Press, 2001, pp. 87-90.
  217. [Aoyama, et al. 2003].
    Aoyama, M., et al.,  "Embracing Requirements Variety for E-Governments Based on Multiple Product-lines Frameworks,"
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 285.
  218. [Aoyama 2005].
    Aoyama, M., "Persona- and Scenario-Based Requirements Engineering for Software Embedded in Digital Consumer Products,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 85-94.
  219. [Aoyama 2007].
    Aoyama, M., "Persona-Scenario-Goal Methodology for User-Centered Requirements Engineering,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  220. [Applewhite 2002].
    Applewhite, A., "Not Just the Facts: What 'Requirements' Mean to a Nonfiction Writer," IEEE Software, 19, 1 (January/February 2002), pp. 87-89.
  221. [Aranda, et al. 2005].
    Aranda, G., et al., "A cognitive-based approach to improve distributed requirements elicitation processes," IEEE International Conference on Cognitive Informatics, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 322-330.
  222. [Aranda, et al. 2005a].
    Aranda, G., et al., "A cognitive perspective for choosing groupware tools and elicitation techniques in virtual teams," International Conference on Computational Science and Its Applications (ICCSA), Berlin: Springer, 2005.
  223. [Aranda, et al. 2007].
    Aranda, G., et al., "Requirements in the wild: How small companies do it," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  224. [Aranda, et al. 2007a].
    Aranda, G., et al., "How to Choose Groupware Tools Considering Stakeholders’ Preferences During Requirements Elicitation?," International Workshop on Groupware: Design, Implementation, and Use, Berlin: Springer, 2007.
  225. [Arao, et al. 2005].
    Arao, T., et al., "'Business Process Requirements'-Oriented Requirements Engineering Process,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 395-402.
  226. [Arara and Benslimane 2004a].
    Arara, A., and D. Benslimane, "Towards Formal Ontologies Requirements with Multiple Perspectives," Lecture Notes in Computer Science, Volume 3055, Berlin: Springer, 2004, pp. 150-160. 
  227. [Araújo and Sawyer 1998].
    Araújo, J., and P. Sawyer, "Integrating Object-Oriented Analysis and Formal Specification," Journal of the Brazilian Computer Society (1998).
  228. [Araújo and Sawyer 1998a].
    Araújo, J., and P. Sawyer, "Generating Object-Oriented Formal Specifications from Process Sequence Diagrams," International Conference on Software and Systems Engineering and their Applications, 1998.
  229. [Araújo and Coutinho 2003].
    Araújo, J., and P. Coutinho, "From viewpoints to (critical) use cases," Australian Workshop on Requirements Engineering, 2003.
  230. [Araújo, et al.  2004].
    Araújo, J., et al., "Modeling, Composing, and Validating Scenario-Based Requirements with Aspects," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 58-67.
  231. [Araújo, et al. 2005].
    Araújo, J., et al., "Towards an aspect-oriented agile requirements approach," International Workshop on Principles of Software Evolution, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 140-143.
  232. [Araújo, et al. 2007].
    Araújo, J., et al., "An evolutionary model of requirements correctness with early aspects," European Conference on Software Quality Assurance, Berlin: Springer, 2007.
  233. [Arayici and Ahmed 2006].
    Arayici, Y., and V. Ahmed, "A requirements engineering framework for integrated systems development for the construction industry," Electronic Journal of Information Technology in Construction, 11 (March 2006), pp. 35-55.
  234. [Archer 2003].
    Archer, J.,  "Requirements Tracking: a Streamlined Approach,"
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 305.
  235. [Ardis, et al. 1995].
    Ardis, M., et al., "A Framework for Evaluating Specification Methods for Reactive Systems," (see abstract) Seventeenth IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
  236. [Ardis 1997].
    Ardis, M., "Formal Methods for Telecommunication System Requirements: A Survey of Standardized Languages," Annals of Software Engineering, 3, N. Mead, ed., 1997.
  237. [Arenas, et al. 2008a].
    Arenas, A., et al., "Modelling security properties in a Grid-based operating system with anti-goals," International Conference on Availability, Reliability and Security (ARES), Los Alamitos, California: IEEE Computer Society Press, 2008.
  238. [Ares and Pazos 1998].
    Ares, J., and J. Pazos, "Conceptual Modeling: An Essential Pillar for Quality Software Development," Knowledge-Based Systems, 11, (1998), pp. 87-104.

    Arias, see Pazos-Arias
     
  239. [Arkley and Riddle 2005].
    Arkley, P., and S. Riddle, "Overcoming the Traceability  Benefit Problem," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 385-389.
  240. [Arkley, et al. 2006].
    Arkley, P., et al., "Tailoring Traceability Information to Business Needs," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  241. [Arlow 1998]
    Arlow, J., "Use Cases, UML Visual Modeling, and the Trivialization of Business Requirements," Requirements Engineering Journal, 3, 2 (February 1998), pp. 150-152.
  242. [Armarego 2004].
    Armarego, J., "Learning Requirements Engineering with an Engineering Ethos," Australian Workshop on Requirements Engineering, 2004.
  243. [Armour and Miller 2001].
    Armour, F., and G. Miller, Advanced Use Case Modeling, New York: Addison Wesley, 2001.
  244. [Armstrong 2003].
    Armstrong, J., "Systems Engineering Methods Compared," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2003.
  245. [Arnold and Corriveau 2008].
    Arnold, D., and J.-P. Corriveau, "Automated instrumentation of contracts and scenarios for requirements validation in .net," International workshop on automation of software test, New York: ACM Press, 2008, pp. 63-66.
  246. [Arnowitz et al.  2006].
    Arnowitz, J., et al., Effective Prototyping for Software Makers, Morgan Kaufman, 2006.
  247. [Arpino and Carmichael 1990].
    Stehle, G., "Configuring integrated CASE tool support for two structured methods, CORE for requirements analysis and HOOD for design," European CASE Conference, Pinner, UK: Blenheim Online, pp. 1-16.
  248. [Arroyo and Sicilia 2008].
    Arroyo, S., and M.-A. Sicilia, "SOPHIE: Use case and evaluation," Information and Software Technology, 50, 12 (November 2008), pp. 1266-1280.
  249. [Arthur and Groener 1999].
    Arthur, J., and M. Groener, "An Operational Model Supporting the Generation of Requirements that Capture Customer Intent," Pacific Northwest Software Quality Conference, Portland, Oregon, October 1999, pp. 286-302.
  250. [Arthur and Groener 2005].
    Arthur, J., and M. Groener, "An operational model for structuring the requirements generation process," ( see abstract) Requirements Engineering, online awaiting publication.
  251. [Arthur and Nance 2007].
    Arthur, J., and R. Nance, "Investigating the use of software requirements engineering techniques in simulation modelling," Journal of Simulation (2007).
  252. [ARTIST FP5 Consortium 2005].
    ARTIST FP5 Consortium, "Tools for Requirements Capture and Exploration," in Embedded Systems Design, Lecture Notes in Computer Science 3436, Berlin: Springer, 2005, pp. 39-53.
  253. [Asanghanwa, et al. 2005].
    Asanghanwa, E., et al., "Requirements Engineering Research: A Microcosm of International Economic and Political Trends," 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
  254. [Ashworth 1988].
    Ashworth, C. "Structured Systems Analysis and Design Method (SSADM)," Information and Software Technology, 30, 3 (April 1988), pp. 153-163.
  255. [Ashworth and Goodland 1988].
    Ashworth, C. and M. Goodland, SSADM - A Practical Approach, New York: McGraw Hill, 1990.
  256. [Aslaksen 2003].
    Aslaksen, E. "Requirements Definition - A Plea for a Return to English," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2003.
  257. [Assawamekin, et al. 2008].
    Assawamekin, N., et al., "Resolving Multiperspective Requirements Traceability through Ontology Integration," International Conference on Semantic Computing, Los Alamitos, California: IEEE Computer Society Press, 2008.
  258. [Assawamekin, et al. 2008a].
    Assawamekin, N., et al., "Automated Multiperspective Requirements Traceability Using Ontology Matching Technique," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2008.
  259. [Astesiano and Reggio 1993].
    Astesiano, E., and G. Reggio, "Specifying Reactive Systems By Abstract Events," (see abstract) IEEE International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, December 1993.
  260. [Astesiano and Reggio 1998].
    Astesiano, E., and G. Reggio, "A Discipline for Handling Feature Interaction," International Workshop on Requirements Targeting Software and Systems Engineering, Berlin: Springer, 1998, pp. 95-120.
  261. [Astesiano and Reggio 2002].
    Astesiano, E., and G. Reggio, "Knowledge Structuring and Representation in Requirement Specification," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2002, pp. 143-150.
  262. [Astesiano and Reggio 2004].
    Astesiano, E., and G. Reggio, "Tight Structuring for Precise UML-Based Requirement Specifications," Lecture Notes in Computer Science, Volume 2941, Berlin: Springer, 2004, pp. 16-34. 
  263. [Atkinson and Griswold 1996].
    Atkinson, D., and W. Griswold, "The Design of Whole Program Analysis Tools," (see abstract) Eighteenth IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996.
  264. [Atkinson 2000].
    Atkinson, C., "Socio-Technical and Soft Approaches to Information Requirements Elicitation in a Post-Methodology Era," Requirements Engineering Journal, 5, 2 (2000), pp. 67-73.
  265. [Atlee and Gannon 1991].
    Atlee, A., and H. Gannon, "State-Based Model Checking of Event-Driven System Requirements," (see abstract) ACM SIGSOFT Conference on Software for Critical Systems, New York: ACM Press, December 1991.
  266. [Atlee and Gannon 1993].
    Atlee, A., and H. Gannon, "Specifying and Verifying Requirements for Real-Time Systems," (
    see abstract) IEEE Transactions on Software Engineering, 19, 1 (January 1993), pp. 41-55.
  267. [Atlee and McDermid 1995].
    Atlee, A., and J. McDermid, "Integrating requirements analysis and safety analysis," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
  268. [Atlee and Wieringa 2006].
    Atlee, J., and R. Wieringa, "RE 05: Engineering Successful Products (Guest Editors' Introduction)," IEEE Software, 23, 3 (May/June 2006), pp. 16-18.
  269. [Atlee 2006].
    Atlee, J., " Introduction to the best research papers from RE’05," Requirements Engineering, 11, 3 (June 2006), pp. 155-156.

    Attar, see El-Attar
     
  270. [Atwood 1977].
    Atwood, J., The Systems Analyst, Rochelle Park, NJ: Hayden Press, 1977.
  271. [Aubrey 2006].
    Aubrey, D, "Controlling the HMS Program through Managing Requirements," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  272. [Aue and Breu 1994].
    Aue, A., and M. Breu, "Distributed Information Systems: An Advanced Methodology," (see abstract) IEEE Transactions on Software Engineering, 20, 8 (August 1994), pp. 594-605.
  273. [Augostinho, et al. 2008].
    Augostinho, S., et al., "A Metadata-driven approach for aspect-oriented requirements analysis," International conference on enterprise information systems, 2008.
  274. [Aurum and Wohlin 2003].
    Aurum, A., and C. Wohlin, "The Fundamental Nature of Requirements Engineering Activities as a Decision-Making Process," Information and Software Technology, 45, 14 (November 2003), pp. 945-954.
  275. [Aurum and Wohlin 2005].
    Aurum, A., and C. Wohlin, Engineering and Managing Software Requirements, Berlin: Springer, 2005.
  276. [Aurum and Wohlin 2005a].
    Aurum, A., and C. Wohlin, "Requirements Engineering: Setting the Context," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 2-15.
  277. [Aurum and Wohlin 2007].
    Aurum, A., and C. Wohlin, "A Value-Based Approach in Requirements Engineering: Explaining Some of the Fundamental Concepts," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ' 07), Berlin: Springer, 2007.
  278. [Austin and Devin 2003].
    Austin, R., and L. Devin, "Beyond Requirements: Software Making as Art," IEEE Software, 20, 1 (January-February 2003), pp. 93-95.
  279. [Autili and Pelliccione 2008].
    Autili, M., and P. Pelliccione, "Towards a Graphical Tool for Refining User to System Requirements,"
    Electronic Notes in Theoretical Computer Science, 211, C (April 2008), pp. 147-157.
  280. [Avellis and Finkelstein 2002].
    Avellis, G., and A. Finkelstein, "How to Annotate Educational Multi-media with Non-Functional Requirements," Educational Technology and Society, 5, 2 (2002), pp.119-124.
  281. [Averill and Vestal 1979].
    Averill, E., and S. Vestal, "Requirements Methodology," AIAA National Conference, 1979.
  282. [Avesani, et al. 2005].
    Avesani, P., et al., "Facing Scalability Issues in Requirements Prioritization with Machine Learning Techniques," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 297-306.
  283. [d'Avila Garcez, et al. 2001].
    d'Avila Garcez , A., et al., "An Analysis-Revision Cycle to Evolve Requirements Specifications," ( see abstract) IEEE Conference on Automated Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 354-358.
  284. [d'Avila Garcez, et al. 2003].
    d'Avila Garcez , A., et al., "Combining Abductive Reasoning and Inductive Learning to Evolve Requirements Specifications," IEE Proceedings on Software Engineering, 150, 1 (February 2003), pp. 25ff.
  285. [Avison, et al. 2006].
    Avison, D., et al., "Reflections on Teaching Information Systems Analysis and Design: From Then to Now!" Journal of Information Systems Education (2006). 
  286. [Avital 2005].
    Avital, M., "ACCELERATED SYSTEMS ANALYSIS AND DESIGN WITH APPRECIATIVE INQUIRY- AN ACTION LEARNING APPROACH," Communications of the AIS, 2005, 15 (2005), pp. 289-314. 
  287. [Axelnath, et al. 2006].
    Axelnath, B., et al., "Systematic Requirements-Driven Evaluation and Synthesis of Alternative Principle Solutions for Advanced Mechatronic Systems," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  288. [Ayalew 2006].
    Ayalew, Y., "A framework for requirements elicitation techniques selection," 15th International Conference on Software Engineering and Data Engineering, Cary, NC: International Society for Computers and Their Applications, 2006, pp. 6ff.
  289. [Azam, et al. 2007].
    Azam, F., et al., "Integrating value-based requirement engineering models to webml using vip business modeling framework," International Conference on the World Wide Web, 2007.
  290. [Azar, et al. 2007].
    Azar, J., et al., "Value-oriented requirements prioritization in a small development organization," IEEE Software, 24, 1 (January-February 2007), pp. 32-37.
  291. [Azuma, et al. 1984].
    Azuma, M., et al., "Integrating and Standardizing Requirements Engineering for Business Systems: An Experimental Study," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1984. 
  292. [Azuma 1993].
    Azuma, R., "Tracking Requirements for Augmented Reality," Communications of the ACM, 36, 7 (July 1993), pp. 50-51.
  1. B

    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


     

  2. [Babar 2003].
    Babar, M., "
    An Experience of Applying Architecture-Based Approach to Build a Component-Based Requirements Management Toolset," (see abstract) Twenty-Seventh International IEEE Conference on Computer Software and Applications, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 550-556.
  3. [Babar and Zowghi 2004].
    Babar, M., and D. Zowghi, "Developing a Requirements Management Toolset: Lessons Learnt," 2004 Australian Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 10-19.
  4. [Babar, et al. 2007].
    Babar, A., "Towards evolution of strategic IT requirements," Symposium on Applied Computing, New York: ACM Press, 2007.
  5. [Babar, et al. 2008].
    Babar, A., et al., "Three integration approaches for map and B-SCP requirements engineering techniques," Symposium on Applied Computing, New York: ACM Press, 2008, pp. 650-655.
  6. [Babar, et al. 2008a].
    Babar, A., et al., "Integrating B-SCP and MAP to manage the evolution of strategic IT requirements," Information and Software Technology, 50, 7-8 (June 2008), pp. 815-831.
  7. [Babar, et al. 2008b].
    Babar, A., et al., "Problem frames and business strategy modelling," International workshop on applications and advances of problem frames, New York: ACM Press, 2008.
  8. [Babb 1982].
    Babb, R., "Coherent Realization of System Requirements," International Symposium on Current Issues of Requirements Environments, 1982.
  9. [Babin and Lustman 2001].
    Babin, G., and F. Lustman, "Application of Formal Methods to Scenario-Based Requirements Engineering," International Journal on Computers and Applications, 23 (2001), pp. 141ff.
  10. [Bach 1999].
    Bach, J., "Reframing Requirements Analysis," IEEE Computer, 32, 2 (February 1999), pp. 120-122.
  11. [Bachmann, et al. 2005].
    Bachmann, C., et al., "Designing software architectures to achieve quality attribute requirements," IEE Proceedings on Software, 152, 4 (August 2005), pp. 153-165.
  12. [Bachmeyer and Delugach2007].
    Bachmeyer, C., and H. Delugach, "Managing knowledge in business requirements identification," International Conference on Conceptual Structures (ICCS), 2007.
  13. [Backer, et al. 2006].
    de Backer, M., et al., "Sequence Constraint Consistency Checking in Requirements Specifications," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
  14. [Bahill and Dean 1997].
    Bahill, A., and F. Dean, "The Requirements Discovery Process," Seventh Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1997.
  15. [Bahn, et al. 2002].
    Bahn, D., et al., "Conversation about Software Requirements with Scenarios and Prototypes," 5th International Workshop on Next Generation Information Technologies and Systems, Berlin, Germany: Springer-Verlag, 2002, pp. 147-157.
  16. [Bail 2006].
    Bail, W., "An Approach to Defining Requirements for Exceptions," Advanced Topics in Exception Handling Techniques, Lecture Notes in Computer Science, Volume 4119, Berlin: Springer, 2006, pp. 243-254. 
  17. [Bail 2006a].
    Bail, W., "Requirements Management for Dependable Software Systems," Advances in Computers, (2007), pp. 21-26.
  18. [Bailin 1989].
    Bailin, S., "An Object-Oriented Requirements Specification Method," Communications of the ACM, 32, 5 (May 1989), pp. 608-623.
  19. [Bailin 1994].
    Bailin, S., "Object-Oriented Requirements Analysis," in Encyclopedia of Software Engineering, J. Marciniak, ed., New York: John Wiley, 1994, pp. 740-756.
  20. [Bailin 2002].
    Bailin, S., "Object-Oriented Analysis," in Encyclopedia of Software Engineering, J. Marciniak, ed., New York: John Wiley, 2002.

    Baixauli, see also Gonzáles-Baixauli
     
  21. [Bajaj 2004].
    Bajaj, A., , "
    The effect of the number of concepts on the readability of schemas: an empirical study with data models," Requirements Engineering, 9, 4 (November 2004), pp. 261-270.
  22. [Bajaj 2005].
    Bajaj, A., et al., "SYSTEMS ANALYSIS AND DESIGN: SHOULD WE BE RESEARCHING WHAT WE TEACH?," Communications of the AIS, 15 (2005), pp. 478-493. 
  23. [Bajaj 2006].
    Bajaj, A., et al., "Large Scale Requirements Modeling: An Industry Analysis, a Model and a Teaching Case," Journal of Information Systems Education, (2006). 
  24. [Bajec and Krisper 2005].
    Bajec, M., and M. Krisper, "A methodology and tool support for managing business rules in organisations," Information Systems, 36, 6 (September 2005), pp. 423-443.
  25. [Baker 1980].
    Baker, F., "Software Design or What Stands Between Requirements and Programs," Conference on Instrumentation in the Pulp and Paper Industry, ASME, August 1980, pp. 297-304.
  26. [Baker and Christian 1998].
    Baker, L., and A.Christian, "Requirements Development & Management Using Models," Eighth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1998.
  27. [Baker 2001].
    Baker, M., "Requirements or Design -- Chicken or Egg?," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2001.
  28. [Baker 2002].
    Baker, T., "A Systems Engineering Approach to Requirements Validation," Medical Device and Diagnostic Industry, 24, 1 (January 2002), pp. 100ff.
  29. [Baker, et al 2005].
    Baker, P., et al., "Detecting and resolving semantic pathologies in UML sequence diagrams," Tenth European Software Engineering Conference, New York: ACM Press, 2005.
  30. [Baligand, et al. 2007]
    Baligand, F., et al., "A Language for Quality of Service Requirements Specification in Web Services Orchestrations," International Conference on Service-Oriented Computing, Lecture Notes in Computer Science, Volume 4716, Berlin: Springer, 2007, pp. 38-49.
  31. [Balikuddembe and Potgieter 2008].
    Balikuddembe, J., and A. Potgieter, "Using Actor Object Operations Structures to Understand Project Requirements Complexities," International Conference on Software Engineering Advances, Los Alamitos, California: IEEE Computer Society Press, 2008.
  32. [Balkovich and Engelberg 1976].
    Balkovich, E. and G. Engelberg, "Research Toward a Technology to Support the Specification of Data Processing System Performance Requirements," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1976, pp. 110-115.
  33. [Ballejos and Montagna 2008].
    Ballejos, L. and J. Montagna, "Method for Stakeholder Identification in Interorganizational Environments," Requirements Engineering, 13, 4 (October 2008), pp. 281-297.
  34. [Ballejos, et al. 2008].
    Ballejos, L.
    , et al., "A Stakeholder Model for Interorganizational Information Systems," International Working Conference on Requirements Engineering: Foundations for Software Quality, Berlin: Springer, 2008.
  35. [Bally, et al. 1977].
    Bally, L. et al., "A Prototype Approach to Information Systems Design and Development," Information and Management, 1, 1 (January 1977), pp. 21-26.
  36. [Balushi, et al. 2006].
    al Balushi, T., et al., "Performing Requirements Elicitation Activities Supported by Quality Ontologies," International Conference on Software Engineering and Knowledge Engineering, 2006.
  37. [Balushi, et al. 2007].
    al Balushi, T., et al., "ElicitO: A Quality Ontology-Guided NFR Elicitation Tool," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ '07), Berlin: Springer, 2007.
  38. [Balushi, et al. 2008].
    al Balushi, T., et al., "Identifying NFR Conflicts Using Quality Ontology," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2008.
  39. [Balzer, et al. 1978]
    Balzer, R., et al., "Informality in Program Specifications," IEEE Transactions on Software Engineering, 4, 2 (February 1978), pp. 94-103.
  40. [Balzer and Goldman 1979]
    Balzer, R., and N. Goldman, "Principles of Good Software Specification and Their Implications for Specification Language," IEEE Conference on Specifications of Reliable Software, Los Alamitos, California: IEEE Computer Society Press, 1979, pp. 58-67.
  41. [Balzer, et al. 1982]
    Balzer, R., et al., "Operational Specifications as the Basis for Rapid Prototyping," ACM Software Engineering Notes, 7, 5 (December 1982), pp. 3-16.
  42. [Balzer, et al. 1990]
    Balzer, R., et al., "Prototyping," Annual Review of Computer Science, 4 (June 1990), pp. 453-465.
  43. [Banach and Poppleton 2003].
    Banach, R., and M. Poppleton, "Retrenching Partial Requirements into System Definitions: A Simple Feature Interaction Case Study," (see abstract) Requirements Engineering, 8, 4 (December 2003), pp. 266-288.
  44. [Baniassad and Clarke 2004].
    Baniassad, E., and S. Clarke, et al., " Finding Aspects in Requirements with Theme/Doc," Third International Conference on Aspect-Oriented Software Development, March 2004.
  45. [Baniassad and Clarke 2004a].
    Baniassad, E., and S. Clarke, et al., "Theme: An Approach for Aspect-Oriented Analysis and Design," 26th International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 158-167.
  46. [Bansler and Břdker 1993]
    Bansler, J., and K. Břdker, "A Reappraisal of Structured Analysis: Design of an Organizational Context," (see abstract) ACM Transactions on Information Systems, 11, 2 (February 1993), pp. 165-193.
  47. [Baragans and Pazos 2004].
    Baragans Martinez, A., and J. Pazos Arias, "
    λ-SCTL/MUS: A Formal Methodology to Evolve Multi-Perspective Software Requirements Specifications," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 72-74.

    Barajas, see Valles-Barajas
     
  48. [Baram and Steinberg 1989]
    Baram, G., and G. Steinberg, "Selection Criteria for Analysis and Design CASE Tools," ACM Software Engineering Notes, 14, 6 (October 1989), pp. 73-80.
  49. [Baranov, et al. 2003].
    Baranov, S., et al., "Verification of Software Requirements on Program Systems Represented by Attribute Transition Systems," Cybernetics and Systems Analysis, 39, 6 (November 2003), pp. 783-789.
  50. [Barber and Jernigan 2000].
    Barber, K., and S. Jernigan, "Hybrid Domain Representation Archive for Requirements Model Synthesis Across Viewpoints," (see abstract) International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2000, p. 780.
  51. [Barber, et al. 1999].
    Barber, K., et al., "The Systems Engineering Process Activities (SEPA) - Supporting Early Requirements Analysis and Integration Prior to Implementation Design," Software Technology and Engineering Practice,
    Los Alamitos, California: IEEE Computer Society Press, 1999.
  52. [Barber, et al. 2003].
    Barber, K., et al., "Arcade: Early Dynamic Property Evaluation of Requirements Using Partitioned Software Architecture Models," Requirements Engineering, 8, 4 (December 2003), pp. 222-235.
  53. [Barcio, et al. 1995]
    Barcio, B., et al., "Object-Oriented Analysis, Modeling, and Simulation of a National Air Defense System," (see abstract) 1995 IEEE International Conference on Systems, Man, and Cybernetics,
    Los Alamitos, California: IEEE Computer Society Press, October 1995, pp. 3983 - 3988.
  54. [Barcio, et al. 1997]
    Barcio, B., et al., "An Object-Oriented Modeling and Simulation Environment for Reactive Systems Development," (see abstract) International Journal of Flexible Manufacturing Systems, 9, 1 (January 1997), pp. 51-80.
  55. [Baresi and Pezze 1998].
    Baresi, L., and M. Pezze, "
    Toward formalizing structured analysis," ACM Transactions on Software Engineering and Methodology, 7, 1 (January 1998), pp. 80-107.
  56. [Barjis 2008].
    Barjis, J., "The importance of business process modeling in software systems design," Science of Computer Programming, 71, 1 (March 2008), pp. 73-87.
  57. [Barnes 2003].
    Barnes, R.,  "Using Convergent Design Processes to Surface Hidden Ambiguity and Conflict in Requirements,"
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 281.
  58. [Barnes 2005].
    Barnes, R.,  "Ethnography in Requirements Engineering Research - Experiences and Confessions of an Auto-Ethnographer,"
    Comparative Evaluation in Requirements Engineering (CERE), Los Alamitos, California: IEEE Computer Society Press, 2005.
  59. [Barney, et al. 2006].
    Barney, S., et al., "Quest for the Silver Bullet: Creating Software Product Value Through Requirements . . .," IEEE EUROMICRO International Conference on Software Engineering and Advanced Applications, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 274-281
  60. [Barney, et al. 2008].
    Barney, S., et al., "A product management challenge: creating software product value through requirements selection," Journal of Systems Architecture, 54, 6 (June 2008), pp. 576-593.
  61. [Baroudi, et al. 1986].
    Baroudi, J., et al., "An Empirical Study of the Impact of User Involvement on System Usage and Information Satisfaction," ( see abstract) Communications of the ACM, 29, 3 (March 1986), pp. 232-238.
  62. [Barragáns-Martinez, et al. 2002].
    Barragáns-Martinez, A., et al., "
    Requirements Specification Evolution in a Multi-Perspective Environment," 26th Annual International Conference on Computer Software and Applications, Los Alamitos, California: IEEE Computer Society Press, 2002, pp. 39-44.
  63. [Barrágans-Martinez, et al. 2008].
    Barragáns-Martinez, A., et al., "Composing requirements specifications from multiple prioritized sources," Requirements Engineering Journal, 13, 3 (November 2008), pp. 187-206.
  64. [Barrágans-Martinez, et al. 2008a].
    Barragáns-Martinez, A., et al., "Composing multi-perspective software requirements specifications," International Journal of Software Engineering and Knowledge Engineering, (2008).
  65. [Barroca and McDermid 1993].
    Barroca, L., and J. McDermid, "Specification of Real-Time Systems -- A View-Oriented Approach," unknown, 1993.
  66. [Barros 1993].
    Barros, "Requirements Elicitation and Formalism Through External Design and Object-Oriented Specification," IEEE International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, December 1993.
  67. [Barth 2005].
    Barth, J.-M., "The Way from Requirements to Production," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005.
  68. [Bartholomew 2008].
    Bartholomew, T., "Book Review: Project Requirements: A Guide to Best Practices," Software Quality Professional, (2008).
  69. [Bartneck and Hu 2004].
    Bartneck, C., and J. Hu, "Rapid prototyping for Interactive Robots," Intelligent Autonomous Systems, 2004.
  70. [Basili and Weiss 1981].
    Basili, V., and D. Weiss, "Evaluation of a Software Requirements Document by Analysis of Change Data," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1981, pp. 314-323.
  71. [Bastani 2007].
    Bastani, B., "A requirements analysis framework for open systems requirements engineering," ACM Software Engineering Notes (2007).
  72. [Bastos and Castro 2005].
    Bastos, L., and J. Castro, "From requirements to multi-agent architecture using organisational concepts," ACM Software Engineering Notes, 30, 4 (May 2005).
  73. [Bastos and Castro 2005a].
    Bastos, L., and J. Castro, "Systematic Integration Between Requirements and Architecture," Software Engineering for Multi-Agent Systems, Lecture Notes in Computer Science 3390, Berlin: Springer, 2005, pp. 85ff.
  74. [Bastos and Castro 2005b].
    Bastos, L., and J. Castro, "Organizational model to derive multi-agent architecture from requirements," Conference on Advanced Information Systems Engineering, 2005, pp. 169-175.
  75. [Bastos, et al. 2006].
    Bastos, L., et al., "Deriving Architectures from Requirements (poster)," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  76. [Batory, et al. 2006].
    Batory, D., et al., "
    Automated analysis of feature models: challenges ahead," Communications of the ACM, 49, 12 (December 2006), pp. 45-47.
  77. [Batra and Satzinger 2006].
    Batra, D., and J. Satzinger, "Contemporary Approaches and Techniques for the Systems Analyst," Journal of Information Systems Education (2006). 
  78. [Bauer, et al. 1978]
    Bauer, J., et al., "The Automatic Generation and Execution of Function Test Plans for Electronic Switching Systems," ACM Software Engineering Notes, 3, 5 (November 1978), pp. 92-100.
  79. [Bauer and Finger 1979]
    Bauer, J., and A. Finger, "Test Plan Generation Using Formal Grammars,"
    IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1979, pp. 425-432.
  80. [Bauer 2006].
    Bauer, M., "Agility vs. requirements," Cutter IT Journal, 19, 7 (July 2006).
  81. [Baxter, et al. 2008].
    Baxter, D., "A framework to integrate design knowledge reuse and requirements management in engineering design," Robotics and Computer-Integrated Manufacturing, 24, 4 (August 2008), pp. 585-593.
  82. [Bayer, et al. 2000].
    Bayer, J., et al., "
    Customizable Domain Analysis," Lecture Notes in Computer Science 1799, Berlin: Springer, 2000, pp. 178ff.
  83. [Bayer 2006].
    Bayer, S., "Hallucinating requirements," Cutter IT Journal, 19, 7 (July 2006).
  84. [Beatty and Agouridis 2007].
    Beatty, J., and V. Agouridis, "Developing Requirements Engineering Skills: A Case Study in Training Practitioners," Requirements Engineering Workshop on Education and Training (REET), Los Alamitos, California: IEEE Computer Society Press, 2007.
  85. [Beatty and Alexander 2008].
    Beatty, J., and M. Alexander, "Games-Based Requirements Engineering Training: An Initial Experience Report," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2008.
  86. [Beatty and Alexander 2008a].
    Beatty, J., and M. Alexander, "Display-action-response model for user interface requirements: case study," IEEE International Workshop on Requirements Engineering Visualization, Los Alamitos, California: IEEE Computer Society Press, 2008, pp. 75-79.
  87. [Bechtold 2005].
    Bechtold, D., "Requirement Analysis and Agility," Workshop on the Interplay of Requirements Engineering and Project Management in Software Projects, 2005.
  88. [Beckenstein 1972]
    Beckenstein, M., "System Requirements Analysis: A Management Tool," IEEE Transactions on Engineering Management, 19, 4 (November 1972), pp. 124-128.
  89. [Beck 2007].
    Beck, K., "Don't Just DWTTY (Point Counterpoint)," IEEE Software, 24, 2 (March-April 2007), pp. 62-65.
  90. [Becker 2003].
    Becker, D.,  "Measuring Requirements Traceability from Multiple Angles at Multiple Lifecycle Entry Points,"
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 291.
  91. [Becker, et al. 2006].
    Becker, M., et al., "Requirements Engineering in the Automotive Development: Known Problems in a New Complexity," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
  92. [Becks and Koller 1999].
    Becks, A., and J. Koller, "Automatically Structuring Textual Requirements Scenarios," IEEE International Conference on Automated Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 271-274.
  93. [Beecham, et al. 2005].
    Beecham, S., et al., "Using an expert panel to validate a requirements process improvement model," Journal of Systems and Software, 76, 3 (June 2005), pp. 251-275.
  94. [Beecham, et al. 2005a].
    Beecham, S., et al., "Defining a Requirements Process Improvement Model," Software Quality Journal, 13, 3 (September 2005), pp. 247-279.
  95. [Beeck 1993].
    von der Beeck, M., "Integration of Structured Analysis and Timed Statecharts for Real-Time and Currency Specification," Software Engineering - ESEC '93 Conference, Lecture Notes in Computer Science, Berlin: Springer Verlag, pp. 313-328, 1993.
  96. [Beeck 1994].
    von der Beeck, M., "Method Integration and Abstraction From Detailed Semantics to Improve Software Quality," International Workshop on Requirements Engineering: Foundations of Software Quality, June 1994.
  97. [Beeck, et al. 1997].
    von der Beeck, M., et al., "A Formal Requirements Engineering Method for Specification, Synthesis, and Verification," Eighth Conference on Software Engineering Environments, Los Alamitos, California: IEEE Computer Society Press, 1997, pp. 131-144.
  98. [Beeck, et al. 1997a].
    von der Beeck, M., et al., "Model-Based Requirements Engineering for Embedded Software," Eighth Conference on Software Engineering Environments, Los Alamitos, California: IEEE Computer Society Press, 1997, pp. 131-144.
  99. [Beeck, et al. 2002].
    von der Beeck, M., et al., "Model Based Requirements Engineering for Embedded Software," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  100. [Beerthuizen 2006].
    Beerthuizen, P., "Design decomposition strategies, and their impact on requirements elicitation and specification," DAta Systems In Aerospace (DASIA 2006), European Space Agency, 2006.
  101. [Beg, et al. 2008].
    Beg, R., et al., "An Approach for Requirement Prioritization Using B-Tree," International Conference on Emerging Trends in Engineering and Technology, Los Alamitos, California: IEEE Computer Society Press, 2008.
  102. [Beg, et al. 2008a].
    Beg, R., et al., "A method to deal with the type of lexical ambiguity in a software requirement specification document," International Conference on Emerging Trends in Engineering and Technology, 2008.
  103. [Behforooz and Hudson 1996].
    Behforooz, A., and F. Hudson, Software Engineering Fundamentals, Oxford, UK: Oxford University Press, 1996, Chapters 4-5.
  104. [Belachew and Shyamasundar 2001].
    Belachew, M., and R. Shyamasundar, "MSC+: From Requirement to Prototyped Systems," 13th Euromicro Conference on Real-Time Systems, 2001, pp. 117ff.

    Belén, see Barragáns-Martinez
     
  105. [Belford, et al. 1976]
    Belford, P., et al., "Specifications: A Key to Effective Software Development,"
    IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1976, pp. 71-79.
  106. [Belgamo, et al. 2005]
    Belgamo, A., et al., "TUCCA: improving the effectiveness of use case construction and requirement analysis,"
    IEEE International Symposium on Empirical Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 257-266.
  107. [Belkhouche and Geraci 1994].
    Belkhouche, B., and B. Geraci, "Ripple: A Formally Specified Prototyping System," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 150-153.
  108. [Bell and Bixler 1976]
    Bell, T., and D. Bixler, "A Flow-Oriented Requirements Statement Language," Symposium on Computer Software Engineering, 1976.
  109. [Bell and Thayer 1976]
    Bell, T., and T. Thayer, "Software Requirements: Are They Really a Problem?,"
    IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1976, pp. 61-68.
  110. [Bell, et al. 1977]
    Bell, T., et al., "An Extendible Approach to Computer-Aided Software Requirements Engineering," IEEE Transactions on Software Engineering, 3, 1 (January 1977), pp. 49-60.
  111. [Bell, et al. 1987]
    Bell, T., et al., Software Engineering: A Programming Approach, Englewood Cliffs, NJ: Prentice Hall, 1987.
  112. [Bell, et al. 1992]
    Bell, T., et al., Software Engineering: A Programming Approach, 2nd edition, Englewood Cliffs, NJ: Prentice Hall, 1992.
  113. [Bell and Jones 1996].
    Bell, M., and D. Jones, "Using MS Access to Manage Requirements," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  114. [Bell 2000].
    Bell, D., Software Engineering: A Programming Approach, Boston, Massachusetts: Addison Wesley, 2000, Chapters 3-4.
  115. [Belscher 1995].
    Belscher, R., "Evaluation of Real-Time Requirements by Simulation-Based Analysis," First IEEE International Conference on Engineering of Complex Computer Systems, Los Alamitos, California: IEEE Computer Society Press, November 1995.
  116. [Ben-Abdallah, et al. 1997].
    Ben-Abdallah, H., et al., "The Integrated Specification and Analysis of Functional, Temporal, and Resource Requirements," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1997.

    Ben Achour, see Achour, Ben
     
  117. [Bendjenna, et al 2008].
    Bendjenna, H., et al., "Enhancing Elicitation Technique Selection Process in a Cooperative Distributed Environment," International Working Conference on Requirements Engineering: Foundations for Software Quality, Berlin: Springer, 2008.
  118. [Benner 1988].
    Benner, K., "RISE: requirements and Incremental specification environment," Software Engineering and its Application to Avionics, Neuilly sur Seine, France: AGARD, 1988, pp. 18/1-18/7.
  119. [Bennett, et al. 2005].
    Bennett, M., et al., "State Analysis Requirements Database for Engineering Complex Embedded Systems," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
  120. [Bennett, et al. 2005a].
    Bennett, S., et al., "Object-oriented Systems Analysis and Design Using UML," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
  121. [Bentley, et al. 2002].
    Bentley, T., et al., "Putting Some Emotion into Requirements Engineering,
    " Australian Workshop on Requirements Engineering, 2002.
  122. [Bento 1994].
    Bento, A., "Systems Analysis: A Decision Approach," Information and Management, 27, 3 (September 1994), pp. 185-193.
  123. [Benyon and Skidmore 1987].
    Benyon, D., and S. Skidmore, "Toward a Toolkit for the Systems Analyst," The Computer Journal, 30, 1 (1987), pp. 2-7.
  124. [Bera 1990].
    Bera, R., "Setting Software Requirements: Scenario for Future Fighters," Information and Software Technology, 32 (October 1990), pp. 531-538.
  125. [Berander 2004].
    Berander, P., "Using Students as Subjects in Requirements Prioritization," International Symposium on Empirical Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 167-176.
  126. [Berander and Andrews 2005].
    Berander, P., and A. Andrews, "Requirements Prioritization," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 69-94.
  127. [Berander and Jonsson 2006].
    Berander, P., and P. Jonsson, "
    Hierarchical Cumulative Voting (HCV) prioritization of requirements in hierarchies," International Journal of Software Engineering and Knowledge Engineering, 16, 6 (December 2006), pp. 819-849.
  128. [Berenbach 2003].
    Berenbach, B.,  "The Automated Extraction of Requirements from UML Models,"
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 287.
  129. [Berenbach 2003a].
    Berenbach, B.,  "Evaluating the Quality of a UML Business Model,"
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 280.
  130. [Berenbach 2006].
    Berenbach, B., "Requirements Engineering: An Industrial Perspective," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  131. [Berenbach 2006a].
    Berenbach, B., "Introduction to Product Line Requirements Engineering," IEEE International Conference on Software Product Lines, Los Alamitos, California: IEEE Computer Society Press, 2006.
  132. [Berenbach and Rayment 2008].
    Berenbach, B., and T. Rayment, "Evaluation of a Requirements Engineering Training Program at Siemens," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2008.
  133. [van den Berg, et al. 2006].
    van den Berg, K., et al., "Analysis of crosscutting across software development phases based on traceability," International workshop on early aspects at ICSE, New York: ACM Press, 2006, pp. 43-50.
  134. [van den Berg, et al. 2007].
    van den Berg, K., et al., "Analysis of Crosscutting in Early Software Development Phases Based on Traceability," Transactions on Aspect-Oriented Software Development, Berlin: Springer, 2007.
  135. [Bergen 1985].
    Bergen, M., et al., "Pinpoint user requirements to select proper software," Bank Systems & Equipment, 22, 8 (August 1985), pp. 28-36.
  136. [Bergman and Mark 2002].
    Bergman, M., and G. Mark, "Exploring the Relationship between Project Selection and Requirements Analysis: An Empirical Study of the New Millennium Program," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  137. [Bergman, et al. 2002].
    Bergman, M., et al., "Large-Scale Requirements Analysis Revisited: The Need for Understanding the Political Ecology of Requirements Engineering," Requirements Engineering Journal, 7, 3 (September 2002), pp. 152-171.
  138. [Bergman and Mark 2003].
    Bergman, M., and G. Mark, "In Situ Requirements Analysis: A Deeper Examination of the
    Relationship between Requirements Formation and Project Selection," International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 11-22.
  139. [Berki, et al. 2004].
    Berki, E., et al., "Requirements Engineering and Process Modelling in Software Quality Management -- Towards a Generic Process Metamodel," Software Quality Journal, 12, 3 (September 2004), pp. 265-283.
  140. [Berlin 1989].
    Berlin, L., "User-Centered Application Definition: A Methodology and Case Study," The Hewlett-Packard Journal, 40, 5 (October 1989), pp. 90-97.
  141. [Berliner and Zave 1987]
    Berliner, E., and P. Zave, "An Experiment in Technology Transfer: PAISLey Specification of Requirements for an Undersea Lightwave Cable System,"
    IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1987, pp. 42-50.
  142. [Bernández, et al. 2004].
    Bernández, B., et al., "A Controlled Experiment for Evaluating a Metric-Based Reading Technique for Requirements Inspections," IEEE International Symposium on Software Metrics, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 257-268.
  143. [Bernández, et al. 2004a].
    Bernández, B., et al., "Empirical Evaluation and Review of a Metrics-Based approach for Use Case Verification," Journal of Research and Practice in Information Technology, 36, 4 (November 2004). pp. 247-258.
  144. [Bernet and Kilov 1999].
    Bernet, O., and H. Kilov, "From Box-and-Line Diagrams to Precise Specifications: Using RM-ODP and GRM to Specify Semantics," Eighth OOPSLA Workshop on Behavioral Semantics, Boston, Massachusetts: Northeastern University, 1999, pp. 11-21.
  145. [Bernstein 2005].
    Bernstein, L., "
    Taking software requirements creation from folklore to analysis," ACM Software Engineering Notes, 30, 5(September 2005), pp. 3-5. 
  146. [Berry 1995].
    Berry, D., "The Importance of Ignorance in Requirements Engineering," Journal of Systems and Software, 28, 1 (January 1995), pp. 179-184.
  147. [Berry 1998].
    Berry, D., "The Safety Requirements Engineering Dilemma," Ninth International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 147-149.
  148. [Berry 1998a].
    Berry, D., "Requirements Engineering," IEEE Software, 15, 2 (March 1998), pp. 26-29.
  149. [Berry 1999].
    Berry, D., "Software and House Requirements Engineering: Lesson Learned in Combating Requirements Creep," Requirements Engineering Journal, 3, 3 & 4 (1999), pp. 242-244.
  150. [Berry 2003].
    Berry, D., "More Requirements Engineering Adventures with Building Contractors," Requirements Engineering, 8, 2 (July 2003), pp. 142-146.
  151. [Berry and Kamsties 2003].
    Berry, D., and E. Kamsties, "Ambiguity in Requirements Specification," in Perspectives on Software Requirements, Leite, J., and J. Doorn, eds., Berlin: Springer, 2003.
  152. [Berry, et al. 2004].
    Berry, D., et al., " User's Manuals as Requirements Specifications: Case Studies," Requirements Engineering, 9, 1 (February 2004), pp. 67-82.
  153. [Berry and Kamsties 2005].
    Berry, D., and E. Kamsties, "The Syntactically Dangerous All and Plural in Specifications," IEEE Software, 22, 1 (January/February 2005), pp. 55-57.
  154. [Berry, et al. 2005].
    Berry, D., et al., "The Four Levels of Requirements Engineering for and In Dynamic Adaptive Systems," 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
  155. [Berry, et al. 2005a].
    Berry, D., et al., "Panel: To do or not to do: If the requirements engineering payoff is so good, why aren’t more companies doing it?," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, p. 447.
  156. [Berry 2006].
    Berry, D., "Book Review: Aybüke Aurum and Claes Wohlin (eds): Engineering and Managing Software Requirements," Requirements Engineering, 11, 2 (April 2006), pp. 152-154.
  157. [Berry, et al. 2006].
    Berry, D., et al., "A New Quality Model for Natural Language Requirements Specifications," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
  158. [Berry 2008].
    Berry, D., "In requirements engineering, everything is an aspect," International workshop on software architectures and mobility, New York: ACM Press, 2008, pp. 1-2.
  159. [Bertolini,et al. 2007].
    Bertolini, A., et al., "Product Line Use Cases: Scenario-Based Specification and Testing of Requirements," International Conference on Software Product Lines, Berlin: Springer, 2007.
  160. [Berzins and Gray 1985]
    Berzins, V., and M. Gray, "Analysis and Design in MSG 84: Formalizing Functional Specifications," IEEE Transactions on Software Engineering, 11, 8 (August 1985), pp. 657-670.
  161. [Berzins and Luqi 1991].
    Berzins, V., and Luqi, Software Engineering with Abstractions, Reading, Massachusetts: Addison-Wesley, 1991.
  162. [Berzins, et al. 1993].
    Berzins, V., et al., "Using Transformations in Specification-Based Prototyping," (see abstract) IEEE Transactions on Software Engineering, 19, 5 (May 1993), pp. 436-452.
  163. [Berzins, et al. 1995].
    Berzins, V., et al., "Computer Aided Prototyping System (CAPS)," International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, 1995.
  164. [Berzins, et al. 1997].
    Berzins, V., et al., "A Requirements Evolution Model for Computer Aided Prototyping," International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, June 1997, pp. 38-47.
  165. [Berzins 1998].
    Berzins, V., "Merging Changes to Software Specifications," International Workshop on Requirements Targeting Software and Systems Engineering, Berlin: Springer, 1998, pp. 121-132.
  166. [Berztiss 2000].
    Berztiss, A., "A Flexible Requirements Process," (see abstract) Eleventh IEEE International Workshop on Database and Expert Systems Applications, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 973-977.
  167. [Beshore, et al. 1998].
    Beshore, D., et al., "Improving Requirements Processes through Modeling and Data to Achieve Level 5 Capability Maturity," Eighth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1998.
  168. [Bestavros 1991].
    Bestavros, A., "Specification and Verification of Real-Time Embedded Systems Using Time-Constrained Reactive Automata," 1991 Real-Time Systems Symposium, Los Alamitos, California: IEEE Computer Society Press, 1991.
  169. [Beuche, et al. 2008].
    Beuche, D., et al., "Using requirements management tools in software product line engineering: the state of the practice," International Conference on Software Product Lines, Los Alamitos, California: IEEE Computer Society Press, 2008, pp. 84-93.
  170. [Beuschel 1989].
    Beuschel, W., "Design of working tasks in the office. The use of skill based requirements analysis," Conference on Analysis, Design and Evaluation of Man-Machine Systems, Pergamon Press, 1989, pp. 229-233.
  171. [Beyer and Holtzblatt 1995].
    Beyer, H., and Holtzblatt, K., "Apprenticing with the Customer," Communications of the ACM, 38, 5 (May 1995), pp. 45-52.
  172. [Beyer and Holtzblatt 1998].
    Beyer, H., and Holtzblatt, K., Contextual Design: Defining Customer-Centered Systems, San Francisco, California: Morgan Kaufmann, 1998.
  173. [Bezanson 1977].
    Bezanson, W., "Reliable Software Through Requirements Definition with Data Abstractions," Microelectronics and Reliability, 17, 1 (January 1977), pp. 85-91.
  174. [Bezivin 1995].
    Bezivin, J., "Object-Oriented Requirements Elicitation in the OSMOSIS Project," IEEE Symposium and Workshop on Systems Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 1995, pp. 289-295.
  175. [Bharadwaj and Heitmeyer 1999].
    Bharadwaj, R., and C. Heitmeyer, "Model Checking Complete Requirements Specifications Using Abstraction," Automated Software Engineering, 6, 1 (January 1999), pp. 37-68.
  176. [Bhat, et al. 2006].
    Bhat, J.,
    et al., "Overcoming Requirements Engineering Challenges: Lessons from Offshore Outsourcing," IEEE Software, 23, 5 (September/October 2006), pp. 38-44.
  177. [Bhat and Gupta 2007].
    Bhat, J., and A. Gupta, "Enhancing Requirement Stakeholder Satisfaction during Far-shore Maintenance of Custom Developed Software using Shift-Pattern Model,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  178. [Bhatia and Vasal 2007].
    Bhatia, M., and A. Vasal, "Localisation and Requirement Engineering in Context to Indian Scenario,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  179. [Bhatt, et al. 2007].
    Bhatt, M., et al., "OntoMove: A Knowledge Based Framework for Semantic Requirement Profiling and Resource Acquisition," Australian Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 137-146. 
  180. [Bhuiyan, et al., 2007].
    Bhuiyan, M., et al., "Integration of Agent-Oriented Conceptual Models and UML Diagrams," IEEE International Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 171-178.
  181. [Bianchi, et al. 1980].
    Bianchi, G., et al., "Requirements Specifications -- Today and Tomorrow (Panel Discussion)," IFAC Real Time Programming Conference, 1980.
  182. [Bicarregui, et al. 2008].
    Bicarregui, J., et al., "Towards Modelling Obligations in Event-B," International Conference on Abstract State Machines, Berlin: Springer, 2008.
  183. [Bickerton and Siddiqi 1993].
    Bickerton, M., and J. Siddiqi, "The Classification of Requirements Engineering Methods," (see abstract) IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 182-186.
  184. [Biddle and Moritz 2006].
    Biddle, M., and S. Moritz, "Context Based Measurement of Requirements Instability," Sixteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2006.
  185. [Biébow and Szulman 1992].
    Biébow, B., and Szulman, S., "DISERT: A Tool for the Detection of Incoherences on Software Engineering Requirements Texts," Fifth International Conference on Software Engineering and Its Applications, Nanterre, France: EC2, 1992.
  186. [Biébow and Szulman 1994].
    Biébow, B., and Szulman, S., "Acquisition and Validation of Software Requirements," Knowledge Acquisition, 6, 4 (December 1994), pp. 343-368.
  187. [Bielkowicz and Tun 2001].
    Bielkowicz, P., and T. Tun, "A Comparison and Evaluation of Data Requirement Specification Techniques in SSADM and the Unified Process," Lecture Notes in Computer Science, Volume 2068, Berlin: Springer, 2001, pp. 46ff. 
  188. [Bienvenu and Godwin 2004].
    Bienvenu, M., and K. Godwin, "DOD AF Views as Requirements Vehicles in an MDA Systems Development Process," Command and Control Research and Technology Symposium 2004, Command and Control Research Program, 2004.
  189. [Biernacki, et al. 1992].
    Biernacki, J., et al., "Applications of Modern Systems Analysis Paradigms to the Development of Complex Systems," Second Annual International Symposium on Requirements Engineering, Seattle, Washington: International Council on Systems Engineering, July 1992.
  190. [Bieser, et al. 2006].
    Bieser, T., et al., "Requirements Engineering," in Multiagent Engineering: Theory and Applications in Enterprises, Berlin: Springer, 2006, pp. 359-381.
  191. [Biffl, et al. 2000].
    Biffl, S., et al., "Evaluation of Inspectors' Defect Estimation Accuracy for a Requirements Document after Individual Inspection," Seventh Asia-Pacific Software Engineering Conference (APSEC), Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 100-109.
  192. [Biffl and Halling 2000].
    Biffl, S., and M. Halling, "Software Product Improvement with Inspection: A Large-Scale Experiment on the Influence of Inspection Processes on Defect Detection in Software Requirements Documents," 26th IEEE Euromicro Conference, Volume 2, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 262-269.
  193. [Biffl, et al. 2000].
    Biffl, S., et al., "Investigating the Effect of a Second Software Inspection Cycle: Cost Benefit Data from a Large-Scale Experiment on Reinspection of a Software Requirements Document," 2000 Australian Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 194-203.
  194. [Binder and Tsai 1990].
    Binder, R., and J. Tsai, "KB/RMS: an intelligent assistant for requirement definition," International Conference on Tools for Artificial Intelligence, Los Alamitos, California: IEEE Computer Society Press, 1990, pp. 610-616.
  195. [Bijl and Harmann 2004].
    Bijl, M., and R. Harmann, "User Requirements for a Technical Risk Assessment Technique," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  196. [Birk and Heller 2007].
    Birk, A., and G. Heller, "Challenges for Requirements Engineering and Management in Software Product Line Development," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ' 07), Berlin: Springer, 2007.
  197. [Biró, et al. 2006].
    Biró, M., et al., "From compliance to business success: improving outsourcing service controls by adopting external regulatory requirements," Software Process: Improvement and Practice, 11, 3 (May/June 2006), pp. 239-249.
  198. [Bischofberger and Pomberger 1992].
    Bischofberger, W., and G. Pomberger, eds., Prototype-Oriented Software Development, Berlin, Germany: Springer Verlag, 1992.
  199. [Bittner, et al. 2002].
    Bittner, K., et al., Use Case Modeling, Reading, Pennsylvania: Addison Wesley, 2002.
  200. [Bittner, et al. 2005].
    Bittner, M., et al., "Managing Variability and Reuse of Features and Requirements for Large and Complex Organizational Structures," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 469-470.
  201. [Bjorner 1995].
    Bjorner, D., "Software Systems Engineering from Domain Analysis via Requirements Capture to Software Architectures," Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society, 1995, pp. 2-11.
  202. [Bjorner 1998].
    Bjorner, D., "Domains as a Prerequisite for Requirements and Software Domain Perspectives and facets, Requirements Aspects, and Software Views," in Requirements Targeting Software and Systems Engineering, Broy, M., and B. Rumpe, eds., Lecture Notes in Computer Science 1526, Berlin: Springer, 1998, pp. 1-41.
  203. [Bjorner 2004].
    Bjorner, D., "Towards Posit and Prove Calculi for Requirement Engineering and Software Design," Lecture Notes in Computer Science, Volume 2635, Berlin: Springer, 2004, pp. 58-82. 
  204. [Bjorner 2006].
    Bjorner, D., Software Engineering 3: Domains, Requirements and Software Design, Berlin: Springer, 2006. 
  205. [Bjorner 2008].
    Bjorner, D., "From domain to requirements," Concurrency, Graphs and Models, Berlin: Springer, 2008, pp. 278-300.
  206. [Blaauboer, et al. 2007].
    Blaauboer, F., et al., "Deciding to Adopt Requirements Traceability in Practice," Advanced Information Systems Engineering, Berlin: Springer, 2007.
  207. [Black 1995].
    Black, J., "Automated Requirements Extraction Generates Productivity Improvements," 1995 Annual International Symposium on Requirements Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
  208. [Blackhurst and Gandee 1976].
    Blackhurst, I., and J. Gandee, "Call Description Language," Electrical Communication, 52 (1976), pp. 202-206.
  209. [Blanchard and Fabrycky 1981].
    Blanchard, B., and W. Fabrycky, Systems Engineering and Analysis, Englewood Cliffs, New Jersey: Prentice Hall, 1981.
  210. [Blandford, et al. 1993].
    Blandford, A., et al., "Integrating User Requirements and System Specification," in Computers, Communication and Usability: Design Issues, Research and Methods for Integrated Services, P. Byerley, et al., eds., New York, New York: Elsevier Science Publishers, 1993.
  211. [Bleistein, et al. 2003].
    Bleistein, S., et al., "Linking Requirements Goal Modeling Techniques to Strategic e-Business Patterns and Best Practice," Australian Workshop on Requirements Engineering, 2003.
  212. [Bleistein, et al. 2004].
    Bleistein, S., et al., "Strategy-Oriented Alignment in Requirements Engineering: Linking Business Strategy to Requirements of E-Business Systems Using the SOARE Approach," Journal of Research and Practice in Information Technology, 36, 4 (November 2004). pp. 259-276.
  213. [Bleistein, et al. 2004a].
    Bleistein, S., et al., "Modeling Business Strategy in E-Business Systems Requirements Engineering," Lecture Notes in Computer Science, Volume 3289, Berlin: Springer, 2004, pp. 617-628. 
  214. [Bleistein, et al. 2004b].
    Bleistein, S., et al., "Requirements engineering for e-business systems: Integrating Jackson problem diagrams with goal modeling and BPM," Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 410-417. 
  215. [Bleistein, et al. 2005].
    Bleistein, S., et al., "Strategic alignment in requirements analysis for organizational IT: an integrated approach," ACM Symposium on Applied Computing, New York: ACM Press, March 2005.
  216. [Bleistein, et al. 2006].
    Bleistein, S., et al., "Requirements Engineering for eBusiness Advantage," Requirements Engineering, 11, 1 (March 2006), pp. 4-16.
  217. [Bleistein, et al. 2006a].
    Bleistein, S., et al., "B-SCP: A requirements analysis framework for validating strategic alignment of organizational IT based on strategy, context, and process," Information and Software Technology, accepted for publication, 2006.
  218. [Bleistein, et al. 2006b].
    Bleistein, S., et al., "Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams," Journal of Systems and Software, 79, 3 (March 2006), pp. 362-378.
  219. [Bleser and Foley 1982].
    Bleser, T., and J. Foley, "Towards Specifying and Evaluating the Human Factors of User-Computer Interfaces," ( see abstract) ACM Human Factors in Computing Systems Conference, New York: ACM Press, 1982, pp. 309-314.
  220. [Blue 1991].
    Blue, D., Joint Integrated Avionics Working Group: Domain Analysis Description, a report to Naval Weapons Center, Rockville, Maryland: CTA Corporation, September 1991.
  221. [Blue 1992].
    Blue, D., "Joint Integrated Avionics Working Group: Domain Analysis Methodology Project," CTA Corporation Technical Newsletter, 1, 3 (May 1991), Rockville, Maryland: CTA Corporation, pp. 1-2.
  222. [Blum 1983].
    Blum, B., "Still More About Prototyping," ACM Software Engineering Notes, 8, 3 (May 1983), pp. 9-11.
  223. [Blum 1993].
    Blum, B., "Representing Open Requirements with a Fragment-Based Specification," (see abstract) IEEE Transactions on Systems, Man and Cybernetics, 23, 3 (May-June 1993), pp. 724-736.
  224. [Blumofe and Hecht 1988]
    Blumofe, R., and A. Hecht, "Executing Real-Time Structured Analysis Specifications," ACM Software Engineering Notes, 13, 3 (July 1988), pp. 32-40.
  225. [Blyth and Chudge 1993].
    Blyth, A., and J. Chudge, "The Role of Interaction Analysis in Requirements Engineering," IFIP WG 8.1 Conference on Information System Development Process, Como, Italy, 1993. Also available as University of Newcastle Technical Report IFIP-wg8.1-isdp, Newcastle, UK.
  226. [Blyth, et al. 1993].
    Blyth, A., et al., "ORDIT: A New Methodology to Assist in the Process of Eliciting and Modelling Organisational Requirements," Conference on Organisational Computing Systems, San Jose, California, November 1993. Also available as University of Newcastle Technical Report #COOCS-93, Newcastle, UK.
  227. [Blyth, et al. 1993a].
    Blyth, A., et al., "A Framework for Modelling Evolving Requirements," IEEE International Conference on Computer Software and Applications, Los Alamitos, California: IEEE Computer Society Press, 1993.
  228. [Boar 1984].
    Boar, B., Application Prototyping, New York: John Wiley, 1984.
  229. [Boar 1986].
    Boar, B., "Application Prototyping: A Life-Cycle Perspective," Journal of Systems Management, (February 1986), pp. 25-31.
  230. [Boddu, et al. 2004].
    Buddo, R., et al., "RETNA: From Requirements to Testing in a Natural Way," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 262-271.
  231. [Bodhuin, et al. 2004].
    Bodhuin, T., et al., "Impact Analysis for Supporting the Co-Evolution of Business Processes and Supporting Software Systems," International Conference on Advanced Information Systems Engineering (CAiSE), Los Alamitos, California: IEEE Computer Society Press, 2004.
  232. [Břdker and Grřnbćk 1991].
    Břdker, S., and K. Grřnbćk, "Cooperative Prototyping: Users and Designers in Mutual Activity," International Journal of Man-Machine Studies, 34, 3, (1991), pp. 453-478.
  233. [Boegh 2008].
    Boegh, J., "A New Standard for Quality Requirements," IEEE Software, 25 (2008).
  234. [Boehm 1974].
    Boehm, B., "Some Steps Toward Formal and Automated Aids to Software Requirements Analysis and Design," Information Processing '74, 1974.
  235. [Boehm, et al. 1975].
    Boehm, B., et al., "Some Experience with Automated Aids to the Design of Large-Scale Reliable Software," ACM SIGPLAN Notices, 10, 6 (June 1975), pp. 105-113.
  236. [Boehm 1984].
    Boehm, B., "Verifying and Validating Software Requirements and Design Specifications," IEEE Software, 1, 1 (January 1984), pp. 75-88.
  237. [Boehm, et al. 1984].
    Boehm, B., et al., "Prototyping vs. Specifying: A Multiproject Experiment," IEEE Transactions on Software Engineering, 10, 3 (May 1984), pp. 290-303.
  238. [Boehm, et al. 1994].
    Boehm, B., et al., "Software Requirements as Negotiated Win Conditions," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 74-83.
  239. [Boehm, et al. 1995].
    Boehm, B., et al., "Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach," (see abstract) Seventeenth IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
  240. [Boehm 1996].
    Boehm, B., "Helping Students Learn Requirements Engineering," Ninth Conference on Software Engineering Education, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 96-97.
  241. [Boehm and In 1996].
    Boehm, B., and H. In, " Identifying Quality-Requirement Conflicts," IEEE Software, 12, 2 (March 1996), pp. 25-36.
  242. [Boehm and Egyed 1998].
    Boehm, B., and A. Egyed, "Software Requirements Negotiation: Some Lessons Learned," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 503-506.
  243. [Boehm, et al. 1999].
    Boehm, B., et al., "Requirements Engineering, Expectations Management, and the Two Cultures," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 14-22.
  244. [Boehm and In 1999].
    Boehm, B., and H. In, "Cost vs. Quality Requirements: Conflict Analysis and Negotiation Aids," Software Quality Professional, 1, 2 (March 1999), pp. 38-50.
  245. [Boehm 2000].
    Boehm, B., "Requirements that Handle IKIWISI, COTS, and Rapid Change," IEEE Computer, 33, 7 (July 2000), pp. 99-102.
  246. [Boehm, et al. 2001].
    Boehm, B., et al., "Developing Groupware for Requirements Negotiation: Lessons Learned," IEEE Software, 18, 3 (May/June 2001), pp. 46-55.
  247. [Boehm 2003].
    Boehm, B., "Value-Based Software Engineering," IEEE Computer, 36, 3 (March 2003), pp. 33-41.
  248. [Boehm and Kitapci 2007].
    Boehm, B., and H. Kitapci, "The WinWin Approach: Using a Requirements Negotiation Tool for Rationale Capture and Use," International Symposium on Software Metrics, Berlin: Springer, 2007.
  249. [Boer 1993].
    de Boer, R., Computer Aided Requirements, Erasmus University Department of Informatics M.S. Thesis, Rotterdam, The Netherlands 1993.
  250. [Boettger, et al. 2002].
    Boettger, K., et al., "RECOCASE-tool: A CASE tool for RECOnciling Requirements Viewpoints,
    " Australian Workshop on Requirements Engineering, 2002.
  251. [Boettger, et al. 2003].
    Boettger, K., et al., "Requirements Reconciliation using a Computer Supported Collaborative Approach,
    " Journal of Integrated Design and Process Science, 7, 2 (April 2003), pp. 113-129.
  252. [Boettger, et al. 2003a].
    Boettger, K., et al., "Towards Reconciling Use Cases via Controlled Language and Graphical Models,
    " Web Knowledge Management and Decision Support, 2003, pp. 115-128.
  253. [Bohner, et al. 1996].
    Bohner, S., et al., "Business Reengineering for Information Technology: From Business Process to System Requirements," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  254. [Bolchini and Paolini 2002].
    Bolchini, D., and P. Paulini, "Goal-Oriented Requirement Specifications for Digital Libraries," Lecture Notes in Computer Science, Volume 2458, Berlin: Springer, 2002, pp. 107-117. 
  255. [Bolchini, et al. 2003].
    Bolchini, D., et al., "Adding Hypermedia Requirements to Goal-Driven Analysis," (see abstract) International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 127-137.
  256. [Bolchini and Paolini 2004].
    Bolchini, D., and P. Paolini, "Goal-Driven Requirements Analysis for Hyper-Media Web Applications," ( see abstract) Requirements Engineering, 9, 2 (May 2004), pp. 85-103.
  257. [Bolchini 2007].
    Bolchini, D., "Goal-Oriented Conceptual Database Design,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  258. [Bolchini, et al. 2007].
    Bolchini, D., et al., "Branding and Communication Goals for Content-Intensive Interactive Applications,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  259. [Bolloju and Sugumaran 2007].
    Bolloju, N., and V. Sugumaran, "Quality Dependencies Among Use Case Models and Sequence Diagrams Developed by Novice Systems Analysts," Advances in Conceptual Modeling - Theory and Practice, Berlin: Springer, 2007.
  260. [Bolloju and Sun 2008].
    Bolloju, N., and S. Sun, "Exploiting the Complementary Relationship between Use Case Models and Activity Diagrams for Developing Quality Requirements Specifications,
    " Advances in Conceptual Modeling - Theory and Practice, Berlin: Springer, 2008.
  261. [Bologna, et al. 1988].
    Bologna, S., et al., "An environment for requirements specification and analysis of real-time software based on timed Petri nets," IFAC/IFIP Workshop on Safety of Computer Control Systems, Oxford, UK: Pergamon Press, 1988, pp. 7-10.
  262. [Bolton, et al. 1986].
    Bolton, D., et al., "Knowledge-Based Support for Requirements Engineering," Journal of Software Engineering and Knowledge Engineering, 2, 2 (1992), pp. 293-319.
  263. [Bolton, et al. 1992].
    Bolton, D., et al., "A Generic Modelling Approach to Requirements Capture in the Domain of Air Traffic Control," IEE Colloquium on Software in Air Traffic Control Systems, 1992.
  264. [Bolton, et al. 1994].
    Bolton, D., et al., "Using Domain Knowledge in Requirements Capture and Formal Specification Construction," in Requirements Engineering Social and Technical Issues, M. Jirotka, and J. Goguen, eds., London: Academic Press, 1994.
  265. [Bondi 2007].
    Bondi, A., "Best Practices for Writing and Managing Performance, Reliability, and Availability Requirements (tutorial)," International Conference on Software Architecture, Los Alamitos, California: IEEE Computer Society Press, 2007.
  266. [Bone 2008].
    Bone, M., "Cyclone Process: Dealing with Vague Requirements," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2008.
  267. [Boness and Harrison 2007].
    Boness, K., and R. Harrison, "Goal Sketching: Towards Agile Requirements Engineering," International Conference on Software Engineering Advances, Los Alamitos, California: IEEE Computer Society Press, 2007.
  268. [Boness, et al. 2008].
    Boness, K., et al., "A lightweight technique for assessing risks in requirements analysis," IEE Proceedings on Software Engineering, (2008).
  269. [Boness and Harrison 2008].
    Boness, K., and R. Harrison, "Goal Sketching with Activity Diagrams," International Conference on Software Engineering Advances, Los Alamitos, California: IEEE Computer Society Press, 2008.
  270. [Bonfatti and Monari 1994].
    Bonfatti, F., and P. Monari, "Towards a General-Purpose Approach to Object-Oriented Analysis," International Symposium on Object-Oriented Methodologies and Systems, Italy, 1994, pp. 108-122.

    Bonilla, see Mendez-Bonilla
     
  271. [Bontemps and Heymans 2003].
    Bontemps, Y., and P. Heymans, "LSC's: That's the Name of the Game! (A Specification Framework based on Live Sequence Charts and Game Theory)," International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003.
  272. [Booch 1986].
    Booch, G., "Object Oriented Development," IEEE Transactions on Software Engineering, 12, 2 (February 1986), pp. 211-221.
  273. [Booch 1994].
    Booch, G., Object-Oriented Analysis and Design with Applications, Redwood City, California: Benjamin/Cummings, 1994.
  274. [Booch, et al. 1998].
    Booch, G., et al., The Unified Modeling Language User Guide, Addison-Wesley, 1998. 
  275. [Boon, et al. 2002].
    Boon, G., et al., "Conceptualising the Requirements of CRM from an Organisational Perspective: a Review of the Literature,
    " Australian Workshop on Requirements Engineering, 2002.
  276. [Booth, et al. 2001].
    Booth, R., et al., "Market-Driven Requirements Engineering Challenges: An Industrial Case Study of a Process Performance Declination,
    " Australian Workshop on Requirements Engineering, 2001.
  277. [Borden, et al. 1992].
    Borden, C., et al., "Systems Engineering with the Right Requirements: An Approach for Assessing User Needs," Second Annual International Symposium on Requirements Engineering, Seattle, Washington: International Council on Systems Engineering, July 1992.
  278. [Borg, et al. 2006].
    Borg, A., et al., "Good Practice and Improvement Model of Handling Capacity Requirements of Large Telecommunication Systems," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  279. [Borg, et al. 2007].
    Borg, A., et al., "Integrating an Improvement Model of Handling Capacity Requirements with OpenUP/Basic Process," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ '07), Berlin: Springer, 2007.
  280. [Borg, et al. 2007a].
    Borg, A., et al., "Extending the OpenUP/Basic Requirements Discipline to Specify Capacity Requirements,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  281. [Borger 2004].
    Borger, E., "The ASM Ground Model Method as a Foundation of Requirements Engineering," Lecture Notes in Computer Science, Volume 2772, Berlin: Springer, 2004, pp. 145-160. 
  282. [Borgida, et al. 1985].
    Borgida, A., et al., "Knowledge Representation as the Basis for Requirements Specification," IEEE Computer, 18, 4 (April 1985), pp. 82-91.
  283. [Borster and Janning 1992].
    Borster, J., and T. Janning, "Traceability Between Requirements and Design: A Transformational Approach," IEEE International Conference on Computer Software and Applications, Los Alamitos, California: IEEE Computer Society Press, 1992.
  284. [Bosse, et al. 2006].
    Bosse, T., "Requirements Analysis of an Agent’s Reasoning Capability," Agent-Oriented Information Systems III, Lecture Notes in Computer Science, Volume 3529, Berlin: Springer, 2006, pp. 48-63. 
  285. [Bostrom and Thomas 1983].
    Bostrom, R., and B. Thomas, "Achieving Excellence in Communications: A Key to Developing Complete, Accurate and Shared Information Requirements," Twentieth Annual Conference on Computer Personnel in Research, New York: ACM Press, 1983, pp. 1-13.
  286. [Bostrom 1989].
    Bostrom, R., "Successful Application of Communication Techniques to Improve the Systems Development Process," Information and Management, 16, 5 (1989), pp. 279-295.
  287. [Botella, et al. 2002].
    Botella, P., et al., "Modeling Non-Functional Requirements," in Applying Requirements Engineering, Duran, A., and M. Toro, eds., Salamanca, Spain: Catedral Publ., 2002, pp. 13-33.
  288. [Botterweck and Hampe 2006].
    Botterweck, G., and J. Hampe, "Capturing the Requirements for Multiple User Interfaces," Australian Workshop on Requirements Engineering, 2006.
  289. [Boulanger 2005].
    Boulanger, J., "BRAIL: Requirements-Based UML Modeling," International Conference on Software and Systems Engineering and Their Applications, Paris: CNAM, 2005.
  290. [Boulanger and Quang Đao 2008].
    Boulanger, J., and V. Quang Đao, "Requirements engineering in a model-based methodology for embedded automotive software," IEEE International Conference on Software Product Lines, Los Alamitos, California: IEEE Computer Society Press, 2006.
  291. [Bounif, et al. 2007].
    Bounif, H., et al., "Requirements Ontology and Multi-representation Strategy for Database Schema Evolution," Ontologies-Based Databases and Information Systems, Lecture Notes in Computer Science 4623, Berlin: Springer, 2007, pp. 68-84. 
  292. [Bouquet, et al. 2005].
    Bouquet, F., et al., "Requirements traceability in automated test generation: application to smart card software validation," ACM Software Engineering Notes, 30, 4 (May 2005).

    Bourae, see AlBourae
     
  293. [Bourdeau and Cheng 1995].
    Bourdeau, R., and B. Cheng, "A Formal Semantics for Object Model Diagrams," IEEE Transactions on Software Engineering, 21, 10 (October 1995), pp. 799-821.
  294. [Bourdeau , et al. 1999].
    Bourdeau, E., et al., "
    Hierarchical Context Diagrams with UML: An Experience Report on Satellite Ground System Analysis," Lecture Notes in Computer Science 1618, Berlin: Springer, 1999, pp. 227-239.
  295. [Bowden, et al. 2000].
    Bowden, P., et al., "Estimation Support by Lexical Analysis of Requirements Documents," Journal of Systems and Software, 51, 2 (April 2000), pp. 99-109.
  296. [Bowen 1985].
    Bowen, T., Specification of Software Quality Attributes, RADC Report #RADC-TR-85-37, Griffis Air Force Base, New York: Rome Air Development Center, February 1985.
  297. [Bowen, et al. 2007].
    Bowen, P., et al., "Reliability factors in business software: volatility, requirements and end-users," Information Systems (2007). 
  298. [Bowles 2004].
    Bowles, J., "Code from Requirements: New Productivity Tools Improve the Reliability and Maintainability of Software Systems," Annual Symposium on Reliability and Maintainability, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 68-72.
  299. [Bowles 2006].
    Bowles, J., "Better software reliability by getting the requirements right," Annual Symposium on Reliability and Maintainability, Los Alamitos, California: IEEE Computer Society Press, 2006.
  300. [Bowman, et al., 1997].
    Bowman, M., et al., Conceptual Modeling, London: Prentice Hall, 1997.
  301. [Boyd, et al. 2005].
    Boyd, S., et al., "Measuring the Expressiveness of Constrained Natural Language: An Empirical Study," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 339-352.
  302. [Boyd, et al. 2007].
    Boyd, S., et al., "Optimal-Constraint Lexicons for Requirement Specifications," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ '07), Berlin: Springer, 2007.
  303. [Boydstun, et al. 1980].
    Boydstun, L., et al., "Computer-Aided Modeling of Information Systems," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1980, pp. 37-41. 
  304. [Boyle and Stoller 1990].
    Boyle, K., and R. Stoller, "TRACER: an automated tool for the capture and tracing of engineering requirements," WESCON, Los Angeles, California: Electronics Conventions Management, 1990, pp. 620-625. 
  305. [Bracchi and Pernici 1984].
    Bracchi, G., and B. Pernici, "The design requirements of office systems,"
    ACM Transactions on Information Systems, 2, 2 (April 1984), pp. 151-170. 
  306. [Brackett 1989].
    Brackett, J., "Performing requirements analysis project courses for external customers," Issues in Software Engineering Education, New York: Springer-Verlag, 1990, pp. 276-285. 
  307. [Bragge, et al. 2005].
    Bragge, J., et al., "Developing Innovative Information Systems Services Together with Wide Audience End-Users," Hawaii International Conference on System Science, Los Alamitos, California: IEEE Computer Society Press, 2005.
  308. [Brathwaite 1988].
    Brathwaite, K., Analysis, Design and Implementation of Data Dictionaries, New York: McGraw Hill, 1988.
  309. [Brauer , et al. 2002].
    Brauer, W., et al., "
    Expectation-Oriented Analysis and Design," Lecture Notes in Computer Science 2222, Berlin: Springer, 2002, pp. 226ff.
  310. [Braun, et al. 2001].
    Braun, A., et al., "Supporting Informal Meetings in Requirements Engineering," Seventh International Workshop on Requirements Engineering: Foundations for Software Quality, Interlocken, Switzerland, June 2001.
  311. [Bravaco and Yadav 1985].
    Bravaco, R., and S. Yadav, "Requirements Definition Architecture: An Overview," Computers in Industry, 6, 4 (August 1985).
  312. [Bray 2002].
    Bray, I., An Introduction to Requirements Engineering, Reading, Massachusetts: Addison-Wesley, 2002.
  313. [Bray 2003].
    Bray, I.,
    "The Simulator: Another Elementary Problem Frame," International Workshop on Requirements Engineering: Foundations for Software Quality, 2003.
  314. [Breaux and Antn 2005].
    Breaux, T., and A. Antón, "Analyzing Goal Semantics for Rights, Permissions and Obligations," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 177-188.
  315. [Breaux, et al. 2006].
    Breaux, T.,
    et al., "Towards Regulatory Compliance: Extracting Rights and Obligations to Align Requirements with Regulations," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  316. [Breaux and Antón 2008].
    Breaux, T., and A. Antón, "Analyzing Regulatory Rules for Privacy and Security Requirements," IEEE Transactions on Software Engineering, 34 (2008).
  317. [Breaux, et al. 2008].
    Breaux, T., et al., "Legal Requirements, Compliance and Practice: An Industry Case Study in Accessibility," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2008.
  318. [Bredereke 2002].
    Bredereke, J., "Maintaining Telephone Switching Software Requirements," (see abstract) IEEE Communications Magazine, 40, 11 (November 2002), pp. 104-109.
  319. [Bredereke 2004].
    Bredereke, J., "On Feature Orientation and on Requirements Encapsulation Using Families of Requirements," Lecture Notes in Computer Science, Volume 2975, Berlin: Springer, 2004, pp. 26-44. 
  320. [Breen 2005].
    Breen, M., "Experience of Using a Lightweight Formal Specification Method for a Commercial Embedded System Product Line," ( see abstract) Requirements Engineering, 10, 2 (May 2005), pp. 161-172.
  321. [Breiter 2004].
    Breiter, A., "Requirements Development in Loosely Coupled Systems: Building a Knowledge Management System with Schools," Thirty-Seventh Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 6-15.

    Breitman, K., see also Sequerra-Breitman, K.
     
  322. [Breitman and Leite 1998].
    Breitman, K., and J. Leite, "A Framework for Scenario Evolution," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 214-221.
  323. [Breitman et al. 1999].
    Breitman, K., et al., "The World's a Stage: A Survey on Requirements Engineering using a Real-Life Case Study," Journal of the Brazilian Computer Society, 6, 1 (July 1999).
  324. [Breitman and Leite 2003].
    Breitman, K., and J. Leite, "Ontology as a Requirements Engineering Product," (see abstract)
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 309-319.
  325. [Breitman et al. 2005].
    Breitman, K., et al., "Supporting Scenario Evolution," ( see abstract) Requirements Engineering, 10, 2 (May 2005), pp. 112-131.
  326. [Brereton, et al. 1996].
    Brereton, P., et al., "Requirements Elicitation for Software-Based Systems," Software Engineering Journal, 11, 3 (May 1996), p. 148.
  327. [Bresciani, et al. 2002].
    Bresciani, P., et al., "Modeling Early Requirements in Tropos: A Transformation Based Approach," Lecture Notes in Computer Science, Volume 2222, Berlin: Springer, 2002, pp. 151ff.
  328. [Bresciani and Donzelli 2003].
    Bresciani, P., and P. Donzelli, "A Practical Agent-Based Requirements Engineering Framework," Lecture Notes in Computer Science, Volume 2814, Berlin: Springer, 2003, pp. 217-228. 
  329. [Bresciani and Sannicolo 2003].
    Bresciani, P., and F. Sannicolo, "Requirements Analysis in Tropos: A Self-Referencing Example," Lecture Notes in Computer Science, Volume 2592, Berlin: Springer, 2003, pp. 21-35. 
  330. [Bresciani, et al. 2003].
    Bresciani, P., et al., "Requirements Engineering for Knowledge Management in eGovernment," Lecture Notes in Computer Science, Volume 2645, Berlin: Springer, 2003, pp. 48-59.
  331. [Bresciani and Donzelli 2004].
    Bresciani, P., and P. Donzelli, "A Practical Agent-Based Approach to Requirements Engineering for Socio-Technical Systems," Lecture Notes in Computer Science, Volume 3030, Berlin: Springer, 2004, pp. 158-173. 
  332. [Bresciani and Donzelli 2004a].
    Bresciani, P., and P. Donzelli, "The Agent at the Center of the Requirements Engineering Process," Lecture Notes in Computer Science, Volume 2940, Berlin: Springer, 2004, pp. 1-18. 
  333. [Bresciani, et al. 2004].
    Bresciani, P., et al., "Multi-Agent Systems and Security Requirements Analysis," Lecture Notes in Computer Science, Volume 2940, Berlin: Springer, 2004, pp. 35-48. 
  334. [Briand, et al. 2005].
    Briand, L., et al., "Automated impact analysis of UML models," Journal of Systems and Software (2005).
  335. [Briand, et al. 2005a].
    Briand, L., et al., "Automated Support for Deriving Test Requirements from UML Statecharts," Software and Systems Modeling ( October 2005).
  336. [Brier, et al 2005].
    Brier, J., et al., "Capturing Change in Socio-Technical Systems with Problem Frames," 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
  337. [Briggs 2001].
    Brigs, B., "Hierarchical Task Analysis: Bridging Organisational Goals and System Requirements," International Symposium on Systems Engineering, Washington: International Council on Systems Engineering, 2001.
  338. [Briggs and Grünbacher 2002].
    Briggs, R., and P. Grünbacher, "EasyWinWin: Managing Complexity in Requirements Negotiation with GSS," 35th Hawaii International Conference on System Science, Los Alamitos, California: IEEE Computer Society Press, 2002.
  339. [Briggs and Samson 2006].
    Briggs, H., and M. Samson, "Tying Requirements to Design Artifacts," Sixteenth International Symposium on Systems Engineering, Washington: International Council on Systems Engineering, 2006. 
  340. [Brinkkemper, et al. 1990].
    Brinkkemper, S., et al., "A CASE tool shell to facilitate the customisation of requirements engineering support," International Workshop on Computer-Aided Software Engineering, Los Alamitos, California; IEEE Computer Society Press, 1990, pp. 302-303.
  341. [Brinkkemper and ter Hofstede 2000].
    Brinkkemper, S., and A. ter Hofstede, "The conceptual task model: a specification technique between requirements engineering and program development," International Conference on Advanced Information Systems Engineering (CAiSE), Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 228-250.
  342. [Brinkkemper 2003].
    Brinkkemper, S.,
    "Requirements Engineering Research the Industry Is and Is Not Waiting For," International Workshop on Requirements Engineering: Foundations for Software Quality, 2003.
  343. [Brinkkemper, et al. 2008].
    Brinkkemper, S., et al., "Process improvement in requirements management: A method engineering approach," International Working Conference on Requirements Engineering: Foundations for Software Quality, Berlin: Springer, 2008.
  344. [Brito and Moriera 2004].
    Brito, I., and A. Moriera, " Integrating the NFR Framework in a RE Model," Third International Conference on Aspect-Oriented Software Development, March 2004, pp. 22-26.
  345. [Brito and Moriera 2006].
    Brito, I., and A. Moriera, "Towards an Integrated Approach for Aspectual Requirements (poster)," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  346. [Brito, et al. 2007].
    Brito, I., et al., "Handling Conflicts in Aspectual Requirements Compositions," Transactions on Aspect-Oriented Software Development, Berlin: Springer, 2007.
  347. [Brookes 1988].
    Brookes, C., "An automated DSS requirements elicitation model applied to non-repeating problem situations," IFIP Working Conference on Organizational Decision Support Systems, Amsterdam: North Holland, 1988, pp. 129-138.
  348. [Broomfield and Chung 1997].
    Broomfield, E., and P. Chung, "Safety Assessment and the Software Requirements Specification," (see abstract) Reliability Engineering & System Safety, 55, 3 (March 1997), pp. 295-309.
  349. [Brown 1988].
    Brown, D., "Requiring CS1 students to write requirements specifications: a rationale, implementation suggestions, and a case study," SIGCSE Bulletin, 20, 1 (February 1988), pp. 13-16.
  350. [Brown 1993].
    Brown, D., "Implementing of a Requirements Verification Database," International Symposium on Systems Engineering, Washington: International Council on Systems Engineering, 1993.
  351. [Brown and Cady 1993].
    Brown, P., and K. Cady, "Functional Analysis vs. Object-Oriented Analysis: A View From the Trenches," Third International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, July 1993.
  352. [Brown, et al. 1994].
    Brown, P., et al., "Improving the System Software Requirements Development Process," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 691-698.
  353. [Brown and Lavender 1995].
    Brown, P., and J. Lavender, "Virtual Prototyping: Results Illustrate Utility in Developing Weapon System Requirements," Fifth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
  354. [Brown 2002].
    Brown, D., An Introduction to Object-Oriented
    Analysis, New York: John Wiley and Sons, 2002.
  355. [Brown, et al. 2002].
    Brown, G., et al., "
    Requirements Analysis for a Multi-Spacecraft Flight System," 2002 IEEE Aerospace Conference, Los Alamitos, California: IEEE Computer Society Press, 2002, pp. 767-782.
  356. [Brown, et al. 2006].
    Brown, G., et al., "Goal-Oriented Specification of Adaptation Requirements engineering in Adaptive systems," International Workshop on Self-Adaptation and Self-Managing Systems, New York: ACM Press, 2006, pp. 23-29. 
  357. [Browne and Rogich 2001].
    Browne, G., and M. Rogich, "An Empirical Investigation of User Requirements Elicitation: Comparing the Effectiveness of Prompting Techniques," Journal of Management Information Systems, 17, 4 (Spring 2001), pp. 223-249.
  358. [Browne and Ramesh 2002].
    Browne, G., and V. Ramesh, "Improving information requirements determination: a cognitive perspective," Information and Management, 39, 8 (September 2002), pp. 625-645.
  359. [Broy and Slotosch 2001].
    Broy, M., and O. Sltotsch, "From Requirements to Validated Embedded Systems," Lecture Notes in Computer Science, Volume 2211, Berlin: Springer, 2001, pp. 51ff. 
  360. [Broy 2006].
    Broy, M., "Requirements Engineering as a Key to Holistic Software Quality,"
    Computer and Information Sciences - ISCIS 2006, Lecture Notes in Computer Science, Volume 4263, Berlin: Springer, 2006, pp. 24-34. 
  361. [Bruce and Cooper 2001].
    Bruce, M., and R. Cooper, Creative Product Design: A Practical Guide to Requirements Capture and Management, New York: Wiley, 2001.
  362. [Bruegge 1995].
    Bruegge, B., "Requirements Analysis and Modeling," IEEE Software Education Conference, Los Alamitos, California: IEEE Computer Society, 1995, pp. 361-364.
  363. [Bruijn, et al. 2007].
    Bruijn, P., et al., "Customer experience requirements for e-commerce websites," International Journal of Web Engineering and Technology, (2007).
  364. [Brunet, et al. 1993].
    Brunet, J., et al., "Object Oriented Analysis in Practice," Fifth Conference on Advanced Information Systems Engineering, Paris, France, June 1993.
  365. [Brunet, et al. 1994].
    Brunet, J., et al., "Applying Object Oriented Analysis on a Case Study," Information Systems, 19, 3 (1994), pp. 199-209.
  366. [Bruno and Manchetto 1986].
    Bruno, G., and G. Manchetto, "Process-Translatable Petri Nets for the Rapid Prototyping of Process Control Systems," IEEE Transactions on Software Engineering, 12, 2 (February 1986), pp. 346-357.
  367. [Bruno and Morisio 1987].
    Bruno, G., and M. Morisio, "An Execution Specification Methodology: Its Application to Computer-Integrated Manufacturing Systems," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1987, pp. 714-720. 
  368. [Bruno, et al. 1988].
    Bruno, G., et al., "A Knowledge-Based System Approach to the Development of a System Functional Requirements Specification Processor," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1988, pp. 387-394. 
  369. [Bruno and Agarwal 1995].
    Bruno, G., and R. Agarwal, "Validating Software Requirements Using Operational Models," Second Symposium on Software Quality Techniques and Acquisition Criteria, Florence, Italy, Springer-Verlag, May 1995.
  370. [Bruyn, et al. 1988].
    Bruyn, W., et al., "ESML: An Extended System Modeling Language Based on the Data Flow Diagram," ACM Software Engineering Notes, 13, 1 (January 1988), pp. 58-67. 
  371. [Bryant 1997].
    Bryant, J., "Requirements capture using SODA," European Journal of Information Systems, 6, 3 (September 1997), pp. 155-163. 
  372. [Bryant 1999].
    Bryant, B., "Object-Oriented Natural Language Requirements Specification," 23rd Australasian Computer Science Conference, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 24-30.
  373. [Bryl, et al. 2006].
    Bryl, V., et al., "Designing security requirements models through planning," 18th International Conference on Advanced Information Systems Engineering (CAiSE 2006), Lecture Notes in Computer Science, Volume 4001, Berlin: Springer, 2006, pp. 33-47.   
  374. [Bubenko, et al. 1994].
    Bubenko, J., et al., "Facilitating 'Fuzzy to Formal' Requirements Modelling," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 154-157.
  375. [Bübl 2006].
    Bübl, F., "Keeping track of crosscutting requirements in UML models via context-based constraints," International OOPSLA Conference, New York: ACM Press, 2006.
  376. [Bucchiarone, et al. 2005].
    Bucchiarone, A., et al., "Quality Analysis of NL Requirements: An Industrial Case Study," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 390-394.
  377. [Bucci, et al. 1994].
    Bucci, G., et al., "An Object-Oriented Dual Language for Specifying Reactive Systems," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 6-15.
  378. [Buckley 1989].
    Buckley, F., Implementing Software Engineering Practices, New York: John Wiley, 1989, Chapters 4-6.
  379. [Buede and Charbonneur 1997].
    Buede, D., and S. Charbonneur, "Considerations in Developing Originating Requirements," Seventh Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1997.
  380. [Buescher and Wilkinson 1990].
    Buescher, T., and R. Wilkinson, "Requirements modeling for real-time software development," IEEE National Aerospace Conference, Los Alamitos, California: IEEE Computer Society Press, 1990, pp. 613-617.
  381. [Bühne, et al. 2003].
    Bühne, S., et al.,
    "Modeling Dependencies Between Variation Points in Use Case Diagrams," International Workshop on Requirements Engineering: Foundations for Software Quality, 2003.
  382. [Bühne, et al. 2004].
    Bühne, S., et al., "Defining Requirements at Different levels of Abstraction," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 346-347.
  383. [Bühne, et al. 2005].
    Bühne, S., et al., "Modeling Requirements Variability for a Set of Product Lines," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 41-52.
  384. [Bühne, et al. 2007].
    Bühne, S., et al., "Scenario-Based Application Requirements Engineering," International Conference on Software Product Lines, Berlin: Springer, 2007.
  385. [Buhr and Dorr 2003].
    Buhr, K., and H. Dorr, "Requirements Driven Quality Assurance," Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2003.
  386. [Bukwa and Rhodes 1992].
    Bukwa, R., and D. Rhodes, "Managing Requirements Effectively in the Concurrent Engineering Environment," Second Annual International Symposium on Requirements Engineering, Seattle, Washington: International Council on Systems Engineering, July 1992.
  387. [Bulllinger 2006].
    Bullinger, T., The Reverse Detective: Pragmatic Software Requirements & Analysis, WME Books, 2006.
  388. [Bultan and Heitmeyer 2006].
    Bultan, T., and C., Heitmeyer, "Analyzing tabular requirements specifications using infinite state model checking," Fourth ACM & IEEE International Conference on Formal Methods and Models for Co-Design, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 7-16.
  389. [Bultan and Heitmeyer 2008].
    Bultan, T., and C., Heitmeyer, "Applying infinite state model checking and other analysis techniques to tabular requirements specifications of safety-critical systems," Design Automation for Embedded Systems, Los Alamitos, California: IEEE Computer Society Press, 2008.
  390. [Burd and Munro 1997].
    Burd, E., and M. Munro, "Implications of Non-Functional Requirements for the Reengineering of Legacy Code," ( see abstract) Fourth Working Conference on Reverse Engineering, Los Alamitos, California: IEEE Computer Society Press, 1997, pp. 215-223.
  391. [Buren and Cook 1998].
    van Buren, J., and D. Cook, "Experiences in the Adoption of Requirements Engineering Technologies," Crosstalk, December 1998, pp. 3-9.
  392. [Burg 1997].
    Burg, J., Linguistic Instruments in Requirements Engineering, Amsterdam, The Netherlands: IOS Press, 1997.
  393. [Burge and Brown 2008].
    Burge, J., and D. Brown, "Software Engineering Using RATionale," Journal of Systems and Software, 81, 3 (March 2008), pp. 395-413.
  394. [Burge, et al. 2008].
    Burge, J., et al., "Chapter 11: Rationale and Requirements Engineering," in
    Rationale-Based Software Engineering, Berlin: Springer, 2008.
  395. [Burgess, et al. 1990].
    Burgess, G., et al., "The Use of Causal Maps as a Requirements Analysis Tool: A Case Assessment of Research Propositions," in Human Factors in Information Systems Analysis and Design, A. Finkelstein, ed., Amsterdam: North-Holland-Elsevier Publ., 1990.
  396. [Burmeister, et al. 2008].
    Burmeister, B., et al., "BDI-agents for agile goal-oriented business processes," International joint conference on autonomous agents and multiagent systems, New York: ACM Press, 2008.
  397. [Burnett 2003]
    Burnett, M., "HCI Research Regarding End-User Requirement Specification: A Tutorial," Knowledge Based Systems, 15, 7-8 (November 2003), pp. 341-349.
  398. [Burns 1991].
    Burns, C., "Parallel Proto: A Prototyping Tool for Analyzing & Validating Sequential and Parallel Processing Software Requirements," IEEE Second International Workshop on Rapid System Prototyping, Los Alamitos, California: IEEE Computer Society Press, June 1991, pp. 151-160.
  399. [Burns and McDermid 1994].
    Burns, A., and J. McDermid, "Real-Time Safety-Critical Systems: Analysis and Synthesis," ( see abstract) IEE Software Engineering Journal, 9, 6 (November 1994), pp. 267-281.
  400. [Burstin and Ben-Bassat 1985].
    Burstin, M., and M. Ben-Bassat, "User's Approach to Requirements Analysis of a Large Software System," IEEE Convention of Electrical and Electronics Engineers in Israel, Los Alamitos, California: IEEE Computer Society Press, 1985, pp. 13ff.
  401. [Bush and Finkelstein 2002].
    Bush, D., and A. Finkelstein, "Environmental Scenarios and Requirements Stability," Workshop on Principles of Software Evolution, New York: ACM Press, May 2002, pp. 133-137.
  402. [Bush and Finkelstein 2003].
    Bush, D., and A. Finkelstein, "Requirements Stability Assessment Using Scenarios," International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 23-32.
  403. [Bustard and Winstanley 1994].
    Bustard, D., and A. Winstanley, "Making Changes to Formal Specifications: Requirements and an Example," (see abstract) IEEE Transactions on Software Engineering, 20, 8 (August 1994), pp. 562-568.
  404. [Bustard and Lundy 1995].
    Bustard, D., and P. Lundy, "Enhancing Soft Systems Analysis with Formal Modeling," Second International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
  405. [Bustard, et al. 1996].
    Bustard, D., et al., "Integrating Soft Systems and Object-Oriented Analysis," ( see abstract) Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 52-59.
  406. [Bustard 2001].
    Bustard, D., "BASE - A Framework for Requirements Engineering Based on Systems Thinking," International Symposium on Systems Engineering, Washington: International Council on Systems Engineering, 2001.
  407. [Bustard 2002].
    Bustard, D., "An Experience of Principled Negotiation in Requirements Engineering," Australian Workshop on Requirements Engineering, 2002.
  408. [Butler and Fitzgerald 1997].
    Butler, T., and B. Fitzgerald, "A Case Study of User Participation in the Information Systems Development Process," Eighteenth International Conference on Information Systems, Atlanta: Association for Information Systems, 1997, pp. 411-426.
  409. [Butterfield, et al. 1994].
    Butterfield, J., et al., "Resolving cognitive conflict in requirements definition: a blackboard-based model and system architecture," Computer Personnel Research Conference on Reinventing, New York: ACM Press, 1994.
  410. [Button and Sharrock 1994].
    Button, G., and W. Sharrock, "Occasioned Practices in the Work of Software Engineers," in Requirements Engineering Social and Technical Issues, M. Jirotka, and J. Goguen, eds., London: Academic Press, 1994.
  411. [Bűyűközkan and Feyzioğlu 2005].
    Bűyűközkan, G., and O. Feyzioğlu, "Group decision making to better respond customer needs in software development," Computers and Industrial Engineering, 48, 2 (March 2005), pp. 427-441.
  412. [Byers 1992].
    Byers, P., "Definition of requirements for a safety critical communications system," International Conference on Software Engineering for Telecommunication Systems and Services, London: IEE, 1992, pp. 98-101.
  413. [Byrd, et al. 1992].
    Byrd, T., et al., "A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques," MIS Quarterly, 16, 1 (March 1992), pp. 117-138.
  414. [Byrne 1994].
    Byrne, E., "IEEE Standard 830: Recommended Practice for Software Requirements Specification," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 58.

    C

    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. [Cabral and Sampaio 2008].
    Cabral, G., and A. Sampaio, "Formal Specification Generation from Requirement Documents," Electronic Notes in Theoretical Computer Science, 195 (January 2008), pp. 171-188. 
  2. [Caffall and Michael 2004].
    Caffall, D., and J. Michael, "A New Paradigm for Requirements Specification and Analysis of Systems of Systems," Lecture Notes in Computer Science, Volume 2941, Berlin: Springer, 2004, pp. 108-121. 
  3. [Cai 2007].
    Cai, K.-Y., "
    Non-Functional Computing: Towards a More Scientific Treatment of Non-Functional Requirements," 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. 493-494.
  4. [Cai, et al. 2007].
    Cai, G., et al.
    , "
    Integrating software requirements analysis and safety control approach," International Multi-Conference of Engineers and Computer Scientists, 2007, pp. 1127-1131.
  5. [Cairns 1975]
    Cairns, G., "Meeting Software Requirements," Computing Weekly, 18, 449 (June 1975).
  6. [Calisaya, et al. 2008].
    Calisaya, E., et al., "Automatic Discovery of Interactions Between Software Requirements," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2008.
  7. [Callele, et al. 2005].
    Callele, D., et al., "Requirements Engineering and the Creative Process in the Videogame Industry," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005., pp. 240-252.
  8. [Callele, et al. 2006].
    Callele, D.,
    et al., "Emotional Requirements in Video Games," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  9. [Callele and Makaroff 2006].
    Callele, D., and D. Makaroff, "
    Teaching requirements engineering to an unsuspecting audience," ACM SIGCSE Bulletin, 38, 1, (January 2006), pp. 433-437. 
  10. [Campbell, et al. 2002]
    Campbell, L., et al., "Automatically Detecting and Visualising Errors in UML Diagrams," Requirements Engineering, 7, 4 (2002), pp. 264-287.
  11. [Canning 1977]
    Canning, R., "Getting the Requirements Right," EDP Analyst, 15, 7 (July 1977), pp. 1-14.
  12. [Cao and Ramesh 2008].
    Cao, L., and B. Ramesh, "Agile Requirements Engineering Practices: An Empirical Study," IEEE Congress on Services, Los Alamitos, California: IEEE Computer Society Press, 2008.
  13. [Cao, et al. 2008].
    Cao, L., et al., "Modeling and refining the service-oriented requirement," International Symposium on Theoretical Aspects of Software Engineering (TASE), Los Alamitos, California: IEEE Computer Society Press, 2008.
  14. [Cappelli, et al. 2007].
    Cappelli, C., et al., "Exploring Business Process Transparency Concepts,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  15. [Caralt and Kim 2007].
    Caralt, J., and J. Kim, "Ontology Driven Requirements Query," Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 2007.
  16. [Cardei, et al. 2007]
    Cardei, I., et al., "Framework for requirements-driven system design automation,"
    IEEE Systems Conference, Los Alamitos, California: IEEE Computer Society Press, 2007.
  17. [Carew, et al. 2005]
    Carew, D., et al., "An empirical investigation of the comprehensibility of requirements specifications,"
    IEEE International Symposium on Empirical Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 247-256.
  18. [Carl and Hofmeister 2004].
    Carl, J., and J. Hofmeister, "Object-Oriented and Structured Analyses Are Homeomorphic," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  19. [Carl 2005].
    Carl, J., "Why Are Requirements So Hard to Get Right?," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
  20. [Carli, et al. 2008]
    de Carli, A., et al., "Requirements documentation of a controlled complex motion system," International Conference on Advanced Motion Control, Los Alamitos, California: IEEE Computer Society Press, 2008.
  21. [Carlshamre and Karlsson 1996].
    Carlshamre, P., and J. Karlsson, "A Utility-Oriented Approach to Requirements Engineering," Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 145-152.
  22. [Carlshamre and Regnell 2000].
    Carlshamre, P., and B. Regnell, "Requirements Lifecycle Management and Release Planning in Market-Driven Requirements Engineering Processes," Eleventh IEEE International Workshop on Database and Expert Systems Applications, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 961-965.
  23. [Carlshamre, et al. 2001].
    Carlshamre, P., et al., "An Industrial Survey of Requirements Interdependencies in Software Product Release Planning," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 84-91.
  24. [Carlshamre 2002].
    Carlshamre, P., "Release Planning in Market-Driven Software Product Development: Provoking an Understanding," Requirements Engineering Journal, 7, 3 (May 2002), pp. 139-151.
  25. [Carmel, et al. 1990].
    Carmel, E., et al., "Automating user requirements elicitation," International Workshop on Computer-Aided Software Engineering, Los Alamitos, California; IEEE Computer Society Press, 1990, pp. 304-305.
  26. [Carmichael, et al. 2007].
    Carmichael, A., et al., "The efficacy of narrative video for raising awareness in ICT designers about older users' requirements," Interacting with Computers, 19, 5-6 (December 2007), pp. 587-596.
  27. [Carod and Cechich 2007].
    Carod, N., and A. Cechich, "A Cognitive Psychology Approach for Balancing Elicitation Goals," International Conference on Cognitive Informatics, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 232-241.
  28. [Carr 2000].
    Carr, J., "Requirements engineering and management: the key to designing quality complex systems," The TQM Magazine, 12, 6 (2000), pp. 304-305.
  29. [Carroll and Swatman 1998].
    Carroll, J., and P. Swatman, " The Process of Deriving Requirements: Learning from Practice," Ninth Annual Australasian Conference on Information Systems, Sydney, Australia, 1998.
  30. [Carroll, et al. 1998].
    Carroll, J., et al., "Requirements Development in Scenario-Based Design," IEEE Transactions on Software Engineering, 24, 12 (December 1998), pp. 1156-1170.
  31. [Carroll and Swatman 1999].
    Carroll, J., and P. Swatman, "Managing the RE Process: Lessons from Commercial Practice," Fifth International Workshop on Requirements Engineering: Foundations for Software Quality, Heidelberg, Germany, June 1999.
  32. [Carroll, et al. 2003].
    Carroll, J., et al., "A User-centred Process for Determining Requirements for Mobile Technologies: the TramMate Project," Asia-Pacific Software Engineering Conference (APSEC), Los Alamitos, California: IEEE Computer Society Press, 2003.
  33. [Carson 1995].
    Carson, R., "A Set Theory Model for Anomaly Handling in System Requirements Analysis," Fifth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
  34. [Carson 1996].
    Carson, R., "Designing For Failure: Anomaly Identification and Treatment in System Requirements Analysis," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  35. [Carson 1998].
    Carson, R., "Requirements Completeness: A Deterministic Approach," Eighth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1998.
  36. [Carson 1999].
    Carson, R., "Fuzzy Sets as Requirements Antecedents," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1999.
  37. [Carson 2000].
    Carson, R., "Fuzzy Sets as Requirements Antecedents," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2000.
  38. [Carson 2001].
    Carson, R., "Keeping the Focus During Requirements Analysis," Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2001.
  39. [Carson 2004].
    Carson, R., "Integrating Failure Modes and Effects with the System Requirements Analysis," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  40. [Carson, et al. 2004].
    Carson, R., et al., "Requirements Completeness," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  41. [Carter and Hendershot 1995].
    Carter, R., and J. Hendershot, "Spacecraft Performance Requirements: Tracking and Verification for the Tropical Rainforest Measuring Mission," Fifth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
  42. [Carter and Jones 2000].
    Carter, J., and W. Jones, "A Requirements Analysis for Information Systems to Support Decision Making in a Managed Care Environment," Journal of Systems Integration, 10, 1 (November 2000), pp. 67-79.
  43. [Carter, et al. 2001].
    Carter, R., et al., "Evolving Beyond Requirements Creep: A Risk-Based Evolutionary Prototyping Model," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 94-101.
  44. [Carter, et al. 2006].
    Carter, J., et al., "Transforming Usability Engineering Requirements into Software Engineering Specifications: From PUF to UML," in Human-Centered Software Engineering - Integrating Usability in the Software Development Lifecycle, Berlin: Springer, 2006.
  45. [Carvallo, et al. 2004].
    Carvallo, J., et al., "QM: A Tool for Building Software Quality Models," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 358-359.
  46. [Carvallo, et al.2005].
    Carvallo, J., et al.,
    "A Quality Model for Requirements Management Tools," in Requirements Engineering for Sociotechnical Systems, J. Maté, and A. Silva, eds., Hershey, Pennsylvania: Information Science Publishing, 2005, pp. 119-137.
  47. [Carvallo, et al. 2006].
    Carvallo, J., et al., "Managing Non-Technical Requirements in COTS Components Selection (Short Paper)," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  48. [Carvallo, et al. 2008].
    Carvallo, J., et al., "Requirements engineering for COTS-based software systems," Symposium on Applied Computing, New York: ACM Press, 2008, pp. 638-644.
  49. [Carver, et al.1990].
    Carver, D
    ., et al., "Object-based measurement in the requirements specification phase," Empirical Foundations of Information and Software Science, New York: Plenum Press, 1990, pp. 369-377.
  50. [Carver, et al. 2006].
    Carver, J., et al., "Finding and fixing problems early: A perspective-based approach to requirements and design inspections," Crosstalk, (2006).
  51. [Carver, et al. 2008].
    Carver, J., et al., "The Impact of Educational Background on the Effectiveness of Requirements Inspections: An Empirical Study," IEEE Transactions on Software Engineering, 34 (2008). 
  52. [Casey 1981]
    Casey, B., "The Impact of the Technical Communicator on Software Requirements," Journal of Technical Writing and Communication, 11, 4 (1981), pp. 361-372.
  53. [Casey and Taylor 1981]
    Casey, B., and B. Taylor, "Writing Requirements in English: A Natural Alternative," IEEE Software Engineering Standards Workshop, Los Alamitos, California: IEEE Computer Society Press, January 1981, pp. 95-101. 
  54. [Casey and Brugha 2005]
    Casey, D., and C. Brugha, "From fighting fires to building bridges: the role of metaphor in systems requirements," IEEE Professional Communication Conference, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 813-838. 
  55. [Cashman 1989].
    Cashman, M., "Object-Oriented Domain Analysis," ACM Software Engineering Notes, 14, 6 (October 1989), p. 67. 
  56. [Caspi and Halbwachs 1986].
    Caspi, P., and N. Halbwachs, "A Functional Model for Describing and Reasoning About Time Behavior of Computing Systems," Acta Informatica, 22, 6 (March 1986), pp. 596-627.
  57. [Castano and De Antonellis 1993].
    Castano, S., and V. De Antonellis, "Reuse of Conceptual Requirements Specification," International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 121-124.
  58. [Castano and De Antonellis 1994].
    Castano, S., and V. De Antonellis, "The F 3 Reuse Environment for Requirements Engineering," ACM Software Engineering Notes, 19, 3 (July 1994), pp. 62-65.
  59. [Castano et al. 1994].
    Castano, S., et al., "Reusability Based Comparison of Requirements Specification Methodologies," IFIP Conference on Methods and Associated Tools for the Information Systems Life Cycle, Amsterdam, The Netherlands: North-Holland, September 1994.
  60. [Castel and Hernandez 1998].
    Castel, N., and A. Hernandez, "The Software Requirements Modeling in SAREL," Fourth International Workshop on Requirements Engineering: Foundations for Software Quality, Pisa, Italy, June 1998.
  61. [Castro 1995].
    Castro, J., "The Process of Requirements Formalisation: The Formlab Project," International Symposium on Systems Research, Informatics and Cybernetics, 1995.
  62. [Castro, et al. 1996].
    Castro, J., et al., "Multi-view: An Environment for Requirements Elicitation and Formalisation," International Conference on Information Systems, Analysis and Synthesis, 1996.
  63. [Castro et al. 1999].
    Castro, J., et al., "Developing Agent-Oriented Information Systems for the Enterprise,” 2nd IEEE International Conference on Enterprise Information Systems, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 78-87.
  64. [Castro et al. 2000].
    Castro, J., et al.,  "
    Closing the Gap between Organizational Requirements and Object Oriented Modeling," Journal of the Brazilian Computer Society, 7, 1 (2000).
  65. [Castro and Kramer 2001].
    Castro, J., and J. Kramer, "From Software Requirements to Architectures," Twenty-third International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 764ff.
  66. [Castro, et al. 2001]
    Castro, J., et al., "A Requirements-Driven Development Methodology," 13th International Conference on Advanced Information Systems Engineering (CAISE-01), Lecture Notes in Computer Science, Volume 2068, Berlin: Springer, 2001, pp. 108ff.
  67. [Castro, et al. 2003].
    Castro, J., et al., "Agent-Driven Requirements Engineering," in Perspectives on Software Requirements, Leite, J., and J. Doorn, eds., Berlin: Springer, 2003.
  68. [Castro, et al. 2003a].
    Castro, J., et al., "Requirements Traceability in Agent Oriented Development," Lecture Notes in Computer Science, Volume 2603, Berlin: Springer, 2003, pp. 57-72.
  69. [Castro, et al. 2008].
    Castro
    , J., et al., "Integrating the Personas Technique into the Requirements Analysis Activity," Mexican International Conference on Computer Science, Los Alamitos, California: IEEE Computer Society Press, 2008.
  70. [Castro-Herrera, et al. 2008].
    Castro-Herrera, C., et al., "Using Data Mining and Recommender Systems to Facilitate Large-Scale, Open, and Inclusive Requirements Elicitation Processes," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2008.
  71. [Cataldo, et al. 2006].
    Cataldo, M., et al.
    ,
    "Identification of Coordination Requirements: Implications for the Design of Collaboration and Awareness Tools," Conference on Group Decision and Negotiation, New York: ACM Press, 2006, pp. 353-362.
  72. [Catanio 2007].
    Catanio, J.
    ,
    "Requirements Analysis: A Review," in Advances in Systems, Computing Sciences, and Software Engineering, Berlin: Springer, 2007, pp. 411-418.
  73. [Catledge and Potts 1996].
    Catledge, L., and C. Potts, "Collaboration During Conceptual Design," ( see abstract) Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 182-189.
  74. [Catrava 2003].
    Catrava, S.,  "Testing with Partial Traced Requirements: a Necessary Step Towards Higher Quality System Level Verification,"
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 303.
  75. [Caulfield and Power 2006].
    Caulfield, I., and N. Power, "Domain focused requirements engineering: A case study of successful requirements engineering in a market-oriented automotive software development company," Australian Workshop on Requirements Engineering, 2006.
  76. [Cavaye 1995].
    Cavaye, A., "User Participation in System Development Revisited," Information and Management, 28 (1995), pp. 311-323.
  77. [Cazzola, et al. 2000].
    Cazzola, W., et al., "
    Shifting Up Reflection from the Implementation to the Analysis Leve," Lecture Notes in Computer Science 1826, Berlin: Springer, 2000, pp. 1ff.
  78. [Cebulla 2004].
    Cebulla, M., "Modeling Concepts for Safety-Related Requirements in Sociotechnical Systems," Lecture Notes in Computer Science, Volume 3219, Berlin: Springer, 2004, pp. 87ff. 
  79. [Cechik, et al. 2007].
    Cechik, M., et al., "Matching and Merging of Statechart Specifications," IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  80. [Celko, et al. 1983].
    Celko, J., et al., "A Demonstration of Three Requirements Language Systems," ACM SIGPLAN Notices, 18, 1 (January 1983), pp. 9-14.
  81. [Cerbah and Euzenat 2001].
    Cerbah, F., and J. Euzenat, "Using Terminology Extraction to Improve Traceability from Formal Models to Textual Requirements," Lecture Notes in Computer Science, Volume 1959, Berlin: Springer, 2001, pp. 115ff. 
  82. [Ceri 1986].
    Ceri, S., "Requirements Collection and Analysis in Information Systems Design," IFIP World Computer Conference '86, Amsterdam, The Netherlands: North-Holland, 1986, pp. 205-214.
  83. [Ceron, et al. 2005].
    Ceron, R., et al.,, "A Metamodel for Requirements Engineering in System Family Context for Software Process Improvement Using CMMI," International Conference on Product-Focused Software Process Improvement, Lecture Notes in Computer Science 3547, Berlin: Springer, 2005, pp. 173-188.
  84. [Cerri, et al. 1998].
    Cerri, S., et al., "The Extension of an Actor Language from Domain-Specific Requirements," International Conference on Intelligent Tutoring Systems, Lecture Notes in Computer Science 1452, Berlin: Springer, 1998, pp. 604ff.
  85. [Cerri, et al. 2008].
    Cerri, S., et al., "The Extension of an Actor Language from Domain-Specific Requirements," International Conference on Intelligent Tutoring Systems, Berlin: Springer, 2008.
  86. [Cerveny, et al. 1986].
    Cerveny, R., et al., "The Application of Prototyping to Systems Development: A Rationale and Model," Journal of Management of Information Systems, 3, 2 (1986).
  87. [Cesare, et al., 2003].
    de Cesare, S., et al., "Actor Perception in Business Use Case Modeling," (see abstract) Communications of the AIS, 12, 15 (September 2003).
  88. [Chafin 1980].
    Chafin, R., "The Systems Analyst and Software Requirements Specification," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1980, pp. 254-258. 
  89. [Chaim, et al. 2003].
    Chaim, M., "A Debugging Strategy Based on Requirements of Testing," (see abstract) 7th IEEE European Conference on Software Maintenance and Reengineering, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 160-169.
  90. [Chakrabarti, et al. 2004].
    Chakrabarti, A., et al., "Identification and Application of Requirements and Their Impact on the Design Process: A Protocol Study," Research in Engineering Design, 15, 1 (2004), pp. 22-39.
  91. [Chalin, et al. 2008].
    Chalin, P., et al., "Capturing business transaction requirements in use case models," Symposium on Applied Computing, New York: ACM Press, 2008, pp. 602-606.
  92. [Chambers and Manos 1992].
    Chambers, G., and K. Manos, "Requirements: Their Origin, Format and Control," Second Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, July 1992.
  93. [Champion 1991].
    Champion, R., Modeling for Requirements Engineering Using Conceptual Graphs, UMIST Ph.D. Dissertation, UK, May 1991.
  94. [Champion and Moores 1996].
    Champion, R., and T. Moores, "Exploiting an Enterprise Model During Systems' Requirements Capture and Analysis," ( see abstract) Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 208-215.
  95. [Chance and Melhart 1999].
    Chance, B., and B. Melhart, "A Taxonomy for Scenario Use in Requirements Elicitation and Analysis of Software Systems," (see abstract) IEEE Conference and Workshop on Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 232-238.

    Chandrasekharan, M.,  see also Shekaran, C.
     
  96. [Chandrasekharan, et al. 1985].
    Chandrasekharan, M., et al., "Requirements-Based Testing of Real-Time Systems: Modeling for Testability," IEEE Computer, 18, 4 (April 1985), pp. 71-80.
  97. [Chandrasekar, et al. 1985].
    Chandrasekar, N., et al., "Challenges in requirements engineering for a platform group: case study with a medical imaging platform," Fourth International Conference on Software Engineering Research, Management and Applications, Los Alamitos, California: IEEE Computer Society Press, 2006. 
  98. [Chang, et al. 1989].
    Chang, C., et al., "Integral: Petri-Net Approach to Distributed Software Development," (see abstract) Information and Software Technology, 31, 10 (December 1989), pp. 535-545.
  99. [Chang, et al. 2008].
    Chang, C.-H., et al., "Improving Software Integration from Requirement Process with a Model-Based Object-Oriented Approach," International Conference on Secure System Integration and Reliability Improvement, Los Alamitos, California: IEEE Computer Society Press, 2008. 
  100. [Chantatub and Holcombe 1994].
    Chantatub, W., and M. Holcombe, "Software testing strategies for software requirements and design," EuroSTAR, 1994.
  101. [Chantree, et al. 2006].
    Chantree, F., et al., "Identifying Nocuous Ambiguities in Natural Language Requirements," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  102. [Chao, et al. 2006].
    Chao, B., et al., "Reliability Management in Software Requirement Analysis," IEEE International Conference on Management of Innovation in Technology, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 1104-1107.
  103. [Chapin 1979].
    Chapin, N., "Some Structured Analysis Techniques," Database, 10, 3 (March 1979), pp. 16-23.
  104. [Chardon and Dorfman 2003].
    Chardon, R., and M. Dorfman,  "One Approach to the Metric Baselining Imperative for Requirements Processes,"
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 292.
  105. [Charette 1986].
    Charette, R., Software Engineering Environments, New York: McGraw Hill, 1986, Chapters 3-4.
  106. [Chastek and Donohoe 2004].
    Chastek, G., and P. Donohoe, "
    Product Line Analysis," Lecture Notes in Computer Science 3154, Berlin: Springer, 2004, pp. 310ff.
  107. [Chatzoglou 1997].
    Chatzoglou, P., "Factors Affecting Completion of the Requirements Capture Stage of Projects with Different Characteristics," Information and Software Technology, 39 (September 1997), pp. 627-640.
  108. [Chatzoglou and Macaulay 1996].
    Chatzoglou, P., and L. Macaulay, "Requirements Capture and Analysis: A Survey of Current Practice," (see abstractRequirements Engineering Journal, 1, 2 (1996), pp. 75-87.
  109. [Chatzoglou and Macaulay 1997].
    Chatzoglou, P., and L. Macaulay, "The Importance of Human Factors in Planning the Requirements Capture Stage of a Project," International Journal of Project Management, 15, 1 (February 1997), pp. 39-53.
  110. [Chatzoglou and Soteriou 1999].
    Chatzoglou, P., and A. Soteriou, "A DEA Framework to Assess the Efficiency of the Software Requirements Capture and Analysis Process," (see abstract) Decision Sciences, 30, 2 (Spring 1999), pp. 503-531.
  111. [Chechik and Gannon 1994].
    Chechik, M., and J. Gannon, "Automated Verification of Requirements Implementation," ACM Software Engineering Notes, Proceedings of the International Symposium on Software Testing and Analysis, Special Issue (October 1994), pp. 1-15.
  112. [Chechik and Gannon 2001].
    Chechik, M., and J. Gannon, "Automated Analysis of Consistency Between Requirements and Design," IEEE Transactions on Software Engineering, 27, 7 (July 2001), pp. 651-672.
  113. [Chen 1977].
    Chen, P., "The Entity Relationship Model: Toward a Unifying View of Data," ACM Transactions on  Database Systems, 1, 1 (March 1977), pp. 9-36.
  114. [Chen and Chou 1988].
    Chen, P., and C. Chou, "A Requirements Model in a Knowledge-Based Rapid Prototyping System," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1988, pp. 418-426. 
  115. [Chen 1990].
    Chen. P., "Entity-Relationship Approach to Data Modeling," in System and Software Requirements Engineering, R. Thayer and M. Dorfman, eds., Los Alamitos, California: IEEE Computer Society Press, 1990, pp. 238-243.
  116. [Chen, et al. 1992].
    Chen, D., et al., "Requirements Organization Approach for Object-Based Construction of Software Systems," Information and Software Technology, 34 (July 1992), pp. 485-493.
  117. [Chen 1999].
    Chen, P., Conceptual Modeling: Current Issues and Future Directions, Berlin: Springer Verlag, 1999.
  118. [Chen and Chou 2001].
    Chen, S., and J. Chou, "An Object-Oriented Analysis Technique Based on the Unified Modeling Language," Journal of Object-Oriented Programming, (2001).
  119. [Chen, et al. 2002].
    Chen, K., et al., "Visual Requirement Representation," (see abstract) Journal of Systems and Software, 61, 2 (March 2002), pp. 129-143.
  120. [Chen, et al. 2002a].
    Chen, X., et al., "
    Requirements Specification and Architecture Design for Internet-Based Control Systems," 26th Annual International Conference on Computer Software and Applications, Los Alamitos, California: IEEE Computer Society Press, 2002, pp. 75-80.
  121. [Chen, et al. 2005].
    Chen, K., et al., "An Approach to Constructing Feature Models Based on Requirements Clustering," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 31-40.
  122. [Chen and Sacket 2005].
    Chen, Y., and P. Sacket, "A Requirements Management System for Maintenance Service Industry," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
  123. [Chen, et al. 2006].
    Chen, K., et al., "Identification of Crosscutting Requirements Based on Feature Dependency Analysis (Short Paper)," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  124. [Chen, et al. 2007].
    Chen, X., et al., "Separation of Concerns and Consistent Integration in Requirements Modelling," Conference on Current Trends in Theory and Practice of Computer Science, Berlin: Springer, 2007.
  125. [Cheng, et al 1982].
    Cheng, L., et al., "Simulation of an I/O-Driven Requirements Language," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1982, pp. 138-143. 
  126. [Cheng and Weiss 2000].
    Cheng, B., and D. Weiss, "Requirements Engineering: Integrating Technology," IEEE Software, 17, 3 (May/June 2000), pp. 18-20.
  127. [Cheng and Atlee 2007].
    Cheng, B., and J. Atlee, "Research Directions in Requirements Engineering," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  128. [Cheng, et al., 2007].
    Cheng, B., et al., "
    An Adaptive User Requirements Elicitation Framework," 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. 487-492.
  129. [Cheng and Liu 2008].
    Cheng, J., and Q. Liu, "Using Stakeholder Analysis for Improving Statechart Merging in Software Requirement Management," International Conference on Young Computer Scientists, Los Alamitos, California: IEEE Computer Society Press, 2008.
  130. [Cherli, et al. 2003].
    Cherli, S., et al., "Conceptual Modeling Quality - From EER to UML Schemas Evaluation," International Conference on Conceptual Modeling, Berlin: Springer, 2003.
  131. [Cherry 1993].
    Cherry, G., "Class/Object Stimulus-Response Machines," ACM Software Engineering Notes, 18, 2 (April 1993), pp. 86-95.
  132. [Cherry and Macredie 1999].
    Cherry, C., and R. Macredie, "
    The Importance of Context in Information System Design: An Assessment of Participatory Design," Requirements Engineering, 4, 2 (July 1999), pp. 103-114.
  133. [Chevallier and Marshall 1997].
    Chevallier, J., and R. Marshall, "How to Properly Specify and Control Essential Project Data," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1997.
  134. [Chevallier and Marshall 2004].
    Chevallier, J., and R. Marshall, "SpecRight: Writing Correctly Requirements, Produce Product Specifications and Requirement Justification File," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  135. [Chevlin and Jorgens 1996].
    Chevlin, D., and J. Jorgens, "Software Requirements: Definition and Specification," Biomedical Instrumentation & Technology / Association for the Advancement of Medical Instrumentation, 30, 2 (March - April 1996), pp. 150-152.
  136. [Chidambaram 1999].
    Chidambaram, L., "Knowledge Transfer in Conceptual Modeling by End Users," Journal of End-User Computing, 11, 1 (January-March 1999), pp. 40-51.
  137. [Chin, et al. 1997].
    Chin, G., et al., "Participatory Analysis: Shared Development of Requirements from Scenarios," Computer-Human Interaction Conference (CHI), 1997.
  138. [Chin 2003].
    Chin, G., Agile Project Management: How to Succeed in the Face of Changing Project Requirements , New York: AMACOM, 2003.
  139. [Chirinos, et al. 2004].
    Chirinos, L., et al., "Identifying Quality-Based Requirements," Information Systems Management, 21, 1 (Winter 2004), pp. 15-26.
  140. [Chisan and Damian 2005].
    Chisan, J., and D. Damian, "Exploring the role of requirements engineering in improving risk management," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 481-482.
  141. [Chitchyan, et al. 2005].
    Chitchyan, R., et al., "CoCA: A Composition-Centric Approach to Requirements Engineering," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 475-476.
  142. [Chitchyan 2007].
    Chitchyan, R., et al., "Semantics-based composition for aspect-oriented requirements engineering," Conference on Aspect-Oriented Software Development, New York: ACM Press, 2007.
  143. [Chitchyan, et al. 2007a].
    Chitchyan, R., et al., "Compass: Composition-Centric Mapping of Aspectual Requirements to Architecture," Transactions on Aspect-Oriented Software Development, Berlin: Springer, 2007, pp. 3-53.
  144. [Chittimalli and Harrold 2008].
    Chittimalli, P., and M. Harrold, "Regression test selection on system requirements," India software engineering conference, New York: ACM Press, 2008, pp. 87-96.
  145. [Choi, et al. 1997].
    Choi, E., et al., "An Information and Telecommunication System Development Methodology -- Requirement Analysis Phase," International Conference on Systems, Man, and Cybernetics, Volume 3, Los Alamitos, California: IEEE Computer Society Press, 1997, pp. 2336-2340.
  146. [Choi, et al. 2002]
    Choi, Y., et al., "Toward Automation for Model-Checking Requirements Specifications with Numeric Constraints," (see abstract) Requirements Engineering, 7, 4 (2002), pp. 225-242.
  147. [Choi and Heimdahl 2003].
    Choi, Y., and M. Heimdahl, "
    Model Checking Software Requirement Specifications using Domain Reduction Abstraction," Eighteenth IEEE International Conference on Automated Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 314-317.
  148. [Choi, et al. 2004].
    Choi, Y., et al., "System Requirement Development Process From Operational Concept and the Application Case-Study of ATACMS," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  149. [Choi, et al. 2005].
    Choi, S.-S., et al., "SRS-Tool: A Security Functional Requirements Specification Development Tool for Application Information System of Organization," International Conference on Computational Science and Its Applications (ICCSA), Lecture Notes in Computer Science, Volume 3481, Berlin: Springer, 2005, pp. 458-467. 
  150. [Choi, et al. 2006].
    Choi, S., et al., "Function point extraction method from goal and scenario based requirements text," International Conference on Applications of Natural Language to Information Systems, Lecture Notes in Computer Science 3999, Berlin: Springer, 2006, pp. 12-24.
  151. [Choi 2007].
    Choi, J., "Context-Driven Requirements Analysis," International Conference on Computational Science and Its Applications (ICCSA), Berlin: Springer, 2007.
  152. [Cholvy and Hunter 2003].
    Cholvy, L., and A. Hunter, "Merging Requirements from a Set of Ranked Agents," Knowledge Based Systems, 16, 2 (March 2003), pp. 113-127.
  153. [Choppy and Reggio 2000].
    Choppy, C., and G. Reggio, "Using CASL to Specify the Requirements and the Design: A Problem Specific Approach," in Recent Trends in Algebraic Development Techniques, Lecture Notes in Computer Science 1827, Berlin: Springer, 2000, pp. 106-126.
  154. [Choppy and Reggio 2004].
    Choppy, C., and G. Reggio, "Improving Use-Case Based Requirements Using 'Formally Grounded' Specifications," Lecture Notes in Computer Science, Volume 2984, Berlin: Springer, 2004, pp. 244-260. 
  155. [Choppy 2006].
    Choppy, C., "Requirements capture and specification for enterprise applications: a UML based attempt," Australian Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2006. 
  156. [Chou and Chung 1994].
    Chou, S., and S. Chung, "An OOA Model With System Function Specifications," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 16-23.
  157. [Chou, et al. 2004].
    Chou, L., "Requirements Analysis and Implementation of Palm-Based Multimedia Museum Guide Systems," Eighteenth International Conference on Advanced Information Networks and Applications, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 352-357.
  158. [Chow 1977].
    Chow, T., "Testing Software Design Modeled by Finite State Machines," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1977, pp. 178-187. 
  159. [Chow and Heung 1996].
    Chow, P., and D. Heung, "Behavioural modelling in object-oriented methodology," Information and Software Technology (1996).
  160. [Christel and Kang 1992].
    Christel, M., and K. Kang, Issues in Requirements Elicitation, Technical Report CMU/SEI-92-TR-012, Software Engineering Institute, Pittsburgh, Pennsylvania, 1992.
  161. [Christensen and Thayer 2001].
    Christensen, M., and R. Thayer, The Project Manager's Guide to Software Engineering's Best Practices, Los Alamitos, California: IEEE Computer Society Press, 2001, Chapter 3.
  162. [Chudge and Fulton 1994].
    Chudge, J., and D. Fulton, "Trust and Cooperation in System Development: Applying Responsibility Modeling to the Problem of Changing Requirements," Conference on Requirements Elicitation for Software-Based Systems, July 1994; also appears in Software Engineering Journal, 11, 3 (May 1996), pp. 193-204.
  163. [Chung, et al. 1991].
    Chung, L., et al., "From Information Systems Requirements to Design: A Mapping Framework," Information Systems, 16, 4 (April 1991), pp. 429-461.
  164. [Chung 1991a].
    Chung, L., "Representation and Utilization of Nonfunctional Requirements for Information System Design," Third International Conference on Advanced Information Systems Engineering (CAiSE '90), Springer-Verlag, 1991, pp. 5-30.
  165. [Chung 1993].
    Chung, L., "Dealing with Security Requirements During the Development of Information Systems" Fifth Conference on Advanced Information Systems Engineering, Paris, France, June 1993.
  166. [Chung 1993a].
    Chung, L., Representing and Using Non-Functional Requirements: A Process-Oriented Approach, Department of Computer Science Ph.D. Thesis, Toronto, Canada: University of Toronto, June 1993.
  167. [Chung and Nixon 1995].
    Chung, L., and B. Nixon, "Dealing with Non-Functional Requirements: Three Experimental Studies of a Process-Oriented Approach," Seventeenth IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
  168. [Chung, et al. 1995].
    Chung, L., et al., "Using Non-Functional Requirements to Systematically Support Change," Second International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
  169. [Chung, et al. 1996].
    Chung, L., et al., "Dealing with Change: An Approach Using Non-Functional Requirements," (see abstract) Requirements Engineering Journal, 1, 3 (1996), pp. 238-260.
  170. [Chung, et al. 2000].
    Chung, L., et al., Non-Functional Requirements in Software Engineering, Norwell, Massachusetts: Kluwer Press, 2000.
  171. [Chung and Cooper 2002].
    Chung, L., and K. Cooper, "A Knowledge-Based COTS-Aware Requirements Engineering Approach," ( see abstract) International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2002, pp. 175-182.
  172. [Chung and Cooper2002a].
    Chung, L., and K. Cooper, "Defining System Agents in a COTS-Aware Requirements Engineering Approach," Australian Workshop on Requirements Engineering, 2002
    .
  173. [Chung and Cooper 2004].
    Chung, L., and K. Cooper, "Defining goals in a COTS-aware requirements engineering approach," Systems Engineering, 7, 1 (December 2004), pp. 61-83.
  174. [Chung, et al. 2006].
    Chung, L., et al., "Requirements elicitation through model-driven evaluation of software components," Fifth International Conference on Commercial-off-the-Shelf (COTS)-Based Software Systems, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 187-196.
  175. [Chung and Sapakkul 2006].
    Chung, L., and S. Sapakkul, "
    Capturing and Reusing Functional and Non-Functional Requirements Knowledge," IEEE International Conference on Information Reuse and Integration, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 539-544.
  176. [Church 1963].
    Church, F., "Requirements Generation, Explosions, and Bills of Materials," IBM Systems Journal, 2 (1963), pp. 268-287.
  177. [Churcher 2007].
    Churcher, C., "Chapter 3: Initial Requirements and Use Cases," In Beginning Database Design, Apress, 2007.
  178. [Chutimaskul 2003].
    Chutimaskul, W., "e-Government Requirements Elicitation," Lecture Notes in Computer Science, Volume 2739, Berlin: Springer, 2003, pp. 496-499. 
  179. [Ciaccia, et al. 1995a].
    Ciaccia, P., et al., "From Formal Requirements to Formal Design," Seventh International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, June 1995, pp. 23-30.
  180. [Ciancarini, et al. 1997].
    Ciancarini, P., et al., "Engineering Formal Requirements: An Analysis and Testing Method for Z Documents," (see abstract) Annals of Software Engineering, 3, N. Mead, ed., 1997.
  181. [Cioch 1988].
    Cioch, F., "Requirements specification understanding and misinterpretation," Northwest Software Quality Assurance Conference, Portland, OR: Lawrence & Craig, 1988, pp. 333-342. 
  182. [Clapp 1987].
    Clapp, J., "Rapid Prototyping for Risk Management," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1987, pp. 17-22. 
  183. [Clark and Moreira 1999].
    Clark, R., and A. Moreira, "Formal Specification of User Requirements," Automated Software Engineering, 6, 3 (July 1999), pp. 217-232.
  184. [Classen, et al. 2008].
    Classen, A., et al., "What's in a feature: A requirements engineering perspective," International Conference on Fundamental Approaches to Software Engineering (FASE), New York: ACM Press, 2008. 
  185. [Claus, et al. 1999].
    Claus, C., et al., "Implementing Systematic Requirements Management in a Large Software Programme," Fifth International Workshop on Requirements Engineering: Foundations for Software Quality, Heidelberg, Germany, June 1999.
  186. [Clavadetscher 1998].
    Clavadetscher, C., "User Involvement Key to Success," IEEE Software, 15, 2 (March 1998), pp. 30, 32.
  187. [Cleland-Huang, et al. 2001].
    Cleland-Huang, J., et al., "Requirement-Based Dynamic Metrics in Object-Oriented Systems," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 212-219.
  188. [Cleland-Huang, et al. 2002].
    Cleland-Huang, J., et al., "Automating Speculative Queries through Event-Based Requirements Traceability," ( see abstract) Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  189. [Cleland-Huang, et al. 2003].
    Cleland-Huang, J.
    , et al., "Event-Based Traceability for Managing Evolutionary Change," (see abstract) IEEE Transactions on Software Engineering, 29, 9 (September 2003), pp. 796-810. 
  190. [Cleland-Huang, et al. 2004].
    Cleland-Huang, J., et al., "A Heterogeneous Solution for Improving the Return on Investment of Requirements Traceability," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 230-239.
  191. [Cleland-Huang 2005].
    Cleland-Huang, J., et al., "Toward improved traceability of non-functional requirements," International workshop on Traceability in emerging forms of software engineering, New York: ACM Press, 2005, pp. 14-19.
  192. [Cleland-Huang, et al. 2005].
    Cleland-Huang, J., et al., "Utilizing Supporting Evidence to Improve Dynamic Requirements Traceability," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 135-144.
  193. [Cleland-Huang, et al. 2005a].
    Cleland-Huang, J., et al., "Goal-Centric Traceability for Managing Non-Functional Requirements," IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 362-371.
  194. [Cleland-Huang 2006].
    Cleland-Huang, J., "Just Enough Requirements Traceability," IEEE International Conference on Computer Software and Applications (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 41-42.
  195. [Cleland-Huang, et al. 2006].
    Cleland-Huang, J., et al., "The Detection and Classification of Non-Functional Requirements with Application to Early Aspects,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  196. [Cleland-Huang 2007].
    Cleland-Huang, J., "Quality Requirements and their Role in Successful Products,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  197. [Cleland-Huang, et al. 2007]
    Cleland-Huang, J., et al., "Automated classification of non-functional requirements," Requirements Engineering, 12, 2 (April 2007), pp. 103-120.
  198. [Cleland-Huang and Mobashi 2008].
    Cleland-Huang, J., and B. Mobashi, "Using Data Mining and Recommender Systems to Scale Up the Requirements Processes,"
    IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2008.
  199. [Cleland-Huang, et al. 2008].
    Cleland-Huang, J., et al., "Goal-Centric Traceability: Using Virtual Plumblines to Maintain Critical Systemic Qualities," IEEE Transactions on Software Engineering, 34 (2008).
  200. [Clements, et al. 1993].
    Clements, J., et al., "MT: A Toolset for Specifying and Analyzing Real-Time Systems," IEEE Real Time Systems Symposium, Los Alamitos, California: IEEE Computer Society Press,
    1993, pp. 12-22. 
  201. [Clymer and Perdue 1974].
    Clymer, R., and J. Perdue, "A top down analysis technique for parallel systems,"  2nd Symposium on Simulation of Computer Systems, Los Alamitos, California: IEEE Computer Society Press,
    1974. 
  202. [Coad and Yourdon 1990].
    Coad, P., and E. Yourdon, "Object-Oriented Analysis," in System and Software Requirements Engineering, R. Thayer and M. Dorfman, eds., Los Alamitos, California: IEEE Computer Society Press, 1990, pp. 272-289.
  203. [Coad and Yourdon 1991].
    Coad, P., and E. Yourdon, Object-Oriented Analysis, Upper Saddle River, New Jersey: Prentice Hall, 1991.
  204. [Coakes and Coakes 2000].
    Coakes, J., and E. Coakes, "Specifications in Context: Stakeholders, Systems, and Modeling of Conflict," Requirements Engineering Journal, 5, 2 (2000), pp. 103-113.
  205. [Cobleigh, et al. 2006].
    Cobleigh, R., "User guidance for creating precise and accessible property specifications," 14th ACM SIGSOFT international symposium on Foundations of software engineering, New York: ACM Press, 2006.
  206. [Cockburn 2001].
    Cockburn, A., Writing Effective Use Cases, Addison Wesley, 2001.
  207. [Cohen 1995].
    Cohen, L., Quality Function Deployment: How to Make QFD Work for You, Reading, Massachusetts: Addison-Wesley, 1995.
  208. [Cohen 1997].
    Cohen, M., "The Impact of Executable Requirements Models," Seventh Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1997.
  209. [Cohen, et al. 2001].
    Cohen, D., et al., "Improving Software Investments through Requirements Validation," ( see abstract) 26th Annual NASA Goddard Software Engineering Workshop, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 106-114.
  210. [Cohene and Easterbrook 2005].
    Cohene, T., and S. Easterbrook, "Contextual Risk Analysis for Interview Design," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 95-104.
  211. [Cohn 2004].
    Cohn, M., User Stories Applied, Boston, Massachusetts: Addison Wesley, 2004.
  212. [Cole 2006].
    Cole, R., "The Changing Role of Requirements and Architecture in Systems Engineering," IEEE International Conference on System of Systems Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  213. [Coleman and Baker 1997].
    Coleman, D., and A. Baker, "Synthesizing Structured Analysis and Object-Based Formal Specifications," Annals of Software Engineering, 3, N. Mead, ed., 1997.
  214. [Collins-Cope 1999].
    Collins-Cope, M., "The Requirements/Service/Interface (RSI) Approach to Use Case Analysis," International Conference on Technology of Object-Oriented Languages and Systems, Los Alamitos, California: IEEE Computer Society Press, 1999.
  215. [Colombo and Francalanci 2005].
    Colombo, E., and C. Francalanci
    , "Selecting CRM Packages based on Architectural, Functional, and Cost Requirements: Empirical Validation of a Hierarchical Ranking Model," ( see abstract) Requirements Engineering, (accepted for publication 2004).
  216. [Colter 1984].
    Colter, M., "A Comparative Examination of Systems Analysis Techniques," MIS Quarterly, 1, 1 (March 1984), pp. 51-67.
  217. [Columbo, et al. 2008].
    Columbo, P., et al., "Using problem frames to model the requirements of a system for monitoring dangerous goods transportation," International workshop on applications and advances of problem frames, New York: ACM Press, 2008, pp. 60-66.
  218. [Compatangela 1997].
    Compatangela, E., "Towards an Open Framework for Conceptual Knowledge in ECBS Domain and Information Modelling," IEEE International Conference and Workshop on Systems Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 1997.
  219. [Condori-Fernandez, et al. 2004].
    Condori-Fernandez, N., et al., "Towards a Functional Size Measure for Object-Oriented Systems from Requirements Specifications," IEEE International Conference on Quality Software, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 94-101.
  220. [Condori-Fernandez, et al. 2007].
    Condori-Fernandez, N., et al., "On the estimation of the functional size of software from requirements specifications," (see abstract) Journal of Computer Science and Technology, 22, 3 (May 2007), pp. 358-370.
  221. [Conejero, et al. 2007].
    Conejero, J., et al., "Discovering Volatile and Aspectual Requirements Using a Crosscutting Pattern,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  222. [Conn 1979].
    Conn, A., "Representation of Decisions in a Requirements Specification Language," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1979, pp. 113-116. 
  223. [Conn 1979a].
    Conn, A., "A Methodology for Broadening the Scope of Computer Requirements Definition," AIAA National Conference, 1979. 
  224. [Conn 1980].
    Conn, A., "Maintenance: A Key Element in Computer Requirements Definition," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1980, pp. 401-406. 
  225. [Connell and Shafer 1989].
    Connell, J., and L. Shafer, Structured Rapid Prototyping, Upper Saddle River, New Jersey, 1989.
  226. [Connelly 1984].
    Connelly, E., "Empirical Investigation of Aids for Non-Programming Users in Developing Cost Effective Requirements Specifications," Annual Meeting of the Human Factors Society, Santa Monica, CA: Human Factors Society, 1984, pp. 67-71.
  227. [Connolly, et al. 2008].
    Connolly, D., et al., "Tag oriented agile requirements identification," IEEE Conference and Workshop on Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2008, pp. 497-498.
  228. [Constantine 1998]
    Constantine, L., "Prototyping from the User's Viewpoint," Software Development, 6, 11 (November 1998), pp. 51-57.
  229. [Conte de Leon and Alves-Foss 2004].
    Conte de Leon, D., and J. Alves-Foss, "Experiences with Processing and Linking Semantically Augmented Requirements Specifications," Thirty-Seventh Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 279-288.
  230. [Cook, et al. 2001].
    Cook, S., et al., "A Frame-Based Approach to Requirements Engineering," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2001.
  231. [Cook, et al. 2008].
    Cook, D., et al., "One Bagel with My Requirements, Please!," Crosstalk, (August 2008).
  232. [Cooke 1995].
    Cooke, D., "Preliminary Thoughts Concerning the Interphase Activity of Requirement Migration," Seventh International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, 1995, pp. 166-172.
  233. [Coolahan and Roussopoulos 1983].
    Coolahan, J., and N. Roussopoulos, "Timing Requirements for Time-Driven Systems Using Augmented Petri Nets," ( see abstract) IEEE Transactions on Software Engineering, 9, 5 (September 1983), pp. 603-616.
  234. [Coombes and McDermid 1994].
    Coombes, A., and J. McDermid, "Using Quantitative Physics in Requirements Specification of Safety Critical Systems" Workshop on Research Issues in the Intersection Between Software Engineering and Artificial Intelligence, Sorrento, Italy, May 1994.
  235. [Cooper and Swanson 1979].
    Cooper, R., and E. Swanson, "Management Information Requirements Assessment: The State of the Art," Database, 11, 2 (February 1979), pp. 5-16.
  236. [Cooper 1998].
    Cooper, R., Product Leadership, Cambridge, Massachusetts: Perseus Books, 1998.
  237. [Cooper and Hsia 1982].
    Cooper, J., and P. Hsia, "Scenario-Based Prototypes for Requirements Identification," ACM SIGSOFT Workshop on Rapid Prototyping, New York: ACM Press, 1982, pp. 17.1-17.11.
  238. [Cooper and Ito 1998].
    Cooper, K., and M. Ito, "Advantages of Stimulus Response Requirement Specification Techniques for System Testing," Eighth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1998.
  239. [Cooper and Chung 2002].
    Cooper, K., and L. Chung, "A COTS-Aware Requirements Engineering Process: A Goal- and Agent-Oriented Approach," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2002.
  240. [Cooper and Chung 2005].
    Cooper, K., and L. Chung, "Managing change in an OTS-aware requirements engineering approach," ACM Software Engineering Notes, 30, 4 (May 2005).
  241. [Cooper, et al. 2005].
    Cooper, K., et al., "Quantifying the Evolution of Goals in Requirements Engineering: A Study on the Quality Assurance Review Assistant Tool," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
  242. [Cooper 2006].
    Cooper, K., "Can Agility be Introduced into Requirements Engineering for COTS Component Development?," IEEE International Workshop on Software Product Management, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 35-37.
  243. [Cooper, et al. 2006].
    Cooper, K., "Integrating visual goal models into the Rational Unified Process," Visual Languages and Computing, 17, 6 (December 2006), pp. 551-583.

    Cope, see Collins-Cope
     
  244. [Cordes and Carver 1989].
    Cordes, D., and D. Carver, "Evaluation Method for User Requirements Documents," Information and Software Technology, 31, 4 (May 1989), pp. 181-188.
  245. [Cornford, et al. 2006].
    Cornford, S., et al., "Fusing Quantitative Requirements Analysis with Model-based Systems Engineering," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  246. [Corniou 2005].
    Corniou, J., "Keynote: The Role of Information Systems within Corporate Strategy and Management Policies: New Challenges," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, p. 4.
  247. [Corradini, et al. 2006].
    Corradini, F., et al., "On relating functional specifications to architectural specifications: A case study," Science of Computer Programming, (February 2006), pp. 171-208.
  248. [Correa and Werner 2004].
    Correa, A., and C. Werner, "Precise Specification and Validation of Transactional Business Software," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 16-25.
  249. [Corriveau 2007]
    Corriveau, J.-P., "Testable Requirements for Offshore Outsourcing," in Software Engineering Approaches for Offshore and Outsourced Development, Lecture Notes in Computer Science, Volume 4716, Berlin: Springer, 2007, pp. 27-43.
  250. [Cortesi and Logozzo 2005].
    Cortesi, A., and F. Logozzo, "Abstract Interpretation-Based Verification of Non-Functional Requirements," International Conference on Coordination Models and Languages, Lecture Notes in Computer Science 3454, Berlin: Springer, 2005, pp. 49-62.

    Cortéz, see Ruiz-Cortéz
     
  251. [Costa, et al. 1987].
    Costa, M., et al., "Tool support for the verification and validation of formal requirements specifications," International Conference on Software Engineering for Real Time Systems, Los Alamitos, California: IEEE Computer Society Press, 1987, pp. 1-9.
  252. [Costal, et al. 2002].
    Costal, D., et al., "Understanding Redundancy in UML Models for Object-Oriented Analysis," Conference on Advanced Information Systems Engineering (CAiSE), Berlin: Springer, 2002. 
  253. [Costello and Liu 1995].
    Costello, R., and D. Liu, " Metrics for Requirements Engineering," Journal of Systems and Software, 29, 1 (April 1995), pp. 39-63.
  254. [Couger 1973].
    Couger, D., "Evolution of Business System Analysis Techniques," ACM Computing Surveys, 5, 3 (September 1973), pp. 167-198.
  255. [Coughlan and Macredie 2002].
    Coughlan, J., and R. Macredie, "Effective Communication in Requirements Elicitation: A Comparison of Methodologies," Requirements Engineering Journal, 6, 2 (June 2002), pp. 47-60.
  256. [Coughlan, et al. 2003].
    Coughlan, J., et al., "Communication Issues in Requirements Elicitation: A Content Analysis of Stakeholder Experiences," Information and Software Technology, 45, 8 (2003), pp. 525-536.
  257. [Coulin and Zowghi 2004].
    Coulin, C., and D. Zowghi, "GONDOLA: An interactive computer game-based teaching and learning environment for Requirements Engineering", 10th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 04), Riga, Latvia, 2004.
  258. [Coulin and Zowghi 2004a].
    Coulin, C., and D. Zowghi, "Requirements Elicitation for Complex Systems: Theory and Practice" in Requirements Engineering for Socio-Technical Systems, edited by Jose Luis Mate and Andres Silva, Idea Group, Inc., 2004.
  259. [Coulin and Sahraoui 2005].
    Coulin, C., and A. Sahraoui, "A Meta-Model Based Guided Approach to Collaboration Requirements Elicitation for Software Systems Development," International Conference on Software and Systems Engineering and Their Applications, Paris: CNAM, 2005.
  260. [Coulin and Zowghi 2005].
    Coulin, C., and D. Zowghi
    , "Requirements Elicitation for Complex Systems: Theory and Practice," in Requirements Engineering for Sociotechnical Systems, J. Maté, and A. Silva, eds., Hershey, Pennsylvania: Information Science Publishing, 2005, pp. 37-52.
  261. [Coulin and Zowghi 2005a].
    Coulin, C., and D. Zowghi, "What Do Experts Think About Elicitation: A State of Practice Survey," Australian Workshop on Requirements Engineering, 2005.
  262. [Coulin, et al. 2005].
    Coulin, C., et al., "Towards a collaborative and combinational approach to requirements elicitation within a systems engineering framework," International Conference on Systems Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 456-461.
  263. [Coulin and Zowghi 2006].
    Coulin, C., and D. Zowghi, "A situational method engineering approach to requirements elicitation workshops in the software development process," Software Process: Improvement and Practice, 11, 5 (September/October 2006), pp. 451-464.
  264. [Courage and Baxter 2004].
    Courage, C. and K. Baxter, Understanding Your Users: A Practical Guide to Requirements Methods, Tools and Techniques, San Francisco, California: Morgan Kauffman, 2004.
  265. [Covvey, et al. 2003].
    Covvey, H., et al., "Formal Structure for Specifying the Content and Quality of the Electronic Health Record," International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003.
  266. [Cox 2000].
    Cox, K., "Fitting Scenarios to the Requirements Process," (see abstract) Eleventh IEEE International Workshop on Database and Expert Systems Applications, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 995-999.
  267. [Cox and Phalp 2000].
    Cox, K., and K. Phalp, "Replicating the CREWS Use Case Authoring Guidelines Experiment," Empirical Software Engineering, 5, 3 (November 2000). pp. 245-267.
  268. [Cox and Phalp 2003].
    Cox, K., and K. Phalp, "From Process Model to Problem Frame -- A Position Paper," International Workshop on Requirements Engineering: Foundations for Software Quality, 2003.
  269. [Cox, et al. 2003].
    Cox, K., et al., "A Use Case Description Inspection Experiment," Australian Workshop on Requirements Engineering, 2003.
  270. [Cox, et al. 2004].
    Cox, K., et al., "An Experiment in Inspecting the Quality of Use Case Descriptions," Journal of Research and Practice in Information Technology, 36, 4 (November 2004). pp. 211-229.
  271. [Cox, et al. 2004a].
    Cox, K., et al., "Connecting Role Activity Diagrams to the Problem Frames Approach," Australian Workshop on Requirements Engineering, 2004.
  272. [Cox, et al. 2005].
    Cox, K., et al., "Deriving requirements from process models via the problem frames approach," Information and Software Technology, 47, 5 (March 2005), pp. 319-337.
  273. [Cox, et al. 2005a].
    Cox, K., et al., "
    A roadmap of problem frames research," Information and Software Technology, (2005).
  274. [Cox and Phalp 2007].
    Cox, K, and K. Phalp, "Practical experience of eliciting classes from use case descriptions," Journal of Systems and Software, 80, 8 (August 2007), pp. 1286-1304.
  275. [Cox, et al. 2007].
    Cox, K., et al., "Editorial: REBNITA '05 -- 1st International Workshop on Requirements engineering for Business Need and IT Alignment
    ," The Journal of Systems and Software, 80, 3 (March 2007), pp. 283-284.
  276. [Coyle, et al. 2002].
    Coyle, L., et al., "A Case-Based Personal Travel Assistant for Elaborating User Requirements and Assessing Offers," Lecture Notes in Computer Science, Volume 2416, Berlin: Springer, 2002, pp. 505ff. 
  277. [Coyne 1993].
    Coyne, B., "Requirements Change Process Development," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1993.
  278. [Crabtree 2003].
    Crabtree, A., Designing Collaborative Systems. A Practical Guide to Ethnography, Berlin: Springer, 2003.
  279. [Creel 1999].
    Creel, C., "Requirements by Pattern," Software Development, 7, 12 (December 1, 1999), pp. 44-47.
  280. [Creighton, et al. 2006].
    Creighton, O., et al., "Software Cinema-Video-based Requirements Engineering," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  281. [Crespo 1994].
    Crespo, R., "We Need to Identify the Requirements of the Statements of Non-Functional Requirements," International Workshop on Requirements Engineering: Foundations of Software Quality, June 1994.
  282. [Crnkovic, et al. 1999].
    Crnkovic, I., et al., "Processing Requirements by Software Configuration Management," 25th Euromicro Conference, Volume 2, Los Alamitos, California: IEEE Computer Society Press, pp. 260-265.
  283. [Crocker 1993].
    Crocker, D., "Database Generated Software Requirements Specification," Third Annual National Council on Systems Engineering International Symposium, Sunnyvale, California: NCOSE.
  284. [Crofts, et al. 2004].
    Crofts, M., et al., "
    Global Software Development: The Next RE Frontier," Australian Workshop on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004.
  285. [Cronholm and Goldkuhl 2005].
    Cronholm, S., and G. Goldkuhl
    ,
    "Communicatio Analysis as Perspective and method for Requirements Engineering," in Requirements Engineering for Sociotechnical Systems, J. Maté, and A. Silva, eds., Hershey, Pennsylvania: Information Science Publishing, 2005, pp. 340-358.
  286. [Crook, et al. 2002].
    Crook, R., et al., "Security Requirements Engineering: When Anti-requirements Hit the Fan," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  287. [Crook, et al. 2003].
    Crook, R., et al., "Modelling Access Policies Using Roles in Requirements Engineering," Information and Software Technology, 45, 14 (November 2003), pp. 979-991.
  288. [Crook, et al. 2005].
    Crook, R., et al., "On Modeling Access Policies: Relating Roles to Their Organizational Context," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 157-166.
  289. [Crowe, et al. 1996].
    Crowe, D., et al., "Adaptation of a Software Requirements Engineering Method To the System Level For Software-Intensive Systems," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  290. [Crowston and Kemmerer 1998].
    Crowston, K., and E. Kemmerer, "Coordination and Collective Mind in Software Requirements Development," IBM Systems Journal, 37, 2 (February 1998), pp. 227-235.
  291. [Cucchiarelli, et al. 1994].
    Cucchiarelli, A., et al., "Supporting User-Analyst Interaction in Functional Requirements Elicitation," First Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society, December 1994, pp. 114-123.
  292. [Cuevos, et al. 2004].
    Cuevos, G., et al., "Assessment of the Requirement Management Process Using a Two-Stage Questionnaire," IEEE International Conference on Quality Software, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 110-116.
  293. [Cunning and Rosenbilt 1999].
    Cunning, S., and J. Rosenbilt, "Test scenario generation from a structured requirements specification," Conference and Workshop on Systems Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society, 1999.
  294. [Cunningham, et al. 1985].
    Cunningham, R., et al., "Formal Requirements Specification: The Forest Project," Third IEEE International Workshop on Specification and Design, Los Alamitos, California: IEEE Computer Society, 1985, pp. 186-191.
  295. [Cunningham and Goldsack 1988].
    Cunningham, R., and S. Goldsack, "Why Forest?," UK IT Conference, London: Inf. Eng. Directorate, 1988, pp. 91-94.
  296. [Curran, et al. 1994].
    Curran, P., et al., "BORIS-R Specification of the Requirements of a Large-Scale Software Intensive System," Conference on Requirements Elicitation for Software-Based Systems, July 1994.
  297. [Curtis 1994].
    Curtis, A., "How to Do and Use Requirements Traceability Effectively," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 57-64.
  298. [Curtis and Cobham 2005].
    Curtis, G., and D. Cobham, Business Information Systems: Analysis, Design & Practice, Pearson, 2005.
  299. [Curtis, et al. 2006].
    Curtis, C., et al., "Analyzing Requirements for and Designing a Collaborative Tool based on Functional and User Input," International Symposium on Collaborative Technologies and Systems, Los Alamitos, California: IEEE Computer Society, 2006, pp. 220-225.
  300. [Cybulski, et al. 1998].
    Cybulski, J., et al., "Reuse of Early Life-Cycle Artifacts: Workproducts, Methods and Tools," Annals of Software Engineering, 5 (January 1998), pp. 227-251.
  301. [Cybulski and Reed 1998].
    Cybulski, J., and K. Reed, " Computer-Assisted Analysis and Refinement of Informal Software Requirements Documents," Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society, 1998, pp. 128-135.
  302. [Cybulski and Reed 2000].
    Cybulski, J., and K. Reed, "Requirements Classification and Reuse: Crossing Domain Boundaries," Sixth International Conference on Software Reuse, Berlin: Springer Verlag, 2000, pp. 190-210.
  303. [Cybulski 2000].
    Cybulski, J., "Automatic Refinement of User Requirements: A Case Study in Software Tool Evaluation," Thirteenth Australasian Conference on Information Systems, Melbourne, Australia, 2000, pp. 757-771.
  304. [Cybulski, et al. 2003].
    Cybulski, J., et al., "Using constructivist experiential simulations in RE education," Australian Workshop on Requirements Engineering, 2003.
  305. [Cybulski and Sarkar 2005].
    Cybulski, J., and P. Sarkar, "Requirements Engineering for Web-Based Information Systems," inEngineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 327-349.
  306. [Cyre 1995].
    Cyre, W., "Automated Analysis of Requirements Specifications," Second International Conference on Software Engineering, 1995.
  307. [Cyre and Thakar 1997].
    Cyre, W., and A. Thakar, "Generating Validation Feedback for Automatic Interpretation of Informal Requirements," Formal Methods in System Design, 10, 1 (February 1997), pp. 73-92.
  308. [Cysneiros and Leite 1999].
    Cysneiros, L.
    , and J. Leite, "Integrating non-functional requirements into data modeling," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999.
  309. [Cysneiros and Leite 2001].
    Cysneiros, L.
    , and J. Leite, "Using UML to Reflect Non-Functional Requirements," 2001 Conference of the Centre for Advanced Studies on Collaborative Research, Toronto, Canada, Canada: IBM Press, 2001, p. 2.
  310. [Cysneiros and Leite 2001a].
    Cysneiros, L.
    , and J. Leite, "Driving Non-Functional Requirements to Use Cases and Scenarios," Brazilian Symposium on Software Engineering, 2001.
  311. [Cysneiros, et al. 2001].
    Cysneiros, L., et al., "A Framework for Integrating Non-Functional Requirements into Conceptual Models," Requirements Engineering Journal, 6, 2 (2001), pp. 97-113.
  312. [Cysneiros 2002].
    Cysneiros, L., "Requirements Engineering in Health Care Domain," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  313. [Cysneiros and Leite 2002].
    Cysneiros, L., and J. Leite, "Non-Functional Requirements: From Elicitation to Modelling Languages," Twenty-fourth International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002, pp. 699-700.
  314. [Cysneiros and Yu 2003].
    Cysneiros, L., and E. Yu, "Non-Functional Requirements Elicitation," in Perspectives on Software Requirements, Leite, J., and J. Doorn, eds., Berlin: Springer, 2003.
  315. [Cysneiros and Yu 2003a].
    Cysneiros, L., and E. Yu, "Requirements Engineering for Large-Scale Multi-Agent Systems," Lecture Notes in Computer Science, Volume 2603, Berlin: Springer, 2003, pp. 39-569.
  316. [Cysneiros and Leite 2004].
    Cysneiros, L., and J. Leite, "Non-Functional Requirements: From Elicitation to Conceptual Models," IEEE Transactions on Software Engineering, 30, 5 (May 2004), pp. 328-350.
  317. [Cysneiros, et al. 2005].
    Cysneiros, L., et al., "Reusable Knowledge for Satisficing Usability Requirements," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 463-464.
  318. [Czerny and Heimdahl 1998].
    Czerny, B., and M. Heimdahl, "Automated Integrative Analysis of State-Based Requirements," 13th IEEE International Conference on Automated Software Engineering, Los Alamitos, California: IEEE Computer Society, 1998, pp. 125-134.
  319. [Czuchry 1987].
    Czuchry, A., "Where's the Intelligence in the Intelligent Assistant for Requirements Analysis," Second Annual RADC Conference on Knowledge-based Assistants, Grifiss AFB, New York: RADC, 1987.
  320. [Czuchry and Harris 1988].
    Czuchry, A., and D. Harris, "KBRA: A New Paradigm for Requirements Engineering," IEEE Expert, (1988), pp. 21-35.

    D

    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. [Dad and Jamil 2006].
    Dad, K., and A. Jamil, "Enhanced Facilitated Application Specification Techniques (eFAST)," 5th IEEE/ACIS International Conference on Computer and Information Science and 1st IEEE/ACIS International Workshop on Component-Based Software Engineering, Software Architecture and Reuse (ICIS-COMSAR'06), Los Alamitos, California: IEEE Computer Society, 2006, pp. 155-159.
  2. [Daft and Lengel 1986].
    Daft, R., and R. Lengel, "Organizational Information Requirements: Media Richness and Structural Design," Management Science, 33 (1986), pp. 554-569.

    Dag, see Natt och Dag
     
  3. [Dahlstedt 2003a].
    Dahlstedt, Ĺ., "Market-Driven Requirements Engineering Processes for Software Products - a Report on Current Practices," International Workshop on COTS and Product Software, Los Alamitos, California: IEEE Computer Society Press, 2003.
  4. [Dahlstedt and Perrson 2003].
    Dahlstedt, Ĺ., and P. Perrson, "Requirements Interdependencies -- Moulding the State of the Research into a Research Agenda," International Workshop on Requirements Engineering: Foundations for Software Quality, 2003.
  5. [Dahlstedt and Perrson 2005].
    Dahlstedt, Ĺ., and P. Perrson, "Requirements Interdependencies: State of the Art and Future Challenges," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 95-116.
  6. [Dahlstedt 2005].
    Dahlstedt, Ĺ., "Guidelines Regarding Requirements Engineering Practices in Order to Facilitate System Testing," 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
  7. [Dale 2004].
    Dale, R., "Using a Requirements Management Tool in Technical Requirements Negotiations," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  8. [Dale 2004a].
    Dale, M., "Capturing User Requirements for a Large Corporate Data Warehouse: An Experiential Case Study," Australian Workshop on Requirements Engineering, 2004.
  9. [Dam 2007].
    Dam, S., "Intelligent Operational Scenarios: A Strategy for Cost-Saving Scenario Selection," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2007.
  10. [Damas, et al. 2006].
    Damas, C., "Scenarios, goals, and state machines: a win-win partnership for model synthesis," 14th ACM SIGSOFT international symposium on Foundations of software engineering, New York: ACM Press, 2006.
  11. [Damian, et al. 1999].
    Damian, D., et al., "Studies in Distributed Software Requirements Engineering," Twelfth Workshop on Knowledge Acquisition, Modeling and Management (KAW’99), Banff, Alberta, Canada, 1999.
  12. [Damian, et al. 2000].
    Damian, D., et al., "Using Different Communication Media in Requirements Negotiation," (see abstract) IEEE Software, May-June 2000, pp. 28-36.
  13. [Damian, et al. 2000a].
    Damian, D., " The Effects of Communication Media on Group Performance in Requirements Engineering," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2000, p. 191.
  14. [Damian, et al. 2001].
    Damian, D., et al., " An Empirical Study of Facilitation of Computer-Mediated Distributed Requirements Negotiations," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 128-135.
  15. [Damian 2001].
    Damian, D., "An Empirical Study of Requirements Engineering in Distributed Software Projects: Is Distance Negotiation More Effective?" Eighth Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 149-152.
  16. [Damian 2002].
    Damian, D., et al., "An Empirical Study of a Multimedia Group Support System for Distributed Software Requirements Meetings," e-Service Journal, 1, 3 (June 2002), pp. 43-60.
  17. [Damian and Zowghi 2002].
    Damian, D., and D. Zowghi, "The Impact of Stakeholders' Geographical Distribution on Managing Requirements in a Multi-Site Organization," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002, pp. 319-330.
  18. [Damian, et al. 2002].
    Damian, D., et al., "A Compositional Knowledge Level Process Model of Requirements Engineering,"
    International Journal of Software Engineering and Knowledge Engineering, 12, 1 (2002), pp. 41-75.
  19. [Damian  2003].
    Damian, D., "A Research Methodology in the Study of Requirements Negotiations in Geographically Distributed Software Teams," 1st International Workshop on Comparative Evaluation in Requirements Engineering, Sydney, Australia: Faculty of Information Technology, University of Technology, Sydney, 2003, pp. 37-47.
  20. [Damian and Zowghi 2003].
    Damian, D., and D. Zowghi, "An Insight into the Interplay between Culture, Conflict and Distance in Globally Distributed Requirements Negotiation," 36th Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 2003.
  21. [Damian and Zowghi 2003a].
    Damian, D., and D. Zowghi, "Requirements Engineering Challenges in Multi-Site Software Development Organizations," Requirements Engineering, 8, 3 (August 2003), pp. 149-160.
  22. [Damian, et al. 2003].
    Damian, D., et al., "
    An Industrial Case Study of the Impact of Requirements Engineering on Downstream Development," International Symposium on Empirical Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 40-49. 
  23. [Damian, et al. 2003a].
    Damian, D., et al., " An Exploratory Study of Facilitation in Distributed Requirements Engineering," Requirements Engineering, 8, 1 (February 2003), pp. 23-41.
  24. [Damian, et al. 2004].
    Damian, D., et al., "An Industrial Case Study of Immediate Benefits of Requirements Engineering Process Improvement at the Australian Center for Unisys Software," Empirical Software Engineering, (2004). 
  25. [Damian, et al. 2005].
    Damian, D., et al., "Requirements Engineering and Downstream Software Development: Findings from a case Study," Empirical Software Engineering, 10, 3 (July 2005). pp. 255-283.
  26. [Damian, et al. 2005a].
    Damian, D., et al., "Integration of behavioural requirements specification within compositional knowledge engineering," Knowledge-Based Systems, (2005).
  27. [Damian 2006].
    Damian, D., "Requirements Engineering in Distributed Projects," International Conference on Global Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 69ff. 
  28. [Damian and Chisan 2006].
    Damian, D., and J. Chisan, "An empirical study of the complex relationships between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management," IEEE Transactions on Software Engineering, 32, 7 (July 2006), pp. 433-453.
  29. [Damian, et al. 2006].
    Damian, D., et al., "
    The role of asynchronous discussions in increasing the effectiveness of remote synchronous requirements negotiations," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 917-920. 
  30. [Damian, et al. 2006a].
    Damian, D., et al., "An empirical study of the impact of asynchronous discussions on remote synchronous requirements meetings," 9th International Conference on Fundamental Approaches to Software Engineering, Lecture Notes in Computer Science 3922, Berlin: Springer, 2006, pp. 155-169. 
  31. [Damian 2007].
    Damian, D., "Stakeholders in Global Requirements Engineering: Lessons Learned from Practice," IEEE Software, 24, 2 (March-April 2007), pp. 21-27. 
  32. [Damian, et al. 2007].
    Damian, D., et al., "Collaboration Patterns and the Impact of Distance on Awareness in Requirements-Centred Social Networks," IEEE International Conference on Requirements Engineering
    , Los Alamitos, California: IEEE Computer Society Press, 2007.
  33. [Damian, et al. 2008].
    Damian, D., et al., "On the Need for Mixed Media in Distributed Requirements Negotiations," IEEE Transactions on Software Engineering, (2008).
  34. [Damm and Westphal 2005].
    Damm, W., and B. Westphal, "Live and let die: LSC based verification of UML models," Science of Computer Programming, 55, 1-3 (March 2005), pp. 117-159. 
  35. [Daneva 1999].
    Daneva, M., "Identifying and Quantifying Reuse in the SAP Requirements Engineering Process," Fifth International Workshop on Requirements Engineering: Foundations for Software Quality, Heidelberg, Germany, June 1999.
  36. [Daneva 2000].
    Daneva, M., "Establishing Reuse Measurement Practices in SAP Requirements Engineering," ( see abstract) International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 168-177.
  37. [Daneva 2000a].
    Daneva, M., "Practical Reuse Measurement of ERP Requirements Engineering," Conference on Advanced Information Systems Engineering (CAiSE), Lecture Notes in Computer Science 1789, Berlin: Springer, 2000, pp. 309ff.
  38. [Daneva 2000b].
    Daneva, M., "Reuse Measurement in the ERP Requirements Engineering Process," in Software Reuse: Advances in Software Reusability, Lecture Notes in Computer Science 1844, Berlin: Springer, 2000, pp. 211-230.
  39. [Daneva  2001].
    Daneva, M., "An Assessment of the Effects of Requirements Reuse Measurements on the ERP Requirements Engineering Process," Lecture Notes in Computer Science, Volume 2006, Berlin: Springer, 2001, pp. 172ff. 
  40. [Daneva 2002].
    Daneva, M., "Using Maturity Assessments to Understand the ERP Requirements Engineering Process," ( see abstract) Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  41. [Daneva 2003].
    Daneva, M., "Lessons Learnt from Five Years of Experience in ERP Requirements
    Engineering," International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 45-54.
  42. [Daneva 2003a].
    Daneva, M., "Six Degrees of Success or Failure in ERP Requirements Engineering
    ," International Workshop on COTS and Product Software, Los Alamitos, California: IEEE Computer Society Press, 2003.
  43. [Daneva 2004].
    Daneva, M., "ERP Requirements Engineering Practice: Lessons Learned," IEEE Software, 21, 2 (March/April 2004), pp. 26-33.
  44. [Daneva and Wieringa 2005].
    Daneva, M., and R. Wieringa, "Requirements Engineering for Cross-Organizational ERP Implementation: Undocumented Assumptions and Potential Mismatches," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 63-74.
  45. [Daneva 2006].
    Daneva, M., "Integrating Reuse Measurement Practices into the ERP Requirements Engineering Process," Product-Focused Software Process Improvement, Lecture Notes in Computer Science 4034, Berlin: Springer, 2006.
  46. [Daneva and Wieringa 2006].
    Daneva, M., and R. Wieringa, "A Coordination Complexity Model to Support Requirements Engineering for Cross-organizational ERP (Short Paper)," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  47. [Daneva and Wieringa 2006a].
    Daneva, M., and R. Wieringa, " A requirements engineering framework for cross-organizational ERP systems," Requirements Engineering, 11, 3 (June 2006), pp. 194-204.
  48. [Daneva 2008].
    Daneva, M., "Integrating Portfolio Management and Simulation Concepts in the ERP Project Estimation Practice," International Working Conference on Requirements Engineering: Foundations for Software Quality, Berlin: Springer, 2008.
  49. [Daniel-Garcia, et al. 2004].
    Daniel-Garcia, J. et al., "
    A Model for Use Case Prioritization Using Criticality Analysis," Lecture Notes in Computer Science 3046, Berlin: Springer, 2004, pp. 496-505.
  50. [Daniels 1984].
    Daniels, H., "The importance of requirements definition for the software development process," Angewandt Informatik, 26, 3 (March 1984), pp. 87-97.
  51. [Daniels, et al. 1991].
    Daniels, R., et al., "Enterprise Analyzer: Electronic Support for Group Requirements Elicitation," 24th Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 1991, pp. 43-52.
  52. [Daniels and Bahill 2004].
    Daniels, J., and T. Bahill, "The hybrid process that combines traditional requirements and use cases," Systems Engineering, 7, 4 (September 2004), pp. 303-319.
  53. [Daniels, et al. 2005].
    Daniels, J., et al., "A Hybrid Requirements Capture Process," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
  54. [Dankel, et al. 1992].
    Dankel, D., et al., "A Model for Capturing Requirements," Fifth International Conference on Software Engineering and Its Applications, Nanterre, France: EC2, 1992.
  55. [Dano, et al. 1997].
    Dano, B., et al., "Producing Object-Oriented Dynamic Specifications: An Approach Based on the Concept of 'Use Case'," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1997.
  56. [Dano, et al. 1997a].
    Dano, B., et al., "A Use Case Driven Requirements Engineering Process," (see abstract) Requirements Engineering Journal, 2, 1 (1997), pp. 79-91.

    Dapena, see Rodriguez-Dapena
     
  57. [Dardenne, et al. 1991].
    Dardenne, A.,  et al., "Goal-Directed Concept Acquisition in Formal Requirements Elicitation," Sixth IEEE International Workshop on Specification and Design, Los Alamitos, California: IEEE Computer Society, 1991, pp. 14-21.
  58. [Dardenne 1993].
    Dardenne, A., On the Use of Scenarios in Requirements Acquisition, University of Oregon Computer and Information Science Department Technical Report #CIS-93-17, Eugene, Oregon, August 4, 1993.
  59. [Dardenne, et al. 1993].
    Dardenne, A., et al., "Goal-Directed Requirements Acquisition," Science of Computer Programming, 20 (1993), pp. 3-50.
  60. [Darimont and van Lamsweerde 1996].
    Darimont, R., and A. van Lamsweerde, "Formal Refinement Patterns for Goal-Driven Requirements Elaboration," Fourth ACM SIGSOFT Symposium on the Foundations of Software Engineering (FSE 4), New York: ACM Press, October 1996, pp. 179-190.
  61. [Darimont and Souquieres 1997].
    Darimont, R., and J. Souquieres, "Reusing Operational Requirements: A Process-Oriented Approach," ( see abstract) IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1997, pp. 16-25.
  62. [Darimont, et al. 2002].
    Darimont, R., et al., " Requirements Engineering with Grail/Kaos : Tell the Requirements, All the Requirements and Nothing Else but the Requirements," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  63. [Darke and Shanks 1996].
    Darke, P., and G. Shanks, "Stakeholder Viewpoints in Requirements Definition: A Framework for Understanding Viewpoint Development Approaches," (see abstract) Journal of Requirements Engineering, 1, 2 (1996), pp. 88-105.
  64. [Das 2008].
    Das, V.
    , "Involvement of users in software requirement engineering," International Conference on Information Technology, Los Alamitos, California: IEEE Computer Society Press, 2008, pp. 230-233.
  65. [Dasarathy 1985].
    Dasarathy, B., "Timing Constraints of Real-Time Systems: Constructs for Expressing Them, Methods for Validating Them," IEEE Transactions on Software Engineering, 11, 1 (January 1985), pp. 80-86.
  66. [Dascalu, et al. 2006].
    Dascalu, S., et al., "
    STORM: Software Tool for the Organization of Requirements Modeling," IEEE International Conference on Electro/Information Technology, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 250-255.
  67. [Dascalu, et al. 2008].
    Dascalu, S., et al., "STORM: Software Tool for the Organization of Requirements Modeling
    ," IEEE International Conference on Electro/Information Technology, Los Alamitos, California: IEEE Computer Society Press, 2008.
  68. [Dasgupta, et al. 2007a].
    Dasgupta, A., et al., "Agent Based Executable Conceptual Models Using i* and CASO," Advances in Conceptual Modeling - Theory and Practice, Berlin: Springer, 2007.
  69. [Dastani, et al. 2004]
    Dastani, M., et al., "A Requirement Specification Language for Configuration Dynamics of Multiagent Systems," International Journal of Intelligent Systems, 19, 3 (March 2004), pp. 277-300.
  70. [Daugulis 2000].
    Daugulis, A., "Time Aspects in Requirements Engineering: Or Every Cloud Has a Silver Lining," Requirements Engineering Journal, 5, 3 (2000), pp. 137-143.
  71. [Davies 2004].
    Davies, P., "Ten Questions to Ask Before Opening the Requirements Document," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
  72. [Davies and Sharp 2006].
    Davies, R., and H. Sharp, "Early and often: elaborating agile requirements," Cutter IT Journal, 19, 7 (July 2006), pp. 6-11.

    d'Avila Garcez see Avila Garcez
     
  73. [Davis and Vick 1977].
    Davis, C., and C. Vick, "The Software Development System," IEEE Transactions on Software Engineering, 3, 1 (January 1977), pp. 69-84.
  74. [Davis and Rataj 1978].
    Davis, A., and W. Rataj, "Requirements Language Processor for the Effective Testing of Real-Time Systems," ACM Software Engineering Notes, 3, 5 (November 1978), pp. 61-66.
  75. [Davis and Vick 1978].
    Davis, C., and C. Vick, "The Software Development System: Status and Evolution," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1978, pp. 326-331. 
  76. [Davis and Rauscher 1979].
    Davis, A.., and T. Rauscher, "Formal Techniques and Automated Processing to Ensure Correctness in Requirements Specifications," IEEE Specifications of Reliable Software Conference, Los Alamitos, California: IEEE Computer Society Press, 1979, pp. 15-35.
  77. [Davis and Rauscher 1979a].
    Davis, A.., and T. Rauscher, "A survey of techniques used for requirements definition of computer based systems," GTE Automatic Electric World-Wide Communications Journal, 9, 5, (September 1979), pp. 161-170.
  78. [Davis, et al. 1979].
    Davis, A.., et al., "RLP: An Automated Tool for the Processing of Requirements," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1979.
  79. [Davis 1980].
    Davis, A., "Automating the Requirements Phase: Benefits to Later Phases of the Software Life Cycle," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1980, pp. 42-48. 
  80. [Davis 1982].
    Davis, G., "Strategies for Information Requirements Determination," IBM Systems Journal, 21, 1 (January 1982), pp. 4-30.
  81. [Davis 1982a].
    Davis, A., "Rapid Prototyping Using Executable Requirements Specifications," ACM Software Engineering Notes, 7, 5 (December 1982), pp. 39-44.
  82. [Davis 1982b].
    Davis, A., "The Design of a Family of Applications-Oriented Requirements Languages," IEEE Computer, 15, 5 (May 1982), pp. 21-28.
  83. [Davis 1982c].
    Davis, A., "The Role of Requirements in the Automated Synthesis for Real-Time Systems," International Symposium on Current Issues of Requirements Environments, Amsterdam: North Holland Publ., 1982, pp. 151-158.
  84. [Davis 1983].
    Davis, W, Systems Analysis and Design, Reading, Massachusetts: Addison-Wesley, 1983.
  85. [Davis 1983a].
    Davis, J., "Transfer of Automated Requirements Tool Technology - A Case Study," IEEE Workshop on Software Engineering Technology Transfer, Los Alamitos, California: IEEE Computer Society Press, 1983, pp. 30-33. 
  86. [Davis 1983b].
    Davis, A., "The software requirements specification guide task force," IEEE Software Engineering Standards Application Workshop, Los Alamitos, California: IEEE Computer Society Press, 1983, pp. 3-5. 
  87. [Davis and Addleman 1986].
    Davis, M., and D. Addleman, "Practical Approach to Specification Technology Selection," Journal of Systems and Software, 6 (1986), pp. 285-294.
  88. [Davis and Monroe 1987].
    Davis, G., and M. Monroe, "Commentary on the Problem of Information Requirements for Computer Applications," Accounting Horizons (December 1987), pp. 105-109.
  89. [Davis 1988].
    Davis, A., "A Comparison of Techniques for the Specification of External Behavior of Systems," Communications of the ACM, 31, 9 (September 1988), pp. 1098-1115.
  90. [Davis 1988a].
    Davis, A., "A Taxonomy of the Early Stages of the Software Development Life Cycle," Journal of Systems and Software, 8, 4 (September 1988), pp. 297-311.
  91. [Davis 1989].
    Davis, J., "Identification of Errors in Software Requirements Through the Use of Automated Requirements Tools," Information and Software Technology, 31 (November 1989), pp. 472-476.
  92. [Davis 1990].
    Davis, A., "System Testing: Implications of Requirements Specifications," Information and Software Technology, 32, 6 (July/August 1990), pp. 407-414.
  93. [Davis 1990a].
    Davis, A., "The Analysis and Specification of System and Software Requirements," in System and Software Requirements Engineering, R. Thayer and M. Dorfman, eds., Los Alamitos, California: IEEE Computer Society Press, 1990, pp. 119-144.
  94. [Davis 1990b].
    Davis, A., Software Requirements: Analysis and Specification, Upper Saddle River, New Jersey: Prentice Hall, 1990.
  95. [Davis and Jordan 1991].
    Davis, A., and K. Jordan, "Some Ideas on a Method-Independent Requirements Environment," 24th Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 1991, pp. 36-42.
  96. [Davis 1992].
    Davis, A., "Operational Prototyping: A New Development Approach," (see abstract) IEEE Software, 9, 5 (September 1992), pp. 70-78.
  97. [Davis 1993].
    Davis, A., Software Requirements: Objects, Functions and States, Upper Saddle River, New Jersey: Prentice Hall, 1993.
  98. [Davis, et al. 1993].
    Davis, A., et al., "Identifying and Measuring Quality in Software Requirements Specifications," IEEE-CS International Software Metrics Symposium, Los Alamitos, California: IEEE Computer Society Press, May 1993, pp. 141-152.
  99. [Davis and Sitaram 1993].
    Davis, A., and P. Sitaram, "A Concurrent Model for Software Development," ACM Software Engineering Notes, (March 1994).
  100. [Davis 1994].
    Davis, A., "Requirements Engineering," in Encyclopedia of Software Engineering, J. Marciniak, ed., New York, New York: Wiley-Interscience, 1994, pp. 1043-1054.
  101. [Davis and Hsia 1994].
    Davis, A., and P. Hsia, "Giving Voice to Requirements Engineering: Guest Editors' Introduction," (see abstract) IEEE Software, 11, 2 (March 1994), pp. 12-16.
  102. [Davis 1995].
    Davis, A., "Object Oriented Analysis to Object Oriented Design: An Easy Transformation?" Journal of Systems and Software, 30, 1 & 2, July-August 1995, pp. 151-159.
  103. [Davis 1995a].
    Davis, A., 201 Principles of Software Development, New York, New York: McGraw Hill, 1995, Chapter 3.
  104. [Davis 1995b].
    Davis, A., "Software Prototyping," in Advances in Computing, 40, M. Zelkowitz, ed., New York, New York: Academic Press, 1995.
  105. [Davis 1995c].
    Davis, A., "Tracing: A Simple Necessity Neglected," IEEE Software, 12, 5 (September 1995), pp. 6-7.
  106. [Davis, et al. 1997].
    Davis, A., et al., "Elements Underlying Requirements Specification," ( see abstract) Annals of Software Engineering, 3, N. Mead, ed., 1997.
  107. [Davis 1998].
    Davis, A., "The Harmony in Rechoirments," IEEE Software, 15, 2 (March/April 1998), pp. 6, 8.
  108. [Davis 1999].
    Davis, A., "Achieving Quality in Software Requirements," Software Quality Professional, 1, 3 (June 1999).
  109. [Davis and Leffingwell 1999].
    Davis, A., and D. Leffingwell, "Making Requirements Management Work For You," Crosstalk, 12, 4 (April 1999).
  110. [Davis and Zweig 2000].
    Davis, A., and A. Zweig, "Requirements Management Made Easy," PM Network Magazine, 14, 12 (December 2000).
  111. [Davis and Zweig 2000a].
    Davis, A., and A. Zweig, "Editor’s Corner: The Missing Piece of Software Development," Journal of Systems and Software 53, 3 (September 2000), pp. 205-206.
  112. [Davis and Hickey 2002].
    Davis, A., and A. Hickey, "Requirements Researchers: Do We Practice What We Preach?," Requirements Engineering Journal, 7, 2 (June 2002), pp. 107-111.
  113. [Davis 2002].
    Davis, A., "Secrets of Requirements Triage: The Most Important (and Most Ignored) Part of Requirements," International Symposium on Future Software Technology, Wuhan, China: Huazhong University of Science and Technology, 2002, pp. 1, 81-87.
  114. [Davis 2002a].
    Davis, A., "Requirements," in Encyclopedia of Software Engineering, J. Marciniak, ed., New York: Wiley-Interscience, 2002.
  115. [Davis 2002b].
    Davis, A., "Requirements Management," in Encyclopedia of Software Engineering, J. Marciniak, ed., New York: Wiley-Interscience, 2002.
  116. [Davis 2002c].
    Davis, A., "Requirements Engineering," in Encyclopedia of Software Engineering, J. Marciniak, ed., New York: Wiley-Interscience, 2002.
  117. [Davis 2003a].
    Davis, A., "The Art of Requirements Triage," IEEE Computer, 36, 3 (March 2003), pp. 42-49.
  118. [Davis 2003b].
    Davis, A., "System Phenotypes," Requirements Column, S. Robertson, ed., IEEE Software, 20, 4 (July/August 2003).
  119. [Davis, et al. 2004].
    Davis, A., et al., "Requirements Management in a Project Management Context," in
    The Wiley Guide to Managing Projects, P. Morris and J. Pinto, eds., New York: Wiley-Interscience, 2004, pp. 391-421.
  120. [Davis and Hickey 2004].
    Davis, A., and
    A. Hickey, "A New Paradigm for Planning and Evaluating Requirements Engineering Research," 2nd International Workshop on Comparative Evaluation in Requirements Engineering, Sydney, Australia: Faculty of Information Technology, University of Technology, Sydney, 2004, pp. 19-30.
  121. [Davis and Venkatesh 2004].
    Davis, F., and V. Venkatesh, "Toward Preprototype User Acceptance Testing of New Information Systems: Implications for Software Project Management," (see abstract) IEEE Transactions on Engineering Management, 15, 1 (January 2004), pp. 31-46. 
  122. [Davis 2005].
    Davis, A., Just Enough Requirements Management, New York: Dorset House, 2005.
  123. [Davis 2005a].
    Davis, A., "Keynote: Just Enough Requirements Management for Web Engineering," International Conference on Web Engineering, Lecture Notes in Computer Science 3579, Berlin: Springer, 2005, pp. 1-2.
  124. [Davis, et al. 2005].
    Davis, A.
    , A. Hickey, and A. Chamillard, "Moving Beyond the Classroom: Integrating Requirements Engineering Research and Education to Improve Practice," Requirements Engineering Workshop on Education and Training (REET), Paris, France, September 2005.
  125. [Davis and Zowghi 2006].
    Davis, A., and D. Zowghi, "Good requirements practices are neither necessary nor sufficient," ( see abstract) Requirements Engineering, 11, 1 (March 2006), pp. 1-3.
  126. [Davis, et al. 2006].
    Davis, A., et al. (primary author: O. Dieste), "Effectiveness of Requirements Elicitation Techniques: Empirical Results derived from a Systematic Review," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  127. [Davis, et al. 2006a].
    Davis, A., et al. (primary author: O. Dieste), "Scientific publication in requirements engineering in Spain: an analysis in a European context," IEEE Latin American Transactions, 4, 2 (April 2006), pp. 55-61.
  128. [Davis, et al. 2006b].
    Davis, C., et al., "Communication Challenges in Requirements Elicitation and the Use of the Repertory Grid Technique,"
    Journal of Computer Information Systems, 47 (2006), pp. 78-86.
  129. [Davis 2007].
    Davis, A., "
    Requirements for Services: Does it Make Sense?" 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. 451-452 (abstract only).
  130. [Davis and Hickey 2007].
    Davis, A., and
    A. Hickey, "An Ontological Approach to Requirements Elicitation Technique Selection," in Ontologies: A Handbook of Principles, Concepts and Applications in Information Systems, R. Sharman, R. Kishore, and R. Ramesh, eds., Berlin: Springer, 2007.
  131. [Davis and Nori 2007].
    Davis, A., and K. Nori, "
    Requirements, Plato's Cave, and Perceptions of Reality," 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. 487-492.
  132. [Davis, et al. 2007].
    Davis, A., et al., "A Quantitative Assessment of Requirements Engineering Publications - 1963-2006," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ' 07), Berlin: Springer, 2007.
  133. [Davis and Hickey 2008].
    Davis, A., and
    A. Hickey, "The Role of China in Requirements Research," in The China Information Technology Handbook, P. Ordóńez de Pablos and M. Lytras, eds., Berlin: Springer, 2008.
  134. [Davis, et al., 2008].
    Davis, A., et al., "Requirements Change: What's the Alternative?," IEEE International Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 2008.
  135. [Davison 2000].
    Davison, R., "The Role of Groupware in Requirements Specification," Group Decision and Negotiation,
    (2000).
  136. [Dawson and Swatman 1999].
    Dawson, L., and P. Swatman, "
    The Use of Object-Oriented Models in Requirements Engineering: A Field Study," 20th International Conference on Information Systems, Atlanta, GA: Association for Information Systems, 1999, pp. 260-273.
  137. [Day, et al. 1987].
    Day, W., et al., "
    Logic programming applied to requirements and specifications," ACM SOUTHEASTCON, New York: ACM Press, 1987, pp. 525-529.
  138. [Dean, et al. 1997].
    Dean, D., et al., "Enabling the Effective Involvement of Multiple Users: Methods and Tools for Collaborative Software Engineering," Journal of Management Information Systems, 14, 3 (1997), pp. 179-222.

    de Antonellis, see Antonellis
    de Backus, see Backus
     
  139. [DeBellis and Haapala 1995].
    DeBellis, M., and C. Haapala, "User Centric Software Engineering," IEEE Expert (1995), pp. 34-41.
  140. [Debnath, et al., 2008].
    Debnath, N., et al., "Improving Model Driven Architecture with Requirements Models," International Conference on Information Technology, Los Alamitos, California: IEEE Computer Society Press, 2008.

    de Boer, see Boer
    de Bruijn, see Bruijn
    de Carli, see Carli
    de Cesare, see Cesare
     

  141. [Deck 2008].
    Deck, P., "Guest viewpoint: Contractors need to adopt next-generation, requirements-management technology," Military and Aerospace Electronics,
    (2008).
  142. [Dedeke and Lieberman 2006].
    Dedeke, A., and B. Lieberman, "Qualifying Use Case Diagram Associations," IEEE Computer, 39, 6,
    (June 2006), pp. 23-29.
  143. [DeFoe 1994].
    DeFoe, J., "Requirements Engineering Technology in Industrial Education," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 145.
  144. [DeFoe 1994a].
    DeFoe, J., "Teaching the Generation of Operations Based Requirements," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 45-48.
  145. [DeFoe and McAuley 1994].
    DeFoe, J., and J. McAuley, "Generating Operations Based Requirements," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 113-119.
  146. [DeFoe and Sheard 1995].
    Defoe, J., and S. Sheard, "Suggestions for Requirements Model Robustness," Fifth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
  147. [Degl'Innocenti, et al. 1990].
    Degl'Innocenti, M., et al., "RSF: A formalism for executable requirement specifications," IEEE Transactions on Software Engineering, 16, 11 (November 1990), pp. 1235-1246.
  148. [Dehlinger and Lutz 2005].
    Dehlinger, J., and R. Lutz, "A product-line requirements approach to safe reuse in multi-agent systems," ACM Software Engineering Notes, 30, 4 (May 2005).
  149. [Dehlinger, et al. 2007].
    Dehlinger, J., et al., "DECIMAL and PLFaultCAT: From Product-Line Requirements to Product-Line Member Software Fault Trees," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  150. [Dehlinger and Lutz 2008].
    Dehlinger, J., and R. Lutz, "Supporting requirements reuse in multi-agent system product line design and evolution," International Conference on Software Maintenance, Los Alamitos, California: IEEE Computer Society Press, 2008.
  151. [Deifel 1998].
    Deifel, B., "Requirements Engineering for Complex COTS," Fourth International Workshop on Requirements Engineering: Foundations for Software Quality, Pisa, Italy, June 1998.
  152. [Deifel 1999].
    Deifel, B., "A Process Model for Requirements Engineering," Tenth International Workshop on Database and Expert Systems Applications, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 316-320.
  153. [Dekhtyar, et al. 2007].
    Dekhtyar, A., et al., "Technique Integration for Requirements Assessment,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  154. [Dekkers and Aguiar 2000].
    Dekkers, C., and M. Aguiar, "Double Duty Metrics," Cutter IT Journal, 13, 5 (May 2000).
  155. [Dekkers 2001].
    Dekkers, M., "Requirements Engineering Is Essential for Successful Projects," Informatie, 43 (2001), pp. 58ff (The Netherlands).
  156. [Dekkers and Aguiar 2001].
    Dekkers, C., and M. Aguiar, "Applying Function Point Analysis to Requirements Completeness," CrossTalk, (February 2001).

    de Landtsheer, see Landtsheer
    de Lemos, see Lemos
     
  157. [Delgadillo and Gotel 2007].
    Delgadillo, L., and O. Gotel, "Story-Wall: A Concept for Lightweight Requirements Management,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  158. [Del Gobbo and Mili 2001].
    Del Gobbo, D., and A. Mili, "Re-engineering fault tolerance requirements: a case study in specifying fault tolerant flight control systems," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 236-245.
  159. [Della Penna, et al. 2006].
    Della Penna, G., et al., "An XML environment for scenario based requirements engineering," Journal of Systems and Software, 79, 3 (March 2006), pp. 379-403.
  160. [DeLozier 1991].
    DeLozier, R., "Pond Waste Management Project: A Tailored Systems Engineering Approach for Requirements Management," International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 1991.
  161. [Delugach 1992].
    Delugach, H., "Specifying Multiple-Viewed Software Requirements with Conceptual Graphs," The Journal of Systems and Software, 19, 3 (November 1992), pp. 207-224.
  162. [Delugach and Lampkin 2001].
    Delugach, H., and B. Lampkin, " Acquiring Software Requirements as Conceptual Graphs," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 296-297.
  163. [DeMarco 1979].
    DeMarco, T., Structured Analysis and System Specification, Upper Saddle River, New Jersey: Prentice Hall, 1979.
  164. [DeMarco and Lister 2003].
    DeMarco, T., and T. Lister, "Risk Management during Requirements," IEEE Software, 20, 5 (September-October 2003), pp. 99-101.
  165. [Demetrovics, et al. 1982].
    Demetrovics, J., et al., "Specification Meta Systems," IEEE Computer, 15, 5 (May 1982), pp. 29-35.
  166. [Demircan, et al. 2005].
    Demircan, H., et al., "
    Service Level Agreement Negotiation: A Theory-based Exploratory Study as a Starting Point for Identifying Negotiation Support System Requirements," 38th Hawaii Conference on Systems Sciences, Los Alamitos, California: IEEE Computer Society Press, 2005, p. 188a.
  167. [Demirors 1997].
    Demirors, E., "A Blackboard Framework for Supporting Teams in Software Development," Ninth International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, June 1997, pp. 232-239.
  168. [Dengel and Klein 2002].
    Dengel, A., and B. Klein, "A Requirements-Driven System for Document Analysis and Understanding," Lecture Notes in Computer Science, Volume 2423, Berlin: Springer, 2002, pp. 433ff. 
  169. [Denger, et al. 2003].
    Denger, C., et al., "
    Higher Quality Requirements Specifications through Natural Language Patterns," IEEE International Conference on Software: Science, Technology, and Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 80-90.
  170. [Denger and Olsson 2005].
    Denger, C., and T. Olsson, "Quality Assurance in Requirements Engineering," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 163-185.
  171. [Denger, et al. 2005].
    Denger, C., et al., "Achieving High Quality of Use-Case-Based Requirements," Informatik -- Forschung und Entwicklung (October 2005), pp. 46ff.
  172. [Dennis, et al. 1999].
    Dennis, A., et al., "Business Process Modeling with Group Support Systems," Journal of Management Information Systems, 15, 4 (Spring 1999), pp. 115-142.
  173. [Dennis, et al. 2001].
    Dennis, A., et al., Systems Analysis and Design : An Object-Oriented Approach with UML, New York, New York: John Wiley and Sons, 2001.
  174. [Deraitus and Miller 2003].
    Deraitus, M., and A. Miller, "Customer Requirements and User Requirements: Why the Discrepencies?,"
    11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 279.
  175. [Deshmukh and Wadhwa 2007].
    Deshmukh, N., and S. Wadhwa, "A Meta Model for Iterative Development of Requirements Leveraging,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  176. [Deursen 2001].
    van Deursen, A., "Customer Involvement in Extreme Programming: XP2001 Workshop Report," ACM Software Engineering Notes, 26, 6 (November 2001).
  177. [Deutsch 1988].
    Deutsch, M., "Focusing Real-Time Systems Analysis on User Operations," IEEE Software, 5, 5 (September 1988), pp. 39-50.
  178. [Dewal and Kelter 1989].
    Dewal, S., and U. Kelter, "Role-based requirements definition for software factories using reusable requirements package," Software Engineering Environments: Research and Practice, London: IEE, 1989, pp. 351-370.
  179. [van Dewerker and Booth 1996].
    van DeWerker, F., and S, Booth, "Requirements Consistency-A Basis for Design Quality," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
  180. [DeWolfe 1977].
    DeWolfe, J., "Requirements Specification and Preliminary Design for Real-Time Systems," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1977, pp. 17-23. 
  181. [Diallo, et al. 2006].
    Diallo, M., et al., "A Comparative Evaluation of Three Approaches to Specifying Security Requirements," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
  182. [DiAngelo and Petrun 1995].
    DiAngelo, M., and C. Petrun, "Collecting Product-Based Usability Requirements," IBM Systems Journal, 34, 1 (January 1995), pp. 4-19.

    Díaz, see also Sánchez-Díaz
     
  183. [Diaz, et al. 2001].
    Diaz, J., et al., "From User Requirements to User Interfaces: A Methodological Approach," 13th International Conference on Advanced Information Systems Engineering (CAiSE), Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 60-75.
  184. [Díaz, et al. 2004].
    Díaz, I., et al., " A Specification Pattern for Use Cases," Information and Management, (April 2004).
  185. [Díaz, et al. 2005].
    Díaz, I., et al., "Modeling Interactions Using Role-Driven Patterns," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 209-220.
  186. [Díaz, et al. 2005a].
    Díaz, I., et al., "Integrating Natural Language Techniques in OO-Method," International Conference on Computational Linguistics and Intelligent Text Processing, Berlin: Springer, 2005, pp. 560ff.
  187. [Díaz, et al. 2007].
    Díaz, J., et al., "Testing time goal-driven requirements with Model Checking Techniques," Conference and Workshop on Systems Engineering of Computer-Based Systems (ECBS), Los Alamitos, California: IEEE Computer Society Press, 2007.
  188. [Diaz-Gonzalez and Urban 1989].
    Diaz-Gonzalez, J, and J. Urban, "A Requirements Engineering Environment for Real-Time Systems," 22nd Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 1989.
  189. [Díaz-Redondo, et al. 2003].
    Díaz-Redondo, R., et al., "Reuse of Formal-Verification Efforts of Incomplete Models at the  Requirements Specification Stage," Lecture Notes in Computer Science, Volume 2693, Berlin: Springer, 2003, pp. 326-351. 
  190. [Díaz-Redondo, et al. 2004].
    Díaz-Redondo, R., et al., "Supporting Software Variability by Reusing Incomplete Models at the  Requirements Specification Stage," Lecture Notes in Computer Science, Volume 3107, Berlin: Springer, 2004, pp. 1-10. 
  191. [Dick 1992].
    Dick, M., "The Supertool: QFD, Structured Analysis & Concurrent Engineering Combined," Second Annual International Symposium on Requirements Engineering, Seattle, Washington: International Council on Systems Engineering, July 1992.
  192. [Dick 2006].
    Dick, J., "A Requirements Guide For All (REGAL): an INCOSE Initiative ," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
  193. [Dick, et al. 2006].
    Dick, J., et al., "A Requirements Guide for All (REGAL)," Sixteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2006.
  194. [Diepstraten 1995].
    Diepstraten, M., "Command and Control System Requirements Analysis and System Requirements Specification for a Tactical System," First IEEE International Conference on Engineering of Complex Computer Systems, Los Alamitos, California: IEEE Computer Society Press, November 1995.
  195. [Dierks and Lettrari 2002].
    Dierks, H., and M. Lettrari, "Constructing Test Automata from Graphical Real-Time Requirements," Lecture Notes in Computer Science, Volume 2460, Berlin: Springer, 2002, pp. 433-453. 
  196. [Dieste, et al. 1999].
    Dieste, ó., et al., "On the Capability of Analysis Techniques in Requirements Engineering," IFIP International Workshop on the Evaluation of Modeling Methods in Systems Analysis and Design (EMMSAD), 1999.
  197. [Dieste and Silva 2000].
    Dieste,
    ó., and A. Silva, "Requirements: Closing the Gap Between Domain and Computing Knowledge," International Conference on Information Systems, Analysis and Synthesis, Volume II, 2000.
  198. [Dieste, et al. 2000].
    Dieste,
    ó., et al., "A Proposal for a Requirements Engineering Process Focused on the User Need," ACIS International Conference on Software Engineering Applied to Networking and Distributed Computing (SNPD), Springer Verlag, 2000.
  199. [Dieste 2001].
    Dieste,
    ó. "Development-Paradigm Independent Conceptual Models," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2001.
  200. [Dieste 2003].
    Dieste,
    ó., Analysis Method for Multi-Paradigm Conceptual Modeling, PhD Dissertation, Polytechnic University of Madrid, Madrid, Spain, 2003.
  201. [Dieste, et al. 2003].
    Dieste,
    ó., et al., "A Conceptual Model Completely Independent of Implementation Paradigm," Journal of Systems and Software, 68, 3 (December 2003), pp. 183-198.
  202. [Dieste, et al. 2008].
    Dieste,
    ó., et al., "Understanding the Customer: What Do We Know about Requirements Elicitation?," IEEE Software, 25 (2008).
  203. [Dieste, et al. 2008a].
    Dieste,
    ó., et al., "Obtaining Well-Founded Practices about Elicitation Techniques by Means of an Update of a Previous Systematic Review," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2008.
  204. [Diethelm, et al. 2005].
    Diethelm, H., et al., "
    Applying Story Driven Modeling to the Paderborn Shuttle System Case Study," Lecture Notes in Computer Science 3466, Berlin: Springer, 2005, pp. 109-133.
  205. [Dietz and Albani 2005].
    Dietz, J., and A. Albani, "Basic Notions Regarding Processes and Supporting Information Systems," Requirements Engineering, 10, 3 (November 2005), pp. 175-183.
  206. [Dietze 2005].
    Dietze, S.
    ,
    "Collaborative Requirements Definition Processes in Open Source Software Development," in Requirements Engineering for Sociotechnical Systems, J. Maté, and A. Silva, eds., Hershey, Pennsylvania: Information Science Publishing, 2005, pp. 189-208.
  207. [Diev 2007]
    Diev, S., "Structuring complex requirements," ACM Software Engineering Notes, (2007).
  208. [Diev 2007a]
    Diev, S., "Requirements development as a modeling activity," ACM Software Engineering Notes, (2007).
  209. [Dilworth and Kochhar 2007].
    Dilworth, J., and R. Kochhar, "Creation of an e-business requirements specification model," Journal of Manufacturing Technology Management (2007). 
  210. [Ding and Katayama 1993].
    Ding, S., and T. Katayama, "Specifying Reactive Systems With Attributed Finite State Machines," IEEE International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, December 1993.
  211. [Dinkle and Baumgarten 2005].
    Dinkle, M., and U. Baumgarten, "Modeling nonfunctional requirements: a basis for dynamic systems management," ACM Software Engineering Notes, 30, 4 (May 2005).
  212. [Dittmar, et al. 2007].
    Dittmar, A., "Requirements Elicitation and Elaboration in Task-Based Design Needs More Than Task Modelling: A Case Study," International Workshop on Task Models and Diagrams for Users Interface Design, Berlin: Springer, 2007.
  213. [DiVito 2000].
    DiVito, B., "High Automation Proofs for Properties of Requirements Models," Journal of Software Tools for Technology Transfer, 3, 1 (September 2000), pp. 20-31.
  214. [Djebbi and Salinesi 2006].
    Djebbi, O., and C. Salinesi, "Criteria for Comparing Requirements Variability Modeling Notations for Product Development," IEEE International Workshop on Comparative Evaluation in Requirements Engineering (CERE), Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 20-35.
  215. [Djebbi and Salinesi 2007].
    Djebbi, O., and C. Salinesi, "RED-PL, a Method for Deriving Product Requirements from a Product Line Requirements Model," Advanced Information Systems Engineering, Berlin: Springer, 2007.
  216. [Djebbi, et al. 2007].
    Djebbi, O., etal., "Industry Survey of Product Lines Management Tools: Requirements, Qualities and Open Issues,"
    IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  217. [Djebbi, et al. 2008].
    Djebbi, O., et al., "Deriving product line requirements: the RED-PL guidance approach," Asia-Pacific Software Engineering Conference (APSEC), Los Alamitos, California: IEEE Computer Society Press, 2008, pp. 494-501.
  218. [Djouab and Suryn 2006].
    Djouab, R., and W. Suryn, "An ISO/IEC standards-based quality requirement definition approach: Applicative analysis of three quality requirements definition methods," IEEE International Symposium on Industrial Electronics, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 3231-3239.
  219. [Dobson 1992].
    Dobson, J., The ORDIT Project, University of Newcastle Report #01-92, June 1992.
  220. [Dobson, et al. 1992].
    Dobson, J., et al., "The ORDIT Approach to Requirements Identification," IEEE International Conference on Computer Software and Applications, Los Alamitos, California: IEEE Computer Society Press, 1992, pp. 356-361.
  221. [Dobson and Strens 1993].
    Dobson, J., and M. Strens, "How Responsibility Modelling Leads to Security Requirements," New Security Paradigms Workshop, Little Compton, Rhode Island, August 1993. Also available as University of Newcastle Technical Report #NSPW, Newcastle, UK.
  222. [Dobson, et al. 1994].
    Dobson, J., et al., "The ORDIT Approach to Organizational Requirements," in Requirements Engineering Social and Technical Issues, M. Jirotka, and J. Goguen, eds., London: Academic Press, 1994.
  223. [Dobson and Strens 1994].
    Dobson, J., and R. Strens, "Organizational Requirements Definition for Information Technology," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 158-165.
  224. [Doernhoefer 1997]
    Doernhoefer, M., "Object-Oriented Specification Documentation: Building Requirement Specifications from OO Models," CrossTalk (June 1997).

    Doerr, see Dörr
     
  225. [Dogru, et al. 1992].
    Dogru, A., et al., "An Integrated System Design Environment: Concepts and a Status Report," Journal of Systems Integration, 3 (1992).
  226. [Doke 1990].
    Doke, E., "An Industry Survey of Emerging Prototyping Methodologies," Information and Management, 18, 4 (April 1990), pp. 169-176.
  227. [Donat and Joyce 1991].
    Donat, M., and J. Joyce, "Applying an Automated Test Description Tool to testing Based on System Level Requirements," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1991.
  228. [Dong, et al. 2003].
    Dong, W., et al., "An Approach to Model Checking UML Statecharts," Journal of Software, 14, 4 (April 2003), pp. 750-756.
  229. [Donzelii and Setola 2002].
    Donzelli, P., and R. Setola, "Handling the Knowledge Acquired during the Requirements Engineering Process: A Case Study," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2002, pp. 379ff.
  230. [Donzelli and Bresciani 2003].
    Donzelli, P., and P. Bresciani, "Domain Ontology Analysis in Agent-Oriented Requirements Engineering," Lecture Notes in Computer Science, Volume 2773, Berlin: Springer, 2003, pp. 1372-1379. 
  231. [Donzelli and Bresciani 2003a].
    Donzelli, P., and P. Bresciani, "Goal-Oriented Requirements Engineering: A Case Study in E-Government," Lecture Notes in Computer Science, Volume 2681, Berlin: Springer, 2003, pp. 601-616. 
  232. [Donzelli 2004].
    Donzelli, P., "A Goal-Driven and Agent-Based Requirements Engineering Framework," Requirements Engineering, 9, 1 (February 2004), pp. 16-39.
  233. [Donzelli and Bresciani 2004].
    Donzelli, P., and P. Bresciano, "Improving Requirements Engineering by Quality Modelling -- A Quality-Based Requirements Engineering Framework," Journal of Research and Practice in Information Technology, 36, 4 (November 2004). pp. 277-294.
  234. [Donzelli and Basili 2006].
    Donzelli, P., and V. Basili, "A Practical Framework for Eliciting and Modeling System Dependability Requirements: Experience from the NASA High Dependability Computing Project," Journal of Systems and Software, 79, 1 (January 2006), pp. 107-119.
  235. [Dooley 1978].
    Dooley, J., "Vast Compatibility Program (VCOMP): A UUT Requirements Analysis Tool," IEEE Automated Test Conference, Los Alamitos, California: IEEE Computer Society Press, 1978, pp. 389-394. 
  236. [Dooley, et al. 1980].
    Dooley, B., et al., "Experience with Software Tools for Nuclear Process System Applications," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1980, pp. 646-654. 
  237. [Dorfman and Flynn 1984].
    Dorfman, M., and R. Flynn, "ARTS -- An Automated Requirements Traceability System," Journal of Systems and Software, 4, 4 (1984), pp. 63-74. 
  238. [Dorfman 1990].
    Dorfman, M., "System and Software Requirements Engineering," in System and Software Requirements Engineering, R. Thayer and M. Dorfman, eds., Los Alamitos, California: IEEE Computer Society Press, 1990.
  239. [Dorfman and Thayer 1990].
    Dorfman, M., and R. Thayer, Standards, Guidelines, and Examples of System and Software Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1990.
  240. [Dori, et al. 2004].
    Dori, D., et al., "SMART: System Modeling Acquisition from Requirement Text," Lecture Notes in Computer Science, Volume 3080, Berlin: Springer, 2004, pp. 179-194. 
  241. [Dörr, et al. 2003].
    Dörr, J., et al., "Eliciting Efficiency Requirements with Use Cases," International Workshop on Requirements Engineering: Foundations for Software Quality, 2003.
  242. [Dörr, et al. 2004].
    D
    örr, J., et al., "Requirements Engineering Process Improvement Based on an Information Model," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004.
  243. [Dörr, et al. 2005].
    D
    örr, J., et al., "Non-Functional Requirements in Industry -- Three Case Studies Adopting and Experience-Based NFR Model," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 373-384.
  244. [Dörr, et al. 2007].
    D
    örr, J., et al., "Built-in User Satisfaction - Feature Appraisal and Prioritization with AMUSE," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
  245. [Dörr, et al. 2008].
    D
    örr, J., et al., "Supporting requirements engineering for medical products: early consideration of user-perceived quality," IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2008, pp. 639-648.
  246. [Dörr, et al. 2008a].
    Dörr, J., et al. "Implementing requirements engineering processes: Using cooperative self-assessment and improvement," IEEE Software, 25, 3 (May-June 2008), pp. 71-77.
  247. [dos Santos Soares and Vrancken 2007].
    dos Santos Soares, M., and J. Vrancken, "Requirements specification and modeling through SysML," International Conference on Systems Man and Cybernetics, Los Alamitos, California: IEEE Computer Society Press, 2007.
  248. [Downing and Fickas 1991].
    Downing, K., and S. Fickas, "Specification Criticism Via Goal-Directed Environment," IEEE International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1991, pp. 22-30.
  249. [Draheim 2005].
    Draheim, D., "
    Tutorial 7: Modeling Enterprise Applications," Lecture Notes in Computer Science 3770, Berlin: Springer, 2005, pp. 473-474.
  250. [Drake, et al. 1992].
    Drake, J., et al., "Document-Driven: Description and Formalism," Journal of Object-Oriented Programming, November-December 1992.
  251. [Drake, et al. 1993].
    Drake, J., et al., "Approach and Case Study of Requirements Analysis Where End Users Take an Active Role," 15th IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, May 1993, pp. 177-186.
  252. [Drake and Tsai 1994].
    Drake, J., and W. Tsai, "System Bounding Issues for Analysis," ( see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 24-31.
  253. [Draper 1999].
    Draper, S., "Analysing fun as a candidate software requirement," Personal and Ubiquitous Computing, 3, 3 (September 1999).
  254. [Driewer, et al. 2005].
    Driewer, F., et al., "Robot-human rescue teams: a user requirements analysis," Advanced Robotics, 19, 8 (October 2005), pp. 819-838
  255. [Dromey 2003].
    Dromey, R., "From Requirements to Design: Formalizing the Key Steps," First International Conference on Software Engineering and Formal Methods, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 2-11. 
  256. [Dromey 2005].
    Dromey, R., "Genetic Design: Amplifying Our Ability to Deal with Requirements Complexity," International Workshop on Scenarios, Lecture Notes in Computer Science 3466, Berlin: Springer, 2005, pp. 95ff.
  257. [Dromey 2006].
    Dromey, R., "Scaleable Formalization of Imperfect Knowledge," Asian Working Conference on Verified Software (AWCVS), 2006. 
  258. [Drusinky 2006].
    Drusinsky, D., Modeling and Verification of UML Statecharts, Elsevier (Newnes), 2006.
  259. [Dssouli, et al. 1999].
    Dssouli, R., et al., "A Service Creation Environment Based on Scenarios," Information and Software Technology, (1999). 
  260. [Duan, et al. 2008].
    Duan, C., et al., "A consensus based approach to constrained clustering of software requirements," Conference on Information and knowledge mining (CIKM), New York: ACM Press, 2008.
  261. [Dubois, et al. 1982].
    Dubois, E., et al., "Towards a Deductive Approach to Information System Specification and Design," International Symposium on Current Issues of Requirements Environments, 1982.
  262. [Dubois, et al. 1986].
    Dubois, E., et al., "A Knowledge-Representation Language for Requirements Engineering," Proceedings of the IEEE, 74, 10 (October 1986), pp. 1431-1444.
  263. [Dubois, et al. 1988].
    Dubois, E., et al., "Formal Requirements Engineering with ERAE," Philips Journal of Research, 43, 3-4 (1988), pp. 393-414.
  264. [Dubois 1990].
    Dubois, E., "Logical Support for Reasoning About the Specification and the Elaboration of Requirements," in Artificial Intelligence in Databases and Information Systems, R. Meersman, et al., eds., Oxford, U.K.: Elsevier Science Publishers, pp. 79-98.
  265. [Dubois, et al. 1993].
    Dubois, E., et al., "Eliciting and Formalising Requirements for C. I. M. Systems," Fifth Conference on Advanced Information Systems Engineering, Paris, France, June 1993.
  266. [Dubois, et al. 1993a].
    Dubois, E., "O-O Requirements Analysis: An Agent Perspective," European Conference on Object-Oriented Programming, Lecture Notes in Computer Science 707, Berlin: Springer, 1993, pp. 458ff.
  267. [Dubois, et al. 1994].
    Dubois, E., et al., "ALBERT: An Agent-Oriented Language for Building and Eliciting Requirements for Real-Time Systems," Twenty-Seventh Hawaii International Conference on System Science, Volume IV, Los Alamitos, California: IEEE Computer Society Press, 1994, pp. 713-722.
  268. [Dubois 1995].
    Dubois, E., The Albert II Language -- On the Design and the Use of a Formal Specification Language for Requirements Analysis, PhD Dissertation, Computer Science Department, University of Namur, Namur, Belgium, 1995.
  269. [Dubois 1998].
    Dubois, E., "ALBERT: A Formal Language and Its Supporting Tools for Requirements Engineering," International Conference on Fundamental Approaches to Software Engineering, Lecture Notes in Computer Science 1382, Berlin: Springer, 1998, pp. 322ff.
  270. [Dubois and Pohl 2003].
    Dubois, E., and K. Pohl, "Guest Editors' Introduction: A Major Step Toward a Mature Requirements Engineering Community," IEEE Software, 20, 1 (January-February 2003), pp. 14-15.
  271. [Dubois and Pohl 2003a].
    Dubois, E., and K. Pohl, "RE'02: The Birth of a New Flagship Conference in Requirements Engineering," Requirements Engineering, 8, 3 (August 2003), pp. 147-148.
  272. [Duboc, et al. 2008].
    Duboc, L., et al., "A Case Study in Eliciting Scalability Requirements," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2008.
  273. [Ducamp and Lagarrigue 2007].
    Ducamp, C., and A. Lagarrigue, "MV2 Tool: A Management Tool for the Validation and Verification of Requirements by Airbus," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2007.
  274. [Ducq, et al 2004].
    Ducq, Y., et al., "
    Interoperability in enterprise modelling: Requirements and roadmap," Advanced Engineering Informatics, 18, 4 (October 2004), pp. 193-203.
  275. [Duffy, et al. 1995].
    Duffy, D., et al., "A Framework for Requirements Analysis Using Automated Reasoning," (see abstract) Seventh International Conference on Advanced Information Systems Engineering (CAiSE '95), Springer-Verlag, 1995.
  276. [Duggan 2003].
    Duggan, E., "Generating Systems Requirements with Facilitated Group Techniques," Human Computer Interaction, 18, (2003), pp. 373-394.
  277. [Duggan and Thachenkary 2003].
    Duggan, E., and C. Thachenkary, "Higher Quality Requirements: Supporting Joint Application Development with a Nominal Group Technique," Information Technology and Management, 4, 4 (2003), pp. 391-408.
  278. [Duke and Harrison 1995].
    Duke, D., and M. Harrison, "Mapping User Requirements to Implementations," (see abstract) Software Engineering Journal, 10, 1 (January 1995), pp. 13-20.
  279. [Dulac, et al. 2002].
    Dulac, N., et al., "On the Use of Visualization in Formal Requirements Specification," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  280. [Duncan 2001].
    Duncan, R., "The Quality of Requirements in Extreme Programming," Crosstalk, (June 2001).
  281. [Dunn 1994].
    Dunn, J., "Give Them What They Asked For," The Engineer, 278 (March 24, 1994), p. 23.

    Duque, see Garcia-Duque
     
  282. [Durán, et al. 1999].
    Durán, A., et al., "Expressing Customer Requirements Using Natural Language Requirements Templates and Patterns," in Modern Applied Mathematics Techniques in Circuits, Systems and Control, N. E. Mastorakis, ed., World Scientific and Engineering Society Press, Athens, Greece, 1999, pp. 337-342.
  283. [Durán 2000].
    Durán, A., Un Entorno Metodológico de Ingeniería de Requisitos para Sistemas de Información Ph.D. Dissertation, University of Sevilla, Sevilla, Spain, 2000.
  284. [Durán and Toro 2002].
    Durán, A., and M. Toro, eds., Applying Requirements Engineering, Salamanca, Spain: Catedral Publ., 2002.
  285. [Durán, et al. 2002].
    Durán, A., et al., "Verifying Software Requirements with XSLT," ACM Software Engineering Notes, 27 (2002), pp. 39ff.
  286. [Durán, et al. 2002a].
    Durán, A., et al., "Assisting the Requirements Verifier with XML Technology," 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. 127-137.
  287. [Durán, et al. 2002b].
    Durán, A., et al., "An Automated Approach for the Verification of Software Requirements Using Web Technologies," in Applying Requirements Engineering, Duran, A., and M. Toro, eds., Salamanca, Spain: Catedral Publ., 2002, pp. 35-55.
  288. [Durán, et al. 2004].
    Durán, A., et al., "Applying System Families Concepts to Requirement Engineering Process Definition," Lecture Notes in Computer Science, Volume 3014, Berlin: Springer, 2004, pp. 140-151. 
  289. [Durant 2007].
    Durant, E., "Combining requirements and interdisciplinary work," Annual ASEE Conference and Exposition, Washington, DC: American Society for Engineering Education, 2007.
  290. [Dusire, et al. 2002].
    Dusire, S., et al., " Requirements Engineering - Applying Theory to Reality," Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
  291. [Dustin 2003].
    Dustin, E., Effective Software Testing: 50 Specific Ways to Improve Your Testing, Boston, Massachusetts: Addison Wesley, 2003, Chapters 1-5.
  292. [Dusting 2001].
    Dusting, J., "The Importance of Business Systems Definition in Requirements Definition-A Case Study of Two,"
    International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2001.
  293. [Dutetre and Stavridou 1997].
    Dutetre, B., and V. Stavridou, "Formal Requirements Analysis of an Avionics Control System," (see abstract) IEEE Transactions on Software Engineering, 23, 5 (May 1997), pp. 267-278.
  294. [Dutoit and Paech 2000].
    Dutoit, A., and B. Paech, "Supporting Evolution: Using Rationale in Use Case Driven Software Development," Sixth International Workshop on Requirements Engineering: Foundations for Software Quality, Stockholm, Sweden, June 2000.
  295. [Dutoit and Paech 2001].
    Dutoit, A., and B. Paech, "Developing Guidance and Tool Support for Rationale-Based Use Case Specification," Seventh International Workshop on Requirements Engineering: Foundations for Software Quality, Interlocken, Switzerland, June 2001.
  296. [Dutoit and Paech 2002].
    Dutoit, A., and B. Paech, "Rationale-Based Use Case Specification," ( see abstract) Requirements Engineering Journal, 7, 1 (2002), pp. 3-19.
  297. [Dutton 1984].
    Dutton, C., "Requirements Tools: Phase I in a Software Development Methodology," ACM Software Engineering Notes, 9, 1 (January 1984), pp. 19-23. 

 

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