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

M

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. [Maarek and Berry 1989].
   Maarek, Y., and D. Berry, "The Use of Lexical Affinities in Requirements Extraction," Fifth International Workshop on Software Specification and Design, ACM Press, May 1989.
2. [Mac an Airchinnigh 1984].
   Mac an Airchinnigh, M., "Some notes on the representation of the user's conceptual model," ACM SIGCHI Bulletin, 16, 2  (October 1984), pp. 62-69.
   
3. [Macaulay et al. 1990].
   Macaulay, L., et al., "USTM: A New Approach to Requirements Specification," Interacting with Computers, 2, 1 (April 1990), pp. 92-118.
   
4. [Macaulay 1993].
   Macaulay, L., "Requirements Capture as a Cooperative Activity," International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 174-181.
5. [Macaulay 1994].
   Macaulay, L., "Cooperative Requirements Capture: Control Room 2000," in Requirements Engineering Social and Technical Issues, M. Jirotka, and J. Goguen, eds., London: Academic Press, 1994.
6. [Macauley and Mylopoulos 1995].
   Macaulay, L., and J. Mylopoulos, "Requirements Engineering: An Educational Dilemma," Automated Software Engineering, 2, 4 (December 1995), pp. 343-351.
   
7. [Macaulay 1996].
   Macaulay, L., Requirements Engineering, London, UK: Springer, 1996.
8. [Macaulay 1996a].
   Macaulay, L., "Requirements for Requirements Engineering Techniques," Second International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 157-164.
9. [Macaulay 1999].
   Macaulay, L., "Seven-Layer Model of the Role of the Facilitator in Requirements Engineering," Requirements Engineering Journal, 4, 1 (1999), pp. 38-59.
10. [Maccari 1999].
    Maccari, A., "The Challenges of Requirements Engineering in Mobile Telephones Industry," International Workshop on Database and Expert System Applications, Los Alamitos, California: IEEE Computer Society Press, 1999.
    
11. [Macfarlane and Reilly 1995].
    Macfarlane, I., and I. Reilly, "Requirements Traceability in an Integrated Development Environment," (see abstract) Second IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, March 1995.
12. [Machado, et al. 2005].
    Machado, R., "Specification of Requirements Models," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 47-68.
13. [Macias and Pulman 1993].
    Macias, B., and S. Pulman, "Natural Language Processing for Requirements Specifications," in Safety Critical Systems: Current Issues, Techniques, and Standards, London: Chapman and Hall, 1993.
    
14. [Maciaszek 2001].
    Maciaszek, L., Requirements Analysis and System Design: Developing Information Systems with UML, Harrow, Essex, UK: Pearson Education Limited, 2001.
15. [Maciaszek 2005].
    Maciaszek, L., Requirements Analysis and System Design, 2nd edition, Reading, Massachusetts: Addison Wesley, 2005.
16. [Maciaszek and Liong 2005].
    Maciaszek, L., and B. Liong, Practical Software Engineering, Harrow, Essex, UK: Pearson Education Limited, 2005, Chapters 6-8.
17. [MacNish and Williams 1998].
    MacNish, C., and M. Williams, "From belief revision to design revision: Applying theory change to changing requirements," From belief revision to design revision: Applying theory change to changing requirements, Lecture Notes in Computer Science, Volume 1359, Berlin: Springer, 1998, pp. 206-220. 
18. [MacStravic 1996].
    MacStravic, J., "An Integrated Procedure For Explaining Software Requirements," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
    
    Maddah, see El-Maddah
     
19. [Madsen and Aiken 1993].
    Madsen, K., and P. Aiken, "Experiences Using Cooperative Interactive Storyboard Prototyping," Communications of the ACM, 36, 4 (June 1993), pp. 57-66.
    
20. [Maßen and Lichter 2004].
    von der Maßen, T., and H. Lichter, "RequiLine: A Requirement Engineering Tool for Software Product Lines," Lecture Notes in Computer Science, Volume 3014, Berlin: Springer, 2004, pp. 168-180. 
21. [Magee, et al. 2000].
    Magee, J., et al., "Hybrid-Model Visualization in Requirements and Design: A Preliminary Investigation," (see abstract) Tenth International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 3-9.
22. [Maguire 2004].
    Maguire, S., "Reconciling the system requirements process in changing business environments," Information Management and Computer Security (2004).
23. [Maguire, et al. 2007].
    Maguire, S., et al., "Identifying the range of customer listening tools: a logical pre-cursor to CRM?," Industrial Management and Data Systems (2007).
24. [Maiden 1992].
    Maiden, N., Analogical Specification Reuse During Requirements Analysis, City University of London Ph.D. Dissertation, 1992.
25. [Maiden and Sutcliffe 1991].
    Maiden, N., and A. Sutcliffe, "Reuse of Analogous Specifications During Requirements Analysis," Sixth International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1991, pp. 220-223. 
26. [Maiden and Sutcliffe 1992].
    Maiden, N., and A. Sutcliffe, "Exploiting Reusable Specifications through Analogy," Communications of the ACM, 34, 5 (May 1992), pp. 55-64. 
    
27. [Maiden and Sutcliffe 1993].
    Maiden, N., and A. Sutcliffe, "Requirements Engineering By Example: An Empirical Study," (see abstract) International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1993, pp. 104-111.
    
28. [Maiden and Rugg 1994].
    Maiden, N., and G. Rugg, "Knowledge Acquisition Techniques in Requirements Engineering," (see abstract) Software Engineering Journal, 1995.
    
29. [Maiden and Sutcliffe 1994].
    Maiden, N., and A. Sutcliffe, "Requirements Critiquing Using Domain Abstractions," (see abstract) IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 184-193.
    
30. [Maiden and Sutcliffe 1994a].
    Maiden, N., and A. Sutcliffe, "Computational Mechanisms for Reuse of Domain Knowledge During Requirements Engineering," (see abstract) IEEE Workshop on Research Issues in the Intersection Between Software Engineering and Artificial Intelligence, Los Alamitos, California: IEEE Computer Society Press, May 1994.
    
31. [Maiden, et al., 1995].
    Maiden, N., et al., "How People Categorise Requirements for Reuse: A Natural Approach," (see abstract) Second International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
    
32. [Maiden, et al. 1995a].
    Maiden, N., et al., "Computational Mechanisms for Distributed Requirements Engineering," (see abstract) Seventh International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, June 1995, pp. 8-15.
    
33. [Maiden, et al. 1996].
    Maiden, N., et al., "Multi-Perspective Requirements Engineering within NATURE," (see abstract) Requirements Engineering Journal, 1, 3 (1996), pp. 157-169.
    
34. [Maiden and Sutcliffe 1996].
    Maiden, N., and A. Sutcliffe, "ACRE: Selecting Methods for Requirements Acquisition," Software Engineering Journal, 11, 3 (May 1996), pp. 183-192.
    
35. [Maiden and Sutcliffe 1996a].
    Maiden, N., and A. Sutcliffe, "Analogical Retrieval in Reuse-Oriented Requirement Engineering," Software Engineering Journal, 11, 5 (September 1996), pp. 281-292.
    
36. [Maiden and Sutcliffe 1996b].
    Maiden, N., and A. Sutcliffe, "A Computational Mechanism for Parallel Problem Decomposition During Requirement Engineering," Eighth International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1996, pp. 159-163.
    
37. [Maiden, et al. 1997].
    Maiden, N., et al., "Lessons Learned During Requirements Acquisition for COTS Systems," Communications of the ACM, 40, 12 (December 1997), pp. 21-25.
38. [Maiden, et al. 1997a].
    Maiden, N., et al., "A Software Tool for Scenario Generation and Use," International Workshop on Requirements Engineering: Foundations for Software Quality, Namur, Belgium: Presses Universitaires de Namur, 1997, pp. 223-238.
39. [Maiden 1998].
    Maiden, N., "CREWS-SAVRE: Scenarios for Acquiring and Validating Requirements," Automated Software Engineering, 5, 4 (October 1998), pp. 419-446.
    
40. [Maiden and Hare 1998].
    Maiden, N., and M. Hare, "Problem Domain Categories in Requirements Engineering," International Journal of Human-Computer Studies, 49, 3 (September 1998), pp. 281-304.
41. [Maiden and Ncube 1998].
    Maiden, N., and C. Ncube, "Acquiring COTS Software Selection Requirements," IEEE Software, 15, 2 (March 1998), pp. 46-56.
42. [Maiden, et al. 1998].
    Maiden, N., et al., "CREWS Validation Frames: Patterns for Validating Systems Requirements," (see abstract) Fourth International Workshop on Requirements Engineering: Foundations for Software Quality, Pisa, Italy, June 1998.
43. [Maiden, et al. 1998a].
    Maiden, N., et al., "CREWS-SAVRE: Systematic Scenario Generation and Use," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 148-155.
