Hubbry Logo
SoftwareSoftwareMain
Open search
Software
Community hub
Software
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Software
Software
from Wikipedia

Software written in the JavaScript language

Software consists of computer programs that instruct the execution of a computer.[1] Software also includes design documents and specifications.

The history of software is closely tied to the development of digital computers in the mid-20th century. Early programs were written in the machine language specific to the hardware. The introduction of high-level programming languages in 1958 allowed for more human-readable instructions, making software development easier and more portable across different computer architectures. Software in a programming language is run through a compiler or interpreter to execute on the architecture's hardware. Over time, software has become complex, owing to developments in networking, operating systems, and databases.

Software can generally be categorized into two main types:

  1. operating systems, which manage hardware resources and provide services for applications
  2. application software, which performs specific tasks for users

The rise of cloud computing has introduced the new software delivery model Software as a Service (SaaS). In SaaS, applications are hosted by a provider and accessed over the Internet.

The process of developing software involves several stages. The stages include software design, programming, testing, release, and maintenance. Software quality assurance and security are critical aspects of software development, as bugs and security vulnerabilities can lead to system failures and security breaches. Additionally, legal issues such as software licenses and intellectual property rights play a significant role in the distribution of software products.

History

[edit]
The integrated circuit is an essential invention to produce modern software systems.[2]

The first use of the word software to describe computer programs is credited to mathematician John Wilder Tukey in 1958.[3][4] The first programmable computers, which appeared at the end of the 1940s,[5] were programmed in machine language. Machine language is difficult to debug and not portable across different computers.[6] Initially, hardware resources were more expensive than human resources.[7] As programs became complex, programmer productivity became the bottleneck. The introduction of high-level programming languages in 1958 hid the details of the hardware and expressed the underlying algorithms into the code .[8][9] Early languages include Fortran, Lisp, and COBOL.[9]

Types

[edit]
A diagram showing how the user interacts with application software on a typical desktop computer. The application software layer interfaces with the operating system, which in turn communicates with the hardware. The arrows indicate information flow.

There are two main types of software:

  • Operating systems are "the layer of software that manages a computer's resources for its users and their applications".[10] There are three main purposes that an operating system fulfills:[11]
    • Allocating resources between different applications, deciding when they will receive central processing unit (CPU) time or space in memory.[11]
    • Providing an interface that abstracts the details of accessing hardware details (like physical memory) to make things easier for programmers.[11][12]
    • Offering common services, such as an interface for accessing network and disk devices. This enables an application to be run on different hardware without needing to be rewritten.[13]
  • Application software runs on top of the operating system and uses the computer's resources to perform a task.[14] There are many different types of application software because the range of tasks that can be performed with modern computers is so large.[15] Applications account for most software[16] and require the environment provided by an operating system, and often other applications, in order to function.[17]
Comparison of on-premise hardware and software, infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS)

Software can also be categorized by how it is deployed. Traditional applications are purchased with a perpetual license for a specific version of the software, downloaded, and run on hardware belonging to the purchaser.[18] The rise of the Internet and cloud computing enabled a new model, software as a service (SaaS),[19] in which the provider hosts the software (usually built on top of rented infrastructure or platforms)[20] and provides the use of the software to customers, often in exchange for a subscription fee.[18] By 2023, SaaS products—which are usually delivered via a web application—had become the primary method that companies deliver applications.[21]

Software development and maintenance

[edit]
Diagram for a traditional software development life cycle from 1988. The numbers represent the typical cost of each phase.

Software companies aim to deliver a high-quality product on time and under budget. A challenge is that software development effort estimation is often inaccurate.[22] Software development begins by conceiving the project, evaluating its feasibility, analyzing the business requirements, and making a software design.[23][24] Most software projects speed up their development by reusing or incorporating existing software, either in the form of commercial off-the-shelf (COTS) or open-source software.[25][26] Software quality assurance is typically a combination of manual code review by other engineers[27] and automated software testing. Due to time constraints, testing cannot cover all aspects of the software's intended functionality, so developers often focus on the most critical functionality.[28] Formal methods are used in some safety-critical systems to prove the correctness of code,[29] while user acceptance testing helps to ensure that the product meets customer expectations.[30] There are a variety of software development methodologies, which vary from completing all steps in order to concurrent and iterative models.[31] Software development is driven by requirements taken from prospective users, as opposed to maintenance, which is driven by events such as a change request.[32]

