More Web Proxy on the site http://driver.im/

article

The brave new world of design requirements

Authors:

Matthias Jarke,

Pericles Loucopoulos,

Kalle Lyytinen,

John Mylopoulos,

William RobinsonAuthors Info & Claims

Information Systems, Volume 36, Issue 7

Pages 992 - 1008

https://doi.org/10.1016/j.is.2011.04.003

Published: 01 November 2011 Publication History

Abstract

Despite its success over the last 30 years, the field of Requirements Engineering (RE) is still experiencing fundamental problems that indicate a need for a change of focus to better ground its research on issues underpinning current practices. We posit that these practices have changed significantly in recent years. To this end we explore changes in software system operational environments, targets, and the process of RE. Our explorations include a field study, as well as two workshops that brought together experts from academia and industry. We recognize that these changes influence the nature of central RE research questions. We identify four new principles that underlie contemporary requirements processes, namely: (1) intertwining of requirements with implementation and organizational contexts, (2) dynamic evolution of requirements, (3) emergence of architectures as a critical stabilizing force, and (4) need to recognize unprecedented levels of design complexity. We recommend a re-focus of RE research based on a review and analysis of these four principles, and identify several theoretical and practical implications that flow from this analysis.

References

[1]

Frederick, P. and Brooks, J., The Mythical Man-Month. 1995. Addison-Wesley.

[2]

Ross, D.T. and Schoman Jr., K.E., Structured analysis for requirements definition. Transactions on Software Engineering. vSE-3 i1. 6-15.

[3]

Cheng, B.H.C. and Atlee, J.M., Current and future research directions in requirements engineering. In: Lyytinen, K., Loucopoulos, P., Mylopoulos, J., Robinson, W. (Eds.), Design Requirements Engineering-A Multi-Disciplinary Perspective for the Next Decade, Springer-Verlag.

[4]

Hansen, S., Lyytinen, K. and Berente, N., Requirements in the 21st century: current practice and emerging trends. In: Lyytinen, K., Loucopoulos, P., Mylopoulos, J., Robinson, W. (Eds.), Design Requirements Engineering-A Multi-disciplinary Perspective for the Next Decade, Springer-Verlag.

[5]

Jacobsen, I., Christerson, M., Jonsson, P. and Övergaard, G., Object-oriented software engineering-a use case-driven approach. In: Carroll, J. (Ed.), Scenario-Based Design, Wiley.

[6]

Boehm, B.W., A spiral model of software development and enhancement. Computer. v21 i5. 61-72.

[7]

Gotel, O.C.Z. and Finkelstein, C.W., An analysis of the requirements traceability problem, in: Proceedings of the First International Conference on Requirements Engineering. 1994. Colorado Springs, CO, USA.

[8]

Ramesh, B. and Jarke, M., Toward reference models for requirements traceability. IEEE Transactions on Software Engineering. v27 i1. 58-93.

[9]

Lyytinen, K., Loucopoulos, P., Mylopoulos, J. and Robinson, B., Design Requirements Engineering: A Ten-Year Perspective, Design Requirements Workshop, Cleveland, OH, USA, June 3-6, 2007, Revised and Invited Papers. 2009. Springer-Verlag, Heidelberg.

[10]

O'Reilly, T., What is web 2.0. Design patterns and business models for the next generation of software. v30. 2005

[11]

Hansen, S., Berente, N. and Lyytinen, K., Principles of Requirements Processes at the Dawn of 21st Century. Ingénierie des Systèmes d'Information. v13 i1. 9-35.

[12]

Scharer, L., Pinpointing requirements. Datamation. v27 i4. 139-151.

[13]

Bergman, M., King, J. and Lyytinen, K., Large-scale requirements analysis revisited: The need for understanding the political ecology of requirements engineering. Requirements Engineering. v7 i3. 152-171.

[14]

Davis, A., . 1993. Prentice-Hall.

[15]

Hull, E., Jackson, K. and Dick, J., Requirements Engineering. 2005. Springer.

[16]

Jackson, M.J., Software requirements and Specifications: A Lexicon of Practice, Principles, and Prejudices. 1995. ACM Press; Addison-Wesley Pub. Co., New York, Wokingham, England; Reading, MA.

[17]

