Terms to Know Flashcards
Requirement
A singular documented physical or functional need that a particular design, product, or process aims to satisfy.
It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or another stakeholder. Requirements can come with different levels of specificity; for example, a requirement specification or requirement “spec” (often imprecisely referred to as “the” spec/specs, but there are actually different sorts of specifications) refers to an explicit, highly objective/clear (and often quantitative) requirement (or sometimes, set of requirements) to be satisfied by a material, design, product, or service.
UAT
User Acceptance Testing (UAT)
The final stage of any software development life cycle. This is when actual users test the software to see if it is able to carry out the required tasks it was designed to address in real-world situations. UAT tests adherence to customers’ requirements. UAT testers aim to validate changes that were made against original requirements. Also referred as Beta testing.
GUI
graphical user interface
SDLC
Software Development Life Cycle
In software engineering, a software development process is a process of dividing software development work into smaller, parallel, or sequential steps or subprocesses to improve design, product management, and project management. It is also known as a software development life cycle (SDLC). The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.