Frequently, software is released in an incomplete state when the development team runs out of time or funding.[33] Despite testing and quality assurance, virtually all software contains bugs where the system does not work as intended. Post-release software maintenance is necessary to remediate these bugs when they are found and keep the software working as the environment changes over time.[34] New features are often added after the release. Over time, the level of maintenance becomes increasingly restricted before being cut off entirely when the product is withdrawn from the market.[35] As software ages, it becomes known as legacy software and can remain in use for decades, even if there is no one left who knows how to fix it.[36] Over the lifetime of the product, software maintenance is estimated to comprise 75 percent or more of the total development cost.[37][38]

Completing a software project involves various forms of expertise, not just in software programmers but also testing, documentation writing, project management, graphic design, user experience, user support, marketing, and fundraising.[39][40][24]

Quality and security

[edit]

Software quality is defined as meeting the stated requirements as well as customer expectations.[41] Quality is an overarching term that can refer to a code's correct and efficient behavior, its reusability and portability, or the ease of modification.[42] It is usually more cost-effective to build quality into the product from the beginning rather than try to add it later in the development process.[43] Higher quality code will reduce lifetime cost to both suppliers and customers as it is more reliable and easier to maintain.[44][45] Software failures in safety-critical systems can be very serious including death.[44] By some estimates, the cost of poor quality software can be as high as 20 to 40 percent of sales.[46] Despite developers' goal of delivering a product that works entirely as intended, virtually all software contains bugs.[47]

The rise of the Internet also greatly increased the need for computer security as it enabled malicious actors to conduct cyberattacks remotely.[48][49] If a bug creates a security risk, it is called a vulnerability.[50][51] Software patches are often released to fix identified vulnerabilities, but those that remain unknown (zero days) as well as those that have not been patched are still liable for exploitation.[52] Vulnerabilities vary in their ability to be exploited by malicious actors,[50] and the actual risk is dependent on the nature of the vulnerability as well as the value of the surrounding system.[53] Although some vulnerabilities can only be used for denial of service attacks that compromise a system's availability, others allow the attacker to inject and run their own code (called malware), without the user being aware of it.[50] To thwart cyberattacks, all software in the system must be designed to withstand and recover from external attack.[49] Despite efforts to ensure security, a significant fraction of computers are infected with malware.[54]

Encoding and execution

[edit]

Programming languages

[edit]
The source code for a computer program in C. The gray lines are comments that explain the program to humans. When compiled and run, it will output "Hello, world!".

Programming languages are the format in which software is written. Since the 1950s, thousands of different programming languages have been invented; some have been in use for decades, while others have fallen into disuse.[55] Some definitions classify machine code—the exact instructions directly implemented by the hardware—and assembly language—a more human-readable alternative to machine code whose statements can be translated one-to-one into machine code—as programming languages.[56] Programs written in the high-level programming languages used to create software share a few main characteristics: knowledge of machine code is not necessary to write them, they can be ported to other computer systems, and they are more concise and human-readable than machine code.[57] They must be both human-readable and capable of being translated into unambiguous instructions for computer hardware.[58]

Compilation, interpretation, and execution

[edit]

The invention of high-level programming languages was simultaneous with the compilers needed to translate them automatically into machine code.[59] Most programs do not contain all the resources needed to run them and rely on external libraries. Part of the compiler's function is to link these files in such a way that the program can be executed by the hardware. Once compiled, the program can be saved as an object file and the loader (part of the operating system) can take this saved file and execute it as a process on the computer hardware.[60] Some programming languages use an interpreter instead of a compiler. An interpreter converts the program into machine code at run time, which makes them 10 to 100 times slower than compiled programming languages.[61][62]

[edit]

Liability

[edit]

Software is often released with the knowledge that it is incomplete or contains bugs.[citation needed] Purchasers knowingly buy it in this state,[citation needed] which has led to a legal regime where liability for software products is significantly curtailed compared to other products.[63]

Licenses

[edit]
Blender, a free software program

Since the mid-1970s, software and its source code have been protected by copyright law that vests the owner with the exclusive right to copy the code. The underlying ideas or algorithms are not protected by copyright law, but are sometimes treated as a trade secret and concealed by such methods as non-disclosure agreements.[64] A software copyright is often owned by the person or company that financed or made the software (depending on their contracts with employees or contractors who helped to write it).[65] Some software is in the public domain and has no restrictions on who can use it, copy or share it, or modify it; a notable example is software written by the United States Government.[citation needed] Free and open-source software also allow free use, sharing, and modification, perhaps with a few specified conditions.[65] The use of some software is governed by an agreement (software license) written by the copyright holder and imposed on the user. Proprietary software is usually sold under a restrictive license that limits its use and sharing.[66] Some free software licenses require that modified versions must be released under the same license, which prevents the software from being sold or distributed under proprietary restrictions.[67]

Patents

[edit]

Patents give an inventor an exclusive, time-limited license for a novel product or process.[68] Ideas about what software could accomplish are not protected by law and concrete implementations are instead covered by copyright law. In some countries, a requirement for the claimed invention to have an effect on the physical world may also be part of the requirements for a software patent to be held valid.[69] Software patents have been historically controversial. Before the 1998 case State Street Bank & Trust Co. v. Signature Financial Group, Inc., software patents were generally not recognized in the United States. In that case, the Supreme Court decided that business processes could be patented.[70] Patent applications are complex and costly, and lawsuits involving patents can drive up the cost of products.[71] Unlike copyrights, patents generally only apply in the jurisdiction where they were issued.[72]

Impact

[edit]
Computer-generated simulations are one of the advances enabled by software.[73]

Engineer Capers Jones writes that "computers and software are making profound changes to every aspect of human life: education, work, warfare, entertainment, medicine, law, and everything else".[74] It has become ubiquitous in everyday life in developed countries.[75] In many cases, software augments the functionality of existing technologies such as household appliances and elevators.[76] Software also spawned entirely new technologies such as the Internet, video games, mobile phones, and GPS.[76][77] New methods of communication, including email, forums, blogs, microblogging, wikis, and social media, were enabled by the Internet.[78] Massive amounts of knowledge exceeding any paper-based library are now available with a quick web search.[77] Most creative professionals have switched to software-based tools such as computer-aided design, 3D modeling, digital image editing, and computer animation.[73] Almost every complex device is controlled by software.[77]

References

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia
from Grokipedia

History

The term "software" emerged in the late 1950s as a counterpart to "hardware," initially used informally to describe the instructions directing computer operations, with formal adoption around 1958–1960. Early computing relied on machine code—binary instructions directly executable by hardware—and assembly languages that used mnemonic codes for human readability, translated via assemblers. The development of higher-level programming languages marked a significant evolution: FORTRAN, introduced in 1957 by IBM for scientific and engineering computations, allowed algebraic notation closer to mathematical expressions; COBOL, standardized in 1959, facilitated business data processing with English-like syntax. These advancements shifted programming from low-level hardware-specific instructions to abstracted, portable code, enabling broader application development amid the growth of mainframe computers in the 1960s.

Types

Software is broadly classified into system software, application software, and network software. System software includes operating systems, device drivers, and utility programs that manage hardware resources and provide essential services to the computer, enabling other software to run efficiently. Examples include Microsoft Windows, Unix-like systems such as Linux, and utilities like disk defragmenters. Application software performs specific tasks for end-users, such as word processing, data analysis, or entertainment; common examples are Microsoft Office suite for productivity and web browsers like Google Chrome. Network software encompasses protocols, middleware, and tools that facilitate communication and data exchange between networked devices, including TCP/IP stacks and distributed application frameworks.

Software development and maintenance

Software development is the process of designing, coding, testing, documenting, and maintaining applications, frameworks, or other software components. It encompasses activities from initial conception through to ongoing support after deployment. The process is typically structured around the software development life cycle (SDLC), which provides a systematic framework for producing high-quality software efficiently and with minimized risks. The SDLC generally includes the following phases:
  • Planning: Defining project goals, scope, feasibility, resource requirements, and scheduling.
  • Requirements analysis: Gathering, analyzing, and documenting user needs and functional/non-functional requirements.
  • Design: Creating architectural and detailed designs, including system structure, interfaces, and data models.
  • Implementation: Writing code and constructing the software product.
  • Testing: Verifying the software against requirements through unit, integration, system, and acceptance testing to identify and fix defects.
  • Deployment: Releasing the software into the production environment for use.
  • Maintenance: Performing post-delivery modifications to address issues, adapt to changes, improve attributes, or prevent problems.
Different methodologies organize these phases variably. The Waterfall model proceeds sequentially through the phases, suitable for projects with well-defined requirements. Agile methodologies, by contrast, use iterative and incremental cycles, allowing flexibility, frequent feedback, and adaptation to changing needs. Software maintenance involves modifying delivered software to correct faults, improve performance or other attributes, or adapt to environmental changes. It is often the longest and most costly phase of the software life cycle, frequently accounting for more than 50% of total lifecycle costs and sometimes significantly higher. ISO/IEC/IEEE 14764 defines four types of software maintenance:
  • Corrective maintenance: Fixes defects or faults to restore the software to its specified functionality.
  • Adaptive maintenance: Modifies the software to accommodate changes in the operational environment, such as new hardware, operating systems, or regulations.
  • Perfective maintenance: Enhances performance, maintainability, usability, or other qualities without altering primary functions.
  • Preventive maintenance: Proactively modifies the software to prevent potential future problems, such as by refactoring code or addressing latent vulnerabilities.
These categories guide maintenance activities and are supported by the standard's iterative process model for planning, executing, and controlling maintenance.

Quality and security

Software quality refers to the degree to which a software product satisfies stated and implied needs under specified conditions, encompassing both the product and the development processes used to create it. Key characteristics include functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, and portability, as defined in ISO/IEC 25010. These attributes are assessed through standards such as ISO 5055, which measures structural quality during development by identifying weaknesses in security, reliability, performance efficiency, and maintainability to prevent operational failures and reduce costs. Security issues in software arise from vulnerabilities that can be exploited to compromise systems. Zero-day vulnerabilities, which are undisclosed flaws exploited before developers can patch them, pose significant risks. Empirical analysis of 200 real-world zero-day vulnerabilities reveals an average lifespan of 6.9 years from discovery to public disclosure or end-of-life, with only 25% surviving beyond 1.51 years or lasting longer than 9.5 years. The median time to develop a functional exploit after identifying an exploitable vulnerability is 22 days. Approximately 5.7% of stockpiled zero-days are publicly discovered by others within a year. Effective management involves timely patching, secure development practices, and considering vulnerabilities as "alive" (undisclosed), "dead" (patched), or "quasi-alive" (exploitable in legacy versions), highlighting the need for ongoing vigilance and disclosure strategies.

Encoding and execution

Software encoding involves representing instructions in forms executable by computer hardware, ranging from binary machine code to higher-level abstractions translated via specialized processes. Execution occurs when these instructions are loaded into memory and processed by the processor.

Programming languages

