You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 3.238.0.0/16 has been blocked by ‪ST47‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider. To prevent abuse, web hosts may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a web host's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and they should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 05:34, 21 January 2026. Your current IP address is 3.238.27.177.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
This IP address range has been globally blocked.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

This block affects editing on all Wikimedia wikis.
The IP address or range 3.238.0.0/16 has been globally blocked by ‪Jon Kolbert‬ for the following reason(s):

Open proxy/Webhost: See the help page if you are affected

This block will expire on 05:35, 21 February 2029. Your current IP address is 3.238.27.177.

Even while globally blocked, you will usually still be able to edit pages on Meta-Wiki.

If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

Other useful links: Global blocks · Help:I have been blocked

You can view and copy the source of this page:

((multiple issues|((technical|date=May 2018))
((Refimprove|date=February 2010))))

In [[software engineering]], '''programming in the large''' and '''programming in the small''' refer to two different aspects of writing software. Programming in the large means designing a larger system as a composition of smaller parts, and programming in the small means creating those smaller parts by writing lines of code in a programming language.
The terms were coined by [[Frank DeRemer]] and [[Hans Kron]] in their 1975 paper "Programming-in-the-large versus programming-in-the-small",<ref>((Cite book|chapter-url=https://doi.org/10.1145/800027.808431|chapter=Programming-in-the large versus programming-in-the-small|first1=Frank|last1=DeRemer|first2=Hans|last2=Kron|title=Proceedings of the international conference on Reliable software -|date=April 1, 1975|volume=10|issue=6|publisher=Association for Computing Machinery|pages=114–121|via=ACM Digital Library|doi=10.1145/800027.808431|s2cid=1022671))</ref> in which they argue that the two are essentially different activities, and that typical programming languages, and the practice of [[structured programming]], provide good support for the latter, but not for the former.

This may be compared to the later [[Ousterhout's dichotomy]], which distinguishes between [[system programming]] languages (for components) and [[scripting language]]s (for [[glue code]], connecting components).

==Description==
[[Fred Brooks]] identifies that the way an individual program is created is different from how a programming systems product is created.<ref name="Brooks" /> 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.

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 [[Interface (computer science)|interface]] to its surrounding modules.

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.

== Programming in the large ==

In [[software development]], programming in the large can involve [[computer programming|programming]] by larger groups of people or by smaller groups over longer time periods.<ref name="Brooks">Brooks, Frederick P., Jr. (1982).  "The Tar Pit", published in ''The Mythical Man-Month – Anniversary Edition''. ((ISBN|0-201-83595-9))</ref> Either of these conditions will result in large, and hence complicated, programs that can be challenging for maintainers to understand.

With programming in the large, coding managers place emphasis on partitioning work into [[Modularity (programming)|modules]] with precisely-specified interactions. This requires careful planning and careful documentation.

With programming in the large, program changes can become difficult.<ref name="Brooks" /> 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 [[Cohesion (computer science)|cohesion]] and loose [[Coupling (computer science)|coupling]].

Programming in the large requires abstraction-creating skills.((Citation needed|date=February 2009)) Until a module becomes implemented it remains an [[abstraction (computer science)|abstraction]]. Taken together, the abstractions should create an [[software architecture|architecture]] unlikely to need change.((Citation needed|date=December 2008)) They should define interactions that have precision and demonstrable correctness.

Programming in the large requires [[management]] 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.

The concept was introduced by ''Frank DeRemer'' and ''Hans Kron'' in their 1975 paper "Programming-in-the-Large Versus Programming-in-the-Small", IEEE Trans. on Soft. Eng. 2(2).

In [[computer science]] terms, ''programming in the large'' can refer to programming code that represents the high-level [[state transition system|state transition]] logic of a [[system]].((Dubious|date=December 2008)) This logic encodes information such as when to wait for [[message (computer science)|messages]], when to send messages, when to compensate for failed non-[[ACID]] transactions, etc.

A language that was designed to explicitly support programming in the large is [[BPEL]].

== Programming in the small ==

In [[software development]], 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.

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 [[Type system|loosely typed]] [[scripting language]] in preference to a [[Type system|strictly typed]] programming language). Programming in the small can also describe an approach to making a prototype software or where [[rapid application development]] is more important than stability or correctness.

In computer science terms, programming in the small deals with short-lived programmatic behavior, often executed as a single [[ACID]] transaction and which allows access to local logic and resources such as files, databases, etc.((Dubious|date=December 2008))

== References ==
((Reflist))

== Further reading ==
* ((cite conference
  | first = Frank
  | last = DeRemer
  |author2=Kron, Hans
  | title = Programming-in-the large versus programming-in-the-small
  | book-title = Proceedings of the international conference on Reliable software
  | pages = 114–121
  | publisher = [[Association for Computing Machinery]]
  | year = 1975
  | location = [[Los Angeles, California]]
  | doi = 10.1145/800027.808431
  | doi-access = free
  ))

((Programming paradigms navbox))

[[Category:Programming paradigms]]
[[Category:Software engineering folklore]]

Pages transcluded onto the current version of this page (help):

Programming in the large and programming in the small (edit)
Template:Ambox (view source) (template editor protected)
Template:Catalog lookup link (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Citation needed (view source) (protected)
Template:Cite book (view source) (protected)
Template:Cite conference (view source) (protected)
Template:Delink (view source) (protected)
Template:Dubious (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Fix (view source) (protected)
Template:Fix/category (view source) (protected)
Template:Hlist/styles.css (view source) (protected)
Template:ISBN (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Multiple issues (view source) (template editor protected)
Template:Multiple issues/styles.css (view source) (template editor protected)
Template:Navbox (view source) (template editor protected)
Template:Programming paradigms navbox (edit)
Template:Refimprove (view source) (template editor protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:Technical (view source) (template editor protected)
Template:Yesno (view source) (protected)
Template:Yesno-no (view source) (template editor protected)
Template:Yesno-yes (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Catalog lookup link (view source) (template editor protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Check isxn (view source) (template editor protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Delink (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Navbar (view source) (protected)
Module:Navbar/configuration (view source) (protected)
Module:Navbar/styles.css (view source) (protected)
Module:Navbox (view source) (template editor protected)
Module:Navbox/configuration (view source) (template editor protected)
Module:Navbox/styles.css (view source) (template editor protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to Programming in the large and programming in the small.

Retrieved from "https://en.wikipedia.org/wiki/Programming_in_the_large_and_programming_in_the_small"