software success

24
King Saud University College of Computer and Information Sciences Information Systems / Graduate Studies Course # IS 524 – Advanced Systems & Design The Dimensions of Software Engineering Success Paul Ralph and Paul Kelly , Lancaster University , Lancaster, UK , 2014 Copyright 2010 ACM

Upload: alanoudsalqoufi

Post on 09-Jan-2017

54 views

Category:

Software


0 download

TRANSCRIPT

Page 1: SoftWare Success

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

Page 2: SoftWare Success

Outlines

• Background• Methodology• Eleven themes • Theoretical Framework• Summary and findings

Page 3: SoftWare Success

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?

Page 4: SoftWare 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

Page 5: SoftWare Success

Background

Page 6: SoftWare Success

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” .

Page 7: SoftWare Success

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...

Page 8: SoftWare Success

Background

Page 9: SoftWare Success

METHODOLOGY

1) Sampling and Data Collection2) Analysis

Page 10: SoftWare Success

Sampling and Data Collection

• expanded the population from developers to design professionals

Page 11: SoftWare Success

Analysis• The interview transcripts were analyzed using

semi-automated content analysis in Leximancer. • The analysis begins with unsupervised semantic

mapping

Page 12: SoftWare Success

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

Page 13: SoftWare Success

Map of the Themes

Page 14: SoftWare Success

Map of the concepts

Page 15: SoftWare Success

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

Page 16: SoftWare 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

Page 17: SoftWare Success

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

Page 18: SoftWare Success

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

Page 19: SoftWare 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

Page 20: SoftWare Success

SPECIAL ABOUT SE

Page 21: SoftWare Success

Theoretical FrameworkDimensions of SW success and framework

SWS={Net impact, Stakeholder, Time}

Page 22: SoftWare Success

Demarcation between Antecedent and Dimensions of success

More sophisticated view of success

Page 23: SoftWare 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

Page 24: SoftWare Success

Thank you