Incomputing,source code, or simplycode orsource, ishuman readableplain text that can eventually result in controlling the behavior of acomputer. In order to control a computer, it must be processed by acomputer program – either executed directly via aninterpreter ortranslated into a more computer-consumable form such as via acompiler. Sometimes, code is compiled directly tomachine code so that it can be run in the native language of the computer without further processing. But, many modern environments involve compiling to anintermediate representation such asbytecode that can either run via an interpreter or be compiled on-demand to machine code viajust-in-time compilation.
The first programmable computers, which appeared at the end of the 1940s,[2] were programmed inmachine language (simple instructions that could be directly executed by the processor). Machine language was difficult to debug and was notportable between different computer systems.[3] Initially, hardware resources were scarce and expensive, whilehuman resources were cheaper.[4] As programs grew more complex,programmer productivity became a bottleneck. This led to the introduction ofhigh-level programming languages such asFortran in the mid-1950s. These languagesabstracted away the details of the hardware,and were designed to express algorithms that could be understood more easily by humans.[5][6] As instructions distinct from the underlyingcomputer hardware, software is therefore relatively recent, dating to these early high-levelprogramming languages such asFortran,Lisp, andCobol.[6] The invention of high-level programming languages was simultaneous with thecompilers needed to translate the source code automatically into machine code that can be directly executed on thecomputer hardware.[7]
Source code is the form of code that is modified directly by humans, typically in a high-level programming language.Object code can be directly executed by the machine and is generated automatically from the source code, often via an intermediate step,assembly language. While object code will only work on a specific platform, source code can be ported to a different machine and recompiled there. For the same source code, object code can vary significantly—not only based on the machine for which it is compiled, but also based on performance optimization from the compiler.[8][9]
Most programs do not contain all the resources needed to run them and rely on externallibraries. Part of the compiler's function is to link these files in such a way that the program can be executed by the hardware.[10]
A more complexJava source code example. Written inobject-oriented programming style, it demonstratesboilerplate code. With prologue comments indicated in red, inline comments indicated in green, and program statements indicated in blue.
Software developers often useconfiguration management to track changes to source code files (version control). The configuration management system also keeps track of which object code file corresponds to which version of the source code file.[11]
The number ofsource lines of code (SLOC) is often used as a metric when evaluating the productivity of computer programmers, the economic value of a code base,effort estimation for projects in development, and the ongoing cost ofsoftware maintenance after release.[12]
Source code is also used to communicatealgorithms between parties, e.g.,code snippets online or in books.[13]
Computerprogrammers can find it helpful to review extant source code to learn about programming techniques.[13] The sharing of source code between developers is often cited as a contributing factor to the maturing of their programming skills.[13] Some consider source code an expressiveartistic medium.[14]
Source code often containscomments—blocks of text marked for the compiler to ignore. This content is not part of the program logic, but is instead intended to help readers understand the program.[15]
Companies often keep the source code confidential in order to hide algorithms considered atrade secret. Proprietary, secret source code and algorithms are widely used for sensitive government applications such ascriminal justice, which results inblack box behavior with a lack oftransparency into the algorithm's methodology. The result is avoidance of public scrutiny of issues such as bias.[16]
Access to the source code (not just theobject code) is essential to modifying it.[17] Understanding extant code is necessary to understand how it works[17] and before modifying it.[18] The rate of understanding depends both on the code base as well as the skill of the programmer.[19] Experienced programmers have an easier time understanding what the code does at a high level.[20]Software visualization is sometimes used to speed up this process.[21]
Many software programmers use anintegrated development environment (IDE) to improve their productivity. IDEs typically have several features built in, including asource-code editor that can alert the programmer to common errors.[22] Modification often includescode refactoring (improving structure without changing function) and restructuring (improving structure and function simultaneously).[23] Nearly every change to code introduces new bugs or unexpectedripple effects, which require another round of fixes.[18]
Code reviews by other developers are often used to scrutinize new code added to a project.[24] The purpose of this phase is often to verify that the code meets style andmaintainability standards and that it is a correct implementation of thesoftware design.[25] According to some estimates, code review dramatically reduce the number of bugs persisting aftersoftware testing is complete.[24] Along with software testing that works by executing the code,static program analysis uses automated tools to detect problems with the source code. Many IDEs support code analysis tools, which might provide metrics on the clarity and maintainability of the code.[26]Debuggers are tools that often enable programmers to step through execution while keeping track of which source code corresponds to each change of state.[27]
Source code files in a high-level programming language must go through a stage of preprocessing intomachine code before the instructions can be carried out.[7] After being compiled, the program can be saved as anobject file and theloader (part of the operating system) can take this saved file andexecute it as aprocess on the computer hardware.[10] Some programming languages use aninterpreter instead of a compiler. An interpreter converts the program into machine code atrun time, which makes them 10 to 100 times slower than compiled programming languages.[22][28]
Another reason many programs are distributed in source code form, instead of as executablebinary files, is that (often) a single source code file can be written once and will run on a variety of different end-user machines (each with their own localized compiler or interpreter), unlike an executable code file which generally only works on nearly-identical machines. Source code was used this way to distribute the Unix operating system early in thehistory of Unix, and later to allow programs written inscripting languages (in particular theJavaScriptclient-side scripting language) to run on a wide variety of machines.
For this goal,minified,obfuscated, ordecompiled source code files (all of which eliminate the comments in the original code) are generally just as portable as the original source code files (which nearly always include commments), even though they are far less useful for modification, and therefore don't meet the definition of source code in theGNU General Public License, version 2 (GPL2).
Software quality is an overarching term that can refer to a code's correct and efficient behavior, its reusability andportability, or the ease of modification.[29] It is usually more cost-effective to build quality into a product from the start rather than try to add it later in a development process.[30] Higher quality code reduces lifetime cost to both suppliers and customers as via higher reliability andmaintainability.[31][32]
Maintainability is the quality of software enabling it to be easily modified without breaking extant functions.[33] Following coding conventions such as using clear function and variable names that correspond to their purpose makes maintenance easier.[34] Use ofconditional loop statements only if the code could execute more than once, and eliminating code that will never execute can also increase understandability.[35] Many software development organizations neglect maintainability during the development phase, even though it will increase long-term costs.[32]Technical debt is incurred when programmers, often out of laziness or urgency to meet a deadline, choose quick and dirty solutions rather than build maintainability into their code.[36] A common cause is underestimates insoftware development effort estimation, leading to insufficient resources allocated to development.[37] A challenge with maintainability is that manysoftware engineering courses do not emphasize it.[38] Development engineers who know that they will not be responsible for maintaining the software do not have an incentive to build in maintainability.[18]
The situation varies worldwide, but in the United States before 1974, software and its source code was notcopyrightable and therefore alwayspublic domain software.[39] In 1974, the US Commission on New Technological Uses of Copyrighted Works (CONTU) decided that "computer programs, to the extent that they embody an author's original creation, are proper subject matter of copyright".[40][41]
Proprietary software is rarely distributed as source code.[42] Although the termopen-source software literally refers topublic access to the source code,[43] open-source software has additional requirements: free redistribution, permission to modify the source code and release derivative works under the same license, and nondiscrimination between different uses—including commercial use.[44][45] The freereusability of open-source software can speed up development.[46]
Campbell-Kelly, Martin; Garcia-Swartz, Daniel D. (2015).From Mainframes to Smartphones: A History of the International Computer Industry. Harvard University Press.ISBN978-0-674-28655-9.
Galin, Daniel (2018).Software Quality: Concepts and Practice. John Wiley & Sons.ISBN978-1-119-13449-7.
Haber, Morey J.; Hibbert, Brad (2018).Asset Attack Vectors: Building Effective Vulnerability Management Strategies to Protect Organizations. Apress.ISBN978-1-4842-3627-7.
Kaczmarek, Stefan; Lees, Brad; Bennett, Gary; Fisher, Mitch (2018).Objective-C for Absolute Beginners: iPhone, iPad and Mac Programming Made Easy. Apress.ISBN978-1-4842-3428-0.
O'Regan, Gerard (2022).Concise Guide to Software Engineering: From Fundamentals to Application Methods. Springer Nature.ISBN978-3-031-07816-3.
Sen, Ravi; Subramaniam, Chandrasekar; Nelson, Matthew L. (2008). "Determinants of the Choice of Open Source Software License".Journal of Management Information Systems.25 (3). Informa UK Limited:207–240.doi:10.2753/mis0742-1222250306.ISSN0742-1222.
Sebesta, Robert W. (2012).Concepts of Programming Languages (10 ed.). Addison-Wesley.ISBN978-0-13-139531-2.
Tracy, Kim W. (2021).Software: A Technical History. Morgan & Claypool Publishers.ISBN978-1-4503-8724-8.
Tripathy, Priyadarshi; Naik, Kshirasagar (2014).Software Evolution and Maintenance: A Practitioner's Approach. John Wiley & Sons.ISBN978-0-470-60341-3.
Varga, Ervin (2018).Unraveling Software Maintenance and Evolution: Thinking Outside the Box. Springer.ISBN978-3-319-71303-8.
