CS 3354 Exam 1

Software engineering is an engineering discipline that is concerned with all aspects of software production.

Maintainability, Dependability & Security, Efficiency, Acceptability.

To ensure that software engineers act responsibly, considering the societal and ethical implications of their work.

Insulin Pump, MentCare, Weather Station, iLearn.

Monitors blood sugar levels and injects the correct insulin dosage.

Incorrect dosage can lead to serious health consequences such as coma or organ damage.

It is a patient information system for mental health care.

Collects weather data like temperature, wind speed, and pressure and transmits it via satellite.

A digital learning environment that integrates tools for online education.

Specification, Development, Validation, Evolution.

A sequential software process model with distinct phases including Requirements, Design, Implementation, Testing, and Maintenance.

A software process where the system is developed in small increments and delivered in stages.

An iterative approach that emphasizes flexibility, customer collaboration, and working software over documentation.

A fixed time period in which a Scrum team develops a working increment of the product.

Product Owner, Scrum Master, Development Team.

A practice where tests are written before the code itself to ensure correct implementation.

Statements that describe what the system should do, such as features and operations.

Constraints on system behavior, including performance, security, and usability.

A UML diagram that represents interactions between a system and external actors.

The interactions between objects over time.

A UML diagram that represents the static structure of a system using classes and relationships.

A general solution to a recurring design problem, such as MVC (Model-View-Controller).

Logical, Process, Development, Physical.

An approach that builds software using existing components or COTS (Commercial Off-The-Shelf) systems.

A model where software code is publicly available for anyone to use, modify, and contribute to.

Testing individual components of a system to ensure they function correctly.

Testing the entire integrated system to verify that it meets the specified requirements.

A form of user testing that determines if the software is ready for deployment.

A testing method where the internal structure of the system is not known; testers focus on inputs and expected outputs.

A testing method that examines the internal logic and structure of the code.

Ensuring that the software meets its specifications and is built correctly.

Ensuring that the software meets user needs and expectations.

A flaw in the software that causes incorrect or unexpected behavior.

A technique where two programmers work together at the same workstation, one writing code and the other reviewing it.

A development practice where code is frequently merged and tested automatically to detect issues early.

The process of adapting and modifying software to meet new requirements over time.

A practice that tracks and controls changes in software to maintain consistency.

An abstract representation of a software development approach, such as Waterfall or Agile.

Creating an early version of a system to refine requirements and design before full-scale development.

The process of improving code without changing its functionality.

A prioritized list of features and requirements for a project.

A graphical representation of work remaining versus time in a Scrum project.

The ease with which software can be modified or extended.

An instance of a class that encapsulates data and behavior.

A contract that defines methods a class must implement.

To validate functionality, identify defects, and ensure reliability.

It helps find errors, ensures quality, and prevents failures in production.

Anyone affected by or involved in the development of a software system, such as users, developers, and managers.

A development approach where software is represented as a set of models that can be transformed into executable code.

An Agile methodology that emphasizes customer involvement, frequent releases, and rigorous testing.

A documented need or functionality that a system must provide.

A diagram that shows how a system interacts with external entities.

A UML diagram that represents workflows or processes.

Checking whether software meets user needs and expectations.

Ensuring that software functions as specified in its documentation.

The process of updating software to meet new requirements or fix defects.

A reusable, self-contained unit of software functionality.

Combining different system components to function as a whole.

A diagram that represents the workflow and activities in an organization.

The process of identifying, analyzing, and mitigating risks in a project.