This link has been bookmarked by 9 people . It was first bookmarked on 07 Feb 2007, by john doe.
-
24 May 07
-
30 Jul 05
Nick GallInteresting analysis of the "software engineering model" introduced at the NATO Conference in 1968. Discusses game theory approach to software development and Donald Schon's reflective practioner.
via_delicious_20101217 ImportedFurl20071006 General programming pinboardimport20141106
-
When "software engineering" was introduced in 1968 as a model for the field of software development, it was introduced as a provocation rather than as a model deduced from experience [Naur-Randell]. This paper reconsidered the model in the light of four decades of experience, and found the model lacking in four respects: * The model does not intrinsically generate topics known to be important to project success, topics such as talent and skill, team cohesion and interpersonal communication [Boehm]. * The model fails to explain the historical record of successful and failing projects [Cockburn 2003a]. In particular, it fails to explain the success of so many low-ceremony, even sloppy-looking projects, and the declared preference of experienced, successful developers with those processes. * After 35 years of use, different people still interpret the term in very different ways, leading to conflicting recommendations for behavior on projects. * The term, and the model, do not lead practitioners on live projects to derive effective advice as to how to proceed. This paper introduced a new model: Software development is a series of resource-limited, goal-directed, cooperative games of invention and communication. The primary goal of each game is the production and deployment of a software system. The residue of the game is a set of markers to assist the players of the next game. People use markers and props to remind, inspire and inform each other in getting to the next move in the game. The successor game is an alteration of the system or the creation of a neighboring system, and so each game has as a secondary goal to create an advantageous position for the next game. The primary and secondary goals compete for resources in a resource-limited situation. This model intrinsically names issues known to be important to project success: cooperation, communication, cost-of-, rate-of-, and sufficiency-in-communication. It quickly h
-
-
05 Jan 05
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.