Bibliography

• Adelson B., Soloway E. (1986):
  A model of software design,
  International Journal of Intelligent Systems 1 (3), pp. 195-213.

• Aste T., Tasca P., Di Matteo T. (2017): Blockchain Technologies: The Foreseeable Impact on Society and Industry, IEEE Computer 50(9), pp. 18-28.

• Bach P.M and Twidale M. (2010): Social participation in open source: what it means for designers, interactions 17 (3), pp. 70-74.

• Bacon, Francos (1620):
  The New Organon.

• Ball L.J., Onarheim B., Bo T. Christensen, (2010):
  Design requirements, epistemic uncertainty and solution development strategies in software design,
  Design Studies 31 (6), pp. 567-589.

• Bell A.E. (2004):
  Death by UML Fever,
  Queue 2 (1), pp. 72-80.

• Berghel H. (1999):
  Digital Village: How Xday Figures in the Y2K Countdown,
  Commun. ACM 42 (5), pp. 11-15.

• Boden M. A., (2004):
  The Creative Mind: Myths and Mechanisms,
  Psychology Press, 2nd edition, expanded/revised.

• Bass L., Clements P.C., and Kazman R. (2012):
  Software Architecture in Practice,
  (3rd Edition) Addison-Wesley Professional.

• Boehm B. and Bhuta J. (2008):
  Balancing Opportunities and Risks in Component-Based Software Development,
  IEEE Software 25 (6), pp. 56-63.

• Booch G. (2008): Measuring Architectural Complexity, IEEE Software 25 (4), pp. 56-63.

• Brooks F.P. (1987):
  No Silver Bullet—Essence and Accidents of Software Engineering,
  Computer 20 (4), pp. 10-19.

• Brooks F.P. (1995):
  The Mythical Man-Month,
  Addison-Wesley Professional; 2nd edition.

• Brooks F.P. (2010):
  The Design of Design,
  Addison-Wesley Professional.

• Brown W.J., Malveau R.C., McCormick H.W., and Mowbray T.J. (1998):
  AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis,
  Wiley.

• Brown G., Fisher M., Stoll N., Beeksma D., Black M., Taylor R., Seok Yon C., Williams A.J., Bryant W., and Jansen B.J. (2000):
  Using the lessons of Y2K to improve information systems architecture,
  Commun. ACM 43 (10), pp. 90-97.

• Buchanan R. (1992):
  Wicked Problem in Design Thinking,
  Design Issues 8 (2), pp. 5-21.

• Buxton B. (2007):
  Sketching User Experiences: Getting the Design Right and the Right Design,
  Morgan Kaufmann Publishers Inc., San Francisco, CA.

• Chan C.-S. (2001): An examination of the forces that generate a style, Design Studies 22 (4), pp. 319-346.

• Charette R. N. (2005):
  Why Software Fails,
  IEEE Spectr. 42 (9), pp. 42-49.

• Chua J. (2015):
  Design Without Final Goals: Getting Around Our Bounded Rationality,
  Artifact 3 (4), pp. 2.1-2.7.

• Cockburn A. (2000):
  Selecting a Project’s Methodology,
  IEEE Softw. 17 (4), pp. 64-71.

• Colwell, B. (2005): Complexity in Design, Computer 38 (10), pp. 10-12.

• Conway, M.E. (1968):
  How do Committees Invent?,
  Datamation 14 (5), pp. 28–31.

• Coplien J.O (1999): Guest Editor’s Introduction: Reevaluating the Architectural Metaphor-Toward Piecemeal Growth, IEEE Software 19 (5), pp. 40-44.

• Coyne R. (2005):
  Wicked problems revisited,
  Design Studies 26 (1), pp. 5-17.

• Cross N. (1999):
  Natural intelligence in design,
  Design Studies 20 (1), pp. 25-39.

• Cross N. (2006):
  Designerly ways of knowing,
  Springer Science & Business Media.

• Curtis B., Guindon R., Krasner H., Walz D., Elam J., and Iscoe N., (1987):
  Empirical Studies of the Design Process: Papers for the Second Workshop on Empirical Studies of Programmers,
  MCC Technical Report Number STP-260-87.

• Ditlea, Steve (1981-10-01):
  An Apple On Every Desk.
  Inc, Retrieved April 22, 12013.

