software success
TRANSCRIPT
King Saud University College of Computer and Information SciencesInformation Systems / Graduate StudiesCourse # IS 524 – Advanced Systems & Design
The Dimensions of Software Engineering Success
Paul Ralph and Paul Kelly , Lancaster University , Lancaster, UK , 2014 Copyright 2010 ACM
Outlines
• Background• Methodology• Eleven themes • Theoretical Framework• Summary and findings
First Questions• What does it mean for a new software engineering (SE)
technology or practice to be good? • what does success mean in a software engineering
context? • What are its dimensions? • How can we measure it?
• Research Question: What are the primary dimensions of software engineering
success?
Background
• Software Engineering Success (SES)• A single variable is needed.• The exact nature of this variable remains
unclear• Measuring success is a major topic of interest
in the project management literature.
Project Triangle
scope
budget schedule
Background
Background• Project success may be distinct from product
success.• Specific success criteria vary across industries and
project types . • Stakeholder Theory.• Developers often view success differently from
Project Managers. • “Different stakeholders involved in the software
development may attribute success to different indicators” .
Background• The success of SE projects is complicated by the
production of artifacts• The ISO/IEC 9126 standard six dimensions :
functionality, reliability, usability, efficiency, maintainability and portability.
• limits of ISO/IEC 9126 standard• Academics and practitioners appear to agree
that...
Background
METHODOLOGY
1) Sampling and Data Collection2) Analysis
Sampling and Data Collection
• expanded the population from developers to design professionals
Analysis• The interview transcripts were analyzed using
semi-automated content analysis in Leximancer. • The analysis begins with unsupervised semantic
mapping
ELEVEN THEMES
• Map of the Themes• Map of the concepts
1.Project 2.Client
6.Emotion
3.Time
10. Parts
4.Design 5.Work
7.Feedback 8.Designer/Developer
9.Analysis
11.Winning
Map of the Themes
Map of the concepts
Project• “The jobs basically come in project form”• Project is the central concept in the map
Client•The explicit client or customer often central
to their conception of success•Addressing the client’s needs is powerful
determinant of success
Time•Important aspect of success
• The Time theme includes : plans, schedules , deadlines, cost, and contracts
•“It is important to stick to the contract”
Design•“Design is a funny word. Some people think design means how it looks. But of course, if you dig deeper, it's really how it works.”
•The success is related to good design
Work• Having motivating to work is an important
aspect of personal success• High-performing team of colleagues
considered highly desirable
Emotion•Feeling completely satisfied and happy •The emotion mediates the relationship
between clients and project results
Feedback• Stakeholder feedback is a primary for
understanding success• Feedback is associated with clients more
often than other stakeholders• Feedback may be: formal or informal, direct or indirect
Designer-Developer•Map suggests a close relationship between
designer or developer. •Designers as being central to success
Analysis• Much of the work involves analysis• Analysis and writing the test cases•The good analysis is critical to success
Parts•The artifacts are composed of parts or components•Properties parts is crucial for success
Winning•“We have to be competitive marketplace”•Success depends on financial success
SPECIAL ABOUT SE
Theoretical FrameworkDimensions of SW success and framework
SWS={Net impact, Stakeholder, Time}
Demarcation between Antecedent and Dimensions of success
More sophisticated view of success
Summary & findings • Framework for understanding SW engineering success• SES is modeled as a Multidimensional variables• Integrates previous research • The framework is supported by an extensive interview study
• Design work is largely organized into projects• Designers are often fixated on an explicit client• Designers appear more concerned with being on time than adhering to budgets or
contracts• Designers desire interesting work and capable colleagues• Designers are more concerned with clients’ emotional with satisfying explicit
requirements• Designers perceive analysis and design as closely related• Designers recognize that contracts, plans, schedules and budgets are often unreasonable
or misguided
Thank you