1/31
Vocabulary practice flashcards covering software engineering principles, process models, requirements engineering, and the agile Scrum framework based on course lectures.
Software Engineering
An engineering discipline that is concerned with all aspects of software production from the early stages of system specification through to maintaining the system after it has gone into use.
Generic Products
Stand-alone software systems that are marketed and sold to any customer who wishes to buy them, where the specification of what the software should do is owned by the software developer.
Customized Products
Software systems commissioned by a specific customer to meet their own individual needs, where the customer owns the specification and makes decisions on required changes.
Maintainability
An essential software product attribute stating that software should be written in such a way that it can evolve to meet the changing needs of customers within an evolving business environment.
Dependability and Security
An essential software product attribute covering reliability, security, and safety, ensuring the software avoids causing physical or economic damage during system failure and blocks malicious access.
Software Efficiency
An essential attribute requiring that software does not make wasteful use of system resources such as memory and processor cycles, encompassing responsiveness, processing time, and memory utilization.
Acceptability
An essential software attribute requiring that software must be understandable, usable, and compatible with other systems used by the target user audience for which it was designed.
Software Process
A structured set of activities required to develop a software system, fundamentally involving specification, design and implementation, validation, and evolution.
Plan-Driven Processes
Processes where all process activities are planned in advance and progress is measured against this predetermined plan.
Agile Processes
Processes where planning is incremental and adaptive, making it easier to change the process to reflect evolving customer requirements.

Waterfall Model
A plan-driven software process model featuring separate and distinct sequential phases: requirements analysis and definition, system and software design, implementation and unit testing, integration and system testing, and operation and maintenance.
Incremental Development
A development approach where specification, development, and validation activities are interleaved rather than staged sequentially, reducing the cost of accommodating requirement changes.
Integration and Configuration
A reuse-oriented software engineering approach where systems are assembled and adapted from existing commercial-off-the-shelf (COTS) components or pre-existing systems.
Change Anticipation
A strategy where the software process includes activities designed to anticipate possible changes before significant rework is needed, such as building a prototype.
Change Tolerance
A strategy where the development process is designed so that modifications can be incorporated at relatively low cost, typically by altering only a single increment or future increments.
Throw-Away Prototype
An initial software version built to explore design options or elicit requirements that is discarded after development because it is unsuited for production and often lacks full documentation and rigorous quality standards.
Incremental Delivery
An approach in which the software is delivered to customers in successive increments containing subsets of prioritized functionality for actual end-user deployment and evaluation.

Requirements Engineering
The process of establishing the services that a customer requires from a system and the constraints under which it operates and is developed, encompassing elicitation, specification, and validation.
User Requirements
Statements written in natural language plus diagrams describing the services the system provides and its operational constraints, crafted primarily for customer and end-user understanding.
System Requirements
A structured document providing detailed, formal descriptions of a software system's functions, services, and operational constraints to define what should be built by developers.
System Stakeholder
Any person or organization affected by the system in some way and who holds a legitimate interest in its development and behavior.
Functional Requirements
Statements detailing the services the system must provide, how it reacts to specific inputs, how it behaves in particular situations, and what it should not do.
Non-Functional Requirements
Constraints placed on the services or functions offered by the system, such as performance, timing, development process mandates, and regulatory or security standards.
Requirements Management
The formal process of managing changing requirements during requirements engineering and system development, maintaining traceability links and assessing cost and impact.
Scrum
An agile, lightweight process framework used since the early 1990s within which teams address complex adaptive problems while creatively and productively delivering products of the highest possible value.

Project Noise Level
A framework mapping project uncertainty across dimensions of agreement on requirements and certainty of technology into Simple, Complicated, Complex, and Anarchy zones.
Sprint
A timeboxed iteration of 1 to 3 weeks (4 weeks at most) during which a development team builds a potentially shippable product increment.
Product Owner
The empowered Scrum role responsible for central product leadership, balancing stakeholder needs, deciding what to build and in what order, and managing economics across releases and sprints.

ScrumMaster
The Scrum role acting as the keeper of the Scrum process and facilitator for the team, serving as a coach, servant leader, process authority, interference shield, impediment remover, and change agent.
Product Backlog Item (PBI)
A placeholder for a requirement that represents desirable business value, initially broad and progressively refined into smaller, actionable items through ongoing conversations.
User Story
A structurally simple, conversational format used to express the desired business value of a product backlog item for both business and technical stakeholders.
Three Cs of User Stories
The three components defining user stories: Card (a physical or digital placeholder capturing intent), Conversation (continuous dialogue detailing requirements), and Confirmation (acceptance criteria and conditions of satisfaction).