Content deleted Content added
Reverting edit(s) by 103.19.122.3 (talk) to rev. 1216450947 by WizardGamer775: non-constructive (RW 16.1) |
Tecno BD4j Tags: Reverted Visual edit Mobile edit Mobile web edit |
||
Line 3:
{{Use dmy dates|date=February 2020|cs1-dates=y}}
The '''software release life cycle''' is the process of developing, testing, and distributing a software product (e.g., an
[[File:Software dev2.svg|thumb|upright=1.1|An example of a basic software release life cycle]]
Pre-alpha refers to the early stages of development, when the software is still being designed and built. Alpha testing is the first phase of formal testing, during which the software is tested internally using [[White-box testing|white-box techniques]]. Beta testing is the next phase, in which the software is tested by a larger group of users, typically outside of the organization that developed it. The beta phase is focused on reducing impacts on users and may include usability testing.
Line 13:
== Stages of development ==
=== Pre-alpha ===
Pre-alpha refers to all activities performed during the software project before formal testing. These activities can include [[requirements analysis]],
=== {{anchor|Alpha}}Alpha ===
The alpha phase of the release life cycle is the first phase of
Alpha software is not thoroughly tested by the developer before it is released to customers. Alpha software may contain serious errors, and any resulting instability could cause crashes or data loss.<ref>{{cite book |editor1-last=Ince |editor1-first=Darrel |title=A Dictionary of the Internet (3 ed.) |chapter=Alpha software |year=2013 |publisher=Oxford University Press |isbn=978-0-19-174415-0 |url=https://www.oxfordreference.com/abstract/10.1093/acref/9780191744150.001.0001/acref-9780191744150-e-95?rskey=VLB7Gk&result=2 |access-date=15 July 2019}}</ref> Alpha software may not contain all of the features that are planned for the final version.<ref>{{cite magazine|title=The Next Generation 1996 Lexicon A to Z|magazine=[[Next Generation (magazine)|Next Generation]]|issue=15 |publisher=[[Imagine Media]]|date=March 1996|page=29|quote=Alpha software generally barely runs and is missing major features like gameplay and complete levels.}}</ref> In general, external availability of alpha software is uncommon for
==== Feature-complete ====
A '''feature-complete''' (FC) version of a piece of [[software]] has all of its planned or primary [[software feature|features]] implemented but is not yet final due to [[software bug|bugs]], [[software performance|performance]] or [[Software testing|stability]] issues.<ref>{{cite book |last=Cusumano |first=Michael |url=https://archive.org/details/microsoftsecrets00cusu |title=Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People |publisher=Free Press |year=1998 |isbn=978-0-684-85531-8 |pages=[https://archive.org/details/microsoftsecrets00cusu/page/202 202–203] |url-access=registration}}</ref> This occurs at the end of alpha testing in [[Software development|development]].
Usually, feature-complete software still has to undergo
=== {{Anchor|BETA}}Beta ===
{{Redirect|Beta test|the 2016 film|Beta Test (film)|the 2021 film|The Beta Test}}
▲}}</ref> A beta phase generally begins when the software is feature-complete but likely to contain several known or unknown bugs.<ref>{{cite magazine|title=The Next Generation 1996 Lexicon A to Z|magazine=[[Next Generation (magazine)|Next Generation]]|issue=15 |publisher=[[Imagine Media]]|date=March 1996|page=30|url=https://archive.org/details/nextgen-issue-015/page/n31/mode/2up}}</ref> Software in the beta phase will generally have many more bugs in it than completed software and speed or performance issues, and may still cause crashes or data loss. The focus of beta testing is reducing impacts on users, often incorporating [[usability testing]]. The process of delivering a beta version to the users is called ''beta release'' and is typically the first time that the software is available outside of the organization that developed it. Software beta releases can be either [[Software release life cycle#Open and closed beta|open or closed]], depending on whether they are openly available or only available to a limited audience. Beta version software is often useful for demonstrations and previews within an organization and to prospective customers. Some developers refer to this stage as a ''preview'', ''preview release'', ''prototype'', ''technical preview'' or ''technology preview'' (''TP''),<ref>{{cite web
''Beta testers'' are people who actively report issues with beta software. They are usually customers or representatives of prospective customers of the organization that develops the software. Beta testers tend to volunteer their services free of charge but often receive versions of the product they test, discounts on the release version, or other incentives.
==== Perpetual beta ====
{{Main article|Perpetual beta}}
Some software is kept in so-called ''perpetual beta'', where new features are continually added to the software without establishing a final "stable" release. As the
==== Open and closed beta ====
Line 54 ⟶ 41:
=== Release candidate ===
A ''release candidate'' (''RC''), also known as gamma testing or "going silver", is a beta version with the potential to be a stable product, which is ready to release unless significant
=== Stable release ===
Also called ''production release'', the ''stable release'' is the last ''release candidate'' (''RC'') which has passed all stages of verification and tests. Any known remaining bugs are considered acceptable. This release goes to
Some software products (e.g.
== {{Anchor|STABLE-RELEASE}}Release ==
Once released, the software is generally known as a "stable release". The formal term often depends on the method of release: physical media, online release, or a web application.<ref name=":0">{{cite web |date=7 July 2009 |title=Google Apps is out of beta (yes, really) |url=http://googleblog.blogspot.com/2009/07/google-apps-is-out-of-beta-yes-really.html |url-status=live |archive-url=https://web.archive.org/web/20110121002635/http://googleblog.blogspot.com/2009/07/google-apps-is-out-of-beta-yes-really.html |archive-date=21 January 2011 |access-date=2011-01-12 |work=Google Blog}}</ref>
=== {{Anchor|RTM|Release to manufacturing|Release to marketing|RTM or RTW}}Release to manufacturing (RTM) ===
The term release to manufacturing (RTM), also known as "going gold", is a term used when a software product is ready to be delivered. This build may be digitally signed, allowing the end user to verify the integrity and authenticity of the software purchase. A copy of the RTM build known as the "
RTM is typically used in certain retail mass-production software contexts—as opposed to a specialized software production or project in a commercial or government production and distribution—where the software is sold as part of a bundle in a related computer hardware sale and typically where the software and related hardware is ultimately to be available and sold on mass/public basis at retail stores to indicate that the software has met a defined quality level and is ready for mass retail distribution. RTM could also mean in other contexts that the software has been delivered or released to a client or customer for installation or distribution to the related hardware end user computers or machines. The term does ''not'' define the delivery mechanism or volume; it only states that the quality is sufficient for mass distribution. The deliverable from the engineering organization is frequently in the form of a golden master media used for duplication or to produce the image for the web.
=== {{Anchor|GA|General availability}}General availability (GA) ===
[[File:ProductEndOfLifeCycle.png|thumb|Milestones in a product life cycle: general availability (GA),
'''General availability''' ('''GA''') is the marketing stage at which all necessary
=== {{Anchor|Web release}}Release to the Web (RTW) ===
Line 78 ⟶ 65:
== Support ==
{{Unsourced section|date=April 2023}}
During its supported lifetime, the software is sometimes subjected to service releases,
=== End-of-life {{Anchor|EOL|End of life}} ===
When software is no longer sold or supported, the product is said to have reached end-of-life, to be discontinued, retired, deprecated, abandoned, or obsolete, but user loyalty may continue its existence for some time, even long after its platform is obsolete—e.g., the
▲When software is no longer sold or supported, the product is said to have reached end-of-life, to be discontinued, retired, deprecated, abandoned, or obsolete, but user loyalty may continue its existence for some time, even long after its platform is obsolete—e.g., the [[Common Desktop Environment]] and Sinclair [[ZX Spectrum]].
After the end-of-life date, the developer will usually not implement any new features, fix existing defects, bugs, or vulnerabilities (whether known before that date or not), or provide any support for the product. If the developer wishes, they may release the source code, so the platform will live again, and be maintained by volunteers, and if not, it may be reverse-engineered later when it becomes [[abandonware]].
== History ==
Usage of the "alpha/beta" test terminology originated at
Major public betas developed afterward, with early customers having purchased a "pioneer edition" of the WordVision word processor for the
In February 2005,
== See also ==
{{Portal|Computer programming}}
*
*
*
*
*
*
*
*
*
==References==
{{Software distribution}}
[[Category:Software release| ]]
| |||