software factory Concepts

Computer: A History of the Information Machine

by Martin Campbell-Kelly and Nathan Ensmenger · 29 Jul 2013 · 528pp · 146,459 words

were inherently unmanageable and recommended, instead, that software developers adopt methods and techniques borrowed from traditional manufacturing. The ultimate goal would be a kind of “software factory” complete with interchangeable parts (or “software components”), mechanized production, and a largely deskilled and routinized workforce. The tools used to achieve this goal included structured

Unit X: How the Pentagon and Silicon Valley Are Transforming the Future of War

by Raj M. Shah and Christopher Kirchhoff · 8 Jul 2024 · 272pp · 103,638 words

start writing software the way startups do. Going significantly further, Wert and his team sat down with Enrique and decided to create an air force “software factory,” based in Boston, that would operate like a tech startup, with a mix of airmen and civilian programmers using modern software development tools and the

…

charge of managing the office space where DIU was located. Luckily, DIU prevailed in maintaining the policy after some crafty maneuvering. create an air force “software factory”: The Defense Innovation Board showed the way on how to modernize DoD software practices in its report, “Software Is Never Done: Refactoring the Acquisition Code

The Computer Boys Take Over: Computers, Programmers, and the Politics of Technical Expertise

by Nathan L. Ensmenger · 31 Jul 2010 · 429pp · 114,726 words

“different,” and “could not work and would not prosper” under the rigid structures of engineering management.32 They organized SDC along the lines of a “software factory” that relied less on skilled workers, and more on centralized planning and control. The principles behind this approach were essentially those that had proven so

…

be neatly broken down into simple, modular components that could be easily understood by any programmer with the appropriate training and experience. Programmers in the software factory were mere machine operators; they had to be trained, but only in the basic mechanisms of implementing someone else’s design. In the SDC hierarchy

…

the SDC approach did not attempt to solve its programmer personnel problem by reducing the number of programmers it required. On the contrary, the SDC software factory strategy (or as detractors dismissively referred to it, the “Mongolian Horde” approach to software development) probably demanded more programmers than was otherwise necessary. But the

…

notion that complex software systems could be readily broken down into simpler modules that even relatively novice programmers—properly managed—could adequately develop. The SDC software factory was a deliberate attempt to industrialize the programming process, to impose on it the lessons learned from traditional industrial manufacturing. Like all industrial systems, the

…

software factory required not only new organizational forms and production technologies (in this case, automated development and testing utilities) but also new forms of workers. As with

…

production of computer programs necessitated the mass production of programmers. As will be discussed further below, it is questionable whether the SDC vision of the software factory was ever truly realized—by SDC itself or any of its many imitators. But for the time being it is enough to say that the

…

. By identifying the minimum level of aptitude required to be a competent programmer, SDC could reduce its dependence on individual programmers. It could construct a software factory out of the interchangeable parts produced by the impersonal and industrial processes of its aptitude test regimes. It is this last consequence of aptitude testing

…

a few of the most prominent development methodologies that emerged in response to the declaration in 1968 of the software crisis: the hierarchical system, or software factory; the superprogrammer, or chief programmer team (CPT) approach; and the adaptive programmer team (or “egoless” programming) model. The hierarchical systems approach—originally developed for large

…

and expert administrator. Programming aptitude could not be abstracted from its embodiment in particular individuals; skilled programmers were anything but replaceable components of an automated software factory. In the elite surgical team model, the contributions of talented professionals far outweighed those provided by traditional management techniques or development methodologies. Besides endowing computer

…

the software factory. One guidebook from 1969 for managers captured the essence of this adversarial approach to programmer management by describing the successful computer manager as the “one

…

, any proposed solution to the software crisis, whether it is technical, managerial, professional, or otherwise, has implications for individuals and organizations. The appeal of the software factory model might appear obvious to corporate managers; for skilled computer professionals, the idea of becoming a factory worker is understandably less desirable. Whether or not

…

, 202–203, 209, 211, 213–214, 232–233 as professionalization strategy, 208 Software engineering, 196–198, 209, 221 as ideology, 219–220 Software evolution, 226 Software factory, 60–61, 63, 232 Special Interest Group on Computing Personnel Research. See SIGCPR Structured programming, 209 and GOTO Statement debate, 109 Superprogrammer, 206, 208, 211

The Second Machine Age: Work, Progress, and Prosperity in a Time of Brilliant Technologies

by Erik Brynjolfsson and Andrew McAfee · 20 Jan 2014 · 339pp · 88,732 words

may not affect all inputs equally, but rather may be ‘biased’ toward some and against others. In particular, in recent years, technologies like payroll processing software, factory automation, computer-controlled machines, automated inventory control, and word processing have been deployed for routine work, substituting for workers in clerical tasks, on the factory

Tools for Thought: The History and Future of Mind-Expanding Technology

by Howard Rheingold · 14 May 2000 · 352pp · 120,202 words

about a special kind of very powerful and portable personal computer that he later came to call "the Dynabook." Everybody, from the programmers in the "software factory" who designed the software operating system and programming tools, to the hardware engineers of the Alto prototype machines, to the Ethernet local-area-network team

DarkMarket: Cyberthieves, Cybercops and You

by Misha Glenny · 3 Oct 2011 · 274pp · 85,557 words

challenges posed to the region’s nascent computer engineers were so considerable that they developed an exceptional ingenuity in overcoming glitches and bugs. Furthermore, the software factories that the East Europeans built in the 1980s could not compete with Silicon Valley during the 1990s after the fall of the Berlin Wall – there

Kanban: Successful Evolutionary Change for Your Technology Business

by David J. Anderson · 6 Apr 2010 · 318pp · 78,451 words

be used to automate away repetitive coding tasks; again, reducing the defect-insertion potential of entering code. The use of software factories also reduces the demands on code inspections, as factory code doesn’t need to be re-inspected. It has a known quality. Some of these

…

quality, limiting WIP, delivering often, and balancing demand against throughput, they will have a reliable, trustworthy, software development capability: an engine for making software! A “software factory” if you will. Once this capability is in place, it would behoove the business to make optimal use out of it. To do this requires

CIOs at Work

by Ed Yourdon · 19 Jul 2011 · 525pp · 142,027 words

the way, that’s what the Chinese are going into. You see, the big problem we have is when you look at the Silicon Valley software factories, half of them are not Americans. The class I’m going to be teaching, half of my class will not be Americans. Yourdon: I think

The C++ Programming Language

by Bjarne Stroustrup · 2 Jan 1986 · 923pp · 516,602 words

extra investment in tools (for design, programming, and project management) and education (of designers, programmers, and managers). It is a sketch of a kind of software factory. Curiously enough, it differs only in scale from the practices of the best individual programmers, who over the years build up a stock of techniques

From Airline Reservations to Sonic the Hedgehog: A History of the Software Industry

by Martin Campbell-Kelly · 15 Jan 2003

. As quoted in Baum, The System Builders, p. 31. 36. For an account of SDC’s factory style of software production, see Cusumano, Japan’s Software Factories, pp. 119–160. 37. Baum, The System Builders, p. 47. 38. Ibid., p. 51. 39. Herbert D. Benington, “Production of Large Computer Programs,” Annals of