Untitled Quiz

The processes and activities that determine quality policies, objectives, and responsibilities for a project to meet its needs.

Fitness for use (meeting customer needs) and conformance to requirements (meeting predefined standards).

Focuses on the design's intent and the degree of functionality.

Defining quality requirements, documenting compliance methods, and allocating time/budget for testing.

Auditing processes to ensure adherence to the quality management plan and collecting metrics.

Standards essential for the project and the product.

Document containing quality standards, processes, metrics, and tools to measure adherence.

Allowable variations from the quality standards for a project.

An organization with well-defined software processes, consistent across projects, and continuously improved based on experience.

A defined set of steps and activities involved in creating software.

Measurable characteristics of a software product, like reliability, usability, and performance.

An immature organization with ad-hoc processes and project success dependent on individuals rather than processes.

A software organization with basic processes and policies to manage projects, enabling repeatable success across teams.

Measurements used to gauge software quality by defining tolerances and detecting defects.

Specific outputs or items (e.g., software, documentation) of a software project.

Quality plan prioritizing customer requirements as quality attributes, then translating those into quantifiable metrics.

Project Quality Management; a management approach encompassing both project deliverables and processes.

The activities undertaken to achieve project deliverables (e.g., scope management, risk management, requirements analysis).

A management theory examining workflow to improve efficiency by breaking down tasks and optimizing each subtask.

A quality management guru known for the 14 Points on Quality Management, emphasizing worker training and statistical methods.

A management approach aiming to improve quality and productivity throughout an organization.

A framework for quality management, encompassing planning, improvement, and control.

After WWII, Japan struggled with a reputation for inferior products, necessitating a focus on improving their manufactured goods to export success.

A process for controlling changes to software throughout the development lifecycle

Ensuring that software meets quality standards and requirements

A plan that outlines how quality is ensured in project deliverables and processes

Beliefs and principles related to the pursuit of quality, emphasizing customer satisfaction and process improvement

The process of monitoring project progress and ensuring that it aligns with plans and objectives

Development and management of plans to achieve software project goals

Managing and evolving the requirements for a software project throughout its lifecycle

Software processes and products for which metrics for measurement, assessment, and estimation of productivity and quality can be established

Documented agreements, protocols, or rules outlining technical specifications or criteria for products, services, processes, or materials to meet their intended purpose.

Measurements of defects introduced by processes involved in creating deliverables.

Metrics that describe intrinsic quality of deliverables, and the final product, like Mean Time To Failure (MTTF).

Metrics used to determine if software or project deliverables meet 'fitness for use' and 'requirements conformance'.

An undesirable behavior of a product or process.

A defect in software that causes a computer system to malfunction during operation.

Activities ensuring project deliverables function as planned and meet intended scope as defined.

Ensuring project activities follow correct procedures to meet requirements before final testing.

Technical, Business, and Management reviews to ensure project adheres to standards, functionality, and progress.

Ensuring IT solution meets specified requirements, like GUI standards, coding, and documentation.

Determining if the system meets customer expectations and performs as intended.

Testing approaches (unit, integration, systems, acceptance) to confirm if the system meets customer needs.

Monitoring project quality activities to eliminate issues and improve processes.

Visual tools like control charts to track process behavior over time (in product-related quality control activities).

The boundaries in a control chart that indicate acceptable process variability.