Software Engineering – Chapter 2 Vocabulary

29 vocabulary flashcards covering key terms and definitions from the Chapter 2 lecture on Software Engineering processes, methods, and best practices.

Software Engineering (IEEE)

The systematic, disciplined, and quantifiable application of engineering approaches to the development, operation, and maintenance of software, and the study of such approaches.

Layered Technology

The view of software engineering as four interrelated layers—quality focus, process, methods, and tools—working together to produce reliable software.

Quality Focus

The top layer in the software‐engineering stack that emphasizes building software products that meet explicit standards of excellence.

Process

A series of actions or operations used to produce a software product; provides the framework for management, methods, work products, and quality.

Key Process Area (KPA)

A critical area within the software process that must be mastered to achieve effective project management and control.

Method

An orderly, technical "how-to" procedure for building software, covering tasks such as requirements analysis, design, coding, testing, and support.

Tool

Software or automated system that supports or enacts a software-engineering method.

Process Framework

The overarching structure containing framework activities, tasks, work products, milestones, deliverables, and quality-assurance checkpoints.

Framework Activities

Core activities present in every software process—communication, planning, modeling, construction (code generation & testing), and deployment.

Umbrella Activities

Supporting actions that span the entire software process, such as project tracking, risk management, quality assurance, configuration management, and measurement.

Communication

A framework activity focused on understanding stakeholders and gathering requirements through interaction.

Planning

A framework activity that creates schedules, estimates resources, and defines the project roadmap.

Modeling

The activity in which analysis and design models are produced to represent data, behavior, and structure of the software.

Construction

The framework activity combining code generation and testing to transform designs into a working system.

Deployment

Delivering the completed software to users and supporting its installation, training, and operational transition.

Software Project Tracking and Control

Umbrella activity that monitors progress and ensures the project stays on schedule and within budget.

Risk Management

Umbrella activity that identifies, analyzes, and mitigates potential problems that could threaten project success.

Software Quality Assurance (SQA)

Umbrella activity employing planned review and audit practices to ensure the software meets quality standards.

Technical Review

A formal, peer-based examination of work products to detect defects early and improve quality.

Measurement

Umbrella activity that collects and analyzes quantitative data to inform decisions and improve the process.

Software Configuration Management (SCM)

Umbrella activity that controls changes to software artifacts to maintain integrity and traceability.

Reusability Management

Umbrella activity concerned with creating, cataloging, and applying reusable software components.

Work Product Preparation & Production

Activities focused on creating, formatting, and distributing documents, models, and other project deliverables.

Polya’s Problem-Solving Steps

Four essential practices—understand the problem, plan the solution, carry out the plan, and examine the result—adapted to software engineering.

Understand the Problem

Identify stakeholders, unknowns, sub-problems, and possible graphical representations to clarify requirements.

Plan the Solution

Search for patterns, reusable elements, sub-problem definitions, and create a design model that guides implementation.

Carry Out the Plan

Develop source code traceable to the design and ensure each component is provably correct through review or formal proof.

Examine the Result

Test and validate that the implemented software meets all data, function, and feature requirements of stakeholders.