Programming-in-the large versus programming-in-the-small

Abstract

We distinguish the activity of writing large programs from that of writing small ones. By large programs we mean systems consisting of many small programs (modules), possibly written by different people. We need languages for programming-in-the-small, i.e. languages not unlike the common programming languages of today, for writing modules. We also need a “module interconnection language” for knitting those modules together into an integrated whole and for providing an overview that formally records the intent of the programmer(s) and that can be checked for consistency by a compiler. We explore the software reliability aspects of such an interconnection language. Emphasis is placed on facilities for information hiding and for defining layers of virtual machines.

Collective agility, paradox and organizational improvisation: the development of a particle physics grid

“…But most studies of agile development still focus on micro‐behaviour and related processes in designing and delivering software, and less attention is paid to organizational cultures, institutional conditions and environmental constraints (Abrahamsson et al ., 2009). This is surprising since, from the days of Brooks' (1979) classic ‘The Mythical Man Month’ and DeRemer and Kron's (1975) concept of ‘programming in the large’, it has been acknowledged that systems are developed within an organizational environment, which is as significant in shaping the character of the project and its outcomes as any particular practices. There is thus a need to develop a better understanding of the implementation of agility at the organizational level (Abrahamsson et al ., 2009) acknowledging explicit linkages to institutional and cultural settings.…”

Choreography-based Consolidation of Multi-instance BPEL Processes

“…BPEL is a workflow language designed for enabling programming in the large (DeRemer and Kron, 1976) based on Web services. BPEL itself does not offer a capturing of multiple processes interacting with each other (Decker et al, 2009).…”

Generating Adapters for Concurrent Component Protocol Synchronisation

“…A general overview over ADLs is given in (Jazayeri eta!., 2000). The separation of architecture and interface definitions goes back perhaps to the mid seventies with work on so-called Module Interconnection Languages (MILs), see e.g., (DeRemer and Kron, 1976).…”