Software Engineering Lecture_1

Vocabulary flashcards covering key concepts, terms, and definitions from the lecture notes on software engineering, Agile, UML, and process models.

Software engineering

A team-based discipline guiding the full software lifecycle (conception to operation and maintenance) using systematic methods; not just coding.

Process model

A framework describing who does what, when, and how to achieve a software objective.

Waterfall model

A traditional, linear software process with sequential phases (requirements, analysis, design, implementation, testing); rigid to change and often results in late testing.

V-model

A variation of Waterfall where each development phase has a corresponding testing activity to validate results at every level.

Iterative/incremental models

Approaches that develop software through repeated cycles and incremental additions, often using prototyping to refine requirements.

Prototyping

Creating a simple or non-working model to elicit user feedback and clarify requirements before full development.

Spiral model

An iterative model emphasizing risk analysis at each cycle; suitable for high-risk or regulated domains but can be costly.

RUP (Rational Unified Process)

An iterative, use-case–driven framework emphasizing architecture and modeling in software development.

UML

Unified Modeling Language; a standard notation with diagrams to model software structure and behavior before coding.

Use case diagram

A UML diagram showing actors and their interactions with the system to capture requirements.

Sequence diagram

A UML diagram depicting how objects interact in time order to realize a workflow or behavior.

Class diagram

A UML diagram illustrating the static structure of a system: classes, attributes, methods, and relationships.

Low-fidelity prototype

A quick, simple mock-up (often paper or basic UI) used to test concepts and gather feedback.

User stories

Lightweight, informal descriptions of features from an end-user perspective, used in Agile contexts as alternatives to formal requirements.

Requirements

Needs and constraints the software must satisfy; can be formal requirements or user stories in Agile contexts.

Agile Manifesto

Foundational values for Agile development: individuals and interactions, working software, customer collaboration, and responding to change.

Agile

An umbrella mindset for flexible, iterative development; not a single process but a family of methods.

Scrum

A popular Agile framework with defined roles, artifacts, and ceremonies to manage work in sprints.

Quality (external vs internal)

External quality includes user-facing attributes like usability and availability; internal quality covers code quality and maintainability.

Usability

The ease with which users can learn and use the system; a key external quality attribute.

Internal quality

Code quality aspects such as readability, simplicity, and maintainability that affect the system's architecture.

Test-driven development (TDD)

Writing tests before code to guide design and ensure testability and quality.

Tollgate

A formal milestone where submitted work is reviewed; passing allows progress, failing requires resubmission with feedback.

Configuration management

Practices to track and control changes to software artifacts, including version control and baselines.

Version control

A system that records changes to files over time, enabling history, branching, and collaboration.

Group agreement

An explicit plan within a team outlining collaboration norms, communication channels, and working expectations.

Oral exam

A group-based spoken assessment where teams present and answer questions about their project.

LEGO Scrum simulation

A hands-on activity using LEGO to model Scrum processes and practice teamwork and agile reasoning.

Generative AI in software engineering

AI tools used to generate content; the course warns against creating content from scratch with AI and emphasizes original, grounded work.

Stakeholders

People or groups with an interest in the project whose needs guide requirements and decisions.