Loucopoulos, P. and Karakostas, V., System Requirements Engineering. 1995. McGraw-Hill Book Co, London, New York.

[18]

Sommerville, I. and Sawyer, P., Requirements Engineering: A Good Practice Guide. 1997. John Wiley & Sons, Chichester, England; New York.

[19]

Wiegers, K., Read my lips: No new models!. Software, IEEE. v15 i5. 10-13.

[20]

Wieringa, R., Requirements Engineering: Frameworks for Understanding. 1996. Wiley, Chichester, England; New York.

[21]

Windle, D. and Abreo, L., Software Requirements Using the Unified Process: A Practical Approach. 2003. Prentice-Hall PTR.

[22]

Vessey, I. and Conger, S., Requirements specification: learning object, process, and data methodologies. Communications of the ACM. v37 i5. 102-113.

[23]

Thayer, R.H. and Dorfman, M., . 1997. 2nd ed. IEEE Computer Society Press, Los Alamitos, California.

[24]

Ghezzi, C., Jazayeri, M. and Mandrioli, D., Fundamentals of Software Engineering. 2002. Prentice-Hall PTR, Upper Saddle River, NJ, USA.

[25]

Boehm, B., Verifying and validating software requirements and design specifications. IEEE Software. v1 i1. 75-88.

[26]

J. Goguen, C. Linde, Techniques for requirements elicitation, in: Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE, San Diego, CA, USA, 1993, pp. 152-164.

[27]

Kotonya, G. and Sommerville, I., Requirements Engineering: Processes and Techniques. 1998. John Wiley, New York.

[28]

Siddiqi, J., Challenging Universal Truths of Requirements Engineering. IEEE Software. v11 i2. 19

[29]

Zowghi, D. and Coulin, C., Requirements elicitation: a survey of techniques, approaches, and tools. Engineering and Managing Software Requirements. 19-46.

[30]

Agarwal, R. and Tanniru, M., Knowledge acquisition using structured interviewing: an empirical investigation. Journal of Management Information Systems. 123-140.

[31]

Byrd, T., Cossick, K. and Zmud, R., A synthesis of research on requirements analysis and knowledge acquisition techniques. MIS Quarterly. v16 i1. 117-138.

[32]

Wright, G. and Ayton, P., Eliciting and modelling expert knowledge* 1. Decision Support Systems. v3 i1. 13-26.

[33]

Beyer, H. and Holtzblatt, K., Apprenticing with the customer. Communications of the ACM. v38 i5. 45-52.

[34]

Viller, S. and Sommerville, I., Social analysis in the requirements engineering process: from ethnography to method. IEEE. 6-13.

[35]

Alavi, M., An assessment of the prototyping approach to information systems development. Communications of the ACM. v27 i6. 556-563.

[36]

Beynon-Davies, P., Tudhope, D. and Mackay, H., Information systems prototyping in practice. Journal of Information Technology. v14 i1. 107-120.

[37]

A. van Lamsweerde, Requirements Engineering in the year 00: a research perspective, in: Proceedings of the 22nd International Conference on Software Engineering (ICSE), IEEE, 2000.

[38]

Borgida, A., Greenspan, S. and Mylopoulos, J., Knowledge representation as the basis for requirements specifications. Computer. v18 i4. 82-91.

[39]

Hsia, P., Davis, A. and Kung, D., Status report: requirements engineering. IEEE Software. v10 i6. 75-79.

[40]

Reubenstein, H.B. and Waters, R.C., The Requirements Apprentice: Automated Assistance for Requirements Acquisition. IEEE Transactions on Software Engineering. v17 i3. 226-240.

[41]

Gervasi, V. and Nuseibeh, B., Lightweight validation of natural language requirements: a case study. IEEE. 140-148.

[42]

Goldin, L. and Berry, D., AbstFinder, a prototype natural language text abstraction finder for use in requirements elicitation. Automated Software Engineering. v4 i4. 375-412.

[43]

K. Ryan, The role of natural language in requirements engineering, in: Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE, San Diego, CA, USA, 1993, pp. 240-242.

[44]

Ross, D.T., Structured analysis (SA): a language for communicating ideas. Transactions on Software Engineering. vSE-3 i1. 16-34.

[45]

