Software Project Management & Software Process Models – Vocabulary Flashcards

A set of vocabulary-style flashcards covering key concepts from Chapter 13 (Software Project Management) and related software process models.

Project management

The act of planning, organizing, and managing a project to achieve predefined goals or outcomes within a set timeframe.

Need (in project management)

The reason for applying project management: to monitor progress, prevent distractions, and keep budgets on track.

Goals (project management)

End results that satisfy the customer’s needs, meet target milestones, maintain team morale, and ensure resources are available and used effectively.

POMA (Phases of Project Management)

Planning, Organizing, Monitoring, and Adjusting—the four phases guiding a project’s lifecycle.

Risk management

The process of identifying, analyzing, and responding to risks to keep a project on track toward its goals.

Risk identification

The process of identifying potential risks that could affect a project (causes include new methods, skill shortages, aggressive schedules, etc.).

Risk prioritization

Ranking risks by likelihood and impact, often using a risk matrix, to focus on high-impact/high-likelihood risks.

Risk mitigation

Actions taken to reduce threats and ensure resiliency, including avoidance, transfer, reduction, and acceptance of risk.

Risk matrix

A tool for prioritizing risks by plotting likelihood versus severity.

Trend analysis

Monitoring project data over time to identify patterns, predict issues, and guide decisions.

Regression analysis

A statistical method to determine which independent variables significantly impact a dependent variable.

Pie chart

A circular chart that shows proportions of categories in a data set.

Histogram

A chart that displays the distribution of a numeric variable using bars of different heights.

Time chart

A chart that shows data values or events over time.

Control chart

A time-series chart with upper and lower control limits to monitor process stability.

Pareto diagram

A bar chart ordered by frequency or impact to highlight the most significant factors.

Kiviat chart

Also called a spiderweb chart; compares multiple variables across several axes.

Trend Analysis

See Trend analysis (monitoring trends in project data over time).

Regression Analysis

See Regression analysis (statistical method to identify which variables influence outcomes).

Phase: Planning (POMA)

First step: understand project requirements and perform estimation of work, schedule, and resources.

Planning steps (POMA)

Define measurable goals, allocate resources, and identify risks and constraints.

Decomposition

Breaking a complex problem into smaller, more manageable parts.

Modularization

Separating a program’s functionality into independent, interchangeable modules.

Incremental iterations

An approach that combines iterative design with incremental builds, delivering progress in increments.

Software development plan (SDP)

A plan guiding the overall software development process, including requirements, architecture, design, testing, and deployment.

Functional requirements

What the program must do (inputs, outputs, processing, and interactions).

Nonfunctional requirements

How the system performs (ilities like reliability, performance, security, usability, modifiability).

Design constraints

Limitations that shape design choices, such as user interface, platforms, and input sizes.

CLI (command-line interface)

A text-based interface for interacting with the system and performing tasks.

GUI (graphical user interface)

A visual interface using graphical elements (icons, menus, windows) for user interaction.

Rationale: Algorithms

Decision on whether to use built-in language facilities or custom implementations based on performance and effort.

Unit testing

Testing individual modules or units to verify they work as intended.

Integration testing

Testing how modules work together after they have been unit tested.

Functional testing

Testing that verifies the software functions correctly as a complete unit or system.

Acceptance testing

Testing performed by clients to determine whether the system meets requirements and can be accepted.

Validation testing

Testing to determine if the product meets the intended use and user needs.

Verification testing

Internal testing to ensure the product is built correctly according to specifications.

Black box testing

Testing without knowledge of internal workings; focuses on inputs and outputs.

White box testing

Testing with knowledge of internal structure and code logic.

Work Breakdown Structure (WBS)

A decomposition of the project into discrete tasks and sub-tasks to organize work and estimate effort.

COCOMO (Constructive Cost Model)

A cost estimation model that calculates effort and schedule; modes include Organic, Semidetached, Embedded.

Function Point Analysis (FPA)

A technique to measure the functional size of software based on inputs, outputs, inquiries, files, and interfaces.

OO (Object-Oriented) effort estimation

Estimation based on the number of classes and UI types, with weights assigned to different UI styles.

Earned Value Analysis (EVA)

A method to assess project status using BCW, BCWS, BAC, BCWP, ACWP, EV, SV, and CV to measure schedule and cost performance.

BCW (Budgeted Cost of Work)

Estimated effort or cost allocated to a task.

BCWS (Budgeted Cost of Work Scheduled)

Sum of estimated effort scheduled to be completed by a specific date.

BAC (Budget at Completion)

Total planned effort or the sum of all BCWs for the project.

BCWP (Budgeted Cost of Work Performed)

Sum of estimated effort for tasks actually completed by a date.

ACWP (Actual Cost of Work Performed)

Sum of actual efforts expended for tasks completed by a date.

Earned Value (EV)

Amount of estimated work actually completed by a date; EV = BCWP/BAC.

Goal-Question-Metric (GQM)

A goal-oriented measurement framework: define goals, formulate questions, and derive metrics.

GQM levels

Goals (conceptual level), Questions (operational level), Metrics (quantitative level).

RUP (Rational Unified Process)

A software development framework with four phases (Inception, Elaboration, Construction, Transition) and building blocks (Roles, Work Products, Workflows, Tasks).

RUP entry criteria

Preconditions that must be met to start an activity, including required artifacts, people, tools, and definitions.

RUP exit criteria

Preconditions that must be met to complete an activity so downstream tasks can begin.

RUP building blocks

Roles (who), Work Products (what), Workflows (when), and Tasks (how) used to organize development.

Software Process Models

Structured approaches to software development (e.g., Waterfall, Incremental, Spiral, RUP) guiding activities and artifacts.

Waterfall model

A traditional, linear software process with sequential phases: requirements, design, implementation, testing.

Incremental model

Development in small increments, delivering core functionality first and expanding in subsequent releases.

Spiral model

A risk-driven model that repeats planning, risk analysis, engineering, and evaluation in cycles.

CMM (Capability Maturity Model)

A framework to assess software process maturity on a scale from 1 (Initial) to 5 (Optimizing).

CMMI (Capability Maturity Model Integration)

An integrated framework with two representations (Staged and Continuous) for process improvement across 25 process areas.

Mature vs. Immature organization

Mature: defined processes, coordination, and measurement; Immature: ad hoc, reactive, and often over budget.