The dimensions of software engineering success
- 31 May 2014
- conference paper
- conference paper
- Published by Association for Computing Machinery (ACM)
Abstract
Background: Software engineering research and practice are hampered by the lack of a well-understood, top-level dependent variable. Recent initiatives on General Theory of Software Engineering suggest a multifaceted variable – Software Engineering Success; however, its exact dimensions are unknown. Aim: This paper seeks to investigate the dimensions (not causes) of software engineering success. Method: An interdisciplinary sample of 191 design professionals (68 in the software industry) were interviewed concerning their perceptions of success. Non- software designers (e.g. architects) were included to increase the breadth of ideas and facilitate comparative analysis. Transcripts were subjected to a supervised, semi-automated semantic content analysis, including a software developer vs. other professionals semantic comparison. Results: Participants view their work as time-constrained projects with explicit clients and many other stakeholders. Success depends on stakeholder impacts – financial, social, physical and emotional – and is understood through feedback. Concern with meeting explicit requirements is peculiar to software engineering and design is not equated with aesthetics in many other fields. Conclusion: Software engineering success is a complex multifaceted variable, which cannot sufficiently be explained by traditional dimensions including user satisfaction, profitability or meeting requirements, budgets and schedules. A proto-theory of success is proposed, which models success as the net impact on a particular stakeholder at a particular time. Stakeholder impacts are driven by project efficiency, artifact quality and market performance. In this view, success is not additive, i.e., ‘low’ success for clients does not average with ‘high’ success for developers to make ‘moderate’ success overall; rather, a project may be simultaneously successful and unsuccessful from different perspectivesKeywords
This publication has 32 references indexed in Scilit:
- Report on the first SEMAT workshop on general theory of software engineering (GTSE 2012)ACM SIGSOFT Software Engineering Notes, 2013
- The project workplace for organizational learning developmentInternational Journal of Project Management, 2011
- Stakeholder: Essentially Contested or Just Confused?Journal of Business Ethics, 2011
- What’s up with software metrics? – A preliminary mapping studyJournal of Systems and Software, 2010
- Measuring information systems success: models, dimensions, measures, and interrelationshipsEuropean Journal of Information Systems, 2008
- Natural myside bias is independent of cognitive abilityThinking & Reasoning, 2007
- What do software practitioners really think about project success: an exploratory studyJournal of Systems and Software, 2005
- Exploring the relationships between design measures and software quality in object-oriented systemsJournal of Systems and Software, 2000
- Software developer perceptions about software project failure: a case studyJournal of Systems and Software, 1999
- A framework for the measurement of software qualityACM SIGMETRICS Performance Evaluation Review, 1978