Enterprise software
software targeted towards corporations/organisations
Enterprise software, also known as enterprise application software (EAS), is computer software that has been specially developed or adapted to meet the complex requirements of larger organizations. Enterprise software is an integral part of a computer-based information system, handling a number of business operations, for example to enhance business and management reporting tasks, or support production operations and back office functions. Enterprise systems must process information at a relatively high speed.
Services provided by enterprise software are typically business-oriented tools. As companies and other organizations have similar departments and systems, enterprise software is often available as a suite of customizable programs. Function-specific enterprise software uses include database management, customer relationship management, supply chain management and business process management.
Definitions and industry
The term enterprise software is used in industry, and business research publications, but is not common in computer science. The term was widely popularized in the early 1990s by major software vendors in conjunction with licensing deals with the show Star Trek. In academic literature, no coherent definition can be found. The computer historian Martin Campbell-Kelly contemplated in 2003 that the growth of the corporate software industry is not well understood.
The public source identifies “Enterprise software” as software targeted towards corporations/organisations. This brief keeps that definition visible, then builds a research path around Enterprise, software and targeted.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Enterprise software”, the useful work is to connect “software targeted towards corporations/organisations” to the records capable of establishing context and consequence.
Stable identifiers, scientific names and standards terminology offer the best bridge between this overview and specialist evidence. The source revision retrieved here is dated Jul 7, 2026. The linked authority identifier is Q1318054. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2003.
Scientific names, classifications and consensus can change while older terminology persists in catalogues and historical literature. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Enterprise software”, its source revision and the description used here.
- Expand the search: follow Enterprise software primary sources, Enterprise software archive and Enterprise research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Enterprise software”?
- Has classification or technical consensus changed since the cited source?
- Which observation, specimen, dataset or publication supports the account?
Search terms from this dossier
This entry incorporates text from “Enterprise software” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.