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

I

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. [Iglezakis and Reinartz 2002].
   Iglezakis, I., and T. Reinartz, "Relationships Between Customer Requirements, Performance Measures, and General case Properties for Case Based Maintenance," Lecture Notes in Computer Science, Volume 2416, Berlin: Springer, 2002, pp. 159ff. 
2. [IEEE 1998].
   IEEE Guide for Developing System Requirements Specifications, IEEE Standard 1233, Los Alamitos, California: IEEE Computer Society Press, December 1998.
   
3. [IEEE 1998a].
   IEEE Recommended Practice for Software Requirements Specifications, IEEE Standard 830, Los Alamitos, California: IEEE Computer Society Press, October 1998.
   
4. [Iida 2002].
   Iida, ., "A Formal Refinement Method for Statecharts," International Symposium on Future Software Technology, Wuhan, China: Huazhong University of Science and Technology, 2002, p. 45.
5. [Iivari 2005].
   Iivari, N., "Usability Specialists - ‘A Mommy Mob’, ‘Realistic Humanists’ or ‘Staid Researchers’? An Analysis of Usability Work in the Software Product Development," Lecture Notes in Computer Science 3585, Berlin: Springer, 2005, pp. 418-430.
6. [Iivari, et al. 2005].
   Iivari, N., et al., "RESEARCH IN INFORMATION SYSTEMS ANALYSIS AND DESIGN: INTRODUCTION TO THE SPECIAL THEME PAPERS," Communications of the Association for Information Systems, 16 (2005), pp. 810-813.
7. [Ikadai, et al. 1985].
   Ikadai, M., et al., "Requirements Specification with M-Box," Third International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1985, pp. 109-113.
8. [Ilić 2007].
   Ilić, D., "Deriving Formal Specifications from Informal Requirements," IEEE International Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 145-152.
9. [Ilieva and Ormandjieva 2005].
   Ilieva, M., and O. Ormandjieva, "Automatic Transition of Natural Language Software Requirements Specification into Formal Presentation," International Conference on Natural Language Processing and Information Systems, Lecture Notes in Computer Science 3513, Berlin: Springer, 2005, pp. 392-397.
10. [Ilieva and Ormandjieva 2006].
    Ilieva, M., and O. Ormandjieva, "Models derived from automatically analyzed textual user requirements," Fourth International Conference on Software Engineering Research, Management and Applications, Los Alamitos, California: IEEE Computer Society Press, 2006.
11. [Imbert and de Antonio 2005].
    Imbert, R., and A. de Antonio, "Combining Requirements Engineering and Agents," in Requirements Engineering for Sociotechnical Systems, J. Maté, and A. Silva, eds., Hershey, Pennsylvania: Information Science Publishing, 2005, pp. 68-83.
12. [In and Boehm 2001].
    In, H., and B. Boehm, "Using WinWin Quality Requirements Management Tools: A Case Study," Annals of Software Engineering, 11, 1 (November 2001), pp. 141-174.
    
13. [In and Roy 2001].
    In, H., and S. Roy, "Visualization Issues for Software Requirements Negotiation," IEEE 25^th Annual COMPSAC, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 10-15.
    
14. [In, et al. 2001].
    In, H., et al., "A Requirements Negotiation Model Based on Multi-Criteria Analysis," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 312-313.
    
15. [In, et al. 2001a].
    In, H., et al., "Applying Win-Win to Quality Requirements: A Case Study," Twenty-third International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 555-564.
    