• Dorst, C.H., Cross, N.G. (2001): Creativity in the design process: co-evolution of problem-solution, Design Studies 22(5), pp. 425-437.

• Ebert C., Jones C. (2009):
  Embedded Software: Facts, Figures, and Future,
  Computer 42 (4), pp. 42-52.

• Farrell R., Hooker C. (2013):
  Design, science and wicked problems,
  Design Studies 34 (6), pp. 681-705.

• Fielding, R.T. (2000):
  Architectural Styles and the Design of Network-based Software Architectures.
  Dissertation. University of California, Irvine.

• Fonseca O., Fazzion E., Cunha I., Las-Casas P.H.B., Guedes D., Meira W., Hoepers C., Steding-Jessen K., Chaves M.H.P. (2016): Measuring, Characterizing, and Avoiding Spam Traffic Costs, IEEE Internet Computing 20 (4), pp. 16-24.

• Frosh, R.A. (1969):
  A new look at systems engineering,
  IEEE Spectrum, September 1969. pp. 24-28.

• Funke J. (1991):
  Solving complex problems: Exploration and control of complex systems,
  Complex problem solving: Principles and mechanisms.

• Gaver W., Bowers J., Kerridge T., Boucher A., and Jarvis N.. (2009):
  Anatomy of a failure: how we knew when our design went wrong, and what we learned from it,
  In Proceedings of the 27th international conference on Human factors in computing systems (CHI ‘09),
  ACM, New York, NY, USA, 2213-2222.

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

• Glass R. L. (2006):
  Software Creativity 2.0,
  developer.* Books.

• Gokpinar B., Hopp W.J., Iravani S.M.R (2010): The Impact of Misalignment of Organizational Structure and Product Architecture on Quality in Complex Product Development, Management Science 56 (3), pp. 468-484.

• Goodman E. (2014): Design and ethics in the era of big data, interactions 21 (3), pp. 22-24.

• Goth G. (2011):
  IBM PC Retrospective: There Was Enough Right to Make It Work,
  Computer 44 (8), pp. 26-33.

• Gravemeijer K. and Cobb P. (2006):
  Design research from a learning design perspective,
  in Akker et al. (Eds.) Educational Design Research.

• Greenberg S. and Buxton B. (2008):
  Usability evaluation considered harmful (some of the time),
  in Proceedings of the twenty-sixth annual SIGCHI conference on Human factors in computing systems (CHI ‘08),
  ACM, New York, NY, USA, 111-120.

• Greenstein S. (2018): The Paradox of Technological Déjà Vu, IEEE Micro 38 (1), pp 118-120.

• Gubbi J., Buyya R., Marusic S., Palaniswami M. (2013):
  Internet of Things (IoT): A vision, architectural elements, and future directions,
  Future Generation Computer Systems 29 (7), pp. 1645-1660.

• Hadjerrouit S. (1998):
  Java as first programming language: a critical evaluation,
  SIGCSE Bull. 30 (2), pp. 43-47.

• Hales C. (1985):
  Designer as chameleon,
  Design Studies 6 (2), pp. 111-114.

• Harrison W. (2004): From the Editor: Best Practices–Who Says?, IEEE Software 21 (1), pp. 8-11.

• Harrison W. (2006):
  Eating Your Own Dog Food,
  IEEE Software 23 (3), pp. 5-7.

• Hatchuel, A. (2001): Towards Design Theory and Expandable Rationality: The Unfinished Program of Herbert Simon, Journal of Management and Governance 5 (3-4), pp. 260-273.

• Heiko G.A. (2004):
  Announcement, entry, and preemption when consumers have switching costs. (econometric analysis),
  RAND Journal of Economics (The RAND Corporation) 35 (1), pp. 184-202.

• Hendler J., Shadbolt N., Wendy Hall, Tim Berners-Lee, and Daniel Weitzner (2008):
  Web science: an interdisciplinary approach to understanding the web, Commun. ACM 51 (7), (July 2008), 60-69.

• Holmquist L. E. (2017): Intelligence on tap: artificial intelligence as a new design material, interactions 24, 4, pp. 28-33.

• Janlert L.E. and Stolterman E. (2008):
  Complex interaction,
  ACM Trans. Comput.-Hum. Interact. 17 (2), Article 8, 32 pages.

