Introduction to Software Engineering

Flashcards covering key terms and definitions from the lecture on Software Engineering.

Software Engineering

An area of Computer Science related to techniques, methods, practices, and tools for systematic software development.

IEEE Standard 610.12

Defines software engineering as the application of engineering principles to software.

Instructions

Computer programs that, when executed, provide desired features, functions, and performance.

Data Structures

Organized formats for storing and managing data used by programs.

Documentation

Information that describes the operation and use of computer programs.

System Software

Programs designed to service other programs, such as operating systems and utilities.

Application Software

Standalone programs that solve specific business needs or facilitate business operations.

Embedded Software

Software contained within a product, controlling its features and functions, typically not directly interacted with by the user.

Product-line Software

Software composed of reusable components designed for multiple customers.

Web/Mobile Applications

Software delivered through web browsers or designed for mobile devices.

Artificial Intelligence Software

Software that utilizes heuristics to solve complex problems, often based on machine learning.

Waterfall Process Model

A sequential model where requirements are defined at the start, followed by planning, modeling, and deployment.

V-Model

A variation of the waterfall model that emphasizes testing at various stages.

Prototyping Process Model

A model where initial requirements are gathered and a prototype is developed for stakeholder feedback.

Spiral Process Model

An evolutionary approach combining iterative development with systematic risk analysis.

Unified Process Model

A use-case-driven and iterative method that emphasizes architecture and stakeholder involvement.

Requirements Engineering

The process of developing a complete requirements specification that describes user and stakeholder needs.

Functional Requirements

Requirements that define specific behaviors or functions of a system.

Non-Functional Requirements (NFR)

Criteria used to judge the operation of a system, not specific behaviors.

User Stories

Short descriptions of features from the perspective of the user, typically formatted to include the actor, action, and goal.

Use Cases

Descriptions of how users interact with a system to achieve a goal, often visualized in diagrams.