Harel, D., Statecharts: a visual formalism for complex systems. Science of Computer Programming. v8 i3. 231-274.

[46]

Peterson, J.L., Petri nets. Computing Surveys. v9 i3. 223-252.

[47]

J. Rumbaugh, I. Jacobson, G. Booch, The Unified Modeling Language Reference Manual, 1998.

[48]

Miller, J., Sheth, A. and Kochut, K., Perspectives in modeling: simulation, database, and workflow. Conceptual Modeling. 154-167.

[49]

Pohl, K., Requirement Engineering: An Overview. Encyclopedia of Computer Science and Technology. 1996. Marcel Dekker, New York.

[50]

Wiegers, K., Software Requirements. 2003. Microsoft Press, Redmond, WA, USA.

[51]

Easterbrook, S., Handling conflict between domain descriptions with computer-supported negotiation* 1,* 2. Knowledge Acquisition. v3 i3. 255-289.

[52]

Grünbacher, P. and Seyff, N., Requirements negotiation. Engineering and Managing Software Requirements. 143-162.

[53]

Robinson, W.N. and Volkov, S., Supporting the negotiation life-cycle. Communications of the ACM. v41 i5. 95-102.

[54]

W.N. Robinson, S. Volkov, S. Pawlowski, Requirements Interaction Management CIS-99-7, Georgia State University, Computer Information Systems Department, Atlanta, GA, 1999.

[55]

M. Jarke, K. Lyytinen, J. Mylopoulos, Perspectives Workshop: Science of Design: High-Impact Requirements for Software-Intensive Systems, ISSN 1862-4405, Leibniz-Zentrum fur Informatik, 2008.

[56]

Schuler, D. and Namioka, A., . 1993. Lawrence Erlbaum Assoc., Hillsdale, New Jersey.

[57]

Glasser, B. and Strauss, A., The Development of Grounded Theory. 1967. Alden, Chicago, IL.

[58]

Jarke, M., Loucopoulos, P., Lyytinen, K., Mylopoulos, J. and Robinson, W., High-impact requirements for software-intensive systems. Informatik Spektrum. v32 i4. 352-353.

[59]

Lindquist, C., . 2005. Fixing the Requirements Mess, 2005.CIO Magazine.

[60]

Aurum, A. and Wohlin, C., Requirements engineering: setting the context. Engineering and Managing Software Requirements. 1-15.

[61]

Crowston, K. and Kammerer, E., Coordination and collective mind in software requirements development. IBM Systems Journal. v37 i2. 227-245.

[62]

Davis, A. and Hickey, A., Requirements researchers: do we practice what we preach?. Requirements Engineering. v7 i2. 107-111.

[63]

Leffingwell, D. and Widrig, D., Managing Software Requirements: A Unified Approach. 1999. Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA.

[64]

Simon, H., The Sciences of the Artificial. 1996. Third Edition. MIT Press.

[65]

Schon, D., The Reflective Practitioner: How Professionals Think in Action. 1983. Basic Books, New York.

[66]

Bowen, J.P. and Hinchey, M.G., . Ten Commandments of Formal Methods.

[67]

Swartout, W. and Balzer, R., On the inevitable intertwining of specification and implementation. Communications of the ACM. v25 i7. 438-440.

[68]

Mathiassen, L., Saarinen, T., Tuunanen, T. and Rossi, M., A contigency model for requirements development. Journal of the Association for Information Systems. v8 i11. 569-597.

[69]

Robinson, W.N., A roadmap for comprehensive requirements monitoring. IEEE Computer. v43 i5. 64-72.

[70]

Chapin, N., Hale, J.E., Khan, K.M., Ramil, J.F. and Tan, W.G., Types of software evolution and software maintenance. Journal of Software Maintenance and Evolution Research and Practice. v13 i1. 3-30.

[71]

Cockburn, A., Agile Software Development. 2002. Addison-Wesley.

[72]

Berger, C., Piller, F., Adidas Salomon, A.G. and Herzogenaurach, G., Customers as co-designers. Manufacturing Engineer. v82 i4. 42-45.

[73]

Ross, J., Weill, P. and Robertson, D., Enterprise Architecture as Strategy: Creating a Foundation for Business Execution. 2006. Harvard Business Press.