• Kölling, M. (1999):
  The Problem of Teaching Object-Oriented Programming, Part 1: Languages,
  Journal of Object-Oriented Programming 11 (8), pp. 8-15.

• Komssi M., Pichlis D., Raatikainen M., Kindstram K. , Jarvinen J. (2015): What are Hackathons for? IEEE Software 2015 (5), pp. 60-67.

• Kraemer K.L., Dedrick J., and Sharma P. (2009):
  One laptop per child: vision vs. reality,
  Commun. ACM 52 (6), pp. 66-73.

• Kromhout B. (2018): Containers Will Not Fix Your Broken Culture (and Other Hard Truths), ACM queue 16 (6).

• Lamers S. (1989):
  Programmers at Work: Interviews with 19 Programmers Who Shaped the Computer Industry,
  Tempus Books.

• Lampson B.W. (1984):
  Hints for Computer System Design,
  IEEE Software vol. 1 (1), pp. 11-28.

• Lawson B. (2005):
  How Designers Think, Architectural Press, 4th edition.

• Lewis J., Fowler M. (2014): Microservices: a definition of this new architectural term, https://martinfowler.com/articles/microservices.html

• Linden J. Ball, Balder Onarheim, Bo T. Christensen (2010):
  Design requirements, epistemic uncertainty and solution development strategies in software design,
  Design Studies 31 (6), pp. 567-589.

• MacCormack A., Carliss Y.B., and Rusnak J. (2012):
  Exploring the Duality Between Product and Organizational Architectures: A Test of the ‘Mirroring’ Hypothesis,
  Research Policy 41 (8), pp. 1309–1324.

• Matsudaira K. (2016): Bad Software Architecture is a People Problem, Communications of the ACM 59 (9), pp. 42-43.

• Melnik G., Jeffries R., Guest Editors’ Introduction: TDD–The Art of Fearless Programming, IEEE Software 24(3), pp. 24-30.

• Mens T. (2012): On the Complexity of Software Systems, Computer 45 (8), pp. 79-81.

• Montagne K. (2010): Tackling Architectural Complexity with Modeling, Communication of the ACM 53 (10), pp. 46-52.

• Marcus A. (2003): User-interface design and China: a great leap forward, interactions 10 (1), pp. 21-25.

• Murray, P. (2004). T The Saga of the Sydney Opera House, London: Spon Press.

• Myers B., Scott E. Hudson, & Randy Pausch. (2000):
  Past, present, and future of user interface software tools,
  ACM Trans. Comput.-Hum. Interact. 7 (1), pp. 3-28.

• Nason R. (2017):
  It’s Not Complicated: The Art and Science of Complexity in Business, Rotman-UTP Publishing, 2017).

• Ncube C., Oberndorf P. and Kark A.W. (2008):
  Opportunistic Software Systems Development: Making Systems from What’s Available,
  IEEE Software 25 (6), pp. 38-41.

• Neumann P.G. and McCullagh D. (1999):
  Inside Risks: Risks of Y2K,
  Commun. ACM 42 (6), p. 144.

• Nelson, H., Stolterman, E. (2012):
  The Design Way—Intentional Change in an Unpredictable World,
  MIT Press.

• Newman S. (2015):
  Building Microservices: Designing Fine-Grained Systems,
  O’Reilly Media; 1st edition.

• Nielsen, J. (1993):
  Iterative User Interface Design,
  IEEE Computer 26 (11), pp. 32-41

• Nielsen, J. (2010):
  iPad Usability: First Findings From User Testing,
  Jakob Nielsen’s Alertbox, April 26, 2010. http://www.useit.com/alertbox/ipad.html

• Norman D.A. (2008):
  Workarounds and hacks: the leading edge of innovation,
  interactions 15 (4), pp. 47-48.

• Norman, D.A. (2010):
  Technology first, needs last: the research-product gulf,
  interactions 17 (2), pp. 38-42.

• Nye, D. E. (2006):
  Technology matters: questions to live with,
  Cambridge, MA: MIT Press.

• Obrenovic Z. (2011):
  Design-Based Research: What We Learn When We Engage in Design of Interactive Systems, interactions 18 (5), pp. 56-59.

• Obrenovic Z. (2013): Software Sketchifying – Bringing Innovation into Software Development, IEEE Software 30 (3), pp. 80-86.

• Obrenovic Z. (2014): The Hawthorne Studies and Their Relevance to HCI Research, interactions 21 (6), pp. 46-51.

• Obrenovic Z. (2015): Design as a Political Activity: Borrowing From Classical Political Theories, interactions 22 (6), pp. 56-59.

• Obrenovic Z. (2017): Insights from the Past: The IEEE Software History Experiment, IEEE Software 34 (4), pp. 71-78.

• Penzenstadler B., Raturi A., Richardson D., and Tomlinson B. (2014):
  Safety, Security, Now Sustainability: The Nonfunctional Requirement for the 21st Century,
  IEEE Software 31 (3), pp. 40-47.

• Petroski H. (1994):
  The Evolution Of Useful Things,
  Vintage; Reprint edition

• Plauger P.J. (1992):
  The Falutin’ Index,
  Embedded Systems Programming, May 1992, pp. 88-92.

• Pescio C. (1997):
  When past solutions cause future problems [Year 2000 problem],
  IEEE Software 14 (5), pp. 19-21.

• Polanyi M. (1966):
  The Tacit Dimension,
  University of Chicago Press: Chicago.

• Reitman, W. (1965):
  Cognition and Thought.
  New York: Wiley.

• Richard H.S. (1995):
  Microsoft and vaporware,
  IEEE Micro Magazine 15 (2), pp. 6–7.

• Richardson E. (2011):
  What an Agile Architect Can Learn from a Hurricane Meteorologist,
  IEEE Software 28 (6), pp. 9-12

• Ries A. and Ries L. (2002):
  The 22 Immutable Laws of Branding,
  HarperBusiness; 1st edition.

• Ries E. (2011):
  The Lean Startup,
  Crown Business.

• Rising L. (2010): The Benefit of Patterns, IEEE Software 2010 (5), pp. 15-17.

• Rittel, H., and Webber M. (1973):
  Dilemmas in a General Theory of Planning,
  Policy Sciences 4, pp. 155–169.

• Rubinstein M.F. (1986):
  Tools for Thinking and Problem Solving,
  Prentice-Hall, Incorporated.

• Shneiderman B. (2007):
  Creativity support tools: accelerating discovery and innovation,
  Commun. ACM 50 (12), pp. 20-32.

• Schön, D. (1983):
  The Reflective Practitioner.
  Basic Books, New York.

• Schön, D. (1987):
  Educating the Reflective Practitioner,
  San Francisco: Jossey-Bass.

• Schön D. (1990): The Design Process, Howard V.A. (1990) Ed. Varieties of Thinking: Essays from Harvard’s Philosophy of Education Research Center. New York, Routledge, pp. 110-141.

• Schön D., Wiggins G. (1992): Kinds of seeing and their functions in designing, Design Studies 13 (2), pp. 135-156.

• Simon H. (1996): The Sciences of the Artificial,
  3rd ed. MIT Press.

• Herbert A. Simon (1973):
  The structure of ill structured problems,
  Artificial Intelligence 4 (3), pp. 181-201.

• Sommerville I., Cliff D., Calinescu R., Keen J., Kelly T., Kwiatkowska M., Mcdermid J., and Paige R. (2012):
  Large-scale complex IT systems,
  Commun. ACM 55 (7), pp. 71-77.

• Stolterman E. (2008):
  The Nature of Design Practice and Implications for Interaction Design Research,
  International Journal of Design (IJDesign) 2 (1).

• Stolterman, E., Mcatee, J., Royer, D. and Thandapani, Selvan (2008b):
  Designerly Tools,
  Undisciplined!, Design Research Society Conference 2008, Sheffield Hallam University, Sheffield, UK, 16-19 July 2008.

• Stolterman, E. & Pierce, J. (2012):
  Design tools in practice: Studying the designer-tool relationship in interaction design,
  DIS 2012, June 11-15, 2012, Newcastle, UK

• Weth, von der R. (1999):
  Design instinct?—the development of individual strategies,
  Design Studies 20 (5), pp. 453-463.

• Wilde E. and Glushko R.J. 2008:
  XML fever,
  Commun. ACM 51 (7), pp. 40-46.

• Williamson J.R. and Sundén D. (2016): Deep cover HCI: the ethics of covert research, interactions 23 (3), pp. 45-49.