Programming languages enable the specification of algorithms and instructions for computers. They are categorized by abstraction level from hardware. Machine language consists of binary numeric codes (0s and 1s) directly interpretable by the processor, specific to each architecture and challenging for humans to compose due to its lack of readability. Assembly language, a low-level step above, employs mnemonic codes (e.g., "ADD") and symbolic addresses, facilitating hardware-specific programming like device drivers while remaining translatable to machine code via assemblers. Higher-level languages abstract hardware details, using syntax akin to natural or mathematical language for broader applicability. FORTRAN, developed in 1957 for scientific computing, supports arrays, loops, and subroutines, optimizing for numerical efficiency. COBOL, introduced in 1959, adopts English-like syntax for business data processing, incorporating record structures for heterogeneous data. ALGOL (1958–1960) emphasizes algorithmic expression, introducing block structures and recursion, influencing subsequent languages.

Compilation, interpretation, and execution

Higher-level languages are translated to machine code through compilation or interpretation. Compilation involves a compiler converting the entire source code into executable machine instructions prior to runtime, producing efficient, architecture-specific binaries as in FORTRAN's design for optimized output. Interpretation executes code line-by-line via an interpreter without full pre-translation, enabling flexibility but potentially at performance cost, contrasting compilation's upfront processing. Assembly code undergoes straightforward substitution to machine language. Once encoded, programs reside in storage (e.g., disk) and execute by loading into RAM, where the processor fetches, decodes, and performs instructions sequentially.

Liability

Software liability refers to the legal responsibility of software developers, manufacturers, vendors, or distributors for damages caused by defects, failures, or vulnerabilities in their software. Liability can arise under several legal theories:
  • Strict liability — applies when software is treated as a product, holding the producer liable for harm caused by unreasonably dangerous defects without requiring proof of fault.
  • Negligence — holds parties liable for failing to exercise reasonable care in design, development, testing, or maintenance, leading to foreseeable harm.
  • Breach of warranty or contract — arises from failure to meet express or implied assurances about the software's performance or fitness.
Historically, many courts have hesitated to apply strict product liability to software, often viewing it as intangible intellectual property or a service rather than a tangible product. However, in cases where software defects cause physical harm—particularly in safety-critical systems—liability has been imposed under negligence or related tort principles. Concerns over software liability grew as software became integral to public-use and safety-critical applications, such as medical devices, transportation, and industrial controls. A seminal case is the Therac-25 incidents (1985–1987), in which software race conditions and other bugs in a radiation therapy machine caused massive radiation overdoses, resulting in at least three deaths and several severe injuries including burns and tissue necrosis. These accidents underscored the dangers of over-reliance on software for safety without complementary hardware protections and inadequate testing. A 1993 report from the Software Engineering Institute at Carnegie Mellon University analyzed software product liability risks, legal theories, and defenses, noting increasing exposure in safety-critical domains and recommending process improvements like maturity models to mitigate defects and liability. The legal framework has evolved significantly in recent years to address software's role in modern technology. In the European Union, Directive (EU) 2024/2853 explicitly includes software in the definition of a "product" for strict (no-fault) product liability purposes. This applies to software regardless of supply mode (embedded, cloud-based, or as-a-service), covering damages such as death, personal injury, property damage, and data corruption. The directive applies to products placed on the market or put into service after 9 December 2026. In the United States, courts have traditionally been reluctant to extend strict liability to pure software, but recent trends show some willingness to treat software—especially when integrated into physical products, medical devices, or AI systems—as subject to product liability principles, particularly where defects cause physical or significant harm. Growing cybersecurity threats and supply chain vulnerabilities have also heightened liability concerns, with increased litigation and regulatory scrutiny related to defects, data breaches, and compliance failures.

Licenses

Software licenses govern the distribution and use of software, specifying permissions, restrictions, and obligations for users and developers. Open source licenses, in particular, promote collaborative development while varying in their conditions. Permissive licenses, such as the MIT License, allow broad reuse, modification, and distribution, including in proprietary software, with minimal requirements like retaining copyright notices. The Apache License 2.0, also permissive, includes explicit patent grants and requires notices for modifications. In contrast, copyleft licenses like the GNU General Public License (GPL) mandate that derivative works be distributed under the same license, ensuring continued openness but restricting integration into closed-source products.

Patents

Impact

References

Sources

Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.