Abstract
We examine how to improve our understanding in stating and managing successfully requirements for large systems, because the current concept of a system requirement is ill suited to develop true requirements for such systems. It regards requirements as goals to be discovered and solutions as separate technical elements. In consequence, current Requirements Engineering (RE) theory separates these issues and reduces RE to an activity where a technical solution is documented for a given set of goals (problems). In contrast, we advocate a view where a requirement specifies a set of mappings between problem and solution spaces, which both are socially constructed and negotiated. Requirements are emergent and need to be discovered through a contracted process, which likens to a “garbage-can” decision-making. System requirements thereby embrace an emergent functional ecology of requirements. This leads to equate requirements engineering with heterogeneous engineering. The admitted heterogeneity of technological activity avoids a commitment to social (or technological) reductionism. Requirements engineers need to be seen as “heterogeneous engineers” who must associate entities that range from people, through skills, to artifacts and natural phenomena. They are successful only, if built socio-technical networks can remain stable in spite of attempts of other entities to dissociate them.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Abdel-Hamid, T. K. and S. E. Madnick (1990). “The Elusive Silver Lining: How We Fail to Learn from Software Development Failures.” Sloan Management Review 32(1): 39–48.
Bacharach, S. B. and E. J. Lawler (1980). Power and politics in organizations. San Francisco, Jossey-Bass.
Baier, V. and J. March (1986). “Implementation and Ambiguity.” Scandinavian Journal of Management Studies 4(May): 197–212.
Bak, P. (1996). How nature works: the science of self-organized criticality. New York, NY, USA, Copernicus.
Berger, P. L. and T. Luckmann (1966). The social construction of reality; a treatise in the sociology of knowledge. Garden City, N.Y., Doubleday.
Bergman, M., J. L. King, et al. (2001). Large Scale Requirements Analysis Revisited: The need for Understanding the Political Ecology of Requirements Engineering, submitted for publication.
Bijker, W. (1987). The Social Construction of Bakelite: Toward a Theory of Invention. The Social Construction of Technological Systems. W. Bijker, T. Hughes and T. Pinch. Cambridge, MA, MIT Press: 159–190.
Boehm, B. W. (1988). “A spiral model of software development and enhancement.” Computer May: 61–72.
Brooks, F. P. (1995). The mythical man-month: essays on software engineering. Reading, Mass., Addison-Wesley Pub. Co.
Checkland, P. (1981). Systems thinking, systems practice. Chichester Sussex; New York, J. Wiley.
Checkland, P. and J. Scholes (1990). Soft systems methodology in action. Chichester, West Sussex, England; New York, Wiley.
Couger, D. and J. Knapp (1974). Systems Analysis Techniques. London, John-Wiley & Son.
Davis, A. M. (1993). Software requirements: objects, functions, and states. Englewood Cliffs, N.J., PTR Prentice Hall.
DeTombe, D. J. (1994). Defining complex interdisciplinary societal problems: a theoretical study for constructing a co-operative problem analyzing method: the method COMPRAM. Amsterdam, Thesis Publishers.
Dowty, D. R., R. E. Wall, et al. (1981). Introduction to Montague semantics. Boston, MA, Kluwer Boston Inc.
Drummond, H. (1996). “The Politics of Risk: Trials and Tribulations of the Taurus Project.” Journal of Information Technology 11: 347–357.
Fairholm, G. W. (1993). Organizational power politics: tactics in organizational leadership. Westport, Conn., Praeger.
Foucault, M. and C. Gordon (1980). Power knowledge: selected interviews and other writings, 1972–1977. New York, Pantheon Books.
Gause, D. C. and G. M. Weinberg (1989). Exploring requirements: quality before design. New York, NY, Dorset House Pub.
Graham, I. (1998). Requirements engineering and rapid development: an object-oriented approach. Harlow, England; Reading, MA, Addison Wesley.
Haumer, P., P. Heymans, et al. (1999). Bridging the Gap Between Past and Future RE: A Scenario-Based Approach. RE’99, Limerick, Ireland, IEEE Computer Society.
Hughes, T. (1979a). “Emerging Themes in the History of Technology.” Technology and Culture 20(4): 697–711.
Hughes, T. (1979b). “The Electrification of America: The system builders.” Technology and Culture 20(1): 124–161.
Hughes, T. (1987). The Evolution of Large Technological Systems. The Social Construction of Technological Systems. W. Bijker, T. Hughes and T. Pinch. Cambridge, MA, MIT Press: 51–82.
Iivari, J. (1990a). “Hierarchical spiral model for information system and software development. Part 1: theoretical background.” Information and Software Technology 32(6): 386–399.
Iivari, J. (1990b). “Hierarchical spiral model for information system and software development, Part 2: design process.” Information and Software Technology 32(7): 450–458.
Keil, M. (1995). “Pulling the Plug: Software Project Management and the Problem of Project Escalation.” MIS Quarterly 19(4): 421–447.
Keil, M. and R. Montealegre (2000). “Cutting your losses: Extricating Your Organization When a Big Project Goes Awry.” Sloan Management Review 41(3): 55–68.
Kotonya, G. and I. Sommerville (1998). Requirements engineering: processes and techniques. Chichester; New York, J. Wiley.
Langefors, B. (1966). Theoretical Analysis of Information Systems. Lund, Sweden, Studentlitteratur.
Latour, B. (1991). Technology is society made durable. A Sociology of Monsters: Essays on Power, Technology and Domination. J. Law. London, Routledge.
Law, J. (1987). Technology and Heterogeneous Engineering: The Case of Portuguese Expansion. The Social Construction of Technological Systems. W. Bijker, T. Hughes and T. Pinch. Cambridge, MA, MIT Press: 111–134.
Lindblom, C. E. (1979). “Still Muddling Through.” Public Administrative Review 39: 517–526.
Loucopoulos, P. and V. Karakostas (1995). System Requirements Engineering. London, UK, McGraw-Hill Book Co.
Lyytinen, K., L. Mathiassen, et al. (1998b). “Attention Shaping and Software Risk-A Categorical Analysis of Four Classical Approaches.” Information Systems Research 9(3): 233–255.
Lyytinen, K., G. Rose, et al. (1998a). “The Brave New World of Development in the internet work computer architecture (InterNCA): or how distributed computing platforms will change systems development.” Information Systems Journal 8(3): 241–253.
Macaulay, L. (1996). Requirements engineering. London; New York, Springer.
March, J. G. and J. P. Olsen (1976). Ambiguity and choice in organizations. Bergen, Universitetsforlaget.
Markus, M. L. and M. Keil (1994). “If We Build It, They Will Come: Designing Information Systems that Users Want to Use.” Sloan Management Review 35(4): 22.
Mitev, N. N. (1996). “More than a Failure? The Computerized Reservation Systems at French Railways.” Information Technology & People 9(4): 8–19.
Myers, M. D. (1994). “A Disaster for Everyone to See: An Interpretive Analysis of a Failed IS Project.” Accounting, Management and Information Technologies 4(4): 185–201.
Noyes, J. M. and C. Baber (1999). User-centered design of systems. London; New York, Springer.
Pfeffer, J. (1981). Power in organizations. Marshfield, Mass., Pitman Pub.
Pohl, K. (1996). Process-centered requirements engineering. New York, NY, Wiley.
Robinson, W. N., S. D. Pawlowski, et al. (1999). Requirements Interaction Management, Unpublished Working Paper, Department of Computer Information Systems, Georgia State University.
Rosenwein, M. (1997). “The Optimization Engine That Couldn’t.” OR/MS Today 24(4): 26–29.
Ross, D. (1977). “Structured Analysis (SA): A Language for Communicating Ideas.” IEEE Transactions on Software Engineering 3(1): 16–34.
Simon, H. A. (1996). The sciences of the artificial. Cambridge, Mass., MIT Press.
Sommerville, I. and P. Sawyer (1997). Requirements engineering: a good practice guide. Chichester, England; New York, John Wiley & Sons.
Suchman, L. A. (1987). Plans and situated actions: the problem of human-machine communication. Cambridge Cambridgeshire; New York, Cambridge University Press.
Wieringa, R. (1996). Requirements engineering: frameworks for understanding. New York, NY, Wiley.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2006 Springer
About this paper
Cite this paper
Lyytinen, K., Bergman, M., King, J.L. (2006). Large Scale Requirements Analysis as Heterogeneous Engineering. In: Seruca, I., Cordeiro, J., Hammoudi, S., Filipe, J. (eds) Enterprise Information Systems VI. Springer, Dordrecht. https://doi.org/10.1007/1-4020-3675-2_2
Download citation
DOI: https://doi.org/10.1007/1-4020-3675-2_2
Publisher Name: Springer, Dordrecht
Print ISBN: 978-1-4020-3674-3
Online ISBN: 978-1-4020-3675-0
eBook Packages: Computer ScienceComputer Science (R0)