n
(countable, computing) The process of locating data in memory.
v
(transitive, computing) To refer to a location in computer memory.
adj
(programming) Of heuristics, source code optimization techniques, etc.: exploiting every opportunity to be applied.
adj
(chiefly software engineering) Of or relating to agile software development, a technique for iterative and incremental development of software involving collaboration between teams.
n
(software engineering) The first versions of a program, usually only available to the developer, and only tested by the developer.
n
(software, testing) A process where a software application approaching full functionality is made available to a group of sophisticated users.
n
(computing, technology) An early version of a program or application, typically unstable, but useful to show what the product will do. Sometimes this stage is referred to as a preview version. Sometimes no more features are added after this release, but bug fixes continue. This release comes after a pre-alpha version and before a beta version. As opposed to a beta version an alpha version is usually not feature complete.
n
(programming) The strategy of writing code so as to minimise the possibility of error.
n
(British spelling) Alternative form of application program [(computing) A computer program written to solve a particular problem or to be used in a particular user-defined application.]
n
Alternative form of application program [(computing) A computer program written to solve a particular problem or to be used in a particular user-defined application.]
n
(computing) automatic installation
n
(by extension) A quantity of anything produced at one operation.
v
To carry out a batch edit
v
edit in batch; change a whole group of items in one
n
(computing, video games, countable) Software in such a phase; a preliminary version.
n
(software) Someone who performs beta testing.
n
(computing) An early version of a program or application that contains most of the major features, but is not yet complete. Sometimes these versions are released only to a select group of people, or to the general public, for testing and feedback. This is the second major stage of development following the alpha version, and comes before the release candidate.
n
(software engineering) The application of agile principles and practices to larger, complex projects, often with teams working from multiple locations.
n
(software engineering) A form of integration testing in which the individual modules are linked together and tested as a whole, without first being tested independently.
n
(software, testing) Any form of testing in which knowledge of the internals of the system being tested are unknown and unimportant.
adj
(software engineering) Being a development that has to integrate with legacy systems.
n
(computing) A tag or value included in a request (such as a URL) purely to differentiate it from previous requests and thus avoid receiving a cached response.
n
(software engineering) The frequency of regular product releases.
n
(programming) A pop-up reminder of the signature of a function or method, to aid the programmer while writing code.
n
(software engineering) combined practices of Continuous Integration and Continuous Delivery.
n
(programming) somebody who writes generally clean code.
n
(software engineering, attributive) Being or relating to a software development process intended to produce software with a certifiable level of reliability.
n
(computing) A testing arrangement in which a beta test version of software is distributed to a small group of testers.
n
A programmer who uses COBOL.
n
(software engineering) The practice, or an instance, of identifying and verifying the choice of algorithms, coding styles and compliance with the software design.
v
(programming) To debug together.
n
(software compilation) A computer program which transforms source code into object code.
n
(software) an approach in software engineering where teams produce software in short cycles, ensuring that the software can be reliably released at any time
n
(software engineering) The practice of merging all branches to a shared mainline several times a day.
n
(software, design) Synonym of design by contract
n
(software engineering) The degree of reliance between two or more software modules.
n
(computing) A file holding the contents of memory at the point when a program crashed, possibly useful in debugging.
n
(computing) A compiler that generates code for a platform other than the one it runs on.
n
(programming) A computer program that helps the user to test and debug other programs, by enabling their step-by-step execution controlled by the user, setting of breakpoints, and monitoring values of variables.
n
(electronics, computing) the original software programming settings as set by the factory
v
(computing, in operating systems derived from Unix) To operate on the file or directory pointed to by a symbolic link, rather than on the link itself.
n
(computing) A software developer; a person or company who creates or modifies computer software.
n
(computing) A developer's feeling about their tools, processes, constrains etc, and how it impacts productivity.
n
An initiative by a company to promote the development of software for one of its platforms or systems.
n
The situation where a movie, a piece of software, etc. is mired in problems that delay its production and release.
n
(computing) A set of development tools that allow the creation of software for a particular platform or framework.
n
(software engineering) A software development method that stresses communication and collaboration between software developers and other information technology professionals.
n
(software engineering) developer relations
n
(software engineering) An augmentation of the DevOps approach that allows for the integration of security practices.
n
(computing) A piece of software responsible for assigning priorities and resources to tasks waiting to be scheduled.
adj
(software engineering) Of code, having the quality of adhering to the principle of DRY; containing as little repetition as possible.
v
(programming, databases) To fetch data as early as possible, before it used.
n
(computing) A program or algorithm for escaping text.
n
(computing) A component of a system that executes or runs something.
n
(computing) A computer programmer who uses extreme programming techniques.
n
(software engineering) A software engineering methodology that promotes agility and simplicity, typically involving pair programming and a cycle of frequent testing and feedback.
n
(software engineering) A structured process of trying to find defects in source code, specifications, and other design documents.
n
(computing) A beneficial capability of a piece of software.
adj
(computing, hardware, software) Of products, created or published by the company responsible for the platform on which it is released (or its internal developers), as opposed to third-party.
n
(software, testing) A testing methodology in which random data (“fuzz”) is supplied as input to a program.
n
(software, testing) Alternative form of grey-box testing. [(software, testing) A combination of black-box testing and white-box testing, where knowledge about the internal data structures and algorithms for purposes of designing tests while executing those tests at the user, or black-box, level.]
adj
(software engineering) Being a completely new development, without the need to integrate with legacy systems etc.
v
(computing) To use a program such as grep to search in a file.
n
(software, testing) A combination of black-box testing and white-box testing, where knowledge about the internal data structures and algorithms for purposes of designing tests while executing those tests at the user, or black-box, level.
n
(software engineering) In agile software development, the reviewing and prioritization of items in the development backlog.
v
(computing) To insert an unchangeable program into a device; to hard-wire.
v
(computing) To implement a feature in hardware rather than in software so that it cannot easily be changed.
n
(programming) A person who programs in Haskell.
n
(topology) The simplest interlinkage of two loops; two interlinked rings.
v
(programming) To load data from a database record into an object's variables
adj
(computing) Done or featured in an application.
n
(programming) The insertion of program code into an application, URL, hardware, etc.; especially when malicious or when the target is not designed for such insertion.
n
(software) the phase in software testing that occurs after unit testing and before validation testing, where individual software modules are combined and tested as a group.
adj
(computer science) Responding to the user.
n
(computing, programming) A program written in Perl that outputs the text Just another Perl hacker, usually programmed in an obfuscated manner so that the output is not obvious until it is run.
n
(computing) A task, or series of tasks, carried out in batch mode (especially on a mainframe computer).
n
(software testing) a testing approach that separates the test automation implementation from the test case design by defining a keyword for each action in the test case that can be used by the test automation assistant without having any programming knowledge.
v
(software compilation) To combine objects generated by a compiler into a single executable.
n
(computing) A program that links modules together, by resolving calls or references to external names, to form a single executable program
n
(often attributive) The point at which multiple binary objects are merged into a larger program; literally, the time at which they are linked.
n
(software compilation) The act or result of linking: the combination of multiple object files into one executable, library, or object file.
n
(computing) A utility program that combines load modules (typically of subroutines) &c to produce an executable program
n
(software compilation) A computer program that takes one or more objects generated by compilers and assembles them into a single executable program.
n
A mechanism of linked components.
n
(computing) The executable form of a program that is produced by a linkage editor, taking as input the output of a compiler and/or assembler
n
(computing) A program that prepares other programs for execution.
adj
(computing) Storing data in such a way that modifications are kept in a buffer rather than overwriting the previous version.
n
(computing) A file that serves as a log.
n
(software engineering) A software development approach where the whole team works on a single project at a single computer at the same time.
n
(software engineering) Mob programming.
n
(computing) a feature that already exists in the environment in which an application is run.
v
(transitive, computing) To direct the central processing unit to seek information at a certain location in memory.
n
A program or application that is not feature-complete and is not usually released to the public. Developers are usually still deciding on what features the program should have at this stage of software development. This stage comes before the alpha version, and is the first software development stage given to a program.
n
(computing) A system or process that prefetches data.
adj
(computing) Of software, already installed on a personal computer at the time of purchase.
v
(computing, transitive) To measure the performance of various parts of (a program) so as to locate bottlenecks.
n
(computing, informal) A program.
n
(US) Alternative form of programmer [(computing) One who writes computer programs; a software developer.]
n
planned obsolescence implemented through deliberate limitations in software or hardware
n
(computing) One who writes computer programs; a software developer.
n
(computing) A lightweight stackless thread used in concurrent programming.
v
(computing, transitive) To add to a queue data structure.
n
Alternative spelling of REM [(computing) A remark (programming language statement used for documentation).]
n
(computing) A permission to access files or directories where the user is only allowed to read or view, not to make changes.
n
(computing) The set of records read from a database, typically by a single transaction
n
(computing) A piece of software that implements a specification of requirements and whose main purpose is to help in the creation of other software implementations of the specification by serving as a point of reference rather than being put to directly productive use.
n
(software engineering) Testing a program after a modification to ensure that areas that should not be affected by the update behave as they did in previous versions.
n
(programming) The mode of the compiler where the code is compiled for the end user, most often with optimisations.
n
(computing) The assigning of addresses to variables either at linkage editing, or at run time
n
(computing) A program or process that performs renaming.
n
(computing) The period of time between a request for a service and the associated response; typically the request is caused by a user at a terminal hitting the return key, and the response is displayed on a screen
n
(computing) A method of dividing labor between several similar subsystems, assigning tasks to each of them in turn in an attempt to use resources more equitably.
n
(computing) a set of procedures prepared by an administrator for the day-to-day maintenance and exception handling of an IT system
n
(software engineering) A hybrid form of integration testing that combines top-down and bottom-up approaches.
n
(programming) A software tool that creates the basic framework or template for a new project.
n
(programming) A user of the Scratch visual programming language.
n
(software engineering) An iterative and incremental agile software development method for managing software projects and product or application development.
n
(computing) A software error that occurs when a program attempts to access a memory location that it is not permitted to access.
adj
(computing) Of software: capable of generating new versions of itself.
n
(computing, slang) A serial number, esp. one required to activate software.
n
A unique number, assigned to a particular unit of some product, to identify it.
n
(computing) A function that is provided by one program or machine for another.
n
(computing, slang) The antipattern of adding similar or identical source code in multiple parts of a software project, rather than implementing the desired functionality in a single place to make it reusable.
n
(computing) Synonym of symbolic link
n
(software engineering) The level of confidence that software is free from vulnerabilities, either intentionally designed or accidentally inserted at any time.
n
(computing) the task of controlling and tracking changes made to software files
n
The subfield of engineering concerned with applying a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software.
n
(development, software) Alternative form of software lifecycle
n
(development, software) Ellipsis of software development lifecycle..
n
(computing) A technology that handles access to computer files containing source code so that several users can work on the files without interfering with each other's changes.
n
(software engineering) In Agile software development, a period of development of a fixed time that is preceded and followed by meetings.
n
A particularly skilful computer programmer.
n
Alternative spelling of swap file [(computing) A file on disk used as auxiliary memory.]
n
(software engineering) The implied cost of additional future work caused by choosing an easy but inferior solution originally.
n
(computing) Any of a set of conditions and variables used to test an application.
n
(software engineering) A software development process that relies on the repetition of a minimal development cycle where the developer writes an (initially failing) automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass that test, and finally refactors the new code to acceptable standards.
n
(computing) A system that parses an input stream into its component tokens.
adj
(computing) Designed for easy interoperation with software tools.
n
(computing) An atomic operation; a message, data modification, or other procedure that is guaranteed to perform completely or not at all (e.g. a database transaction).
n
(software engineering) A software testing methodology in which individual tests (unit tests) are developed for each small part of a program.
n
(software engineering) A usage scenario for a piece of software; often used in the plural to suggest situations where a piece of software may be useful.
n
(computing) any of a large range of software, often included with the operating system, that runs specific tasks associated with the computer or its environment
n
(computing) Synonym of test suite
v
(transitive, software engineering) As the software vendor, to bundle one's own, possibly modified version of dependencies with a standard program.
n
(computing) A particular revision (of software, firmware, CPU, etc.).
n
(software engineering) A system responsible for managing modifications and additions to digital works, giving each revision a time-stamp and showing its difference to the previous revision.
n
(software engineering) An initial, bare-bones implementation of a system or application which provides only the basic core functionality, in order to be able to demonstrate a minimal working product to be further fleshed out later.
n
(software engineering) The process of inspecting algorithms and source code by following paths through the algorithms or code as determined by input conditions and choices made along the way.
n
(software, testing) The testing of the internal structure, rather than the functionality, of a system.
n
(topology) One of the most basic interlinkages of two loops; a link with one ring passing through the two lobes of a singly twisted loop.
Note: Concept clusters like the one above are an experimental OneLook
feature. We've grouped words and phrases into thousands of clusters
based on a statistical analysis of how they are used in writing. Some
of the words and concepts may be vulgar or offensive. The names of the
clusters were written automatically and may not precisely describe
every word within the cluster; furthermore, the clusters may be
missing some entries that you'd normally associate with their
names. Click on a word to look it up on OneLook.
Our daily word games Threepeat and Compound Your Joy are going strong. Bookmark and enjoy!
Today's secret word is 10 letters and means "Practical approaches prioritizing results, efficiency." Can you find it?