Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Programming in the large and programming in the small
open-in-new
<h2 id="description">Description</h2> <p><a href="/facts/Fred_Brooks/1FNtgMgE">Fred Brooks</a> identifies that the way an individual program is created is different from how a programming systems product is created.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> The former likely does one relatively simple task well. It is probably coded by a single engineer, is complete in itself, and is ready to run on the system on which it was developed. The programming activity was probably fairly short-lived as simple tasks are quick and easy to complete. This is the endeavor that DeRemer and Kron describe as programming in the small. </p><p>Compare with the activities associated with a programming systems project, again as identified by Brooks. Such a project is typified by medium-sized or large industrial teams working on the project for many months to several years. The project is likely to be split up into several or hundreds of separate modules which individually are of a similar complexity to the individual programs described above. However, each module will define an <a href="/facts/Interface_(computer_science)/zdfp8unT">interface</a> to its surrounding modules. </p><p>Brooks describes how programming systems projects are typically run as formal projects that follow industry best practices and will comprise testing, documentation and ongoing maintenance activities as well as activities to ensure that the product is generalized to work in different scenarios including on systems other than the development systems on which it was created. </p> <h2 id="programming-in-the-large">Programming in the large</h2> <p>In <a href="/facts/Software_development/UUfsAaYY">software development</a>, programming in the large can involve <a href="/facts/Computer_programming/QmSsFnu0">programming</a> by larger groups of people or by smaller groups over longer time periods.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> Either of these conditions will result in large, and hence complicated, programs that can be challenging for maintainers to understand. </p><p>With programming in the large, coding managers place emphasis on partitioning work into <a href="/facts/Modularity_(programming)/sNoqKvRD">modules</a> with precisely-specified interactions. This requires careful planning and documentation. </p><p>With programming in the large, program changes can become difficult.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> If a change operates across module boundaries, the work of many people may need re-doing. Because of this, one goal of programming in the large involves setting up modules that will not need altering in the event of probable changes. This is achieved by designing modules so they have high <a href="/facts/Cohesion_(computer_science)/4hgqzcsf">cohesion</a> and loose <a href="/facts/Coupling_(computer_science)/QEeSaXF3">coupling</a>. </p><p>Programming in the large requires <a href="/facts/Management/8KMV9yMM">management</a> skills. The process of building abstractions aims not just to describe something that can work but also to direct the efforts of people who will make it work. </p><p>The concept was introduced by <i>Frank DeRemer</i> and <i>Hans Kron</i> in their 1975 paper "Programming-in-the-Large Versus Programming-in-the-Small", IEEE Trans. on Soft. Eng. 2(2). </p><p>In <a href="/facts/Computer_science/lN3pEyPz">computer science</a> terms, <i>programming in the large</i> can refer to programming code that represents the high-level <a href="/facts/State_transition_system/AABVmNzn">state transition</a> logic of a <a href="/facts/System/hmqQ4ASX">system</a>.[<i>dubious – discuss</i>] This logic encodes information such as when to wait for <a href="/facts/Message_(computer_science)/RYf3hD3J">messages</a>, when to send messages, when to compensate for failed non-<a href="/facts/ACID/XdHkYzHN">ACID</a> transactions, etc. </p><p>A language that was designed to explicitly support programming in the large is <a href="/facts/BPEL/HUmdnJEb">BPEL</a>. </p> <h2 id="programming-in-the-small">Programming in the small</h2> <p>In <a href="/facts/Software_development/UUfsAaYY">software development</a>, programming in the small describes the activity of writing a small program. Small programs are typified by being small in terms of their source code size, are easy to specify, quick to code and typically perform one task or a few very closely related tasks very well. </p><p>Programming in the small can involve programming by individuals or small groups over short time periods and may involve less formal practices (for instance less emphasis on documentation or testing), tools and programming languages (e.g. the selection of a <a href="/facts/Type_system/Tz0bAMS9">loosely typed</a> <a href="/facts/Scripting_language/8pF4ajBL">scripting language</a> in preference to a <a href="/facts/Type_system/Tz0bAMS9">strictly typed</a> programming language). Programming in the small can also describe an approach to building prototype software, or when <a href="/facts/Rapid_application_development/LX6JuaE4">rapid application development</a> is more important than stability or correctness. </p><p>In computer science terms, programming in the small deals with short-lived programmatic behavior, often executed as a single <a href="/facts/ACID/XdHkYzHN">ACID</a> transaction and which allows access to local logic and resources such as files, databases, etc.[<i>dubious – discuss</i>] </p> <h2 id="further-reading">Further reading</h2> <ul><li>DeRemer, Frank; Kron, Hans (1975). "Programming-in-the large versus programming-in-the-small". <i>Proceedings of the international conference on Reliable software</i>. <a href="/facts/Los_Angeles,_California/pyXpYEX9">Los Angeles, California</a>: <a href="/facts/Association_for_Computing_Machinery/abI2atlP">Association for Computing Machinery</a>. pp. 114–121. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1145%2F800027.808431">10.1145/800027.808431</a>.</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>DeRemer, Frank; Kron, Hans (April 1, 1975). "Programming-in-the large versus programming-in-the-small". Proceedings of the international conference on Reliable software -. Vol. 10. Association for Computing Machinery. pp. 114–121. doi:10.1145/800027.808431. S2CID 1022671 – via ACM Digital Library. <a href="https://doi.org/10.1145/800027.808431" target="_blank">https://doi.org/10.1145/800027.808431</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Brooks, Frederick P., Jr. (1982). "The Tar Pit", published in The Mythical Man-Month – Anniversary Edition. ISBN 0-201-83595-9 <a href="/wiki/ISBN_(identifier)" target="_blank">/wiki/ISBN_(identifier)</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Brooks, Frederick P., Jr. (1982). "The Tar Pit", published in The Mythical Man-Month – Anniversary Edition. ISBN 0-201-83595-9 <a href="/wiki/ISBN_(identifier)" target="_blank">/wiki/ISBN_(identifier)</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Brooks, Frederick P., Jr. (1982). "The Tar Pit", published in The Mythical Man-Month – Anniversary Edition. ISBN 0-201-83595-9 <a href="/wiki/ISBN_(identifier)" target="_blank">/wiki/ISBN_(identifier)</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> </ol>