44. [Maiden, et al. 1999].
    Maiden, N., et al., "Guidelines for Better Scenarios: Supporting Theories and Evidence," International Workshop on Database and Expert System Applications, Los Alamitos, California: IEEE Computer Society Press, 1999.

45. [Maiden, et al. 1999a].
    Maiden, N., et al., "Co-operative scenario based approach to acquisition and validation of system requirements: how exceptions can help!," Interacting with Computers, 1999.

46. [Maiden and Gizikis 2001].
    Maiden, N., and A. Gizikis, "Where Do Requirements Come From?" IEEE Software, 18, 5 (September/October 2001), pp. 10-12.
47. [Maiden, et al.  2002].
    Maiden, N., et al., "Making Decisions with Requirements: Integrating I* Goal Modeling and the AHP," International Workshop on Requirements Engineering -- Foundations for Software Quality, Essen, Germany: Essener Informatik Beitiage, 2002, pp. 24-35.
48. [Maiden, et al.  2003].
    Maiden, N., et al., "Integrating RE Methods to Support Use Case Based Requirements Specification," 11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 369-370.
49. [Maiden, et al. 2004].
    Maiden, N., et al., "Towards Pattern-Based Generation of Requirements from System Models," International Workshop on Requirements Engineering -- Foundations for Software Quality, Essen, Germany: Essener Informatik Beitiage, 2004.
50. [Maiden, et al. 2004a].
    Maiden, N., et al., "Provoking Creativity: Imagine What Your Requirements Could Be Like," IEEE Software, 21, 5 (September/October 2004), pp. 68-75.
51. [Maiden, et al. 2004b].
    Maiden, N., et al., "Model-Driven Requirements Engineering: Synchronising Models in an Air Traffic Management Case Study," Lecture Notes in Computer Science, Volume 3084, Berlin: Springer, 2004, pp. 368-383. 
52. [Maiden, et al. 2004c].
    Maiden, N., et al., "Integrating creativity workshops into structured requirements processes," conference on Designing interactive systems: processes, practices, methods, and techniques, New York: ACM Press, 2004, pp. 113-122.
53. [Maiden 2005]
    Maiden, N., "What has requirements research ever done for us? (goal-modeling techniques)," IEEE Software, 22, 4 (July/August 2005), pp. 104-105.
54. [Maiden and Robertson 2005].
    Maiden, N., and S. Robertson, "Integrating Creativity into Requirements Processes: Experiences with an Air Traffic Management System," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 105-116.
55. [Maiden and Robertson 2005a].
    Maiden, N., and S. Robertson, "Developing Use Cases and Scenarios in the Requirements Process," IEEE International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 561-570.
    
56. [Maiden, et al. 2005].
    Maiden, N., et al., "Shake, Rattle, and Requirements," IEEE Software, 22, 1 (January/February 2005), pp. 13-15.
57. [Maiden, et al. 2005a]
    Maiden, N., et al., "Generating Requirements from System Models Using Patterns: A Case Study," Requirements Engineering, Requirements Engineering, 10, 4 (December 2005), pp. 276-288.
58. [Maiden 2006].
    Maiden, N., "The RE’04 conference," Requirements Engineering, 11, 2 (April 2006), pp. 109-110.
59. [Maiden 2006a].
    Maiden, N., et al., "Servicing Your Requirements," IEEE Software, 23, 5 (September/October 2006), pp. 14-16.
60. [Maiden 2006b].
    Maiden, N., et al., "Improve Your Requirements: Quantify Them," IEEE Software, 23, 6 (November/December 2006), pp. 68-69.
61. [Maiden, et al. 2006].
    Maiden, N., et al., "Making Mobile Requirements Engineering Tools Usable and Useful," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
62. [Maiden, et al. 2006a].
    Maiden, N., et al., "Analyzing I* System Models for Dependability Properties: The Uberlingen Accident," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
63. [Maiden, et al. 2007].
    Maiden, N., et al., "Can Requirements Be Creative?," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 632-641.
64. [Maiden, et al. 2007a].
    Maiden, N., et al., "Using Satisfaction Arguments to Enhance i* Modelling of an Air Traffic Management System," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
65. [Maiden, et al. 2007b].
    Maiden, N., et al., "Exploring Scenario Forms and Ways of Use to Discover Requirements on Airports that Minimize Environmental Impact," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
66. [Maiocchi 1983].
    Maiocchi, M., "The use of Petri nets in requirements and functional specification," Tanulmanyok Magyar Tudomanyos Akademia Szamitastechnikai es Automatizalasi Kutato Intezet, 150 (1983), pp. 167-188.
67. [Malmqvist 2001].
    Malmqvist, J., "Implementing Requirements Management: A Task for Specialized Software Tools or PDM Systems?" Systems Engineering, 4 (2001), pp. 49ff.
68. [Maindantchik, et al. 2002].
    Maindantchik, C., et al., "Learning Organizational Knowledge: An Evolutionary Proposal for Requirements Engineering," (see abstract) International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2002, pp. 151-157.
    
69. [Mala and Uma 2006].
    Mala, G., and G. Uma, "Automatic Construction of Object Oriented Design Models [UML Diagrams] from Natural Language Requirements Specification," PRICAI 2006: Trends in Artificial Intelligence, Lecture Notes in Computer Science 4099, Berlin: Springer, 2006.
    
70. [Malaiya and Denton 1999].
    Malaiya, Y., and J. Denton, "Requirements Volatility and Defect Density," Tenth International Symposium on Software Reliability Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 285-294.
    
71. [Malhart 1995].
    Malhart, B., "Software Fault Tree Analysis for a Requirements System Model," IEEE Symposium and Workshop on Systems Engineering of Computer-Based Systems, Los Alamitos, California: IEEE Computer Society Press, 1995, pp. 133-140.
72. [Malin, et al., 2005].
    Malin, J., et al., "Transforming Functional Requirements and Risk Information into Models for Analysis and Simulation," IEEE Aerospace Conference, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 1-7.
73. [Malinowski and Zimányi 2006].
    Malinowski, E., and E. Zimányi, "Requirements specification and conceptual modeling for spatial data warehouses," in On the Move to Meaningful Internet Systems, 2006.
    
74. [Mallick and Krishna 1999].
    Mallick, S., and S. Krishna, "Requirements Engineering: Problem Domain Knowledge Capture and the Deliberation Process Support," (see abstract) Tenth International Workshop on Database and Expert Systems Applications, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 392-397.
    
75. [Malmqvist 2001].
    Malmqvist, J., "Implementing Requirements Management: A Task for Specialized Software Tools or PDM Systems?" Systems Engineering, 4 (2001), pp. 49ff.
76. [Mamalaki, et al. 1988].
    Mamalaki, M., et al., "On the development of information systems - from requirements modeling to system design," European Conference on Information Technology for Organisational Systems, Amsterdam: North Holland, 1988, pp. 560-567.
77. [Maniatty and Zaki 2000].
    Maniatty, W., and M. Zaki, "A Requirements Analysis for Parallel KDD Systems," Workshop on Parallel and Distributed Processing (IPDPS), Lecture Notes in Computer Science 1800, Berlin: Springer, 2000, pp. 358ff.
78. [Mannion, et al. 1998].
    Mannion, M., et al., "Using Viewpoints to Define Domain Requirements," (see abstract) IEEE Software, 15, 1 (January-February 1998), pp. 95-102.
    
79. [Mannion, et al. 1999].
    Mannion, M., et al., "Reusing Single System Requirements from Application Family Requirements," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 453-462.
    
80. [Mannion, et al. 2000].
    Daneva, M., "Representing Requirements on Generic Software in an Application Family Model," in Software Reuse: Advances in Software Reusability, Lecture Notes in Computer Science 1844, Berlin: Springer, 2000, pp. 153-169.
81. [Manos 1993].
    Manos, K., "Strategies for Preventing Future 'Requirements Creep,'" Third Annual National Council on Systems Engineering International Symposium, Sunnyvale, California: NCOSE, pp. 375-380.
    
82. [Mao, et al. 2006].
    Mao, C., et al., "A study on the distribution and cost prediction of requirements changes in the software life-cycle," International Software Process Workshop (SPW 2005), Lecture Notes in Computer Science, Volume 3840, Berlin: Springer, 2006, pp. 136-150. 
83. [Mar 1994].
    Mar, B., "Requirements for Development of Software Requirements," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 39-44.
    
84. [Marakas and Elam 1998].
    Marakas, G., and J. Elam, "Semantic Structuring in Analyst Acquisition and Representation of Facts in Requirements Analysis," Information Systems Research, 9, 1 (January 1998), pp. 37-63.
85. [Marca and Thornhill 1982].
    Marca, D., and D. Thornhill, "Modeling Software Configurability Requirements," International Symposium on Current Issues of Requirements Environments, 1982.
86. [Marca and McGowan 1988].
    Marca, D., and C. McGowan, SADT, New York: McGraw Hill, 1988.
