Skip to main content
SpringerLink
Log in
Book cover

Design Requirements Engineering: A Ten-Year Perspective pp 103–136Cite as

A Proposal for a Formal Definition of the Design Concept

  • Conference paper

Part of the book series: Lecture Notes in Business Information Processing ((LNBIP,volume 14))

Abstract

A clear and unambiguous definition of the design concept would be useful for developing a cumulative tradition for research on design. In this article we suggest a formal definition for the concept design and propose a conceptual model linking concepts related to design projects. The definition of design incorporates seven elements: agent, object, environment, goals, primitives, requirements and constraints. The design project conceptual model is based on the view that projects are temporal trajectories of work systems that include human agents who work to design systems for stakeholders, and use resources and tools to accomplish this task. We demonstrate how these two suggestions can be useful by showing that 1) the definition of design can be used to classify design knowledge and 2) the conceptual model can be used to classify design approaches.

This is a preview of subscription content, log in via an institution.

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Freeman, P., Hart, D.: A science of design for software-intensive systems. Communications of the ACM 47(8), 19–21 (2004)

    Article  Google Scholar 

  2. Simon, H.A.: The Sciences of the Artificial, 3rd edn. MIT Press, Cambridge (1996)

    Google Scholar 

  3. Hevner, A.R., March, S.T., Park, J., Ram, S.: Design science in information systems research. MIS Quarterly 28(1), 75–105 (2004)

    Google Scholar 

  4. March, S.T., Smith, G.F.: Design and natural science research on information technology. Decision Support Systems 15(4), 251–266 (1995)

    Article  Google Scholar 

  5. Accreditation board for engineering and technology, Inc. Annual report for the year ending September 30, 1988. New York, USA (1988)

    Google Scholar 

  6. van Engers, T.M., Gerrits, R., Boekenoogen, M., Glassée, E., Kordelaar, P.: Power: using uml/ocl for modeling legislation - an application report. In: ICAIL 2001: Proceedings of the 8th international conference on Artificial intelligence and law, pp. 157–167. ACM Press, New York (2001)

    Chapter  Google Scholar 

  7. Bradel, B., Stewart, K.: Exploring processor design using genetic programming. In: ECE1718 Special Topics in Computer Hardware Design: Modern and Emerging Architectures. University of Toronto, Toronto (April 2004)

    Google Scholar 

  8. Eekels, J.: On the fundamentals of engineering design science: The geography of engineering design science. part 1. Journal of Engineering Design 11, 377–397 (2000)

    Article  Google Scholar 

  9. Breuer, T., Ndoundou-Hockemba, M., Fishlock, V.: First observation of tool use in wild gorillas. PLoS Biol. 3(11) (2005)

    Google Scholar 

  10. Mulcahy, N., Call, J.: Apes save tools for future use. Science 312(5776), 1038–1040 (2006)

    Article  Google Scholar 

  11. Churchman, C.W.: The design of inquiring systems: Basic concepts of systems and organization. Basic Books, New York (1971)

    Google Scholar 

  12. Alexander, C.W.: Notes on the synthesis of form. Harvard University Press (1964)

    Google Scholar 

  13. Gero, J.S.: Design prototypes: A knowledge representation schema for design. AI Magazine 11(4), 26–36 (1990)

    Google Scholar 

  14. Bourque, P., Dupuis, R. (eds.): Guide to the software engineering body of knowledge (SWEBOK). IEEE Computer Society Press, Los Alamitos (2004)

    Google Scholar 

  15. Siddiqi, J., Shekaran, M.: Requirements engineering: The emerging wisdom. IEEE Software, 15–19 (March 1996)

    Google Scholar 

  16. Kruchten, P.: The Rational Unified Process: An Introduction, 3rd edn. Addison-Wesley Professional, Reading (2003)

    Google Scholar 

  17. Pahl, G., Beitz, W.: Engineering Design: A Systematic Approach. Springer, London (1996)

    Google Scholar 

  18. Lamsweerde, A.v.: Goal-oriented requirements engineering: a guided tour. In: Proceedings of the Fifth IEEE International Symposium on Requirements Engineering, pp. 249–262 (August 2001)

    Google Scholar 

  19. Hammer, M., Champy, J.: Reengineering the corporation: A manifesto for business revolution. Business Horizons 36(5), 90–91 (1993), http://ideas.repec.org/a/eee/bushor/v36y1993i5p90-91.html

    Article  Google Scholar 

  20. van der Alast, W.M.P.: Workflow verification: Finding control-flow errors using petri-net-based techniques. In: van der Aalst, W.M.P., Desel, J., Oberweis, A. (eds.) Business Process Management. LNCS, vol. 1806, pp. 161–183. Springer, Heidelberg (2000)

    Chapter  Google Scholar 

  21. Soffer, P., Wand, Y.: Goal-driven analysis of process model validity. Advanced Information Systems Engineering, 521–535 (2004)

    Google Scholar 

  22. Royce, W.: Managing the Development of Large Software Systems. Proceedings of IEEE WESCON 26 (1970)

    Google Scholar 

  23. Alter, S.: The Work system method: Connecting people, processes, and IT for business results. Work System Press (2006)

    Google Scholar 

  24. Freeman, R.: Strategic Management: A stakeholder approach. Pitman, Boston (1984)

    Google Scholar 

  25. Bera, P., Wand, Y.: Conceptual Models for Knowledge Management Systems. Working paper, University of British Columbia (2007)

    Google Scholar 

  26. Checkland, P.: Systems Thinking, Systems Practice. John Wiley & Sons, Ltd., Chichester (1999)

    Google Scholar 

  27. Jacobson, I., Booch, G., Rumbaugh, J.: The unified software development process. Addison-Wesley Longman Publishing Co., Inc., Boston (1999)

    Google Scholar 

  28. Department of Justice. The department of justice systems development life cycle guidance document

    Google Scholar 

  29. Manlei, M., Teorey, T.: Incorporating behavioral techniques into the systems development lifecycle. MIS Quarterly 13(3), 257–274 (1989)

    Article  Google Scholar 

  30. Fenton, N.: Software measurement: A necessary scientific basis. IEEE Trans. Softw. Eng. 20(3), 199–206 (1994)

    Article  Google Scholar 

  31. Finkelstein, L.: A review of the fundamental concepts of measurement. Measurement 2(I), 25–34 (1984)

    Article  Google Scholar 

  32. Roberts, F.: Measurement Theory with Applications to Decision Making, Utility and the Social Sciences. Addison Wesley, Reading (1979)

    Google Scholar 

  33. Polya, G.: How to Solve It: A New Aspect of Mathematical Method, 2nd edn. Princeton University Press, Princeton (1957)

    Google Scholar 

  34. Kessler, A.: WSJ: Weekend interview with Facebook’s Mark Zuckerberg

    Google Scholar 

  35. Beck, K.: Extreme programming eXplained: embrace change. Addison-Wesley, Reading (2000)

    Google Scholar 

  36. Grüninger, M., Fox, M.: Methodolgy for the design and evaluation of ontologies. In: Proceedings of the IJCAI Workshop on Basic Ontological Issues in Knoweldge Sharing, Menlo Park CA, USA. AAAI Press, Menlo Park (1995)

    Google Scholar 

  37. Noy, N., Hafner, C.: The state of the art in ontology design. AI Magazine, 53–74 (Fall 1997)

    Google Scholar 

  38. Mili, H., Mili, F., Mili, A.: Reusing software: Issues and research directions. IEEE Transactions on Software Engineering 21(6), 528–562 (1995)

    Article  Google Scholar 

  39. Ambler, S.: A realistic look at object-oriented reuse. Software Development 6(1), 30–38 (1998)

    Google Scholar 

  40. Alexander, C., Ishikawa, S., Silverstein, M., Jacobson, M., Fiksdahl-King, I., Angel, S.: A Pattern Language: Towns, Buildings, Construction. Oxford University Press, Oxford (1977)

    Google Scholar 

  41. Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design patterns: Elements of reusable object-oriented software. Addison-Wesley, Boston (1995)

    Google Scholar 

  42. Desouza, K.C., Awazu, Y., Tiwana, A.: Four dynamics for bringing use back into software reuse. Commun. ACM 49(1), 96–100 (2006)

    Article  Google Scholar 

  43. Reubenstein, H., Waters, R.: The requirements apprentice: Automated assistance for requirements acquisition. IEEE Trans. Softw. Eng. 17(3), 226–240 (1991)

    Article  Google Scholar 

  44. Hansen, S., Berente, N., Lyytinen, K.: Requirements in the 21st century: Current practice and emerging trends. In: The Design Requirements Workshop, Cleveland, Ohio, USA, June 3-6 (2007)

    Google Scholar 

  45. Gregor, S., Jones, D.: The anatomy of a design theory. Journal of the Association for Information Systems 8, 312 (2007)

    Google Scholar 

  46. Aghion, P., Tirole, J.: Real and Formal Authority in Organizations. Journal of Political Economy 105, 1–29 (1997)

    Article  Google Scholar 

  47. Pfeffer, J.: Managing with Power: Politics and Influence in Organizations. Harvard Business School Press, Cambridge (1992)

    Google Scholar 

  48. Garlan, D., Shaw, M.: An introduction to software architecture. In: Ambriola, V., Tortora, G. (eds.) Advances in software engineering and knowledge engineering, pp. 1–39. World Scientific, Singapore (1993)

    Google Scholar 

  49. Wynekoop, J., Russo, N.: Studying system development methodologies: an examination of research methods. Information Systems Journal 7, 47–65 (1997)

    Article  Google Scholar 

  50. Van de Ven, A., Poole, M.: Explaining Development and Change in Organizations. Acad. Manage. Rev. 20, 510 (1995)

    Article  Google Scholar 

  51. Hinrichs, T.R.: Problem-solving in open worlds: a case study in design. PhD thesis, Atlanta, GA, USA (1992)

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Sauder School of Business, University of British Columbia, Canada

    Paul Ralph & Yair Wand

Authors
  1. Paul Ralph
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Yair Wand
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. Case Western Reserve University, Cleveland, OH, USA

    Kalle Lyytinen

  2. Loughborough University, UK

    Pericles Loucopoulos

  3. University of Toronto, ON, Canada

    John Mylopoulos

  4. Georgia State University, Atlanta, GA, USA

    Bill Robinson

Rights and permissions

Reprints and permissions

Copyright information

© 2009 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Ralph, P., Wand, Y. (2009). A Proposal for a Formal Definition of the Design Concept. In: Lyytinen, K., Loucopoulos, P., Mylopoulos, J., Robinson, B. (eds) Design Requirements Engineering: A Ten-Year Perspective. Lecture Notes in Business Information Processing, vol 14. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-92966-6_6

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-92966-6_6

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-92965-9

  • Online ISBN: 978-3-540-92966-6

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation