Wikipedia

User:Buidhe paid/Software

< User:Buidhe paid
For other uses, see User:Buidhe paid/Software (disambiguation).
Credit cards are one of many everyday technologies that are dependent on software.[1]

Software is defined narrowly as unambiguous instructions that can be transformed into a form executable on computer hardware, or more broadly including supporting concepts, tools and methods needed to make the computer system operational.

Building off of previous innovations in mathematics and technology, software was created for the programmable digital computers that emerged in the late 1940s and was necessary to realize their usefulness. The first software was tied closely to the underlying computer hardware, but over time, the lower layers of the system have become more standardized, and software has become increasingly portability between different systems and abstracted from the underlying machine code. Operating systems manage the hardware resources and mediate between different applications that accomplish tasks for the user. Programming languages are the format in which software is written, and must be both human-readable and capable of being translated into unambiguous instructions for computer hardware. Compilers or interpreters are needed to link a program with other code that it relies on and convert the software into machine code that can be executed on the hardware. Programs are combined with each other and with external input to be capable of accomplishing a complex task.

Programming and maintaining the source code is the central step of software development, but it also includes conceiving the project, evaluating its feasibility, analyzing the business requirements, software design, and release. Software quality assurance, including code review and testing, is an essential part of the process as delivering quality code lowers the cost of reliability failures, cyberattacks enabled by security vulnerabilities, and maintenance cost. Maintenance typically consumes 75 percent or more of the software's lifetime engineering budget. Source code is protected by copyright law that vests the owner with the exclusive right to copy the code. Software has become ubiquitous in everyday life in developed countries. In many cases, software augments the functionality of pre-existing technologies, but it has also enabled the creation of entirely new technologies such as the Internet, video games, social media, mobile phones, and GPS.

Definition

edit

Software can be defined more narrowly as the instructions executed by the computer hardware, or more broadly including other concepts, tools, and methods needed to make an executable system on computer hardware, such as design documents, specifications, and testing suites.[2][3] An individual program or source code file consists of unambiguous instructions and algorithms. Programs are combined with each other and with external input to be capable of accomplishing a complex task.[4][3] Tools such as compilers, assemblers, flowcharts, design tools, simulators, and architectural diagrams—some of which are also software—are essential to the design and execution of most computing systems.[3] Although software is intangible,[5][6] software makes instructions for computer hardware to produce visible and tangible effects.[7]

History

edit
Main article: History of software
 
07R01, an integrated circuit by Motorola. Integrated circuits were an essential enabling invention allowing the creation of software.[8]

A host of earlier inventions were necessary for the creation of software, including mathematics—especially binary and decimal number systems, and zero—alphabets, writing, mechanical calculators,[9] boolean algebra, transistors, integrated circuits, and plastics.[10] Software could not exist without digital computers, as it was created specifically for these devices and was necessary to realize their usefulness.[11]

The first programmable computers, which appeared at the end of the 1940s,[12] were programmed in machine language (simple instructions that could be directly executed by the processor). Machine language was difficult to debug and was not portable between different computer systems.[13] Initially, hardware resources were scarce and expensive, while human resources were cheaper.[14] As programs grew more complex, programmer productivity became a bottleneck. This led to the introduction of high-level programming languages in the mid-1950s. These languages abstracted away the details of the hardware, instead being designed to express algorithms that could be understood more easily by humans.[15][16] As instructions distinct from the underlying computer hardware, software is therefore relatively recent, dating to these early high-level programming languages such as Fortran, Lisp, and Cobol.[16] The first use of the word software is credited to mathematician John Wilder Tukey in 1958.[3]

The first software was tied closely to the underlying hardware and consequently was not portable to other systems. As it has evolved, newer software can be built and run on a wide variety of platforms. Much of the increase in portability can be attributed to standardization of lower-level aspects of the system, such as networking, operating systems, and databases. Because there are only a relatively few operating systems, TCP and IP are used for virtually all networking, and SQL is used for many database queries, application software can run more easily over a wide variety of hardware.[17] Increasing the number of layers of abstraction in the system is a related development: both in programming languages where it enables better structure and increased modularity, as well as enabling virtualization of system resources. As a result of the increase in stability and abstraction, software has become increasingly complex and can solve more problems.[18] Both industry and academia have had a strong influence on the development of different aspects of software.[19]

Types

edit
See also: Software categories
 
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".[20] There are three main purposes that an operating system fulfills:[21]
    • Allocating resources between different applications, deciding when they will receive central processing unit (CPU) time or space in memory.[21]
    • Providing an interface that abstracts the details of accessing hardware details (like physical memory) to make things easier for programmers.[21][22]
    • 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.[23]
  • Application software runs on top of the operating system and uses the computer's resources to perform a task.[24] There are many different types of application software because the range of tasks that can be performed with modern computers is so large.[25] Applications account for most software[26] and require the environment provided by an operating system, and often other applications, in order to function.[27]
 
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.[28] The rise of the Internet and cloud computing enabled a new model, software as a service (SaaS),[29] in which the provider hosts the software (usually built on top of rented infrastructure or platforms)[30] and provides the use of the software to customers, often in exchange for a subscription fee.[28] By 2023, SaaS products—which are usually delivered via a web application—had become the primary method that companies deliver applications.[31]

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.[32] Software development begins by conceiving the project, evaluating its feasibility, analyzing the business requirements, and making a software design.[33][34] 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.[35][36] Software quality assurance is typically a combination of manual code review by other engineers[37] 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.[38] Formal methods are used in some safety-critical systems to prove the correctness of code,[39] while user acceptance testing helps to ensure that the product meets customer expectations.[40] There are a variety of software development methodologies, which vary to completing all steps in order to concurrent and iterative models.[41] Software development is driven by requirements taken from prospective users, as opposed to maintenance that is driven by events such as a change request.[42]

Frequently, software is released in an incomplete state when the development team runs out of time or funding.[43] 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 its the environment changes over time.[44] New features are often added after release. Over time, the level of maintenance becomes increasingly restricted before being cut off entirely when the product is withdrawn from the market.[45] 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.[5] Over the lifetime of the product, software maintenance is estimated to comprise 75 percent or more of the total development cost.[46][47]

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.[48][49][34]

Quality and security

edit
Main articles: Software quality and Computer security

Software quality is defined as meeting the stated requirements as well as customer expectations.[50] 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.[51] 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.[52] Higher quality code will reduce lifetime cost to both suppliers and customers as it is more reliable and easier to maintain.[53][54] Software failures in safety-critical systems can be very serious including death.[53] By some estimates, the cost of poor quality software can be as high as 20 to 40 percent of sales.[55] Despite developers' goal of delivering a product that works entirely as intended, virtually all software contains bugs.[56]

The rise of the Internet also greatly increased the need for computer security as it enabled malicious actors to conduct cyberattacks remotely.[57][58] If a bug creates a security risk, it is called a vulnerability.[59][60] 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.[61] Vulnerabilities vary in their ability to be exploited by malicious actors,[59] and the actual risk is dependent on the nature of the vulnerability as well as the value of the surrounding system.[62] 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.[59] To thwart cyberattacks, all software in the system must be designed to withstand and recover from external attack.[58] Despite efforts to ensure security, a significant fraction of computers are infected with malware.[63]

Encoding and execution

edit

Programming languages

edit
Main article: Programming language
 
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 give the 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.[64] 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.[65] 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.[66] They must be both human-readable and capable of being translated into unambiguous instructions for computer hardware.[67]

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.[68] 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.[69] 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.[70][71]

edit

Liability

edit
Main article: Software product liability

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

Licenses

edit
Main articles: Software license and Software copyright
 
Blender, a free software program

Source code is 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 often treated as a trade secret and concealed by such methods as non-disclosure agreements.[73] Software copyright has been recognized since the mid-1970s and is vested in the company that makes the software, not the employees or contractors who wrote it.[74] The use of most software is governed by an agreement (software license) between the copyright holder and the user. Proprietary software is usually sold under a restrictive license that limits copying and reuse (often enforced with tools such as digital rights management (DRM)).[75] Open-source licenses, in contrast, allow free use and redistribution of software with few conditions.[74] Most open-source licenses used for software require that modifications be released under the same license, which can create complications when open-source software is reused in proprietary projects.[76]

Patents

edit
Main articles: Software patent and Software patent debate

Patents give an inventor an exclusive, time-limited license for a novel product or process.[77] 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.[78] 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.[10] Patent applications are complex and costly, and lawsuits involving patents can drive up the cost of products.[79] Unlike copyrights, patents generally only apply in the jurisdiction where they were issued.[80]

Impact

edit
Further information: Information Age
 
Computer-generated simulations are one of the advances enabled by software.[81]

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".[82] It has become ubiquitous in everyday life in developed countries.[83] In many cases, software augments the functionality of existing technologies such as household appliances and elevators.[1] Software also spawned entirely new technologies such as the Internet, video games, mobile phones, and GPS.[1][84] New methods of communication, including email, forums, blogs, microblogging, wikis, and social media, were enabled by the Internet.[85] Massive amounts of knowledge exceeding any paper-based library are now available with a quick web search.[84] Most creative professionals have switched to software-based tools such as computer-aided design, 3D modeling, digital image editing, and computer animation.[81] Almost every complex device is controlled by software.[84]

References

edit
  1. ^ a b c Kitchin & Dodge 2011, p. 5.
  2. ^ Osterweil 2013, p. 61.
  3. ^ a b c d Tracy 2021, p. 2.
  4. ^ Kitchin & Dodge 2011, pp. 3, 24.
  5. ^ a b Tracy 2021, p. 3.
  6. ^ Kitchin & Dodge 2011, p. 24.
  7. ^ Kitchin & Dodge 2011, pp. 3–4.
  8. ^ Jones 2014, pp. 19, 22.
  9. ^ Jones 2014, pp. 9, 21.
  10. ^ a b Jones 2014, p. 19.
  11. ^ Jones 2014, p. 22.
  12. ^ Gabbrielli & Martini 2023, p. 519.
  13. ^ Gabbrielli & Martini 2023, pp. 520–521.
  14. ^ Gabbrielli & Martini 2023, p. 522.
  15. ^ Gabbrielli & Martini 2023, p. 521.
  16. ^ a b Tracy 2021, p. 1.
  17. ^ Tracy 2021, p. 249.
  18. ^ Tracy 2021, p. 250.
  19. ^ Tracy 2021, pp. 250–251.
  20. ^ Anderson & Dahlin 2014, p. 6.
  21. ^ a b c Anderson & Dahlin 2014, p. 7.
  22. ^ Tanenbaum & Bos 2023, p. 5.
  23. ^ Anderson & Dahlin 2014, pp. 7, 9, 13.
  24. ^ Anderson & Dahlin 2014, pp. 6–7.
  25. ^ Jones 2014, p. 121.
  26. ^ Tracy 2021, p. 66.
  27. ^ Tracy 2021, p. 72.
  28. ^ a b O'Regan 2022, p. 386.
  29. ^ Campbell-Kelly & Garcia-Swartz 2015, pp. 156–157.
  30. ^ Rosati & Lynn 2020, p. 23.
  31. ^ Watt 2023, p. 4.
  32. ^ O'Regan 2022, p. 7.
  33. ^ O'Regan 2022, p. 5.
  34. ^ a b Dooley 2017, p. 1.
  35. ^ O'Regan 2022, pp. 18, 110–111.
  36. ^ Tracy 2021, pp. 43, 76.
  37. ^ O'Regan 2022, pp. 117–118.
  38. ^ O'Regan 2022, p. 54.
  39. ^ O'Regan 2022, p. 267.
  40. ^ O'Regan 2022, p. 20.
  41. ^ O'Regan 2022, p. 9.
  42. ^ Tripathy & Naik 2014, p. 26.
  43. ^ Reifer 2012, p. 22.
  44. ^ Tripathy & Naik 2014, pp. 4, 27.
  45. ^ Tripathy & Naik 2014, p. 89.
  46. ^ Varga 2018, p. 6.
  47. ^ Ulziit et al. 2015, p. 764.
  48. ^ Tucker, Morelli & de Silva 2011, p. 7.
  49. ^ Stull 2018, pp. 24–25.
  50. ^ Galin 2018, p. 3.
  51. ^ Galin 2018, p. 26.
  52. ^ O'Regan 2022, pp. 68, 117.
  53. ^ a b O'Regan 2022, pp. 3, 268.
  54. ^ Varga 2018, p. 12.
  55. ^ O'Regan 2022, p. 119.
  56. ^ Ablon & Bogart 2017, p. 1.
  57. ^ Campbell-Kelly & Garcia-Swartz 2015, p. 164.
  58. ^ a b O'Regan 2022, p. 266.
  59. ^ a b c Ablon & Bogart 2017, p. 2.
  60. ^ Daswani & Elbayadi 2021, p. 25.
  61. ^ Daswani & Elbayadi 2021, pp. 26–27.
  62. ^ Haber & Hibbert 2018, pp. 5–6.
  63. ^ Kitchin & Dodge 2011, p. 37.
  64. ^ Tracy 2021, p. 117.
  65. ^ Tracy 2021, pp. 118–120.
  66. ^ Tracy 2021, pp. 118–119.
  67. ^ Kitchin & Dodge 2011, p. 26.
  68. ^ Tracy 2021, p. 121.
  69. ^ Tracy 2021, pp. 122–123.
  70. ^ O'Regan 2022, p. 375.
  71. ^ Sebesta 2012, p. 28.
  72. ^ Kitchin & Dodge 2011, pp. 36–37.
  73. ^ O'Regan 2022, pp. 394–396.
  74. ^ a b O'Regan 2022, p. 403.
  75. ^ O'Regan 2022, pp. 394, 404.
  76. ^ Langer 2016, pp. 44–45.
  77. ^ O'Regan 2022, p. 395.
  78. ^ Gerardo Con Díaz, "The Text in the Machine: American Copyright Law and the Many Natures of Software, 1974–1978", Technology and Culture 57 (October 2016), 753–79.
  79. ^ O'Regan 2022, p. 398.
  80. ^ O'Regan 2022, p. 399.
  81. ^ a b Manovich 2013, p. 333.
  82. ^ Jones 2014, p. 32.
  83. ^ Kitchin & Dodge 2011, p. iv.
  84. ^ a b c Jones 2014, p. xxviii.
  85. ^ Manovich 2013, p. 329.

Sources

