Software Process Improvement: Blueprints versus Recipes

Authors:
Ivan Aaen
Affiliations:
-
Venue:
IEEE Software
Year:
2003

Citing 5
Cited 10

Software processes are software too

ICSE '87 Proceedings of the 9th international conference on Software Engineering
Software processes are software too, revisited: an invited talk on the most influential paper of ICSE 9

ICSE '97 Proceedings of the 19th international conference on Software engineering
Introduction to the team software process

Introduction to the team software process
Extreme programming explained: embrace change

Extreme programming explained: embrace change
Computers in Context: The Philosophy and Practice of Systems Design

Computers in Context: The Philosophy and Practice of Systems Design

Deeper questions: the metaproblem of large organizations developing complex systems and the limits of process

ACM SIGSOFT Software Engineering Notes
Practical knowledge and its importance for software product quality

Information and Software Technology
Interpretation, interaction and reality construction in software engineering: An explanatory model

Information and Software Technology
An approach for concurrent evaluation of technical and social aspects of software development methodologies

Information and Software Technology
How to steer an embedded software project: tactics for selecting the software process model

Information and Software Technology
Social networks in software process improvement

Journal of Software Maintenance and Evolution: Research and Practice
THINKING ISSUES: A 'potted guide' to quality assurance for computing capstone projects

ACM Inroads
Tool support for disseminating and improving development practices

Software Quality Control
Understanding the importance of roles in architecture-related process improvement: a case study

PROFES'05 Proceedings of the 6th international conference on Product Focused Software Process Improvement
From chaos to the systematic harmonization of multiple reference models: A harmonization framework applied in two case studies

Journal of Systems and Software

Quantified Score

Hi-index	0.01

Visualization

Abstract

Viewing software processes as blueprints emphasizes that design is separate from use, and thus that software process designers and users are independent. In the approach presented here, software processes are viewed as recipes; developers individually and collectively design their own software processes through facilitation, reflection, and improvisation.