CPE 3600 Midterm 1

Agile

An iterative approach to software development that emphasizes flexibility, collaboration, customer feedback, and rapid delivery of functional software.

Agile Manifesto

A set of guiding principles for Agile software development, emphasizing individuals, working software, customer collaboration, and responding to change.

Waterfall

A sequential and rigid software development methodology that requires full completion of one phase before moving to the next.

Sprint

A time-boxed period (usually 1-4 weeks) during which specific work is completed and ready for review in Agile development.

Stand-up Meeting

A daily meeting in Scrum to synchronize team members and discuss progress, roadblocks, and plans for the day.

Product Backlog

An ordered list of features, enhancements, and fixes needed for the product in Agile development.

Sprint Backlog

A subset of the product backlog items that the team commits to completing in a sprint.

User Story

A high-level requirement focused on user needs, typically structured as "As a [type of user], I want [goal] so that [reason]."

Scrum Master

The role responsible for facilitating the Scrum process, ensuring adherence to Agile principles, and supporting the team.

Project Owner

The role that represents stakeholders, manages the product backlog, prioritizes needs, and ensures the team delivers value.

Good Requirements

Characteristics of good requirements include being clear, testable, and feasible.

Extra-Functional Requirements

Specifications that define the system's operational qualities, such as performance, security, and usability.

EARS Template

A requirement writing template structured as "In the event that [condition], the system shall [action] to [result]."

High-Level Design

The overall structure and organization of a system, including its components and their interactions.

Sequence Diagrams

Diagrams that illustrate how objects interact in a particular scenario over time, detailing message flow.

Use Case

A detailed description of how users will interact with the system, including title, actors, preconditions, and flows of events.

CubeMX

A tool that simplifies configuration for embedded systems, providing a graphical interface and reducing human error.

USER Code Block

A section in CubeMX that allows developers to add custom code without being overwritten during reconfiguration.

HAL Interfaces

Familiar interfaces in hardware abstraction layers, including GPIO, TIM, ADC, USART, and I2C.

Interrupt Handler

A function that executes in response to hardware interrupts, managing events triggered by hardware.

SPI

A high-speed, synchronous, full-duplex communication protocol that requires more pins.

I2C

A multi-master communication protocol that supports multiple devices on two wires, slower than SPI.

UART

An asynchronous communication protocol that uses two wires (TX, RX) for point-to-point communication.

8N1 Protocol

A UART communication format consisting of 8 data bits, no parity, and 1 stop bit.

Baud Rate

The number of signal changes per second in a communication protocol.

RTOS

A real-time operating system that is deterministic and prioritizes time-critical tasks, guaranteeing response times.

CMSIS-RTOS

A standardized API for RTOS operations that promotes code portability and compatibility.

OS Tick

A periodic interrupt that increments a system timer, used for task scheduling and timekeeping in an RTOS.