This alert has been successfully added and will be sent to: You will be notified whenever a record that you have chosen has been cited.
To manage your alert preferences, click on the button below. Manage my Alerts
Avison, D. E., and Fitzgerald, G. Information Systems Development: Methodologies, Techniques and Tools, London: McGraw Hill, 1995.]]
Boehm, B. W. "Software Engineering," IEEE Transactions on Computers (25), 1996, pp. 1226-1241.]]Boehm, B. W. "A Spiral Model of Software Development and Enhancement," IEEE Computer (25), 1988, pp. 61-72.]]
Boehm-Davis, D., and Ross, L. "Program Design Methodologies and the Software Development Process," International Journal of Man-Machine Studies (36), 1992, pp. 1-19.]]
Booch, G. Object-Oriented Design, Menlo Park, CA: Benjamin/Cummings, 1991.]]Booch, G. Object-Oriented Analysis and Design with Applications, Redwood City, CA: Benjamin/Cummings, 1994.]]
Booch, G.; Rumbaugh, J.; and Jacobson, I. The Unified Modeling Language User Guide, Reading, MA: Addison-Wesley, 1999.]]
Chaiyasut, P., and Shanks, G. "Conceptual Data Modeling Process: A Study of Novice and Expert Data Modelers," in Proceedings of First International Conference on Object Role Modeling, Magnetic Island, Australia, 1994.]]
Checkland, P., and Scholes, J. Soft Systems Methodology in Practice, Chichester, England: Wiley, 1990.]]
Coad, P., and Yourdon, E. Object-Oriented Analysis, Englewood Cliffs, NJ: Yourdon Press/Prentice-Hall, 1991.]]
Dawson, L. L., and Swatman, P. A. "The Role of Object-Oriented Modeling Methods in Requirements Engineering," in Methodologies for Developing and Managing Emerging Technology Based Information Systems, A. T. Wood-Harper, N. Jayaratna, and J. R. G. Woods (eds.), London: Springer-Verlag, 1999, pp. 353-368.]]
DeMarco, T. Controlling Software Projects: Management, Measurement and Estimation, New York: Yourdon Press, 1982.]]
Eisenhardt, K. M. "Building Theories from Case Study Research," Academy of Management Review (14), 1989, pp. 532-550.]]
Fitzgerald, B. "The Use of Systems Development Methodologies in Practice: A Field Study," Information Systems Journal (7), 1997, pp. 201-212.]]
Fowler, D. Formal Methods in a Commercial Information Systems Setting: The FOOM Methodology, unpublished Ph.D. Thesis, Centre For Information Systems Research, Swinburne University of Technology, Melbourne, 1996.]]
Fowler, D.; Swatman, P. A.; and Wafula, E. N. "Formal Methods in the IS Domain: Introducing a Notation for Presenting Object-Z Specifications," Object Oriented Systems (2), 1995.]]
Graham, I. Object Oriented Methods, Reading, MA: Addison-Wesley, 1994.]]Graham, I.; Henderson-Sellers, B.; and Younessi, H. The OPEN Process Specification, Reading, MA: Addison-Wesley, 1997.]]
Guindon, R. "Knowledge Exploited by Experts During Software System Design," International Journal of Man-Machine Studies (33), 1990, pp. 279-304.]]
Henderson-Sellers, B. A Book of Object-Oriented Knowledge, Upper Saddle River, NJ: Prentice-Hall, 1997.]]
Henderson-Sellers, B. and Edwards, J. BOOKTWO of Object-Oriented Knowledge: The Working Object, Englewood Cliffs, NJ: Prentice Hall, 1994.]]
Jackson, M. C. "Critical Systems Thinking and Information Systems Development," in Proceedings of Eighth Australasian Conference on Information Systems, University of South Australia, Adelaide, South Australia, 1997, pp. 1-20.]]
Jacobson, I. "The Use-Case Construct in Object-Oriented Software Engineering," in Scenario-Based Design: Envisioning Work and Technology in System Development, J. M. Carroll (ed.), New York: John Wiley and Sons, Inc, 1995, pp. 309-336.]]
Jacobson, I.; Booch, G.; and Rumbaugh, J. The Unified Software Development Process, Reading, MA: Addison Wesley Longman, 1999.]]
Jacobson, I., and Christerson, M. "Modeling with Use Cases: A Growing Consensus on Use Cases," Journal of Object-Oriented Programming (8), 1995, pp. 15-19.]]
Jacobson, I.; Christerson, M.; Jonsson, P.; and Overgaard, G. Object-Oriented Software Engineering: A Use Case Driven Approach, Reading, MA: Addison-Wesley/ACM,1992.]]
Kotonya, G., and Sommerville, I. Requirements Engineering: Processes and Techniques, Chichester, England: John Wiley and Sons, 1998.]]
Lee, Y., and Pennington, N. "The Effects of Paradigm on Cognitive Activities in Design," International Journal of Human-Computer Studies (40), 1994, pp. 577-601.]]
Loucopoulos, P., and Karakostas, V. Systems Requirements Engineering, London: McGraw-Hill, 1995.]] Macaulay, L. Requirements Engineering, London: Springer-Verlag, 1996.]] Meyer, B. Object-Oriented Software Construction, Englewood Cliffs, NJ: Prentice-Hall, 1988.]]Miles, M. B., and Huberman, A. M. Qualitative Data Analysis: A Sourcebook of New Methods, Newbury Park, CA: Sage Publications Inc, 1984.]]
Morris, M.; Speier, C.; and Hoffer, J. "The Impact of Experience on Individual Performance and Workload Differences Using Object-oriented and Process-oriented Systems Analysis Techniques," in Proceedings of Twenty-ninth Hawaii International Conference on System Sciences, Maui, Hawaii, 1996.]]
Neuman, W. L. Social Research Methods: Qualitative and Quantitative Approaches, Boston: Allyn and Bacon, 1994.]]
OASIG. In OR Newsletter (309), 1996, pp. 12-16.]]Pohl, K. "The Three Dimensions of Requirements Engineering," in Proceedings of Fifth International Conference on Advanced Information Systems Engineering (CAiSE'93), Paris, 1993, pp. 275-292.]]
Rumbaugh, J.; Blaha, M.; Premerlani, W.; Eddy, F.; and Lorensen, W. Object-Oriented Modeling and Design, Englewood Cliffs, NJ: Prentice-Hall,1991.]]
Shlaer, S., and Mellor, S. J. Modeling the World in States, Englewood Cliffs, NJ: Yourdon Press,1991.]]
Sutcliffe, A. G., and Maiden, N. A. M. "Analyzing the Novice Analyst: Cognitive Models in Software Engineering," International Journal of Man-Machine Studies (36), 1992, pp. 719-740.]]
Swatman, P. A. "Formal Object-oriented Method: FOOM," in Specification of Behavioral Semantics in Object-Oriented Information Systems, W. Harvey (ed.), Norwell, MA: Kluwer Academic Publishers, 1996.]]
Urquhart, C. "Analysts and Clients in Conversation: Cases in Early Requirements Gathering," in Proceedings of Nineteenth International Conference on Information Systems, R. Hirschheim, M. Newman, and J. I. DeGross (eds.), Helsinki, Finland, 1998, pp. 115-127.]]
Vessey, I., and Conger, S. "Requirements Specification: Learning Object, Process, and Data Methodologies," Communications of the ACM (37), 1994.]]
Vitalari, N. P., and Dickson, G. W. "Problem Solving for Effective Systems Analysis: An Experimental Exploration," Communi-cations of the ACM (26), 1983.]]
Wafula, E. N., and Swatman, P. A. "FOOM: A Diagrammatic Illustration of Object-Z Specifications," Object Oriented Systems (3), 1996, pp. 215-243.]]
Weidenhaupt, K.; Pohl, K.; Jarke, M.; and Haumer, P. "Scenarios in System Development: Current Practice," IEEE Software (15), 1998, pp. 34-45.]]
Wirfs-Brock, R. J.; Wilkerson, B.; and Wiener, L. Designing Object-Oriented Software, Englewood Cliffs, NJ: Prentice Hall, 1990.]]
Wynekoop, J. L., and Russo, N. L. "Studying System Development Methodologies: An Examination of Research Methods," Information Systems Journal (7), 1997, pp. 47-65.]]
Yin, R. K. Case Study Research: Design and Methods, Thousand Oaks, CA: Sage Publications Inc.,1994.]]
This work presents MOQARE (misuse-oriented quality requirements engineering), a method to explore quality requirements. The aim of MOQARE is to support intuitive and systematic identification of quality requirements. It was developed by integrating and .
Goal models have been used in Requirements Engineering (RE) to elicit, model and analyse stakeholder requirements. In a goal model, stakeholder requirements are represented as root-level goals that are iteratively refined through AND/OR-refinements to .
The first argument presented in this paper is that if we have a clear understanding of the objectives of the requirements engineering (RE) process then we can identify what techniques we need. No single method or technique will be sufficient. The second .
