cole

[ar

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

© 1996 - 2008, Alan M. Davis

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

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

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

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. [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.
  9. [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.
  10. [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.
  11. [Ä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).
  12. [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.
  13. [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.
  14. [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.
  15. [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.
  16. [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.
  17. [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.
  18. [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.
  19. [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.
  20. [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.
  21. [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.
  22. [Adolph, et al. 2003].
    Adolph, S., et al., Patterns for Effective Use Cases, Boston, Massachusetts: Addison Wesley, 2003.
  23. [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.
  24. [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.
  25. [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.
  26. [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.
  27. [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.
  28. [Ĺ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.
  29. [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.
  30. [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.
  31. [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.
  32. [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.
  33. [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.
  34. [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.
  35. [Ahmed, et al. 2007].
    Ahmed, F., et al., "Exploring Traceability-based Requirements Inspection," IASTED International Conference on Software Engineering and Applications (SEA), 2007.
  36. [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.
  37. [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.
  38. [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.
  39. [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.
  40. [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.
  41. [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, (2008).
  42. [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.
  43. [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.
  44. [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.
  45. [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.
  46. [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.
  47. [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.
  48. [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.
  49. [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.
  50. [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.
  51. [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.
  52. [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
     
  53. [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
     
  54. [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.
  55. [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.
  56. [Alderson 1999].
    Alderson, A., "False Requirements Express Real Needs," (see abstract) Requirements Engineering Journal, 4, 1 (1999), pp. 60-61.
  57. [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.
  58. [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.
  59. [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.
  60. [Alexander 1997].
    Alexander, I., "A Historical Perspective on Requirements," Requirenautics Quarterly, 12 (October 1997), pp. 13-20.
  61. [Alexander 1998].
    Alexander, I., "Why You Need Requirements Engineering," Requirenautics Quarterly, 15 (October 1998), pp. 9-10.
  62. [Alexander 1999].
    Alexander, I., "Extreme Programming: Rapid Requirements," Requirenautics Quarterly, 14 (1999).
  63. [Alexander 1999a].
    Alexander, I., "Do User Requirements Exist?" Requirenautics Quarterly, 14 (1999).
  64. [Alexander 1999b].
    Alexander, I., "Is There Such a Thing as a User Requirements?" (see abstract) Requirements Engineering Journal, 4, 4 (1999), pp. 221-223.
  65. [Alexander 1999c].
    Alexander, I., "Migrating Towards Cooperative Requirements Engineering," Computing and Control Engineering Journal, 10, 1 (February 1999), pp. 17-22.
  66. [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.
  67. [Alexander 2001].
    Alexander, I., "What is Requirements Engineering Anyway?" Requirenautics Quarterly, 16 (1999).
  68. [Alexander 2001a].
    Alexander, I., "Requirements Are Either Needs or Specifications," Requirenautics Quarterly, 16 (1999).
  69. [Alexander 2001b].
    Alexander, I., "On Abstraction in Scenarios," Requirements Engineering Journal, 6, 4 (2001), pp. 252-255.
  70. [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.
  71. [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.
  72. [Alexander and Stevens 2002].
    Alexander, I., and R. Stevens, Writing Better Requirements, London, UK: Addison-Wesley, 2002.
  73. [Alexander 2003].
    Alexander, I., "Misuse Cases: Use Cases with Hostile Intent," IEEE Software, 20, 1 (January-February 2003), pp. 58-66.
  74. [Alexander 2003a].
    Alexander, I., "Misuse Cases Help to Elicit Non-Functional Requirements," Computing and Control Engineering, 14, 1 (February 2003), pp. 40-45.
  75. [Alexander 2003b].
    Alexander, I., "Stakeholders: Who Is Your System For?," (see abstract) Computing and Control Engineering, 14, 2 (March 2003).
  76. [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.
  77. [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.
  78. [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.
  79. [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.
  80. [Alexander 2005].
    Alexander, I., "Book Review: Agile or Analytic: Cohn vs. Lavi and Kudish," Requirements Engineering, 10, 4 (December 2005), pp. 307-308.
  81. [Alexander 2006].
    Alexander, I., "10 Small Steps to Better Requirements" IEEE Software, 23, 2 (March-April 2006), pp. 19-21.
  82. [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.
  83. [Alexander 2007].
    Alexander, I., "Building What Stakeholders Desire (Point Counterpoint)," IEEE Software, 24, 2 (March-April 2007), pp. 62-65.
  84. [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.
  85. [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.
  86. [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.
  87. [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. 
  88. [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. 
  89. [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. 
  90. [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.
  91. [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.   
  92. [Alford 1985].
    Alford, M., "SREM at the Age of Eight: the Distributed Computing Design System," IEEE Computer, 18, 4 (April 1984), pp. 36-46.   
  93. [Alford 1991].
    Alford, M., "Strengthening the Systems Engineering Process," International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 1991.
  94. [Alford 1993].
    Alford, M., "Behavior Based System Test Planning," International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 1993.
  95. [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.
  96. [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.
  97. [Alford 1995].
    Alford, M., "Taming the Software Monster with Threads," International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 1995.
  98. [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.
  99. [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.
  100. [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).
  101. [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.
  102. [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.
  103. [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).
  104. [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
     
  105. [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.
  106. [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.
  107. [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.
  108. [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.
  109. [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.
  110. [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.
  111. [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.
  112. [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).
  113. [Alshawi and Al-Karaghouli 2003].
    Alshawi, S., and W. Al-Karaghouli, "Managing knowledge in business requirements identification," Logistics Information Management (2003).
  114. [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.
  115. [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.
  116. [Alspaugh 2002].
    Alspaugh, T., Scenario Networks and Formalization for Scenario Management, Ph.D. dissertation, North Carolina State University, Raleigh, North Carolina, September 2002.
  117. [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.
  118. [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.
  119. [Alspaugh and Antón 2008].
    Alspaugh, T., and A. Antón,  "Scenario support for effective requirements," Information and Software Technology (2008).
  120. [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.
  121. [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.

    Alvarez, see also Granja-Alvarez
     
  122. [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.
  123. [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.
  124. [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.
  125. [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.
  126. [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.
  127. [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. 
  128. [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.
  129. [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.
  130. [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.
  131. [Ambler 2002].
    Ambler, S., Agile Modeling, New York: John Wiley, 2002, Chapters 24-25.
  132. [Ambler 2004].
    Ambler, S., "Come In Out of the Requirements Cold," Computing Canada, 30, 17 (November 2004), p. 11.
  133. [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.
  134. [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.
  135. [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.
  136. [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.
  137. [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.
  138. [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.
  139. [America and van Wijgerden 2000].
    America, P., and J. Van Wijgerden, "Requirements Modeling for Families of Complex Systems," in Software Architectures for Product Families, Lecture Notes in Computer Science 1951, Berlin: Springer, 2000, pp. 199-209.
  140. [Amirat 2007].
    Amirat, A., "Towards a requirements model for crosscutting concerns," Information Technology Journal, 6, 3 (April 2007), pp. 332-337. 
  141. [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.
  142. [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.
  143. [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.
  144. [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. 
  145. [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.
  146. [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.
  147. [Anderson 1985].
    Anderson, T., Software Requirements: Specification and Testing, Oxford, UK: Blackwell Publishing, 1985.
  148. [Anderson 1989].
    Anderson, L., "Supporting Traceability Requirements with CASE," Defense Computing, 1989.
  149. [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.
  150. [Anderson and Shaw 1997].
    Anderson, A., and G. Shaw, "Executable Requirements and Specifications," Journal of VLSI Signal Processing, 1997.
  151. [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.
  152. [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.
  153. [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. 
  154. [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.
  155. [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.
  156. [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.
  157. [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.
  158. [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. 
  159. [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.
  160. [Andrews 1991].
    Andrews, D., "JAD: A Crucial Dimension for Rapid Application Development," Journal of Systems Management, (March 1991), pp. 23-31.
  161. [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.
  162. [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.
  163. [Andriole 1987].
    Andriole, S., "Storyboard Prototyping For Requirements Verification," Large Scale Systems, 12 (1987), pp. 231-247.
  164. [Andriole 1989].
    Andriole, S., Storyboard Prototyping: A New Approach to User Requirements Analysis, Wellesley, Massachusetts: QED, 1989.
  165. [Andriole 1992].
    Andriole, S., Rapid Application Prototyping, Wellesley, Massachusetts: QED, 1992.
  166. [Andriole 1994].
    Andriole, S., "Fast, Cheap Requirements: Prototype, or Else!" (see abstract) Manager Column, IEEE Software, 11, 2 (March 1994), pp. 85-87.
  167. [Andriole 1994a].
    Andriole, S., "Requirements Analysis & Prototyping: Fast, Cheap & Robust," Software Development, 2, 5 (May 1994).
  168. [Andriole 1998].
    Andriole, S., "The Politics of Requirements Management," IEEE Software, 15, 6 (November/December 1998), pp. 82-84.
  169. [Andriole and Monsanto 1995].
    Andriole, S., and C. Monsanto, "Tracking Requirements: Interactive Collaborative Requirements Management," Software Development, 3, 9 (September 1995), pp. 34-40.
  170. [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
    Ansary, see El-Ansary
     
  171. [ANSI 1977].
    American National Standards Institute, Standard Guidelines for Developing Functional Requirements for Computerized Laboratory Systems, 1977.
  172. [Anthes 1994].
    Anthes, G., "No More Creeps! Are You a Victim of Creeping User Requirements?" Computerworld, 28, 18 (May 2, 1994), pp. 107-110.
  173. [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.
  174. [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.
  175. [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.
  176. [Antón 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.
  177. [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.
  178. [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.
  179. [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.
  180. [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.
  181. [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.
  182. [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.
  183. [Antón 2002]
     Antón, A., "Guest Editorial: Requirements Engineering for Information Security," Requirements Engineering, 7, 4 (2002), pp. 177-178.
  184. [Antón 2003]
     Antón, A., "Successful Software Projects Need Requirements Planning," IEEE Software, 20, 3 (May/June 2003), pp. 44-47.
  185. [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.
  186. [Antón and Earp 2003]
     Antón, A., and J. Earp, "A Requirements Taxonomy for Reducing Website Privacy Vulnerabilities," Requirements Engineering, 29 (2003).
  187. [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.
  188. [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.
  189. [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.
  190. [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.
  191. [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.
  192. [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.
  193. [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.
  194. [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.
  195. [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.
  196. [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.
  197. [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.
  198. [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.
  199. [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.
  200. [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. 
  201. [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).
  202. [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.
  203. [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.
  204. [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.
  205. [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.
  206. [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.
  207. [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.
  208. [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.
  209. [Ardis 1997].
    Ardis, M., "Formal Methods for Telecommunication System Requirements: A Survey of Standardized Languages," Annals of Software Engineering, 3, N. Mead, ed., 1997.
  210. [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
     
  211. [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.
  212. [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.
  213. [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.
  214. [Armour and Miller 2001].
    Armour, F., and G. Miller, Advanced Use Case Modeling, New York: Addison Wesley, 2001.
  215. [Armstrong 2003].
    Armstrong, J., "Systems Engineering Methods Compared," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2003.
  216. [Arnowitz et al.  2006].
    Arnowitz, J., et al., Effective Prototyping for Software Makers, Morgan Kaufman, 2006.
  217. [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.
  218. [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.
  219. [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.
  220. [Arthur and Nance 2007].
    Arthur, J., and R. Nance, "Investigating the use of software requirements engineering techniques in simulation modelling," Journal of Simulation (2007).
  221. [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.
  222. [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.
  223. [Ashworth 1988].
    Ashworth, C. "Structured Systems Analysis and Design Method (SSADM)," Information and Software Technology, 30, 3 (April 1988), pp. 153-163.
  224. [Ashworth and Goodland 1988].
    Ashworth, C. and M. Goodland, SSADM - A Practical Approach, New York: McGraw Hill, 1990.
  225. [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.
  226. [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.
  227. [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.
  228. [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.
  229. [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. 
  230. [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.
  231. [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.
  232. [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.
  233. [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.
  234. [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.
  235. [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.
  236. [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
     
  237. [Atwood 1977].
    Atwood, J., The Systems Analyst, Rochelle Park, NJ: Hayden Press, 1977.
  238. [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.
  239. [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.
  240. [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.
  241. [Aurum and Wohlin 2005].
    Aurum, A., and C. Wohlin, Engineering and Managing Software Requirements, Berlin: Springer, 2005.
  242. [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.
  243. [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.
  244. [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.
  245. [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.
  246. [Averill and Vestal 1979].
    Averill, E., and S. Vestal, "Requirements Methodology," AIAA National Conference, 1979.
  247. [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.
  248. [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.
  249. [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.
  250. [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). 
  251. [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. 
  252. [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.
  253. [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.
  254. [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.
  255. [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.
  256. [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. 
  257. [Azuma 1993].
    Azuma, R., "Tracking Requirements for Augmented Reality," Communications of the ACM, 36, 7 (July 1993), pp. 50-51.

    B

    A  B  C  D  E  F  G  H  I  J  K  L</