edit
  • Ablon, Lillian; Bogart, Andy (2017). Zero Days, Thousands of Nights: The Life and Times of Zero-Day Vulnerabilities and Their Exploits (PDF). Rand Corporation. ISBN 978-0-8330-9761-3.
  • Anderson, Thomas; Dahlin, Michael (2014). Operating Systems: Principles and Practice (2 ed.). Recursive Books. ISBN 978-0-9856735-2-9.
  • Campbell-Kelly, Martin; Garcia-Swartz, Daniel D. (2015). From Mainframes to Smartphones: A History of the International Computer Industry. Harvard University Press. ISBN 978-0-674-28655-9.
  • Daswani, Neil; Elbayadi, Moudy (2021). Big Breaches: Cybersecurity Lessons for Everyone. Apress. ISBN 978-1-4842-6654-0.
  • Dooley, John F. (2017). Software Development, Design and Coding: With Patterns, Debugging, Unit Testing, and Refactoring. Apress. ISBN 978-1-4842-3153-1.
  • Gabbrielli, Maurizio; Martini, Simone (2023). Programming Languages: Principles and Paradigms (2nd ed.). Springer. ISBN 978-3-031-34144-1.
  • Galin, Daniel (2018). Software Quality: Concepts and Practice. John Wiley & Sons. ISBN 978-1-119-13449-7.
  • Haber, Morey J.; Hibbert, Brad (2018). Asset Attack Vectors: Building Effective Vulnerability Management Strategies to Protect Organizations. Apress. ISBN 978-1-4842-3627-7.
  • Jones, Capers (2014). The Technical and Social History of Software Engineering. Pearson Education. ISBN 978-0-321-90342-6.
  • Kitchin, Rob; Dodge, Martin (2011). Code/space: Software and Everyday Life. MIT Press. ISBN 978-0-262-04248-2.
  • Langer, Arthur M. (2016). Guide to Software Development: Designing and Managing the Life Cycle. Springer. ISBN 978-1-4471-6799-0.
  • Manovich, Lev (2013). Software Takes Command. Bloomsbury Academic. ISBN 978-1-62356-745-3.
  • O'Regan, Gerard (2022). Concise Guide to Software Engineering: From Fundamentals to Application Methods. Springer Nature. ISBN 978-3-031-07816-3.
  • Osterweil, Leon J. (2013). "What Is Software? The Role of Empirical Methods in Answering the Question". Perspectives on the Future of Software Engineering: Essays in Honor of Dieter Rombach. Springer. pp. 237–254. ISBN 978-3-642-37395-4.
  • Rahman, Hanif Ur; da Silva, Alberto Rodrigues; Alzayed, Asaad; Raza, Mushtaq (2024). "A Systematic Literature Review on Software Maintenance Offshoring Decisions". Information and Software Technology. 172: 107475. doi:10.1016/j.infsof.2024.107475.
  • Reifer, Donald J. (2012). Software Maintenance Success Recipes. CRC Press. ISBN 978-1-4398-5167-8.
  • Rosati, Pierangelo; Lynn, Theo (2020). "Measuring the Business Value of Infrastructure Migration to the Cloud". Measuring the Business Value of Cloud Computing. Springer International Publishing. pp. 19–37. ISBN 978-3-030-43198-3.
  • Sebesta, Robert W. (2012). Concepts of Programming Languages (10 ed.). Addison-Wesley. ISBN 978-0-13-139531-2.
  • Stull, Edward (2018). UX Fundamentals for Non-UX Professionals: User Experience Principles for Managers, Writers, Designers, and Developers. Apress. ISBN 978-1-4842-3811-0.
  • Tanenbaum, Andrew S.; Bos, Herbert (2023). Modern Operating Systems, Global Edition. Pearson Higher Ed. ISBN 978-1-292-72789-9.
  • Tracy, Kim W. (2021). Software: A Technical History. Morgan & Claypool Publishers. ISBN 978-1-4503-8724-8.
  • Tripathy, Priyadarshi; Naik, Kshirasagar (2014). Software Evolution and Maintenance: A Practitioner's Approach. John Wiley & Sons. ISBN 978-0-470-60341-3.
  • Tucker, Allen; Morelli, Ralph; de Silva, Chamindra (2011). Software Development: An Open Source Approach. CRC Press. ISBN 978-1-4398-8460-7.
  • Ulziit, Bayarbuyan; Warraich, Zeeshan Akhtar; Gencel, Cigdem; Petersen, Kai (2015). "A conceptual framework of challenges and solutions for managing global software maintenance". Journal of Software: Evolution and Process. 27 (10): 763–792. doi:10.1002/smr.1720.
  • Watt, Andy (2023). Building Modern SaaS Applications with C# And . NET: Build, Deploy, and Maintain Professional SaaS Applications. Packt. ISBN 978-1-80461-087-9.
  • Varga, Ervin (2018). Unraveling Software Maintenance and Evolution: Thinking Outside the Box. Springer. ISBN 978-3-319-71303-8.

Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Buidhe_paid/Software&oldid=1225045731"