87. [Marca 1991].
    Marca, D., "Specifying Groupware Requirements from Direct Experience," Sixth International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1991, pp. 224-232.
    
88. [Marca and McGowan 1993].
    Marca, D., and C. McGowan, "Specification Approaches Express Different World Hypotheses," IEEE International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, December 1993.
89. [Marconi, et al. 2006].
    Marconi, A., et al., "Specifying Data-Flow Requirements for the Automated Composition of Web Services," IEEE International Conference on Software Engineering and Formal Methods, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 147-156.
90. [Marconi, et al. 2006a].
    Marconi, A., et al., "Implicit vs. Explicit Data-Flow Requirements in Web Service Composition Goals," Service-Oriented Computing – ICSOC 2006, Lecture Notes in Computer Science, Volume 4294, Berlin: Springer, 2006, pp. 459-464.
91. [Marietto, et al. 2003].
    Marietto, M., et al., "Requirements Analysis of Agent-Based Simulation Patterns: State of the Art and New Prospects," Lecture Notes in Computer Science, Volume 2581, Berlin: Springer, 2003, pp. 125-141. 
92. [Mark, et al. 2004].
    Mark., G., et al., "Expanding Horizons in Requirements Engineering: Examining Requirements During Groupware Tool Diffusion," International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 186-195.
93. [Markus and Keil 1994].
    Markus, M., and M. Keil, "If We Build It, They Will Come: Designing Information Systems that People Want To Use," Sloan Management Review (1994), pp. 11-25. 
94. [Marliss 2005].
    Marliss, G., "Book review: Review of "Systems Modeling & Requirements Specification Using ECSAM: An Analysis Method for Embedded and Computer-Based Systems," ACM Software Engineering Notes, 30, 4 (July 2005), pp. 83-84. 
95. [Marmaridis and Unhelkar 2005].
    Marmaridis, I., and B. Unhelkar, "Challenges in mobile transformations: a requirements modeling perspective for small and medium enterprises," IEEE International Conference on Mobile Business, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 16-22.

96. [Martin, et al. 1989].
    Martin, M., et al., "The BEST Method for Requirements Capture and Functional Specification," International Conference on Software Engineering for Telecommunication Switching Systems, 1989.

97. [Martin 1990].
    Martin, J., Information Engineering, Vols. I to III, Upper Saddle River, New Jersey: Prentice Hall, 1990.
98. [Martin and Tsai 1990].
    Martin, J., and W. Tsai, "N-Fold Inspection: A Requirements Analysis Technique," Communications of the ACM, 33, 2 (February 1990), pp. 225-232.
99. [Martin 1993].
    Martin, J., "Managing Integrated Product Teams During the Requirements Definition Phase," Third International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, July 1993.
100. [Martin 1995].
     Martin, J., "Requirements Mythology: Shattering Myths About Requirements and the Management Thereof," Fifth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.
101. [Martin 1997].
     Martin, J., "A Process for Requirements and Architecture Definition," Seventh Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1997.
102. [Martin 1998].
     Martin, C., User-Centered Requirements Analysis, Upper Saddle River, New Jersey: Prentice Hall, 1998.
103. [Martin, et al. 2002].
     Martin, E., et al., Managing Information Technology, Third Edition, Upper Saddle River, New Jersey: Pearson, 2002, Chapter 9.
104. [Martin and Arnold 2005].
     Martin, J., and S. Arnold,  "Requirements: The Good, The Bad, and the Ugly," Fifteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2005.
105. [Martin and Gregor 2005].
     Martin, N., and S. Gregor, "Requirements Engineering: A Case of Developing and Managing Quality Software Systems in the Public Sector," in Engineering and Managing Software Requirements, A. Aurum and C. Wohlin, eds., Berlin: Springer, 2005, pp. 353-372.
106. [Martin-Rubio and Martinez-Bejar 1997].
     Martin-Rubio, F., and R. Martinez-Bejar, "A Mathematical Functions-Based for Analyzing Elicited Knowledge," Ninth IEEE International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, June 1997, pp. 62-69.
     
     Martinez, see Perez-Martinez
     
     
107. [Martinka 1995].
     Martinka, J., "Functional Requirements for Client/Server Performance Modeling: An Implementation Using Discrete Event Simulation," First IEEE International Conference on Engineering of Complex Computer Systems, Los Alamitos, California: IEEE Computer Society Press, November 1995.
     
108. [Martins and Daltrini 1999].
     Martins, L., and B. Daltrini, "An Approach to Software Requirements Elicitation Using Precepts from Activity Theory," IEEE International Conference on Automated Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 15-23.
     
109. [Marx-Gomez, et al. 2003].
     Marx-Gomez, J., et al., "Analysis of User's Behaviour in Very Large Business Application Systems with Methods of the Web Usage Mining - A Case Study on SAP ," Lecture Notes in Computer Science 2663, Berlin: Springer, 2003, pp. 329-338.
110. [Masera and Morris 1998].
     Masera, M., and P. Morris, "Embedded Systems: The Challenges for Requirements Engineering," Fourth International Workshop on Requirements Engineering: Foundations of Software Quality, June 1998.
111. [Mason and Carey 1983].
     Mason, R., and T. Carey, "Prototyping Interactive Information Systems," Communications of the ACM, 26, 5 (May 1983), pp. 347-354.
112. [Mason, et al. 2003].
     Mason, P., et al., "On The Role of Traceability for Standards Compliance Tracking Requirements to Code," Lecture Notes in Computer Science, Volume 2788, Berlin: Springer, 2003, pp. 303-316. 
113. [Mason 2006].
     Mason, D., "The tools dilemma: The necessity of developing functional requirements before purchasing tools and solutions," Water Environment and Technology, 18, 6 (June, 2006), p 53-54.
114. [Massacci, et al. 2005].
     Massacci, F., et al., "Using a security requirements engineering methodology in practice: The compliance with the Italian data protection legislation," Computer Standards and Interfaces, 27, 5 (June 2005), pp. 445-455.
115. [Massonet and van Lamsweerde 1997].
     Massonet, P., and A. van Lamsweerde, "Analogical Reuse of Requirements Frameworks," (see abstract) IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1997, pp. 26-37.