16. [In, et al. 2002].
    In, H., et al., "Multi-Criteria Preference Analysis for Systematic Requirements Negotiation," International Conference on Computer Software and Applications (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 2002.
17. [Ince 1985].
    Ince, D., "Drawing up a requirements specification," Computing, The Magazine, (April 4, 1985), pp. 22ff.
    
18. [Ince and Hekmatpour 1986].
    Ince, D., and S. Hekmatpour, "Software prototyping and requirements validation," Software Quality Assurance, Reliability and Testing Conference, Uxbridge, UK: Unicom Seminars, 1986, pp. 102-127.
    
19. [Ingevaldson 2006].
    Ingevaldson, P., "The True Cost of Off-the-Shelf," ComputerWorld, 40, 31 (July 31, 2006), p. 36.
    
20. [Ingham 2006].
    Ingham, M., et al., "Generating requirements for complex embedded systems using state analysis," Acta Astronautica, 58, 12 (June 2006), pp. 646-661.
    
21. [Ingram 1987].
    Ingram, D., "Requirements Management is Key to Software Quality," CASE Outlook, 1, 5 (November 1987).
    
22. [Insfrán, et al. 2002].
    Insfrán, E., et al., "Requirements Engineering-Based Conceptual Modeling," Requirements Engineering Journal, 6, 2 (June 2002), pp. 61-72.
23. [Insfrán, et al. 2002a].
    Insfrán, E., et al., "Generating Conceptual Schemas from Requirements Models," in Applying Requirements Engineering, Durán, A., and M. Toro, eds., Salamanca, Spain: Catedral Publ., 2002, pp. 131-141.
24. [Insfrán, et al. 2002b].
    Insfrán, E., et al., "Modelado Requitos Para La Obstención de Esquemas Conceptuales," V Workshop Iberoamericano de Ingenieria de Requisitos y Ambientes Software (IDEAS '2002), Havana, Cuba, 2002, ISBN 959-7160-14-5.
25. [Insfrán, et al. 2002c].
    Insfrán, E., et al., "Transformación de Especificación de Requisitos en Esquemas Conceptuales Usando Diagramas de Interacción," V Workshop on Requirements Engineering (WER 2002), Valencia, España, 2002, ISBN: 959-7160-14-5.
26. [Insfrán, et al. 2002d].
    Insfrán, E., et al., "Conceptual Modeling in the eXtreme," Information and Software Technology, 44, 11 (August 2002), pp. 659-669.

27. [Interrante, et al. 1989].
    Interrante, M., et al., "Software Requirements Determinations Strategy Utilizing Provisional Solutions," Annual Computer Science Conference, 1989.

28. [Ippolito and Murman 2000].
    Ippolito, B., and E. Murman, "End User Involvement in Establishing Software Requirements for Aerospace Software Systems," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2000.
29. [Iris, et al. 1992].
    Iris, J., et al., "Formalizing Requirements: The ARC2 Method," Fifth International Conference on Software Engineering and Its Applications, Nanterre, France: EC2, 1992.
    
30. [Irvine, et al. 2002]
    Irvine, C., et al., "An Approach to Security Requirements Engineering for a High Assurance System," Requirements Engineering, 7, 4 (2002), pp. 192-206.
    
31. [Isazadeh, et al., 1996].
    Isazadeh, A., et al., "Behavioural Views for Software Requirements Engineering," IEEE Symposium and Workshop on Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 300-307; also appears in Requirements Engineering Journal, 4, 1 (1999), pp. 19-37.
32. [Ishihara, et al. 1993].
    Ishihara, Y., et al., "A Translation Method From Natural Language Specifications into Formal Specifications Using Contextual Dependencies," International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 232-239.
33. [Isla, et al. 2007].
    Isla, J., et al., "A Pattern-based Approach for Conceptual Modeling of Cooperative Systems," IEEE Transactions on Latin America (2007).
    
34. [Itani and Logrippo 2006].
    Itani, W., and L. Logrippo, "Formal approaches to requirements engineering: from behavior trees to alloy," Canadian Conference on Electrical and Computer Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 916-919.
35. [Itoga and Ohnishi 2006].
    Itoga, H., and A. Ohnishi, "An Elicitation Method of Security Requirements using Conditions of Actors on Scenarios," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
36. [Ivannikov, et al. 2007].
    Ivannikov, V., "The use of contract specifications for representing requirements and for functional testing of hardware models," Programming and Computer Software, 33, 5 (September 2007), pp. 272-282.
37. [Ivanovic, et al. 2005].
    Ivanovic, A., et al., "Eliciting User Requirements for Ambient Intelligent Systems: A Case Study," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 477-478.
38. [Ives and Olson 1984].
    Ives, B., and M. Olson, "User Involvement and MIS Success: A Review of Literature," Management Science, 30, 5 (1984), pp. 586-603.
    
39. [Iwach and Sims 1996].
    Iwach, A., and S. Sims, "Closing the Gap Between Requirements Definition and Product Development: A Case Study," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.

    J

    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. [Jackacky 2005].
   Jackacky, R., "Requirements Management: From the RFP to the Project," Sixteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
2. [Jackson 1983].
   Jackson, M., Systems Development, Upper Saddle River, New Jersey: Prentice Hall, 1983.
3. [Jackson and Vermeersch 1983].
   Jackson, D., and B. Vermeersch, "A Requirements Analysis and Documentation Methodology," Second Phoenix Conference on Computers and Communications, Los Alamitos, California: IEEE Computer Society Press, 1983, pp. 262-267.
   
4. [Jackson and Zave 1993].
   Jackson, M., and P. Zave, "Domain Descriptions," International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 56-64.
   
5. [Jackson 1994].
   Jackson, M., "The Role of Architecture in Requirements Engineering," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 241.
   
6. [Jackson 1995].
   Jackson, M., Software Requirements and Specifications, Reading, Massachusetts: Addison Wesley, 1995.
   
7. [Jackson and Zave 1995].
   Jackson, M., and P. Zave, "Deriving Specifications from Requirements: An Example," Seventeenth IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
8. [Jackson, et al. 1995].
   Jackson, R., et al., "Developing Formal Object-Oriented Requirements Specifications: A Model, Tool, and Technique," Information Systems, 20, 4 (1995), pp. 273-289.
9. [Jackson 1997].
   Jackson, M., "The Meaning of Requirements," (see abstract) Annals of Software Engineering, 3 (January 1997), pp. 5-21.
10. [Jackson 1998].
    Jackson, M., "Problem Analysis using Small Problem Frames," South African Computer Journal, 22 (1998), pp. 47-60.
11. [Jackson and Rinard 2000].
    Jackson, D., and M. Rinard, "Software Analysis: A Roadmap," in The Future of Software Engineering, A. Finkelstein, ed., New York: ACM Press, 2000.
    
12. [Jackson 2001].
    Jackson, M., Problem Frames, Reading, Massachusetts: Addison Wesley, 2001.
13. [Jackson 2004].
    Jackson, M., "Seeing More of the World," IEEE Software, 21, 6 (November 2004), pp. 83-85.
    
14. [Jackson 2005].
    Jackson, D., "Keynote: Dependable Software: An Oxymoron," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, p. 3.
15. [Jackson and Jackson 2006].
    Jackson, D., and M. Jackson, "Separating Concerns in Requirements Analysis: An Example," Rigorous Development of Complex Fault-Tolerant Systems, Lecture Notes in Computer Science, Volume 4157, Berlin: Springer, 2006, pp. 210-225. 
16. [Jacobs and Holten 1995].
    Jacobs, D., and R. Holten, "Goal-Driven Business Modelling -- Supporting Decision Making within Information Systems Development," Conference on Organizational Computing Systems, New York: ACM Press, 1995.
    
17. [Jacobs 1999].
    Jacobs, S., "Introducing Measurable Quality Requirements: A Case Study," (see abstract) IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 172-179.
18. [Jacobs 2004].
    Jacobs, D., "Requirements Engineering So Things Don't Get Ugly," Crosstalk, 2004, pp. 172-179.
19. [Jacobs and Ip 2005].
    Jacobs, G., and B. Ip, "Establishing user requirements: incorporating gamer preferences into interactive games design," Design Studies, 26, 3 (May 2005), pp. 243-255.
    
20. [Jacobs 2006].
    Jacobs, D., "Interpreting requirements in a he said/she said world," Crosstalk, 16, 12 (2006), pp. 9-13.
21. [Jacobs 2007].
    Jacobs, D, "Requirements Engineering so Things Don't Get Ugly," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
    
22. [Jacobson, et al. 1993].
    Jacobson, I., et al., Object-Oriented Software Engineering: A Use-Case Driven Approach, Reading, Massachusetts: Addison-Wesley, 1992.
23. [Jacobson 2007].
    Jacobson, I., "Enough of RE Processes- Let's Do Practices (keynote)," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.

24. [Jaffe and Leveson 1989].
    Jaffe, M., and N. Leveson, "Completeness, Robustness, and Safety in Real-Time Software Requirements Specification," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1989.

25. [Jaffe and Leveson 1989a].
    Jaffe, M., and N. Leveson, "The impact of the man-machine interface on software requirements completeness," IFAC/IFIP Workshop on Safety of Computer Control Systems, Oxford, UK: Pergamon Press, 1989, pp. 41-48.

26. [Jaffe, et al. 1991].
    Jaffe, M., et al., "Software Requirements Analysis for Real-Time Control Systems," IEEE Transactions on Software Engineering, 17, 3 (March 1991), pp. 241-258.
    
27. [Jahanian and Mok 1986].
    Jahanian, F., and A. Mok, "A Graph-Theoretic Approach for Timing Analysis in Real Time Logic," 1986 Real-Time Systems Symposium, Los Alamitos, California: IEEE Computer Society Press, 1986.
28. [Jahanian and Mok 1986a].
    Jahanian, F., and A. Mok, "Safety Analysis of Timing Properties in Real-Time Systems," IEEE Transactions on Software Engineering, 12, 9 (September 1986), pp. 890-904.
    
29. [Jahanian and Stuart 1988].
    Jahanian, F., and D. Stuart, "A Method for Verifying Properties of Modechart Specifications," (see abstract) Ninth Real-Time Systems Symposium, Los Alamitos, California: IEEE Computer Society Press, 1988.
    
30. [Jahanian, et al. 1988].
    Jahanian, F., et al., "Semantics of Modechart in Real Time Logic," 21st Hawaii International Conference on System Science, Los Alamitos, California: IEEE Computer Society Press, 1987.
31. [Jahanian and Mok 1994].
    Jahanian, F., and A. Mok, "Modechart: A Specification Language for Real-Time Systems," IEEE Transactions on Software Engineering, (1994).
    
32. [Jain, et al. 2003].
    Jain, H., et al., "An Assessment Model for Requirements Identification in Component-Based Software Development," ACM SIGMIS Database, 34, 4 (November 2003), pp. 48-63.
    
33. [Jaiu and Yu 2006].
    Jaiu, H., and D.-F. Yu, "Comments on 'Automatic analysis of consistency between requirements and designs'," IEEE Transactions on Software Engineering, 32, 4 (April 2006), pp. 279-280.
34. [Jakob 1983].
    Jakob, R., "Using Formal Specifications in the Design of a Human-Computer Interface," Communications of the ACM, 26, 4 (April 1983), pp. 259-264.
    
35. [James 1996].
    James, L., "What's Wrong with Requirements Management Tools," Requirements Engineering Journal, 1, 3 (March 1996), pp. 190-194; also appears in Seventh Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1997.
36. [James 1996a].
    James, K., "Current Trends In Requirements and Specification Management," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.

37. [James 1997].
    James, L., "What's Wrong with the Requirements Management Tools?," International Symposium on Systems Engineering, 1997.

38. [Janakiram and Rajasree 2005].
    Janakiram, D., and M. Rajasree, "ReQuEst: Requirements-Driven Quality Estimator," ACM Software Engineering Notes, 30, 1 (January 2005), pp. 1-7.
39. [Janning and Lefering 1990].
    Janning, T., and M. Lefering, "A transformation from requirements engineering into design: the method & the tool," International Conference on Software Engineering and Its Applications, Nanterre, France: EC2, 1990, pp. 223-237.
40. [Janson and Smith 1985].
    Janson, M., and L. Smith, "Prototyping for Systems Development," MIS Quarterly, 9, 4 (December 1985), pp. 305-316.
    
41. [Jantunen, et al. 2007].
    Jantunen, S., et al., "How Internationalization of a Product Changes Requirements Engineering Activities: An Exploratory Study," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
42. [Jaramillo, et al. 2006].
    Jaramillo, C., et al., "Pre-conceptual Schema: A Conceptual-Graph-Like Knowledge Representation for Requirements Elicitation," MICAI 2006: Advances in Artificial Intelligence, Lecture Notes in Computer Science, Volume 4293, Berlin: Springer, 2006, pp. 27-37. 
43. [Jarke, et al. 1993].
    Jarke, M., et al., "Theories Underlying Requirements Engineering: An Overview of NATURE at Genesis," (see abstract) IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 19-31.
    
44. [Jarke, et al. 1993a].
    Jarke, M., et al., "Requirements Engineering: An Integrated View of Representation, Process, and Domain," 4th European Conference on Software Engineering, September 1993.
    
45. [Jarke and Pohl 1993].
    Jarke, M., and K. Pohl, "Establishing Visions in Context: Towards a Model of Requirements Processes," Twelfth International Conference on Information Systems, Orlando, Florida, 1993.
    
46. [Jarke and Pohl 1994].
    Jarke, M., and K. Pohl, "Requirements Engineering in 2001: Virtually Managing a Changing Reality," IEE Software Engineering Journal, 9, 6 (November 1994), pp. 257-266.
47. [Jarke, et al. 1996].
    Jarke, M., et al., "Conflict Analysis Across Heterogeneous Viewpoints: Formalization and Visualization," Hawaii International Conference on System Science, Los Alamitos, California: IEEE Computer Society Press, 1996.
    
48. [Jarke 1998].
    Jarke, M., "Requirements Tracing," Communications of the ACM, 41, 12 (December 1998), pp. 32-36.
49. [Jarke 1998a].
    Jarke, M., "Guest Editorial: Interdisciplinary Uses of Scenarios," Requirements Engineering Journal, 3, 3 (1998), pp. 153-154.
50. [Jarke, et al. 1998].
    Jarke, M., et al., "Scenario Management: An Interdisciplinary Approach," Requirements Engineering Journal, 3, 3 (1998), pp. 155-173.
51. [Jarke, et al.  2003].
    Jarke, M., et al., "Media-Assisted Product and Process Requirements Traceability in Supply Chains," 11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 375-376.
52. [Jarvinen, et al. 1990].
    Jarvinen., et al., "Object-Oriented Specification of Reactive Systems," Twelfth International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1990.
    
53. [Jarzabek and Zhang 2001].
    Jarzabek, S., and H. Zhang, "XML-Based Method and Tool for Handling Variant Requirements in Domain Models," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 166-173.
54. [Jarzabek, et al. 2003].
    Jarzabek, S., et al., "Handling Variant Requirements in Domain Modeling," Journal of Systems and Software, 68, 3 (December 2003), pp. 171-182; also appears in Thirteenth International Conference on Software Engineering and Knowledge Engineering, Knowledge Systems Institute, 2001, pp. 61-68.
55. [Javed, et al. 2004].
    Javed, T., et al., "A Study to Investigate the Impact of Requirements Instability on Software Defects," ACM Software Engineering Notes, 29, 3 (May 2004), pp. 1-7.
56. [Jean-Baptiste, et al. 2005].
    Jean-Baptiste, L., et al., "Sharing Methodological Knowledge with REGAL: "Requirements Engineering Guide for All"," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 461-461.
57. [Jefferson 1979].
    Jefferson, D., "Analysis of Requirements for a Large-Scale Information System," International Conference on Computer Software and Applications (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1979.
    
58. [Jeffords and Heitmeyer 1998].
    Jeffords, R., and C. Heitmeyer, "Automatic Generation of State Invariants from Requirements Specifications," Sixth International Symposium on Foundations of Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1998.
59. [Jeffords and Heitmeyer 2001].
    Jeffords, R., and C. Heitmeyer, "An Algorithm for Strengthening State Invariants Generated from Requirements Specifications," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 182-191.
    
60. [Jenkins 1994].
    Jenkins, M., "Requirements Capture," Conference on Requirements Elicitation for Software-Based Systems, July 1994.
    
61. [Jeremaes, et al. 1986].
    Jeremaes, P., et al., "A Modal (Action) Logic for Requirements Specification," in Software Engineering '86, P. Brown and D. Barnes, eds., Peter Peregrinus, 1986.
62. [Jha and Cox 2005].
    Jha, A., and K. Cox, "Selling Web Services as Capabilities," 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
63. [Jha, et al. 2006].
    Jha, A., et al., "Creating the Best Fit Between Business strategy and Web Services Capabilities Using Problem Frames Modeling Approach," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
64. [Jiang, et al. 2000].
    Jiang, L., et al., "Embedding UML and Type Theory to Formalize the Process of Requirement Engineering," International Conference on Technology of Object-Oriented Languages and Systems, Los Alamitos, California: IEEE Computer Society Press, 2000.
65. [Jiang and Eberlein 2003]
    Jiang, L., and A. Eberlein, "Decision Support for Requirements Engineering Process Development," Canadian Conference on Electrical and Computer Engineering, 2003, pp. 1359-1362.
66. [Jiang, et al. 2004].
    Jiang, L., et al., "Case Studies on the Application of the CORE Model for Requirement Engineering Process Assessment," Canadian Conference on Electrical and Computer Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, Volume 1, pp. 323-326.
67. [Jiang, et al. 2004a].
    Jiang, L., et al., "A Methodology for Requirement Engineering Process Development," IEEE Conference and Workshop on Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 263-272.
68. [Jiang, et al. 2004b].
    Jiang, L., et al., "A Multi-Tiered Structured Tool for Requirement Engineering Process Development," Lecture Notes in Computer Science, Volume 3007, Berlin: Springer, 2004, pp. 928-931. 
69. [Jiang, et al. 2005].
    Jiang, L., et al., "Combining requirements engineering techniques -Theory and case study," IEEE Conference and Workshop on Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 105-112.
70. [Jiang, et al. 2006].
    Jiang, L., et al.,  "Incorporating Goal Analysis in Database Design: A Case Study from Biological Data Management," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
71. [Jiang and Eberlein 2007].
    Jiang, L., and A. Eberlein, "Selecting Requirements Engineering Techniques Based on Project Attributes--A Case Study," IEEE Symposium and Workshop on Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 269-278.
72. [Jiau and Yu 2006].
    Jiau, H., and D.-F. Yu, "Comments on 'Automatic analysis of consistency between requirements and designs'," IEEE Transactions on Software Engineering, 32, 4 (April 2006), pp. 279-280.
    
    Jimenez, see Almendros-Jimenez
    
    
73. [Jin, et al. 1998]
    Jin, Z., et al., "Automatically Acquiring Requirements of Business Information Systems by Reusing Business Ontology," Workshop on Applications of Ontologies and Problem Solving Methods (ECAI'98), Brighton, England, August 1998.
    
74. [Jin, et al. 2000].
    Jin, Z., et al., "Requirement Elicitation based on Enterprise Ontology and Domain Ontology," International Conference on Information Systems, Analysis and Synthesis, Volume II, 2000.
75. [Jin, et al. 2003].
    Jin, Z., et al., "Automated Requirement Elicitation: Combining a Model-Driven Approach with Concept Reuse," International Journal of Software Engineering and Knowledge Engineering, 13, 1 (February 2003), pp. 53-82.
    
76. [Jin 2006].
    Jin, Z., "Revisiting the Meaning of Requirements," Journal of Computer Science and Technology , 21, 1 (January 2006), pp. 32-40.
    
77. [Jin, et al. 2007].
    Jin, Z., et al., "Using Root Cause Data Analysis for Requirements and Knowledge Elicitation," International Conference on Engineering Psychology and Cognitive Ergonomics, Berlin: Springer, 2007.
78. [Jirotka 1991].
    Jirotka, M., Ethnomethodology and Requirements Engineering, Centre for Requirements and Foundations Technical Report, Oxford, UK: Oxford University Computing Laboratory, 1991.
    
79. [Jirotka and Goguen 1994].
    Jirotka, M., and J. Goguen, eds., Requirements Engineering: Social and Technical Issues, London, U.K.: Academic Press, 1994.
    
80. [Jirotka and Heath 1995].
    Jirotka, M., and C. Heath, "Ethnography by Video for Requirements Capture," Second International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
81. [Jirotka and Luff 2006].
    Jirotka, M., and P. Luff,  "Supporting Requirements with Video-Based Analysis," IEEE Software, 23, 3 (May/June 2006), pp. 42-44.
    
82. [Johansen and Baker 1984].
    Johansen, R., and E. Baker, "User Needs Workshops: A New Approach to Anticipating User Needs for Advanced Office Systems," Office: Technology and People, 2 (1984), pp. 103-199. 
83. [John, et al. 1999].
    John, G., et al., "Using a Common Information Model as a Methodological Basis for a Tool-Supported Requirements Management Process," Ninth International Council on Systems Engineering Symposium, INCOSE, 1999.
    
84. [John, et al. 2002].
    John, I., et al., "Efficient and Systematic Software Evolution through Domain Analysis," (see abstract) Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
85. [Johnson 1983].
    Johnson, D., "Seeking a Methodology for Requirements Analysis," Second Phoenix Conference on Computers and Communications, Los Alamitos, California: IEEE Computer Society Press, 1983, pp. 357-362.
86. [Johnson 1988].
    Johnson, W., "Deriving Specification from Requirements," Tenth International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1988.
    
87. [Johnson, et al. 1991].
    Johnson, W., et al., "The KBSA Requirements/Specification Facet: ARIES," Sixth Annual Knowledge-Based Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, September 1991.
    
88. [Johnson, et al. 1991a].
    Johnson, W., et al., "Integrating Domain Knowledge, Requirements, and Specification," Journal of Systems Integration, 1 (1991), pp. 283-320.
    
89. [Johnson, et al. 1992].
    Johnson, W., et al., "Representation and Presentation of Requirements Knowledge," IEEE Transactions on Software Engineering, 18, 10 (October 1992), pp. 853-869.
90. [Johnson, et al. 1992a].
    Johnson, W., et al., "Applying domain and design knowledge to requirements engineering," ACM SIGOIS Bulletin (1992).
91. [Johnson and Henderson 2002].
    Johnson, J., and A. Henderson, "Conceptual models: begin by designing what to design," Interactions, 9, 1 (January 2002), pp. 25-32.
    
92. [Johnson 2005].
    Johnson, B., Flexible Software Design: Systems Development for Changing Requirements , Auerbach, 2005.
    
93. [Johnson and Holloway 2006].
    Johnson, C., and C. Holloway, "Questioning the role of requirements engineering in the causes of safety-critical software failures," 1st Institution of Engineering and Technology International Conference on System Safety, Stevenage, UK: Institute of Engineering Technology, 2006.
    
94. [Jokela and Lindberg 1990].
    Jokela, T., and K. Lindberg, "Statecharts-Based Requirements: Deriving User-Oriented Models," Microprocessing and Microprogramming, 30 (August 1990), pp. 289-296.
95. [Jokela, et al. 2005].
    Jokela, T., et al., "Methods for Quantitative Usability Requirements: A Case Study on the Development of the User Interface of a Mobile Phone," Personal and Ubiquitous Computing, (November 2005), pp. 1-11.
    
96. [Jones 1976].
    Jones, M., "HIPO for Developing Specifications," Datamation, 22, 3 (March 1976), pp. 112-125.
    
97. [Jones 1994].
    Jones, L., "Practical Experiences in Automating Requirements in Elicitation: The Real Issues," Conference on Requirements Elicitation for Software-Based Systems, July 1994.
    
98. [Jones 1995].
    Jones, D., "Repeatable Software Development Part II: Configuration and Requirements Management," Software Development, 3, 6 (June 1, 1995), pp. 55-57.
99. [Jones 1995a].
    Jones, D., "Experience with Automated Requirements Management," 1995 Annual International Symposium on Requirements Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
100. [Jones 1995b].
     Jones, D., "Some Lessons Learned in Requirements Management," 1995 Annual International Symposium on Requirements Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
     
101. [Jones 1996].
     Jones, C., "Strategies for Managing Requirements Creep," IEEE Computer, 29, 5 (May 1996), pp. 92-94.
     
102. [Jones and Britton 1996].
     Jones, S., and C. Britton, "Early Elicitation and Definition of Requirements for an Interactive Multimedia Information System," (see abstract)  Second IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1996, pp. 12-19.
     
103. [Jones and Brooks 1994].
     Jones, M., and L. Brooks, "Addressing Organizational Context in Requirements Analysis Using Cognitive Mapping," Conference on Requirements Elicitation for Software-Based Systems, July 1994.
     
104. [Jones and Till 1998].
     Jones, S., and D. Till, "Formal Methods and Requirements Engineering: Challenges and Synergies," Journal of Systems and Software, 40, 3 (March 1998), pp. 263-273.
     
105. [Jones, et al. 2000].
     Jones, S., et al., "Trust Requirements in E-Business," Communications of the ACM, 43, 12 (December 2000), pp. 81-87.
106. [Jones and Maiden 2005].
     Jones, S., and N. Maiden, "RESCUE: An Integrated Method for Specifying Requirements for Complex Sociotechnical Systems," in Requirements Engineering for Sociotechnical Systems, J. Maté, and A. Silva, eds., Hershey, Pennsylvania: Information Science Publishing, 2005, pp. 245-265.
107. [Jones, et al. 2005].
     Jones, S., et al., "How Service-Centric Systems Change the Requirements Process," 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
108. [Jones 2007].
     Jones, S., "Tips for Writing Scenarios," IEEE Software 24, 4 (July/August 2007), p. 27.
109. [Jones, et al. 2007].
     Jones, S., et al., "Informing the specification of a large-scale socio-technical system with models of human activity," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ' 07), Berlin: Springer, 2007.
110. [Jonker, et al. 2002].
     Jonker, C., et al., "Diagnostics of the Dynamics within an Organization by Trace Checking of Behavioral Requirement," Lecture Notes in Computer Science, Volume 2222, Berlin: Springer, 2002, pp. 17ff. 
111. [Jonsson, et al. 2001].
     Jonsson, B., et al., "Incremental Requirements Specification for Evolving Systems," Nordic Journal of Computing, 8 (2001), pp. 65ff (Finland).
112. [Jonsson and Lindvall 2005].
     Jonsson, P., and M. Lindvall, "Impact Analysis," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 117-142.
113. [Jordan, et al. 1989].
     Jordan, P., et al., "Software Storming: Combining Rapid Prototyping and Knowledge Engineering," (see abstract) IEEE Computer (May 1989), pp. 39-48.
114. [Jordan and Davis 1991].
     Jordan, K., and A. Davis, "An Integrated View of Requirements," International Conference on Computer Software and Applications (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1991, pp. 472-478.
115. [Jordan, et al. 2005].
     Jordan, N., et al., "An Extravehicular Mobility Unit: Case Study in Requirements Evolution," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 434-438.
116. [Jorgensen 1986].
     Jorgensen, P., "Complete Specifications and the Sorcerer's Apprentice Problem," International Conference on Computer Software and Applications (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1986.
     
117. [Jorgensen 1998].
     Jorgensen, R., "Untangling the Twists in Requirements Analysis," Eighth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1998.
118. [Jorgensen 2002].
     Jorgensen, R., "Requirements Variability Management," Eighth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2002.
119. [Jørgensen and Bossen 2003].
     Jørgensen, J., and C. Bossen, "Requirements Engineering for a Pervasive Health Care System," (see abstract) International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 55-64.
120. [Jørgensen and Bossen 2004].
     Jørgensen, J., and C. Bossen, "Executable Use Cases: Requirements for a Pervasive Health Care System," IEEE Software, 21, 2 (March/April 2004), pp. 34-41.
121. [Jorgensen 2007].
     Jorgensen, J., "Executable Use Cases: a Supplement to Model-Driven Development?," IEEE International Workshop on Model-Based Methodologies for Pervasive & Embedded Software, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 8-15.
122. [Joseph 1996].
     Joseph, M., Real-Time Systems: Specification, Verification, and Analysis, Upper Saddle River, New Jersey: Prentice Hall, 1996.
     
123. [Joshi 1984].
     Joshi, R., "Specifying Software Requirements Using SREM/REVS - A User Experience," IEEE Global Telecommunications Conference,  Los Alamitos, California: IEEE Computer Society Press, 1984, pp. 1290-1294.
124. [Joshi 1992].
     Joshi, K., "Interpersonal Skills for Cooperative User Analyst Relationships: Some Research Issues," Database, (1992), pp. 23-25.
125. [Jovalekic 1983].
     Jovalekic, S., "Specification and automatic evaluation of system requirements for automation systems," Conference on Industrial Electronics, 1983, pp. 231-236.
126. [Joyce 1994].
     Joyce, D., "Examining the Potential of Fuzzy Software Requirements Specifications," Information Sciences Applications, 2, 2 (September 1994), pp. 85-102.
127. [Juang, et al. 2006].
     Juang, Y. S., et al., "Design and implementation of a fuzzy inference system for supporting customer requirements," Expert Systems with Applications, (accepted 2006).
128. [Jun, et al. 2003].
     Jun, S., et al., "A Prototype of Information Requirement Elicitation in M-Commerce," (see abstract) International Conference on eCommerce, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 53-56.
     
129. [Jung 1998].
     Jung, H., "Optimizing Value and Cost in Requirements Analysis," (see abstract) IEEE Software, 15, 4 (July 1998), pp. 74-78.
     
130. [Jung, et al. 2001].
     Jung, H., et al., "Development of a Safety Analysis Method for Requirements Based on Statecharts Using Combined SCR and ISO Tables," Transactions of the American Nuclear Society, 85 (2001), pp. 398ff.
131. [Jung and Fraunholz 2002].
     Jung, J., and B. Fraunholz, "Resource Modeling in an Object-Oriented Process Modeling Language," Australian Workshop on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
132. [Jungclaus, et al. 1996].
     Jungclaus, R., et al., "TROLL: A Language for Object-Oriented Specification of Information Systems," ACM Transactions on Information Systems, 14, 2 (April 1996), pp. 175-211.
     
133. [Jureta, et al. 2006].
     Jureta, I., et al., "Justifying Goal Models," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
134. [Jureta, et al. 2006a].
     Jureta, I., et al., "A More Expressive Softgoal Conceptualization for Quality Requirements Analysis," Conceptual Modeling - ER 2006, Lecture Notes in Computer Science, Volume 4215, Berlin: Springer, 2006, pp. 281-295.
135. [Jureta, et al. 2007].
     Jureta, I., et al., "Dynamic Requirements Specification for Adaptable and Open Service Systems," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
136. [Jureta, et al. 2007a].
     Jureta, I., et al., "Achieving, Satisficing, and Excelling," Advances in Conceptual Modeling - Theory and Practice, Berlin: Springer, 2007.
137. [Juric and Kuljis 1999].
     Juric, R., and J. Kuljis, "Engineering Requirements Through Use Cases in Complex Business Environments," Requirements Engineering Journal, 4, 2 (1999), pp. 65-76.
138. [Juristo and Moreno 2000].
     Juristo, N., and A. Moreno, "Reflections on Conceptual Modeling," Data and Knowledge Engineering, 33 (2000), pp. 103-117.
139. [Juristo, et al. 2002].
     Juristo, N., et al., "Is the European Industry Moving Toward Solving Requirements Engineering Problems?," (see abstract) IEEE Software, 19, 6 (November-December 2002), pp. 70-77.
140. [Juristo, et al. 2007].
     Juristo, N., et al., "Guidelines for Eliciting Usability Functionalities," IEEE Transactions on Software Engineering, 33, 11 (November 2007), pp. 744-758.
     
141. [Justo 1996].
     Justo, J., " A Repository to Support Requirement Specifications Reuse," Information Systems Conference of New Zealand, Los Alamitos, California: IEEE Computer Society Press, 1996.

     K

     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. [Kaariainen, et al. 2004].
   Kaariainen, J., et al., "Improving Requirements Management in Extreme Programming with Tool Support -- An Improvement Attempt that Failed," 30th EUROMicro Conference, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 342-351.
   
2. [Kabeli and Shoval 2003].
   Kabeli, J., and P. Shoval, "Software Analysis Process - Which Order of Activities is Preferred? An Experimental Comparison using FOOM Methodology," (see abstract) IEEE International Conference on Software: Science, Technology, and Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 111-119. 
3. [Kabeli and Shoval 2005].
   Kabeli, J., and P. Shoval, "Comprehension and quality of analysis specifications—a comparison of FOOM and OPM methodologies," Information and Software Technology, 47, 4 (March 2005), pp. 271-290. 
   
   Kadir, see Wan-Kadir
    
4. [Kaffenberger 2002].
   Kaffenberger, R., "Requirements Engineering with Goal-Driven Use Cases," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2002.
5. [Kaffenberger 2004].
   Kaffenberger, R., "The Difference - On the Use of Pattern-Based Requirements," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
6. [Kaffenberger 2005].
   Kaffenberger, R., "A Markup Language to Support the Exchange of Requirements During a RFQ," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
7. [Kahn, et al., 2004].
   Kahn, K, et al., "Incorporating business requirements and constraints in database conceptual models," Asian-Pacific Conference on Conceptual Modelling, Darlinghurst, Australia: Australia Computer Society, 2004, pp. 59-64.
8. [Kahn, et al., 2005].
   Kahn, S, et al., "An enhanced framework for validation of aspectual requirements," IEEE International Symposium on Emerging Technologies, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 435-439.
9. [Kaindl 1993].
   Kaindl, H., "Missing Link in Requirements Engineering," ACM Software Engineering Notes, 18, 2 (April 1993), pp. 30-39.
10. [Kaindl 1997].
    Kaindl, H., " Practical Approach to Combining Requirements Definition and Object-Oriented Analysis," Annals of Software Engineering, 3 (August 1997), pp. 319-343.
    
11. [Kaindl, et al. 1998].
    Kaindl, H., et al., "A Case Study of Decomposing Functional Requirements Using Scenarios," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 156-163.
    
12. [Kaindl 2000].
    Kaindl, H., "Using Hypermedia in Requirements Engineering Practice," Sixth International Workshop on Requirements Engineering: Foundations for Software Quality, Stockholm, Sweden, June 2000.
13. [Kaindl 2000a].
    Kaindl, H., "A Design Process Based on a Model Combining Scenarios with Goals and Functions," IEEE Transactions on Systems, Man and Cybernetics, 30, 5 (September 2000), pp. 537-551.
14. [Kaindl and Mylopoulus 2000].
    Kaindl, H., and J. Mylopoulos, "Why Is It So Difficult to Introduce RE Research Results into Mainstream RE Practice?," International Conference on Advanced Information Systems Engineering (CAiSE), Berlin: Springer, 2000, p. 7ff.
15. [Kaindl 2001].
    Kaindl, H., "Using Hypermedia in Requirements Engineering Practice," The New Review of Hypermedia and Multimedia, 7 (2001), pp. 185-205.
    
16. [Kaindl, et al. 2002].
    Kaindl, H., et al., "Requirements Engineering and Technology Transfer: Obstacles, Incentives and Improvement Agenda," Requirements Engineering Journal, 7, 3 (May 2002), pp. 113-123.
17. [Kaindl 2004].
    Kaindl, H., "Active Tool Support for Requirements Engineering Through RETH," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 362-263.
18. [Kaindl, et al. 2004].
    Kaindl, H., et al., "Interactive Metamodel-Compliance Checking of Requirements in a Semiformal Representation," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
19. [Kaindl 2005].
    Kaindl, H., "Is object-oriented requirements engineering of interest?," Requirements Engineering, 10 (2005), pp. 81-84.
20. [Kaindl 2005a].
    Kaindl, H., "A scenario-based approach for requirements engineering: Experience in a telecommunication software development project," Systems Engineering, 8, 3 (2005), pp. 197-210.
21. [Kaindl and Mannion 2005].
    Kaindl, H., and M. Mannion, "Verification of Selection from Product Line Requirements," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
22. [Kaindl 2007].
    Kaindl, H., "How to Combine Requirements and Interaction Design Through Usage Scenarios," Human Computer Interaction, Lecture Notes in Computer Science 4663, Berlin: Springer, 2007, pp. 706-707.
23. [Kaiser 1985]
    Kaiser, K., "The relationship of cognitive style to the derivation of information requirements," ACM CIGCPR Computer Personnel, 1985.
24. [Kaiya and Kaijiri 1999].
    Kaiya, H., and K. Kaijiri, "Conducting Requirements Evolution by Replacing Components in the Current System," (see abstract) Sixth Asia Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 224-227.
    

25. [Kaiya, et al. 2002].
    Kaiya, H., et al., "AGORA: Attributed Goal-Oriented Requirements Analysis Method," (see abstract) Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.

26. [Kaiya, et al. 2004].
    Kaiya, H., et al., "Identifying Stakeholders and Their Preferences about NFR by Comparing Use Case Diagrams of Several Existing Systems," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 112-121.
27. [Kaiya and Saeki 2004].
    Kaiya, H., and M. Saeki, "Weaving multiple viewpoint specifications in goal oriented requirements analysis," Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 418-427. 
28. [Kaiya, et al. 2005].
    Kaiya, H., et al., "Improving the detection of requirements discordances among stakeholders," Requirements Engineering, 10, 4 (December 2005), pp. 289-303.
29. [Kaiya and Saeki 2006].
    Kaiya, H., and M. Saeki, "Using Domain Ontology as Domain Knowledge for Requirements Elicitation," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
30. [Kakune, et al. 2006].
    Kakune, A., et al., "FBCM: Strategy modeling method for the validation of software requirements," Journal of Systems and Software (accepted 2006).

31. [Kalinsky and Ready 1989].
    Kalinsky, D., and J. Ready, "Distinctions Between Requirements Specification and Design of Real Time Systems," International Conference on Software Engineering for Real Time Systems, 1989.

32. [Kamata 2002].
    Kamata, M., "Software Requirements Elicited through Human-Centric Chance Discovery," International Symposium on Chance Discovery, 2002.

33. [Kamata and Tamai 2007].
    Kamata, M., and T. Tamai, "How Does Requirements Quality Relate to Project Success or Failure?," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
34. [Kampen 1982].
    Kampen, G., "SWIFT: A Requirements Specification System for Software," International Symposium on Current Issues of Requirements Environments, Amsterdam: North Holland Publ., 1982, pp. 77-84.
35. [Kampfner 1985].
    Kampfner, R., "Formal Specification of Information System Requirements," Information Processing and Management, 21, 5 (1985), pp. 401-414.
36. [Kamsties and Rombach 1998].
    Kamsties, E., and D. Rombach, "A Framework for Evaluating System and Software Requirements Specification Approaches," in Requirements Targeting Software and Systems Engineering, Broy, M., and B. Rumpe, eds., Lecture Notes in Computer Science 1526, Berlin: Springer, 1998, pp. 203-222.

37. [Kamsties, et al. 1998].
    Kamsties, E., et al., "Requirements Engineering in Small and Medium Enterprises: State of the Practice Problems Solutions and Technology Transfer," Conference on European Industrial Requirements Engineering, 1998.

38. [Kamsties, et al. 1998a].
    Kamsties, E., et al., "Requirements Engineering in Small and Medium Enterprises: State of the Practice Problems Solutions and Technology Transfer," Requirements Engineering, 1998.
39. [Kamsties, et al. 2001].
    Kamsties, E., et al., "Detecting Ambiguities in Requirements Documents Using Inspections," Workshop on Inspections in Software Engineering (WISE'01), Paris, France, pp. 68-80.
    
40. [Kamsties, et al. 2002].
    Kamsties, E., et al., "A Controlled Experiment on the Understandability of Different Requirements Specification Styles," International Workshop on Requirements Engineering: Foundations for Software Quality, Essen, Germany: Essener Informatik Beitiage, 2002, pp. 57-70.
41. [Kamsties, et al. 2003].
    Kamsties, E., et al., "A Controlled Experiment to Evaluate How Styles Affect the Understandability of Requirements Specifications," Information and Software Technology, 45, 14 (November 2003), pp. 955-965.
42. [Kamsties 2005].
    Kamsties, E., "Understanding Ambiguity in Requirements Engineering," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 245-266.
43. [Kang and Ko 1995].
    Kang, K., and K. Ko, "PARTS - A Temporal Logic-Based Real-Time Software Specification Method Supporting Multiple Views," First Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society, December 1994, pp. 328-335.
    
44. [Kang and Ko 1995].
    Kang, K., and G. Ko, "PARTS: A Temporal Logic-based Real-Time Software Specification and Verification Method Supporting Multiple Viewpoints," Seventeenth IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
    
45. [Kantorowitz, et al. 1997].
    Kantorowitz, E., et al., "The Performance of the N-Fold Requirements Inspection Method," (see abstract) Requirements Engineering Journal, 2, 4 (1997), pp. 152-164.
46. [Kanyaru and Phalp 2005].
    Kanyaru, J., and K. Phalp, "Supporting the Consideration of Dependencies in Use-Case Specifications," 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
    
    Karaghouli, see Al-Karaghouli
     
47. [Karagiannis, et al. 2007].
    Karagiannis, D., "Business Process-Based Regulation Compliance: The Case of the Sarbanes-Oxley Act," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
48. [Karakostas, et al. 2002].
    Karakostas, B., et al., "Workflow Requirements Modelling Using XML," Requirements Engineering Journal, 7, 3 (May 2002), pp. 124-138.

49. [Karas and Rhodes 1993].
    Karas, L., and D. Rhodes, "Enabling Concurrent Engineering Through Behavior Analysis," International Symposium on Systems Engineering, 1993.

50. [Karatzas, et al. 2003].
    Karatzas, K., et al., "Identification of Major Components for Integrated Urban Air Quality Management and Information Systems via User Requirements Prioritisation," Environmental Modeling and Software, 18, 2 (2003), pp. 173-178.
51. [Kargi 1989].
    Kargi, H., "The Specification of User Requirements for Data Processing Systems," Angewandt Informatik, 31, 11-12 (November-December 1989), pp. 471-477.
52. [Karlsson 1996].
    Karlsson, J., "Software Requirements Prioritizing," (see abstract) Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 110-116.
53. [Karlsson and Ryan 1996].
    Karlsson, J., and K. Ryan, "Supporting the Selection of Requirements," Eighth International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 146-149.
    
54. [Karlsson and Ryan 1997].
    Karlsson, J., and K. Ryan, "A Cost-Value Approach for Prioritizing Requirements," (see abstract) IEEE Software, 14, 5 (September 1997), pp. 67-74.
    
55. [Karlsson 1997].
    Karlsson, J., "Managing Software Requirements using Quality Function Deployment," Software Quality Journal, 6, 4 (January 1997), pp. 311-326.
    
56. [Karlsson et al. 1997].
    Karlsson, J., et al., "Improved Practical Support for Large-Scale Requirements Prioritizing," (see abstract) Requirements Engineering Journal, 2, 1 (January 1997), pp. 51-60.
    
57. [Karlsson et al. 1998a].
    Karlsson, J., et al., "An Evaluation of Methods for Prioritizing Software Requirements," Information and Software Technology, 39, 14-15 (February 1998), pp. 939-947.
58. [Karlsson et al. 2002].
    Karlsson, L., et al., "Challenges in Market-Driven Requirements Engineering -- An Industrial Interviewing Study," International Workshop on Requirements Engineering: Foundations for Software Quality, Essen, Germany: Essener Informatik Beitiage, 2002, pp. 37-49.
59. [Karlsson and Regnell 2004].
    Karlsson, J., and B. Regnell, "Aligning the Requirements Engineering Process with the Maturity of Markets and Products," International Workshop on Requirements Engineering -- Foundations for Software Quality, Essen, Germany: Essener Informatik Beitiage, 2004.
60. [Karlsson, et al. 2004].
    Karlsson, L., et al., "Requirements Prioritisation: An Experiment on Exhaustive Pair-Wise
    Comparisons versus Planning Game Partitioning," International Conference on Empirical Software Engineering, 2004.
61. [Karlsson, et al. 2007].
    Karlsson, L., et al., "Requirements engineering challenges in market-driven software development An interview study with practitioners," Information and Software Technology, 49, 6 (June 2007), pp. 588-604. 
62. [Karlsson, et al. 2007a].
    Karlsson, L., et al., "Pair-wise comparisons versus planning game partitioning—experiments on requirements prioritisation techniques," Empirical Software Engineering, (2007).
    
63. [Karol 1988].
    Karol, A. "A knowledge-based approach to software requirements specification," Koezlemenyek Magyar Tudomanyos Akademia Szamitastechnikai es Automatizalasi Kutato Intezete, 39, (1988), pp. 67-81.
64. [Karsai et al. 1998].
    Karsai, G., et al., "Model-Integrated Development of Embedded Software," Proceedings of the IEEE, 91, 1 (January 2003), pp. 145-164.
65. [Karsak et al. 2003].
    Karsak, E., et al., "Product Planning in Quality Function Deployment using a Combined Analytic Network Process and Goal Programming Approach," Computers and Industrial Engineering, 44, 1 (January 2003), pp. 171-190.
66. [Kartseva, et al. 2007].
    Kartseva, V., et al., "Value-based Design of Networked Enterprises Using e³control Patterns," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
67. [Kasirun 2005].
    Kasirun, Z. "A Survey of the Requirements Elicitation Practices Among Courseware Developers," Malaysian Journal of Computer Science, 18, 1 (June 2005), pp. 70-77.
68. [Kassab, et al. 2005].
    Kassab, M., et al., "Specifying and separating concerns from requirements to design: a case study," International Multi-Conference on Automation, Control, and Information Technology, Anaheim, California: ACTA Press, 2005, pp. 18-27.
69. [Kassab, et al. 2007].
    Kassab, M., et al., "Towards a Scope Management of Non-Functional Requirements in Requirements Engineering," Workshop on Measuring Requirements for Project and Product Success (MeReP), 2007.
70. [Kassel and Malloy 2003].
    Kassel, N., and B. Malloy, "An Approach to Automate Requirements Elicitation and Specification," IASTED International Conference on Software Engineering and Applications (SEA), 2003.
71. [Kasser 2002].
    Kasser, J., "Does Object-Oriented System Engineering Eliminate the Need for Requirements?," (see abstract) International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 2002.
72. [Kasser 2002a].
    Kasser, J., "A Prototype Tool for Improving the Wording of Requirements," (see abstract) International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 2002.

73. [Kasser and Cook 2002].
    Kasser, J., and S. Cook, "The Communications Requirements Evaluation & Assessment Prototype (CREAP)," International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 2002.

74. [Kasser, et al. 2002].
    Kasser, J., et al., "The Communications Requirements Evaluation & Assessment Prototype (CREAP) Project: A Case Study of a System Engineering Educational Project," (see abstract) International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 2002.
75. [Kasser 2004].
    Kasser, J., "The First Requirements Elucidator Demonstration (FRED) Tool," Systems Engineering, 7, 3 (June 2004), pp. 243-246.
76. [Kasser and Michandani 2005].
    Kasser, J., and C. Michandani, "The MSOCC Data Switch Replacement: A Case Study in Eliciting and Elucidating Requirements," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
77. [Katasonov and Sakkinen 2006]
    Katasonov, A. and M. Sakkinen, "Requirements Quality Control: A Unifying Framework," Requirements Engineering, 11, 1 (March 2006), pp. 42-57.
    
78. [Katic, et al., 1996].
    Katic, N., et al., "Bridging the Gap Between Structured Requirements and Object-Oriented Analysis and Design," (see abstract) 29^th Hawaii International Conference on System Science, Volume 3, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 525-535.
    
79. [Kato, et al. 2001].
    Kato, J., et al., "A Model for Navigating Interview Processes in Requirements Elicitation," (see abstract) Eighth Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 141-148.
    
80. [Kato, et al. 2003].
    Kato, J., et al., "PAORE: Package Oriented Requirements Elicitation," Tenth Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 17-26.
81. [Kato and Namba 2008].
    Kato, Y., and Y. Namba, "Proposal of an Instructional Design for Teaching the Requirement Process for Designing Information Systems," Journal of Informing Science and Information Technology, 5, (2008), pp. 267-279.
82. [Katz and Rashid 2004].
    Katz, S. and A. Rashid, "From Aspectual Requirements to Proof Obligations for Aspect-Oriented Systems," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 48-57.
83. [Kauppinen and Kujala 2001].
    Kauppenin, M., and S. Kujala, "Assessing Requirements Engineering Processes with the REAIMS Model: Lessons Learned," (see abstract) International Symposium on Systems Engineering, Sunnyvale, California: International Council on Systems Engineering, 2001.
    
84. [Kauppinen and Kujala 2001a].
    Kauppenin, M., and S. Kujala, "Starting Improvement of Requirements Engineering Processes: An Experience Report," Lecture Notes in Computer Science 2188, Berlin: Springer, 2001, pp. 196ff.
85. [Kauppinen, et al. 2002].
    Kauppenin, M., et al., "Introducing Requirements Engineering: How to Make a Cultural Change Happen in Practice," (see abstract) Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2002.
    
86. [Kauppinen, et al. 2002a].
    Kauppenin, M., et al., "Lessons Learned from Applying the Requirements Engineering Good Practice Guide for Process Improvement," International Conference on Software Quality (ECSQ), Lecture Notes in Computer Science 2349, Berlin: Springer, 2002, pp. 73ff.
87. [Kauppinen, et al. 2004].
    Kauppenin, M., et al., "Introducing Requirements Engineering Processes throughout Organizations: Success Factors and Challenges," Information and Software Technology, (2004).
88. [Kauppinen, et al. 2007].
    Kauppenin, M., et al., "Requirements Engineering as a Driver for Innovations," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
89. [Kavakli, et al. 1996].
    Kavakli, E., et al., "Using Scenarios to Systematically Support Goal-Directed Elaboration for Information System Requirements," (see abstract) IEEE Symposium and Workshop on Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 308-314.
    
90. [Kavakli 2001].
    Kavakli, E., "Goal-Oriented Requirements Engineering: A Unifying Framework," Requirements Engineering Journal, 6, 4 (2001), pp. 237-251.
91. [Kawashima, et al. 1971].
    Kawashima, H., et al., "Functional Specification of Call Processing by State Transition Diagram," IEEE Transactions on Communications, 19, 5 (October 1971), pp. 581-587.
92. [Kayaligil and Hashemipour 2001].
    Kayaligil, S., and M. Hashemipour, "Integration Needs and Consistency Evaluation for Requirements Analysis in CIM Development," International Journal of Computer Applications in Technology, 14 (2001), pp. 145ff (Switzerland).

93. [Kazhamiakin, et al. 2004].
    Kazhamiakin, R., et al., "Formal Verification of Requirements Using SPIN: A Case Study on Web Services," Second International Conference on Software Engineering and Formal Methods, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 406-415.

94. [Kazman, et al. 2005].
    Kazman, R., et al., "From requirements negotiation to software architecture decisions," Information and Software Technology, 47, 8 (June 2005), pp. 511-520.
95. [Kazmierczak, et al. 2000].
    Kazmierczak, E., et al., "Verifying Requirements Through Mathematical Modeling and Animation," International Journal of Software Engineering and Knowledge Engineering, 10, 2 (2000), pp. 251-272.
    
96. [Kealey, et al. 2007].
    Kealey, J., et al., "Integrating an Eclipse-based scenario modeling environment with a requirements management system," Canadian Conference on Electrical and Computer Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 4ff.
97. [Kececi, et al. 2006].
    Kececi, N., et al., "Modeling functional requirements to support traceability analysis," IEEE International Symposium on Industrial Electronics, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 3305-3310.
    
98. [Kecheng, et al. 1999].
    Ketheng, L., et al., "Requirements Recovery from Legacy Systems by Analyzing and Modeling Behavior," IEEE International Conference on Software Maintenance, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 3-12.
    
99. [Keck and Kuehn 1998].
    Keck, D., and P. Kuehn, "The Feature and Service Interaction Problem in Telecommunications Systems: A Survey," IEEE Transactions on Software Engineering, 24, 10 (October 1998), pp. 779-796.
    
    Kedian, see Mu, K.
    
    
100. [Keenan and Bustard 2005].
     Keenan, F., and D. Bustard, "BPUF: Big Picture Up Front," Lecture Notes in Computer Science 3556, Berlin: Springer, 2005, pp. 251-254.
101. [Keepence, et al. 1995].
     Keepence, B., et al., "SMARTRe Requirements: Writing Reusable Requirements," IEEE Symposium and Workshop on Systems Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 1995, pp. 27-34.
     
102. [Kefer 1994].
     Kefer, M., "Improving Requirements Processing, A Case Study," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 987-990.
     
103. [Keil and Carmel 1995].
     Keil, M., and E. Carmel, "Customer-Developer Links in Software Development," Communications of the ACM, 38, 5 (May 1995), pp. 33-44.

104. [Keller 1983].
     Keller, R., The practice of structured analysis: Exploding myths, 1983.

105. [Keller, et al. 1990].
     Keller, S., et al., "Specifying Software Quality Requirements with Metrics," in System and Software Requirements Engineering, R. Thayer and M. Dorfman, eds., Los Alamitos, California: IEEE Computer Society Press, 1990, pp. 145-163.
106. [Kelly, et al. 1992].
     Kelly, J., et al., "An Analysis of Defect Densities Found During Software Inspections," Journal of Systems and Software, 17 (1992).
107. [Kenley 2004].
     Kenley, C., "Requirements Risk Assessment - Integrating QFD and Risk Assessment," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
108. [Kennedy, et al. 1998].
     Kennedy, L., et al., "A Proven Approach to Requirements Baseline Management," Eighth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1998.
109. [Kennedy 1999].
     Kennedy, L., "A Proven Approach to Requirements Baseline Management," (see abstract) International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1999.
110. [Kent, et al. 1993].
     Kent, S., et al., "Formally Specifying Temporal Constraints and Error Recovery," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 208-215.
     
111. [Kepchar 1994].
     Kepchar, K., "Breathing Life into Existing DoD Programs," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 121-127.
112. [Kepchar and Yeager-Key 2002].
     Kepchar, K., and J. Yeager-Key, "Requirements Management by the Numbers: Applying Common Criteria Beyond the INFOSEC Arena," International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, 2002.
113. [Kerkow, et al. 2005].
     Kerkow, D., et al., "Elicitation and Documentation of Non-Functional Requirements for Sociotechnical Systems," in Requirements Engineering for Sociotechnical Systems, J. Maté, and A. Silva, eds., Hershey, Pennsylvania: Information Science Publishing, 2005, pp. 284-302.
114. [Kerner and Malhotra 1983].
     Kerner, D., and A. Malhotra, "Generating Requirements from Enterprise Analysis," AFIPS National Computer Conference, Arlington, VA: AFIPS, 1983, pp. 255-260.
115. [Kesten and Pnueli 1991].
     Kesten, Y., and A. Pnueli, "Timed and Hybrid Statecharts and Their Textual Representation," (see abstract) Formal Techniques in Real-Time and Fault Tolerant Systems, Berlin: Springer-Verlag, 1991, pp. 591-620.
     
116. [Keuffels 1999].
     Keuffel, W., "Great Books on Gathering Requirements," Software Development, 7, 12 (December 1, 1999), pp. 23-24.

117. [Khamooshi and King 2004].
     Khamooshi, H., and A. King, "IS/IT REQUIREMENTS ELICITATION AND SPECIFICATION PROCEDURE ASSESSMENT WITHIN A UK GOVERNMENT SERVICE," Journal of Information Technology Management, (2004).

118. [Khazaei and Roast 2004].
     Khazaei, B., and C. Roast, "The Influence of Formal Representation on Solution Specification," Requirements Engineering, 2004.

119. [Kholkar, et al. 2005].
     Kholkar, D., et al., "Visual specification and analysis of use cases," Symposium on Software Visualization, 2005.

120. [Kiedaisch, et al. 2001].
     Kiedaisch, F., et al., "Requirements Archeology: From Unstructured Information to High-Quality Specifications (in the Automotive Industry)," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 304-305.
     
121. [Kiedaisch and Alexander 2002].
     Kiedaisch, F., and I. Alexander, "Toward Recyclable Requirements," Ninth International Conference on Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2002, pp. 9-16.
122. [Kilov 1994].
     Kilov, H., Information Modeling: An Object-Oriented Approach, Upper Saddle River, New Jersey: Prentice Hall, 1994.
     
123. [Kilov 1996].
     Kilov, H., and I. Simmonds, "Business Patterns: Reusable Abstract Constructs for Business Specification," in Implementing Systems for Supporting Management Decisions: Concepts, Methods and Experiences, P. Humphreys et al., eds., Chapman and Hall, 1996, pp. 225-248.
     
124. [Kilov 1996].
     Kilov, H., Object-Oriented Behavioral Specifications, Norwell, Massachusetts: Kluwer Academic Publishers, 1996.
125. [Kilov 1998].
     Kilov, H., Business Specifications: The Key to Successful Software Engineering, Upper Saddle River, New Jersey: Prentice Hall, 1998.
     
126. [Kilov and Ash 1999].
     Kilov, H., and A. Ash, "On the Structure of Convincing Specifications," in Behavioral Specifications of Businesses and Systems, H. Kilov, et al., eds., Norwell, Massachusetts: Kluwer Academic Publishers, 1999, pp.141-160.
     
127. [Kilov, et al. 1999].
     Kilov, H. et al., eds., Behavioral Specifications of Businesses and Systems, Norwell, Massachusetts: Kluwer Academic Publishers, 2002.
     
128. [Kilov 2000].
     Kilov, H., "Business Specifications and RM-ODP," 34th International Conference on Technology of Object-Oriented Languages and Systems (TOOLS 34), Los Alamitos, California: IEEE Computer Society, 2000, pp. 411-420.
     
129. [Kilov 2000a].
     Kilov, H., "Representing Business Specifications in UML," 9th OOPSLA Workshop on Behavioral Semantics, Boston, Massachusetts: Northeastern University, 2000, pp. 102-111.
130. [Kilov 2002].
     Kilov, H., Business Models: A Guide for Business and IT, Upper Saddle River,