[74]

Lehman, M.M., Software evolution. Encyclopedia of Software Engineering. v2. 1507-1513.

[75]

Nuseibeh, B., Weaving together requirements and architectures. Computer. v34 i3. 115-119.

[76]

Pohl, K., Böckle, G. and Linden, F.J.V.D., . 2005. Springer, Berlin, Heidelberg.

[77]

Godet, M., Scenarios and Strategic Management. 1987. Butterworth-Heinemann.

[78]

Anderson, P., Complexity theory and organization science. Organization Science. 216-232.

[79]

Cilliers, P., Complexity and Postmodernism: Understanding Complex Systems. 1998. Routledge.

[80]

Garfield, J. and Loucopoulos, P., Requirements Elaboration for System Co-development. Ingenierie des Systemes d'information. v14 i4. 77-98.

[81]

Vidgen, R. and Wang, X., Coevolving systems and the organization of agile software development. Information Systems Research. v20 i3. 355-376.

[82]

P. Loucopoulos, K. Zografos, N. Prekas, Requirements elicitation for the design of venue operations for the Athens 2004 Olympic games, in: Proceedings of the 11th IEEE International Conference on Requirements Engineering, Monterey Bay, California, 2003, pp. 223-232.

[83]

Scacchi, W., Understanding Open Source Software Evolution, Software Evolution and Feedback, Theory and Practice. 2006. Wiley, NY.

[84]

J.M. Carroll, Scenarios and design cognition, in: Proceedings of the IEEE Joint International Conference on Requirements Engineering, 2002, pp. 3-5.

[85]

Napier, N., Mathiassen, L. and Johnson, R., Combining perceptions and prescriptions in requirements engineering process assessment: an industrial case study. IEEE Transactions on Software Engineering. 593-606.

[86]

Davis, A. and Zowghi, D., Good requirements practices are neither necessary nor sufficient. Requirements Engineering. v11 i1. 1-3.

[87]

B. Nuseibeh, S. Easterbrook, Requirements engineering: a roadmap, in: Proceedings of the Conference on the Future of Software Engineering, 2000, pp. 35-46.

[88]

Jackson, M., The meaning of requirements. Annals of Software Engineering. v3. 5-21.

[89]

Glinz, M., A risk-based, value-oriented approach to quality requirements. Software, IEEE. v25 i2. 34-41.

[90]

G. Jung, B. Lee, Analysis on social network adoption according to the change of network topology-the impact of "Open API" on the adoption of Facebook, in: The 12th International Conference on Electronic Commerce (ICEC-2010), ACM, Honolulu, HI, USA, 2010, pp. 22-31.

Cited By

Melegati JWiese IGuerra EChanin RAldaeej AMikkonen TPrikladnicki RWang X(2024)Product managers in software startupsInformation and Software Technology10.1016/j.infsof.2024.107516174:COnline publication date: 1-Oct-2024
https://dl.acm.org/doi/10.1016/j.infsof.2024.107516
Camargo‐Henríquez ISilva A(2023)Understanding Software‐centered Evolutive Ecosystems through Activity TheoryJournal of Software: Evolution and Process10.1002/smr.256035:12Online publication date: 16-Mar-2023
https://dl.acm.org/doi/10.1002/smr.2560
Kotronis CNikolaidou MBardaki CKühn TSousa V(2022)QoS-aware model-based systems design using systems modeling languageProceedings of the 25th International Conference on Model Driven Engineering Languages and Systems: Companion Proceedings10.1145/3550356.3561579(296-305)Online publication date: 23-Oct-2022
https://dl.acm.org/doi/10.1145/3550356.3561579
Show More Cited By

Recommendations

Requirements-driven software evolution

It is often the case that stakeholders want to strengthen/weaken or otherwise change their requirements for a system-to-be when certain conditions apply at runtime. For example, stakeholders may decide that if requirement R is violated more than N ...
The brave new world of design requirements: four key principles
CAiSE'10: Proceedings of the 22nd international conference on Advanced information systems engineering

Despite its undoubted success, Requirements Engineering (RE) needs a better alignment between its research focus and its grounding in practical needs as these needs have changed significantly recently. We explore changes in the environment, targets, and ...
(Requirement) evolution requirements for adaptive systems
SEAMS '12: Proceedings of the 7th International Symposium on Software Engineering for Adaptive and Self-Managing Systems