116. [Mate 1986].
     Mate, L., "Requirement specification techniques in hardware design," Joint Bulgarian-Hungarian Workshop on `Mathematical Cybernetics and Data Processing', 1986, pp. 103-109.
117. [Maté and Silva 2005].
     Maté, J., and A. Silva, Requirements Engineering for Sociotechnical Systems, Hershey, Pennsylvania: Information Science Publishing, 2005.
118. [Matsumoto 1977].
     Matsumoto, Y., "A Method of Software Requirements Definitions in Process Control," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1977, pp. 128-132.
119. [Matsumoto and Kawakita 1980].
     Matsumoto, Y., and S. Kawakita, "A Method of Bridge Discontinuity Between Requirements Specification and Design," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1980, pp. 259-266.
120. [Matsumoto and Matsumura 1981].
     Matsumoto, Y., and K. Matsumura, "A Specification Analysis and Documentation System for Process Control Software," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1981, pp. 411-417.
121. [Matsumoto 1982].
     Matsumoto, Y., "SOFTWARE DESIGN METHODOLOGY: BRIDGE FROM REQUIREMENTS SPECIFICATION TO SOFTWARE DESIGN," Japan Annual Reviews in Electronics, Computers & Telecommunications, Ohmsha, pp. 175-192.
122. [Matsumoto, et al. 1982].
     Matsumoto, Y., et al., "Specification Transformations and a Requirements Specification of Real-Time Control," International Symposium on Current Issues of Requirements Environments, 1982.
123. [Matsumoto, et al. 1984].
     Matsumoto, Y., et al., "Flow Sketch Methodology: A Practical Requirements Definition Technique Based on Data Flow Concept," IEEE International Conference on Data Engineering, Los Alamitos, California: IEEE Computer Society Press, 1984, pp. 342-347.   
124. [Matsumoto and Ajisaka 1990].
     Matsumoto, Y., and T. Ajisaka, "A distributed type computer-aided software requirements engineering environment," IFAC Workshop on Distributed Computer Control Systems, Oxford, UK: Pergamon Press, 1990, pp. 1-7.   
125. [Matsumura, et al. 1987].
     Matsumura, K., et al., "An Application of Structural Modeling to Software Requirements and Design," IEEE Transactions on Software Engineering, 13, 4 (April 1987), pp. 461-471.
126. [Matsushita, et al. 2004].
     Matsushita, M., et al., "An Interactive Visualization Method of Numerical Data Based on Natural Language Requirements," International Journal of Human-Computer Studies, 60, 4 (April 2004), pp. 469-488.
     
127. [Matthews and Ryan 1989].
     Matthews, B., and K. Ryan, "Requirements Specification Using Conceptual Graphs," (see abstract) 2nd International CASE Conference, London, UK, 1989.
128. [Matulevicius and Straunskas 2003].
     Matulivicius, R., and D. Straunskas, "Evaluation Framework of Requirement Engineering Tools for Verification and Validation," Lecture Notes in Computer Science, Volume 2784, Berlin: Springer, 2003, pp. 251-263. 
129. [Matulevicius 2004].
     Matulivicius, R., "How Requirement Specification Quality Depends on Tools: A Case Study," Lecture Notes in Computer Science, Volume 3084, Berlin: Springer, 2004, pp. 353-367. 
130. [Matulevicius 2005].
     Matulivicius, R., "Prototype of the Evaluation Framework for Functional Requirements of RE-tools," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 483-484.
131. [Matulevicius and Heymans 2007].
     Matulivicius, R., and P. Heymans, "Comparison of Goal Modelling Languages: an Experiment," International Working Conference on Requirements Engineering Foundations for Software Quality (REFSQ' 07), Berlin: Springer, 2007.
132. [Matulevicius and Heymans 2007a].
     Matulivicius, R., and P. Heymans, "Visually Effective Goal Models Using KAOS," Advances in Conceptual Modeling - Theory and Practice, Berlin: Springer, 2007.
133. [Mavin and Maiden 2003].
     Mavin, A., and N. Maiden, "Determining Socio-Technical Systems Requirements: Experiences with Generating and Walking through Scenarios," (see abstract) International Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 213-222.
134. [Mauco, et al. 2006].
     Mauco, M., et al., "Formalising a derivation strategy for formal specifications from natural language requirements models," International Symposium on Signal Processing and Information Technology, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 646-651.
     
135. [May 2004].
     May, H., "What Do You Get if Your Cross a Project Manager with a Requirements Engineer?," IEE Engineering Management, April/May 2004, pp. 18-20.
     
136. [Mayhew and Alessi 1994].
     Mayhew, M., and R. Alessi, "Responsive Constructivist Requirements Engineering: A Paradigm," Fourth International Symposium on Systems Engineering, Sunnyvale, California: National Council on Systems Engineering, August 1994, pp. 91-98.
     
137. [Mayr, et al. 2007].
     Mayr, H., et al., "Business Process Modeling and Requirements Modeling," IEEE International Conference on the Digital Society, Los Alamitos, California: IEEE Computer Society Press, 2007.
138. [Mays, et al. 1985].
     Mays, R., et al., "PDM: A Requirements Methodology for Software System Enhancements," IBM Systems Journal, 24, 2 (February 1985), pp. 134-149.
     
139. [Mazón, et al. 2007].
     Mazón, J.-N., "A Model-Driven Goal-Oriented Requirement Engineering Approach for Data Warehouses," Advances in Conceptual Modeling - Theory and Practice, Berlin: Springer, 2007.
140. [Mazza, et al., 1996].
     Mazza, C., et al., Software Engineering Standards, Upper Saddle River, New Jersey: Prentice Hall, 1996, Chapters 1-2.

141. [McAllister, et al. 1987].
     McAllister, A., et al., "Constraints for Automatically Generated Requirements Specification Environments," Hawaii International Conference on System Sciences, Los Alamitos, California: IEEE Computer Society Press, 1987.

142. [McCabe, et al. 1985].
     McCabe, T., et al., "Structured Real-Time Analysis and Design," International Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1985.

143. [McCall and Mistrik 2005].
     McCall, R., and I. Mistrik, "Capture of Software Requirements and rationale through Collaborative Software Development," in Requirements Engineering for Sociotechnical Systems, J. Maté, and A. Silva, eds., Hershey, Pennsylvania: Information Science Publishing, 2005, pp. 303-317.

144. [McChesney, et al. 1990].
     McChesney, I., et al., "Case Tool Support for Requirements Capture and Analysis," Microprocessing and Microprogramming, 1990.

145. [McCluskey, et al. 1995].
     McCluskey, T., et al., "A Requirements Capture Method and its Use in an Air Traffic Control Application," Software Practice and Experience, 25, 1 (January 1995), pp. 47-71.
     
146. [McCluskey and West 1998].
     McCluskey, T., and M. West, "Towards the Automated Debugging and Maintenance of Logic-Based Requirements Models," (see abstract) 13^th IEEE International Conference on Automated Software Engineering, Los Alamitos, California: IEEE Computer Society, 1998, pp. 105-114.
     
147. [McCluskey and West 2001].
     McCluskey, T., and M. West, "The Automated Refinement of a Requirements Domain Theory," (see abstract) Automated Software Engineering, 8, 2 (April 2001), pp. 195-218 (The Netherlands).
     
148. [McCoy 2001].
     McCoy, J., "NASA Software Tools for High-Quality Requirements Engineering," 26^th Annual NASA Goddard Software Engineering Workshop, Los Alamitos, California: IEEE Computer Society Press, 2001, p. 69.
149. [McCoy 2002].
     McCoy, J., "NASA software tools for high-quality requirements engineering," NASA Goddard Software Engineering Workshop, Los Alamitos, California: IEEE Computer Society Press, 2002.
150. [McDermid 1989].
     McDermid, J., "Requirements analysis: problems and the STARTS approach," Requirements Capture and Specification for Critical Systems, London: IEE, 1989, pp. 4/1-4/4.
151. [McDermid 1994].
     McDermid, J., "Requirements Analysis: Orthodoxy, Fundamentalism, and Heresy," in Requirements Engineering Social and Technical Issues, M. Jirotka, and J. Goguen, eds., London: Academic Press, 1994.
152. [McFadyen 1980].
     McFadyen, W., "SPEC-the functional requirements phase," GTE Automatic Electric World-Wide Communications Journal, 18,  2 (March 1980), pp. 61-68.
     
153. [McFarlane and Reilly 1995].
     McFarlane, I., and I. Reilly, "Requirements Traceability in an Integrated Development Environment," (see abstract) Second International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1995.
     
154. [McGovern 2002].
     McGovern, F., "Managing Software Projects with Business-Based Requirements," (see abstract) IT Professional, 4, 5 (September-October 2002), pp. 18-23.
155. [McGowan, et al. 1985].
     McGowan, C., et al., "The Metafor Approach to Executable Specifications," Third International Workshop on Software Specification and Design, Los Alamitos, California: IEEE Computer Society Press, 1985, pp. 163-169. 
     
156. [McGowan 1994].
     McGowan, C., "Requirements Engineering: A Different Analogy," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 147.
157. [McGrath 2006].
     McGrath, O., "Balancing act: community and local requirements in an open source development process," 34th Annual ACM SIGUCCS Conference on User services, New York: ACM Press, 2006. 
     
158. [McGraw and Harbison 1997].
     McGraw, K., and K. Harbison, User-Centered Requirements: The Scenario-Based Engineering Process, Mahway, New Jersey: Lawrence Erlbaum Associates, 1997.
     
159. [McGregor 1998].
     McGregor, J., "Testing Models: the Requirements Model," Journal of Object-Oriented Programming, 11, 3 (June 1998), p. 20ff.
160. [McIntyre and Higgins 1988].
     McIntyre, S., and L. Higgins, "Object-oriented Systems Analysis and Design: Methodology and Application," Journal of Management Information Systems, 5, 1 (Summer 1988), pp. 25-35.
161. [McKay 1998].
     McKay, B., "Requirements Management Best Practices within the Medical Device Industry," Eighth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1998.
162. [McKay, et al. 2001].
     McKay, A., et al., "Requirements Management: A Representation Scheme for Product Specifications," Computer Aided Design, 33 (2001), pp. 511ff.
     
163. [McKeen, et al. 1994].
     McKeen, J., et al., "The Relationship Between User Participation and User Satisfaction," MIS Quarterly (December 1994), pp. 427-451.
164. [McLeod 1996].
     McLeod, R., "Comparing Undergraduate Courses in Systems Analysis and Design," Communications of the ACM, 39, 5 (May 1996), pp. 113-121.
165. [McMenamin and Palmer 1984].
     McMenamin, S., and J. Palmer, Essential Systems Analysis, Upper Saddle River, New Jersey: Prentice Hall, 1984.
     
166. [McPhee and Eberlein 2000].
     McPhee, C., and A. Eberlein, "An Approach to Evaluating Requirements Engineering Methods for Applicability to Time-to-Market Projects," 13th International Conference on Software & Systems Engineering and their Applications (ICCSEA2000), Paris, France, 2000.
     
167. [McPhee and Eberlein 2002].
     McPhee, C., and A. Eberlein, "Requirements Engineering for Time-to-Market Projects," 9th Annual IEEE International Conference on the Engineering of Computer Based Systems, Los Alamitos, California: IEEE Computer Society Press, 2002, pp. 17-24.
168. [McSherry 2002].
     McSherry, D., "A Generalised Approach to Similarity-Based Retrieval in Recommender Systems," Artificial Intelligence Review, 18, 3 (December 2002), pp. 309-341.
     
169. [Mead 1993].
     Mead, N., "Mostly Theory at First Requirements Symposium," IEEE Software, 10, 2 (March 1993), p. 107.
     
170. [Mead 1994].
     Mead, N., "The Role of Software Architecture in Requirements Engineering," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 242.
171. [Mead 1997].
     Mead, N., "Preface to Special Issue," Annals of Software Engineering, (1997).
     
172. [Mead 2000].
     Mead, N., "What Do You Mean I'm Practicing Without a License? Certification and Licensing of Requirements Engineering Professionals," (see abstract) Fourth International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2000, p. 152.
173. [Mead 2000a].
     Mead, N., "Why Is It So Difficult to Introduce Requirements Engineering Research Results into Mainstream Practice," 4th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 75-76. 
174. [Mead 2000b]
     Mead, N., "Requirements Management and Requirements Engineering: You Can't Have One Without the Other," Cutter IT Journal, 13, 5 (May 2000).
175. [Mead and Kameli 2003].
     Mead, N., and N. Kameli, "Requirements Engineering in Practice: Making the Business Case for Requirements Engineering," (see abstract) 11th IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003, p. 342.
176. [Mead and Stehney 2005].
     Mead, N., and T. Stehney, "Security quality requirements engineering (SQUARE) methodology," ACM Software Engineering Notes, 30, 4 (May 2005).
177. [Mead 2006].
     Mead, N., "Experiences in eliciting security requirements," Crosstalk, (2006).
178. [Meadows 2004].
     Meadows, C., "Ordering from Satan's Menu: A Survey of Requirements Specification for Formal Analysis of Cryptographic Protocols," Science of Computer Programming, 50, 1-3 (March 2004), pp. 3-22.
179. [Meadows and Syverson 1998].
     Meadows, C., and P. Syverson, "A formal specification of requirements for payment transactions in the SET protocol," Financial Cryptography, Lecture Notes in Computer Science 1465, Berlin: Springer, 1998, pp. 122-140. 

180. [Medina 1981].
     Medina, B., Structured System Analysis: A New Technique, 1981.

181. [Medvidovic, et al. 2003].
     Medvidovic, N., et al., "Bridging Models Across the Software Lifecycle," Journal of Systems and Software, 68, 3 (December 2003), pp. 199-215.
182. [Mehandjiev and Gaskell 2000].
     Mehandjiev, N., and C. Gaskell, "Requirements Engineering and Strategic Decision Exploration: An Area for Interdisciplinary Research," (see abstract) Seventh Asia-Pacific Software Engineering Conference (APSEC), Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 127-131.
183. [Mehner, et al. 2006].
     Mehner, K., et al., "Interaction Analysis in Aspect-Oriented Models," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
184. [Mei, et al. 2003].
     Mei, H., et al., "A Feature Oriented Approach to Modeling and Reusing Requirements of Software Product Lines," Twenty-seventh International IEEE Conference on Computer Software and Applications, Los Alamitos, California: IEEE Computer Society Press, 2003, pp. 250-255.
     
185. [Meilich 1997].
     Meilich., A., "Lessons Learned from Use of a Computer-based Requirements Management Tool in the Project Configuration Control Board Environment," Seventh Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1997.
186. [Mejri, et al. 2003].
     Mejri, M., et al., "Static Analysis of Lyee Requirements," Knowledge Based Systems, 16, 7-8 (November 2003), pp. 361-382.

187. [Melhart, et al. 1989].
     Melhart, B., et al., "Analysis Capabilities for Requirements Specified in Statecharts," International Workshop on Software Specification & Design, Los Alamitos, California: IEEE Computer Society Press, 1989.

188. [Melhart, et al. 1989a].
     Melhart, B., et al., "Analysis Capabilities for Requirements Specified in Statecharts," ACM Software Engineering Notes, 1989.
189. [Mellado, et al. 2006].
     Mellado, D., et al., "Applying a Security Requirements Engineering Process," Computer Security – ESORICS 2006, Lecture Notes in Computer Science Volume 4189, Berlin, Germany: Springer, 2006, pp. 192-206.
190. [Mellado, et al. 2007].
     Mellado, D., et al., "A common criteria based security requirements engineering process for the development of secure information systems," Computer Standards & Interfaces, 29, 2 (February 2007), pp. 244-253.
191. [Mellado, et al. 2007].
     Mallado, D., et al., "A security requirements engineering process," IEEE Transactions on Latin America (2007).
     
192. [Mellor 1989].
     Mellor, S.,"An Object-Oriented Approach to Domain Analysis," ACM Software Engineering Notes, 14, 5 (July 1989), pp. 66-77.
     
193. [Mellor 2001].
     Mellor, S., "Managing Changing Requirements," Embedded System Programming, 15, 8 (August 2001), pp. 14-19.
     
194. [Melnik, et al. 2004].
     Melnik, G., et al., "Suitability of FIT User Acceptance Tests for Specifying Functional Requirements: Developer Perspective," Lecture Notes in Computer Science, Volume 3134, Berlin: Springer, 2004, pp. 60-72. 
195. [Melnik and Maurer 2005].
     Melnik, G., and F. Maurer, "The practice of specifying requirements using executable acceptance tests in computer science courses," OOPSLA Conference, New York: ACM Press, 2005, pp. 365-370.
196. [Mendes 1980].
     Mendes, K., "Structured Systems Analysis: A Technique to Define Business Requirements," Sloan Management Review, 21, 4 (Summer 1980), pp. 51-63.
197. [Menzies and Waugh 1998].
     Menzies, T., and S. Waugh, "On the practicality of viewpoint-based requirements engineering," PRICAI’98: Topics in Artificial Intelligence, Lecture Notes in Computer Science, Volume 1531, Berlin: Springer, 1998, pp. 110-121. 
198. [Menzies, et al. 1999].
     Menzies, T., et al., "An Empirical Investigation of Multiple Viewpoint Reasoning in Requirements Engineering," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1999, pp. 100-109.
     
199. [Menzies, et al. 2001].
     Menzies, T., et al., "Fast Formal Analysis of Requirements Via 'Topoi Diagrams'," Twenty-third International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 391-400.
200. [Menzies 2003].
     Menzies, T., "Editorial: Model-Based Requirements Engineering," Requirements Engineering, 8, 4 (December 2003), pp. 193-194.
201. [Menzies and Richardson 2006].
     Menzies, T., and J. Richardson, "Making Sense of Requirements, Sooner," Computer, 39, 10 (October 2006), pp. 112-114.
202. [Merill and Feldman 2004].
     Merill, C., and D. Feldman, "Rethinking the Path to Usability: How to Design What Users Really Want," IT Professional 6, 3 (May/June 2004), pp. 51-57.
203. [Merrick and Barrow 2004].
     Merrick, P., and P. Barrow, "Testing a Requirements Pattern Language Through Reverse Engineering," (see abstract) Fourteenth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 2004.
204. [Merrick and Barrow 2005].
     Merrick, P., and P. Barrow, "Testing the Predictive Ability of a Requirements Pattern Language," Requirements Engineering, 10, 2 (May 2005), pp. 85-94.
205. [Merunka 2003].
     Merunka, V., "BORM -- Overview of the Methodology and Case Study of the Agrarian Information System," Agricultural Economics, 49, 9 (September 2003), pp. 397-406.
206. [Merunka 2005].
     Merunka, V., "Object-Oriented Approach in Requirements Engineering for the Analysis of Information Systems," Journal of Forest Science, 51 (2005), pp. 13-18.
207. [Methlie 1980].
     Methlie, L., "Systems Requirements Analysis -- Methods and Models," in The Information Systems Environment, H. Lucas, et al., eds., Amsterdam, The Netherlands: North-Holland, 1981.
     
208. [Metzger, et al. 2007].
     Metzger, A., et al., "Disambiguating the Documentation of Variability in Software Product Lines: A Separation of Concerns, Formalization and Automated Analysis," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
209. [Meyer 1985].
     Meyer, B., "On Formalism in Specification," IEEE Software, 2, 1 (January 1985), pp. 6-26.

210. [Meyer 1995].
     Meyer, A., "Specification Development within the IPT: A Case Study of the F-22," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1995.

211. [Meyer 1999].
     Meyer, A., "Metrics and Processes for F-22 Requirements Management," Ninth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1999.
212. [Meyer, et al. 2005a].
     Meyer, N., et al., "Towards a Risk-Based Security Requirements Engineering Framework," 11th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 05), Porto, Portugal, 2005.
213. [Meyers and White 1983].
     Meyers, S., and S. White, Software Requirements Methodology and Tool Study: A-6E Technology Transfer, Grumman Aerospace Corporation Technical Report, prepared for Naval Weapons Center, Bethpage, New York, July 1983.
     
214. [Meziane and Vadera 1997].
     Meziane, F., and S. Vadera, "Tools for Producing Formal Specifications: A View of Current Architectures and Future Directions," Annals of Software Engineering, 3, N. Mead, ed., 1997.
215. [Miedema, et al. 2007].
     Miedema, J., et al., "Synergy of Technical Specifications, Functional Specifications and Scenarios in Requirements Specifications," International Conference on Future of Product Development, Berlin: Springer, 2007.
216. [Might 1993].
     Might, R., "Requirements Analysis: Going From User Needs to Specific Performance Parameters," Third Annual National Council on Systems Engineering International Symposium, Sunnyvale, California: NCOSE, 1993.
217. [Mihail 1999].
     Mihail, M., "Set Cover with Requirements and Costs Evolving Over Time," in Randomization, Approximation, and Combinatorial Approximation: Algorithms and Techniques, Lecture Notes in Computer Science 1671, Berlin: Springer, 1999, pp. 63-72.
218. [Mikulovic and Heiss 2006].
     Mikulovic, V., and M. Heiss, "How do I know what I have to do?": the role of the inquiry culture in requirements communication for distributed software development projects," International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 921-925. 
219. [Mili 1982].
     Mili, A., "System Requirements Specification: A Simplified Approach," International Symposium on Current Issues of Requirements Environments, 1982.
220. [Millard, et al. 1998].
     Millard, N., et al., "Child's Play: Using Techniques Developed to Elicit Requirements from Children with Adults," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 66-73.
221. [Miller and Taylor 1982].
     Miller, T., and B. Taylor, "A Requirements Methodology for Complex Real-Time Systems," International Symposium on Current Issues of Requirements Environments, Amsterdam: North Holland Publ., 1982, pp. 133-141.
222. [Miller and Sabor 1994].
     Miller, L., and B. Sabor, "IEEE Draft Standard P1233: Guide for Developing System Requirements Specification," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, p. 61.
223. [Miller 1996].
     Miller, W., "DOORS (tm) to Automated Metrics," Sixth Annual International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1996.
224. [Miller 2002].
     Miller, R., Learning and Using Requirements Representation Notations by Information Technology Professionals, PhD Dissertation, Department of Information Technology, Philadelphia, Pennsylvania: Drexel University, December 2002.
225. [Miller and Overmyer 2004].
     Miller, R., and S. Overmyer, "Connecting the User View with the System View of Requirements," Lecture Notes in Computer Science, Volume 3101, Berlin: Springer, 2004, pp. 610-614. 
226. [Miller 2006].
     Miller, S., "Proving the Shalls: Requirements, Proofs, and Model-Based Development," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
227. [Miller, et al. 2006].
     Miller, S., et al., "Proving the Shalls," International Journal on Software Tools for Technology Transfer, 8, 4/5 (August 2006), pp. 303-319.
228. [Miller, et al. 2006a].
     Miller, S., et al., "From requirements development to verification ~ designing reliability into a large scale chemical manufacturing system," Annual IEEE Reliability and Maintainability Symposium (RAMS), Los Alamitos, California: IEEE Computer Society Press, 2006, pp. 641-648.
229. [Miller and Madhavji 2007].
     Miller, J., and N. Madhavji, "The architecture-requirements interaction," IEEE/IFIP Conference on Software Architecture, Los Alamitos, California: IEEE Computer Society Press, 2007. 
230. [Millet 2000].
     Millet, I., "Improving the Quality of the Analysis Phase," Journal of Systems and Software, 50 (2000).
231. [Millington 1981].
     Millington, D., Systems Analysis and Design for Computer Applications, Chichester, UK: Ellis Horwood Limited, 1981.
232. [Mills, et al. 1986].
     Mills, H., et al., Information Systems Analysis and Design, Orlando, Florida: Academic Press, 1986.
     
233. [Milovanovic, et al. 1995].
     Milovanovic, R., et al., "Organic Growth via Development: The Early Life Cycle," in Automated Systems Based on Human Skill, D. Brandt and T. Martin, eds., Berlin, Germany: Pergamon Press, 1995.

234. [Milsom 1989].
     Milsom, F., "Using CORE with SDL to Specify Requirements," International Conference on Software Engineering for Telecommunication Switching Systems, London: IEE, 1989, pp. 137-141.

235. [Minkkinen and Eerola 2007].
     Minkkinen, I., and A. Eerola, "Improving requirements engineering from the client's perspective in the health care domain," IASTED International Conference on Software Engineering, 2007, pp. 93-98.
236. [Minor and Armarego 2004].
     Minor, O., and J. Armarego, "Requirements Engineering: A Close Look at Industry Needs and Model Curricula," Australian Workshop on Requirements Engineering (AWRE '04).
237. [Miranskyya, et al. 2005].
     Miranskyya, A., et al., "Modelling Assumptions and Requirements in the Context of Project Risk," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 471-472.
238. [Miranskyya, et al. 2007].
     Miranskyya, A., et al., "Requirements Escalation," Workshop on Measuring Requirements for Project and Product Success (MeReP), 2007.
239. [Mirbel and Ralyte 2006].
     Mirbel, I., and J. Ralyte, "Situational method engineering: combining assembly-based and roadmap-driven approaches," Requirements Engineering, 11, 1 (March 2006), pp. 58-78.
240. [Mishkat, et al. 2004].
     Mishkat, L., et al., "Requirements-Based System Level Risk Modeling," Annual Symposium on Reliability and Maintainability, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 500-506.
241. [Mishra 2004].
     Mishra, A., Graf, "UML Xtra-light: How to Specify Your Software Requirements," Computer Journal, 47, 4 (July 2004), p. 507.
242. [Misic and Graf 1993].
     Misic, M., and D. Graf, "The Interpersonal Environments of the Systems Analyst," Journal of Systems Management, 44 (1993), pp. 12-16.
243. [Misic 1996].
     Misic, M., "The Skills Needed by Today's Systems Analysts," Journal of Systems Management, 47, (1996), pp. 34-40.
244. [Misic and Russo 1996].
     Misic, M., and N. Russo, "Educating Systems Analysts: A Comparison of Educators' and Practitioners' Opinions Concerning the Relative Importance of Systems Analyst Tasks and Skills," Journal of Computer Information Systems, 4  (1996), pp. 86-91.
245. [Misic and Russo 2000].
     Misic, M., and N. Russo, "Reading Between the Lines: An Examination of Systems Analysis and Design Texts," Journal of Systems and Software, 50 (2000), pp. 65-73.
246. [Misic and Graf 2004].
     Misic, M., and D. Graf, "Systems Analyst Activities and Skills in the New Millennium," Journal of Systems and Software, 71, 1-2 (April 2004), pp. 31-36.
247. [Misra, et al. 2005].
     Misra, S., et al., "Goal-oriented or scenario-based requirements engineering technique - what should a practitioner select?," Canadian Conference on Electrical and Computer Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 2288-2292.  
248. [Mitani, et al. 2007].
     Mitani, Y., et al., "Proposal of a Complete Life Cycle In-Process Measurement Model Based on Evaluation of an In-Process Measurement Experiment Using a Standardized Requirement Definition Process," IEEE International Symposium on Empirical Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007, pp. 11-20.
249. [Mitchell, et al. 2005].
     Mitchell, B., et al., "Scenario-Synthesis from Imprecise Requirements," International Workshop on Systems Analysis and Modeling, Lecture Notes in Computer Science 3319, Berlin: Springer, 2005, pp. 122-137.
250. [Mitra 1987].
     Mitra, S., "Techniques and tools for requirements specification," Conference on Software Tools, Pinner, UK: Online Publications, 1987, pp. 75-805.
251. [Mitri and Cole 2006].
     Mitri, M., and C. Cole, "A Systems Analysis Role Play Case: We Sell Stuff, Inc.," Journal of Information Systems Education (2006). 
252. [Mittermeir 1979].
     Mittermeir, R., "Enhanced SADT for Requirements Analysis," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1979, pp. 300-305.
253. [Mittermeir, et al. 1982].
     Mittermeir, R., et al., "Alternatives to Overcome the Communications Problem of Formal Requirements Analysis," International Symposium on Current Issues of Requirements Environments, Amsterdam: North Holland Publ., 1982, pp. 163-169.
254. [Miura, et al. 1995].
     Miura, N., et al., "Building the Structure of Specification Documents from Utterances of Requirements Elicitation Meetings," (see abstract) Asia-Pacific Software Engineering Conference, Los Alamitos, California: IEEE Computer Society, 1995, pp. 64-73.
255. [Mixon 1992].
     Mixon, H., "Using RDD to Support the Systems Engineering Process," International Symposium on Systems Engineering, Seattle, Washington: International Council on Systems Engineering, 1992.
256. [Miyamoto 1981].
     Miyamoto, I., "On The Way to a Practical Requirements Analysis and Definition Methodology," Hawaii International Conference on Systems Sciences, IEEE Computer Society Press, 1981, pp. 140-152.
     
257. [Miyamoto and Yeh 1981].
     Miyamoto, I., and R. Yeh, "Software Requirements Analysis and Definition Methodology for Business Data Processing," AFIPS National Computer Conference, Arlington, VA: AFIPS, 1981, pp. 271-281.
258. [Mock 2004].
     Mock, M., "Expressing Real-Time Requirements on Object Interactions," Seventh IEEE Symposium on Object-Oriented Distributed Real-Time Computing, Los Alamitos, California: IEEE Computer Society Press, 2004, pp. 201-208.
259. [Modell 1988].
     Modell, M., A Professional's Guide to Systems Analysis, New York: McGraw Hill, 1988.
     
260. [Modell 1996].
     Modell, M., A Professional's Guide to Systems Analysis, 2nd Edition, New York: McGraw Hill, 1996.
     
261. [Modugno, et al. 1997].
     Modugno, F., et al., "Integrating Safety Analysis of Requirements Specification," IEEE International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, January 1997, pp. 148-159; also appears in Requirements Engineering Journal, 2, 1 (1997), pp. 65-78.
     
262. [Moffet, et al. 1996].
     Moffet, J., et al., "A Model for Causal Logic for Requirements Engineering," Requirements Engineering Journal, 1, 1 (1996), pp. 27-46.
263. [Mogyorodi 2003].
     Mogyorodi, G., "What Is Requirements-Based Testing?," Crosstalk, (March 2003).
     
264. [Mohamed, et al. 2008].
     Mohamed, A., et al., "MiHOS: an approach to support handling the mismatches between system requirements and COTS products," Requirements Engineering Journal, (2008).
265. [Mok 1984].
     Mok, A., "Decomposition of Real-Time System Requirements into Process Models," Real-Time Systems Symposium, Los Alamitos, California: IEEE Computer Society Press, 1984, pp. 125-134.
     
266. [Molin and Pettersson 2005].
     Molin, L., and J. Pettersson, "How Should Interactive Media Be Discussed For Successful Requirements Engineering?," Perspectives on Multimedia: Communication, Media and Information, 2005..
267. [Molderez and Ponsard 2005].
     Molderez, J., and C. Ponsard, "Deriving Acceptance Tests from Goal Requirements," International Conference on Multi-Paradigm Programming in Mozart/OZ, Lecture Notes in Computer Science 3389, Berlin: Springer, 2005, pp. 78-88.

268. [Mondragon and Gates 2004].
     Mondragon, O., and A. Gates, "Supporting Elicitation and Specification of Software Properties through Patterns and Composite Propositions," International Journal of Software Engineering and Knowledge Engineering, 2004.

269. [Montero, et al. 2007].
     Montero, S., et al., "From requirements to implementations: a model-driven approach for web development," European Journal of Information Systems (2007). 
270. [Moody, et al. 1998].
     Moody, J., et al., "A Theoretically Grounded Approach to Assist Memory Recall During Information Requirements Determination," Journal of Management Information Systems, 15, 1 (January 1998), pp. 79-98.
271. [Moody 2005].
     Moody, D., "Theoretical and practical issues in evaluating the quality of conceptual models: current state and future directions," Data and Knowledge Engineering, 55, 3 (December 2005), pp. 243-276.
     
272. [Moody 2006].
     Moody, D., "Dealing with 'Map-Shock': A Systematic Approach for Managing Complexity in Requirements Analysis," 12th International Workshop on Requirements Engineering Foundations for Software Quality (REFSQ' 06), Luxembourg, 2006.
273. [Moon and Yeom 2004].
     Mon, M., and K. Yeom, "An Approach to Develop Requirement as a Core Asset in Product Lines," Lecture Notes in Computer Science, Volume 3107, Berlin: Springer, 2004, pp. 23-34. 
274. [Moon, et al. 2005].
     Moon, M., et al., "An approach to developing domain requirements as a core asset based on commonality and variability analysis in a product line," IEEE Transactions on Software Engineering, 31, 7 (July 2005), pp. 551-569.
275. [Moore 1990].
     Moore, A., "The Specifications and Verified Decomposition of System Requirements Using CSP," IEEE Transactions on Software Engineering, 16, 9 (September 1990).
276. [Moore and Shipman 2000].
     Moore, J., and F. Shipman, "A Comparison of Questionnaire-Based and GUI-Based Requirements Gathering," Fifteenth International Conference on Automated Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 35-43.
     
277. [Moore and Shipman 2001].
     Moore, J., and F. Shipman, "Requirements Elicitation Using Visual and Textual Information," Fifth International Symposium on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2001, pp. 308-309.
278. [Moore 2003].
     Moore, M., "Communicating Requirements Using End-User GUI Constructions with Augmentation," Eighteenth International Conference on Automated Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 2003.

279. [Moores and Champion 1994].
     Moores, T., and R. Champion, "Software quality through the traceability of requirements specifications," International Conference on Software Testing, Reliability and Quality Assurance, 1994.

280. [Moreira and Clark 1994].
     Moriera, A., and R. Clark, "Rigorous Object-Oriented Analysis," International Symposium on Object-Oriented Methodologies and Systems, Berlin: Springer, 1994.
281. [Moreira, et al. 2002].
     Moriera, A., et al., "Crosscutting Quality Attributes for Requirements Engineering," International Conference on Software Engineering and Knowledge Engineering, New York: ACM Press, 2002, pp. 167-174.
282. [Moreira, et al. 2003].
     Moreira, A., et al., "Evolving Requirements Through Coordination Contracts," Fifteenth Conference on Advanced Information System Engineering (CAiSE), 2003, Lecture Notes in Computer Science, 2681, Springer Verlag, pp. 633-646.
     
283. [Moreira, et al. 2005].
     Moreira, A., et al., "Multi-Dimensional Separation of Concerns in Requirements Engineering," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2005, pp. 285-296.
     
284. [Moreira, et al. 2005a].
     Moreira, A., et al., "A Concern-Oriented Requirements Engineering Model," in Conference on Automated Information Software Engineering (CAISE), Lecture Notes in Computer Science 3520, Berlin: Springer, 2005, pp. 293-308.
285. [Moreno 1997].
     Moreno, A., "Object-Oriented Analysis From Textual Specifications," (see abstract) International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, June 1997, pp. 48-55.
286. [Moreno 1998].
     Moreno, A., "A Formal Approach for Generating Object-Oriented Specifications from Natural Language," Journal of Systems and Software, (December 1998).
287. [Moreno 1999].
     Moreno, A., "Results of the Application of a Linguistic Approach to Object-Oriented Analysis," (see abstract) Journal of Software Engineering and Knowledge Engineering, 8, 4 (1999), pp. 449-459.
288. [Moreno and Silva 2001].
     Moreno, A., and A. Silva, "A Method for Detection, Classification, and Resolution of Discrepancies in Viewpoint-Based Requirements Engineering," International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, 2001.
289. [Moret 1982].
     Moret, B., "Decision Trees and Diagrams," ACM Computing Surveys, 14, 1 (December 1982), pp. 593-623.
290. [Morgan 2002].
     Morgan, T., Business Rules and Information Systems: Aligning IT with Business Goals, Reading, Massachusetts: Addison-Wesley, 2002.
     
291. [Morgan and Schahczenski 1994].
     Morgan, N., and C. Schahczenski, "Transitioning to Rigorous Software Specification," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, April 1994, pp. 110-117.
292. [Mori and Katsumoto 2005].
     Mori, T., and M. Katsumoto, "A Quality Decision Method for Multi-Object Content based on User Requirements," IEEE International Conference on Distributed Frameworks for Multimedia Applications, Los Alamitos, California: IEEE Computer Society Press, February 2005, pp. 231-238.
     
293. [Morik 1999].
     Morik, K., "Tailoring Representations to Different Requirements," International Conference on Algorithmic Learning Theory, Lecture Notes in Computer Science 1720, Berlin: Springer, 1999, pp. 1ff.
294. [Morris, et al. 1994].
     Morris, P., et al., "Requirements and Traceability," (see abstract) International Workshop on Requirements Engineering: Foundations of Software Quality, June 1994.
295. [Morris, et al. 1998].
     Morris, P., et al., "Requirements Engineering and Industrial Uptake," 3rd IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 1998, pp. 130-137. 
296. [Morrison 1988].
     Morrison, W., "Communicating with Users During Systems Development," Information and Software Technology, 30, 5 (June 1988), pp. 295-298.
297. [Morton and Freburger 1980].
     Morton, R., and K. Freburger, "Toward Methodology for Function Specification," IEEE Computer Software and Applications Conference (COMPSAC), Los Alamitos, California: IEEE Computer Society Press, 1980, pp. 201-206.
298. [Mostert and von Solms 1995].
     Mostert, D., and S. von Solms, "A Technique to Include Computer Security, Safety, and Resilience Requirements as Part of the Requirements Specification," Journal of Systems and Software, 31, 1 (October 1995), pp. 45-53.
299. [Moths, et al. 1999].
     Moths, M., et al., "An Examination of Procedural and Object-oriented Systems Analysis Methods: Does Prior Experience Help or Hinder Performance," Decision Sciences, 30, 1 (Winter 1999), pp. 107-136.
300. [Motschnig-Pitrik, et al. 1997].
     Motschnig-Pitrik, RH., et al., "View-Directed Requirements Engineering: A Framework and Metamodel," International Conference on Software Engineering and Knowledge Engineering, Skokie, Illinois: Knowledge Systems Institute, June 1997, pp. 366-373.
301. [Mousavi, et al. 2007].
     Mousavi, A., et al., "An Approach for Generating State Machine Designs from Scenarios," IASTED International Conference on Software Engineering and Applications (SEA), 2007.
302. [Moynihan 2000].
     Moynihan, T., "Coping with Requirements Uncertainty: The Theories-of-Action of Experienced IS/Software Project Managers," Journal of Systems and Software, 53, 2 (August 2000), pp. 99-109.
     
303. [Moynihan 2000a].
     Moynihan, T., "Requirements Uncertainty: Should it Be a Latent, Aggregate or Profile Construct?," 2000 Australian Software Engineering Conference, Los Alamitos, California: IEEE Computer Society Press, 2000, pp. 181-188.
304. [Mrenak 1990].
     Mrenak, G., "Evolving Concepts, or Why Users Often Don't Recognize the Software They Asked For," Seventh Washington Ada Symposium on Ada, New York: ACM Press, 1990.
305. [Mu, et al. 2005].
     Mu, K., et al., "Measuring Inconsistency in Requirements Specifications," European Conference on Symbolic and Quantitative Approaches to Reasoning with Uncertainty, Lecture Notes in Computer Science 3571, Berlin: Springer, 2005, pp. 440-451.
306. [Mu, et al. 2005a].
     Mu, K., et al., "Inconsistency-Based Strategy for Clarifying Vague Software Requirements," Australian Joint Conference on Artificial Intelligence, Lecture Notes in Computer Science 3809, Berlin: Springer, 2005, pp. 39-48.
307. [Mu and Jin 2007].
     Mu, K., and Z. Jin, "Identifying Acceptable Common Proposals for Handling Inconsistent Software Requirements," International Conference on Formal Techniques for Networked and Distributed Systems (FORTE), Berlin: Springer, 2007.
308. [Mu, et al., 2007].
     Mu, K., et al., "Handling non-canonical software requirements based on annotated predicate calculus," Knowledge and Information Systems, 11, 1 (January 2007), pp. 85-104.
     
309. [Mu, et al., 2007a].
     Mu, K., et al., "A Merging-Based Approach to Handling Inconsistency in Locally Prioritized Software Requirements," International Conference on Knowledge Science, Engineering and Management (KSEM), Berlin: Springer, 2007.
     
310. [Mueller, et al. 2007].
     Mueller, D., et al., "Intelligent Assistance for a Task-oriented Requirements Management," Innovations and Advanced Techniques in Computer and Information Sciences and Engineering, Berlin: Springer, 2007, pp. 151-156.
311. [Mueller-Glaser, et al. 1992].
     Mueller-Glaser, K., et al., "Towards a requirements definition, specification and system design environment," European Design Automation Conference, Los Alamitos, California: IEEE Computer Society Press, 1992, pp. 238-243.
     
312. [Mueller-Glaser, et al. 2004].
     Mueller-Glaser, K., et al., "Multiparadigm Modeling in Embedded System Design," IEEE Transactions on Control Systems Technology, 12, 2 (March 2004), pp. 279-292.
     
313. [Muery, et al. 2006].
     Muery, K., et al., "Automated derivation of complex system constraints from user requirements," 2nd IEEE International Conference on Space Mission Challenges for Information Technology, Los Alamitos, California: IEEE Computer Society Press, 2006.
     
314. [Mulet and Vidal 2006].
     Mulet, E., and R. Vidal, "Functional requirements for computer-based design support systems, derived from experimental studies," Knowledge Based Systems, 19, 1 (March 1996), pp. 32-42.
315. [Mullery 1979].
     Mullery, G., "CORE -- A Method for Controlled Requirements Expression'," Fourth International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1979, pp. 126-135.
316. [Mullery 1996].
     Mullery, G., "The Perfect Requirements Myth," Requirements Engineering Journal, 1, 2 (1996), pp. 132-134.

317. [Mullery 1996a].
     Mullery, G., "Tool support for multiple viewpoints," Symposium on the Foundations of Software Engineering, 1996.

318. [Mumford 1985].
     Mumford, E., "Defining System Requirements to Meet Business Needs: A Case Study Example," Computer Journal, 28, 2 (1985), pp. 97-104.
319. [Mumford 1995].
     Mumford, E., Effective Systems Design And Requirements Analysis, London: Palgrave Macmillian, 1995.
     
320. [Muniraj and Jagannatha 2007].
     Muniraj, G., and V. Jagannatha, "Requirements Engineering using Prototyping Projects in Healthcare Diagnostic Software Applications," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2007.
321. [Muñoz, et al. 2006].
     Muñoz, J., et al., "Requirements Engineering for Pervasive Systems. A Transformational Approach
      (poster session)," IEEE International Conference on Requirements Engineering, Los Alamitos, California: IEEE Computer Society Press, 2006.
322. [Muntz and Lichota 1991].
     Muntz, A., and R. Lichota, "A Requirements Specification Method for Real Time Systems," 1991 IEEE Real Time Systems Symposium, Los Alamitos, California: IEEE Computer Society Press, 1991, pp. 264-273.
323. [Murai, et al. 1982].
     Murai, J., et al., "Requirements Specification Description System in Japanese Language JISDOS," Sixth International Conference on Software Engineering, Los Alamitos, California: IEEE Computer Society Press, 1982, pp. 127-136.
324. [Murai, et al. 1982a].
     Murai, J., et al., "A Software Development Tool Under Japanese Environments," International Symposium on Current Issues of Requirements Environments, Amsterdam: North Holland Publ., 1982.
325. [Murray 1987].
     Murray, J., "Requirements statement," System Development, 7, 7 (July 1987), pp. 1-3.
326. [Murray, et al. 2002].
     Murray, L., "Requirements Traceability for Embedded Software – An Industry Experience Report," IASTED International Conference on Software Engineering and Applications (SEA), 2002.
327. [Mussbacher, et al. 2006].
     Mussbacher, G., et al., "Visualizing Aspect-Oriented Requirements Scenarios with Use Case Maps," IEEE International Workshop on Requirements Engineering Visualization, Los Alamitos, California: IEEE Computer Society Press, 2006, p. 4.
328. [Mussbacher, et al. 2007].
     Mussbacher, G., et al., "Visualizing Early Aspects with Use Case Maps," Transactions on Aspect-Oriented Software Development, Berlin: Springer, 2007.
329. [Myhill 2003].
     Myhill, C., "Get Your Product Used in Anger!: (before Assuming You Understand its Requirements)," Interactions, 10, 3 (March 2003), pp. 12-17.
330. [Mylopoulos 1981].
     Mylopoulos, J., "A perspective for research on conceptual modelling," ACM SIGPLAN Notices, 16, 1 (January 1981), pp. 167-170.
     
331. [Mylopoulos and Greenspan 1983].
     Mylopoulos, J., and S. Greenspan, "Knowledge Representation Issues for Requirements Specification," IFIP World Computer Conference '83, 1983.
     
332. [Mylopoulos, et al. 1992].
     Mylopoulos, J., et al., "Representing and Using Nonfunctional Requirements: A Process-Oriented Approach," (see abstract) IEEE Transactions on Software Engineering, 18, 6 (June 1992), pp. 483-497.

333. [Mylopoulos 1997].
     Mylopoulos, J., "Foreword to the Special Issue," Requirements Engineering, 1997.

334. [Mylopoulos 1998]
     Mylopoulos, J., "Information Modeling in the Time of the Revolution," Information Systems, 23, 3-4 (June 1998).
     
335. [Mylopoulos, et al. 1999].
     Mylopoulos, J., et al., "From Object-Oriented to Goal-Oriented Requirements Analysis," Communications of the ACM, 42, 1 (January 1999), pp. 31-37.
336. [Mylopoulos and Castro 2000]
     Mylopoulos, J., and J. Castro, "TROPOS: Framework for Requirements-Driven Software Development," in Information Systems Engineering: State of the Art and Research Themes, A. Solvberg, S., et al., eds., Springer Verlag, 2000.
337. [Mylopoulos, et al. 2001].
     Mylopoulos, J., et al., "Exploring Alternatives During Requirements Analysis," (see abstract) IEEE Software, 18, 1 (January/February 2001), pp. 92-96.
338. [Mylopoulos, et al. 2007].
     Mylopoulos, J., et al., "An Ontology for Requirements," Advances in Conceptual Modeling - Theory and Practice, Berlin: Springer, 2007.
     

     N

     A  B  C  D