It is often the case that stakeholders want to strengthen/weaken or otherwise change their requirements for a system-to-be when certain conditions apply at runtime. For example, stakeholders may decide that if requirement R is violated more than N times ...

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image Information Systems

Information Systems Volume 36, Issue 7

November, 2011

114 pages

ISSN:0306-4379

Issue’s Table of Contents

Copyright © © 2011.

Publisher

Elsevier Science Ltd.

United Kingdom

Publication History

Published: 01 November 2011

Author Tags

Qualifiers

Article

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

29
Total Citations
View Citations
0
Total Downloads

Downloads (Last 12 months)0
Downloads (Last 6 weeks)0

Reflects downloads up to 13 Dec 2024

Other Metrics

View Author Metrics

Citations

Cited By

Melegati JWiese IGuerra EChanin RAldaeej AMikkonen TPrikladnicki RWang X(2024)Product managers in software startupsInformation and Software Technology10.1016/j.infsof.2024.107516174:COnline publication date: 1-Oct-2024
https://dl.acm.org/doi/10.1016/j.infsof.2024.107516
Camargo‐Henríquez ISilva A(2023)Understanding Software‐centered Evolutive Ecosystems through Activity TheoryJournal of Software: Evolution and Process10.1002/smr.256035:12Online publication date: 16-Mar-2023
https://dl.acm.org/doi/10.1002/smr.2560
Kotronis CNikolaidou MBardaki CKühn TSousa V(2022)QoS-aware model-based systems design using systems modeling languageProceedings of the 25th International Conference on Model Driven Engineering Languages and Systems: Companion Proceedings10.1145/3550356.3561579(296-305)Online publication date: 23-Oct-2022
https://dl.acm.org/doi/10.1145/3550356.3561579
Vössing MKühl NLind MSatzger G(2022)Designing Transparency for Effective Human-AI CollaborationInformation Systems Frontiers10.1007/s10796-022-10284-324:3(877-895)Online publication date: 1-Jun-2022
https://dl.acm.org/doi/10.1007/s10796-022-10284-3
Naous DLegner C(2021)A preference-based approach to incorporate the "voice of the customer" in mass-market software product designACM SIGAPP Applied Computing Review10.1145/3447332.344733520:4(35-49)Online publication date: 12-Jan-2021
https://dl.acm.org/doi/10.1145/3447332.3447335
van der Linden D(2021)Interspecies information systemsRequirements Engineering10.1007/s00766-021-00355-326:4(535-556)Online publication date: 1-Dec-2021
https://dl.acm.org/doi/10.1007/s00766-021-00355-3
Lessard LAmyot DAswad OMouttham A(2020)Expanding the nature and scope of requirements for service systems through Service-Dominant Logic: the case of a telemonitoring serviceRequirements Engineering10.1007/s00766-019-00322-z25:3(273-293)Online publication date: 1-Sep-2020
https://dl.acm.org/doi/10.1007/s00766-019-00322-z
Jarke M(2020)Data Sovereignty and the Internet of ProductionAdvanced Information Systems Engineering10.1007/978-3-030-49435-3_34(549-558)Online publication date: 8-Jun-2020
https://dl.acm.org/doi/10.1007/978-3-030-49435-3_34
Franch XSeyff NOriol MFricker SGroher IVierhauser MWimmer M(2020)Towards Integrating Data-Driven Requirements Engineering into the Software Development Process: A Vision PaperRequirements Engineering: Foundation for Software Quality10.1007/978-3-030-44429-7_10(135-142)Online publication date: 24-Mar-2020
https://dl.acm.org/doi/10.1007/978-3-030-44429-7_10
Chen FPower NCollins JIshikawa FHung CPapadopoulos G(2019)Contemporary requirements challenges and issuesProceedings of the 34th ACM/SIGAPP Symposium on Applied Computing10.1145/3297280.3297435(1592-1599)Online publication date: 8-Apr-2019
https://dl.acm.org/doi/10.1145/3297280.3297435
Show More Cited By

View Options

View options

Media

Figures

Other

Tables

View Issue’s Table of Contents