Untitled Quiz

Containers grouping elements, potentially classifiable items.

Describing objects based on identified classes in the domain model.

Shows a system's behavior over time.

Shows user interaction with the system through message exchange.

One-directional communication between objects, potentially with parameters.

Shows time-ordered interactions between objects via messages.

Collection of interacting objects, showing behavior in context.

Shows object states and transitions during the application's lifecycle.

The ease of making modifications to software to fix bugs, improve performance, or adapt to changes.

Planned, monitored, and controlled attribute of software, ensuring it meets expected quality requirements.

Establishes procedures & standards to ensure software is developed correctly from the start, focusing on preventing defects through standardized processes and audits.

How easy and satisfying it is for users to use the software.

Identifies and corrects defects in software through activities like testing and reviews. It's reactive.

The ability to move software from one environment to another, including how easy it is to install on different platforms.

Define criteria for what 'quality' means in a specific context.

Protecting software data and preventing unauthorized access or malicious behavior.

Defines procedures, tools, and activities needed to ensure software meets established requirements.

A focus on adapting quickly to changes, collaborating, and continually delivering value.

Expectations regarding functionality, performance, and security within software.

The methods, procedures, and tools used to develop software.

Techniques and instruments used to implement quality assurance, such as integration testing and code reviews.

Individuals and interactions over processes and tools, Working software over comprehensive documentation, Customer collaboration over contract negotiation, Responding to change over following a plan.

Activities that ensure software quality through identification, analysis, and correction of defects.

Measurements of software quality, including defects per thousand lines of code and development cycle times.

A set of principles that guide teams to create software in an iterative and incremental way, promoting flexibility and continuous improvement.

The practice of frequently delivering functional versions of software in short time periods (iterations or sprints).

Agile teams adjust scope, requirements, and priorities as new needs emerge.

Clients are actively involved throughout the development process to ensure the final product meets real needs and evolves with expectations.

Agile teams are responsible for planning, execution, and delivery within each iteration.

Teams reflect on what worked well and what could be improved at the end of each iteration, adjusting processes and practices for the next cycle.

A framework that divides work into fixed-length sprints (typically 2-4 weeks), with daily stand-up meetings for coordination and a sprint review.

A visual system for task management to improve workflow, limit work in progress (WIP), and focus on continuous delivery.

Condition of an object during an activity.

Significant event that might cause a state change.

Relationship between two states, showing actions for transition.

UML diagram showing system structure (classes, attributes, methods, relations).

Group of objects with shared characteristics and behaviors.

General relationship between classes; minimal semantic content.

Part-of relationship; one entity as collection of parts.

Components belong to only one object; destroyed when object is destroyed.

Representation of a relationship where a class inherits properties and methods from another class (parent class).

A UML diagram showing the flow of actions and decisions in a system, highlighting the sequence of activities and conditions.

The starting point of execution in an activity diagram.

The ending point of execution in an activity diagram.

A single, indivisible step in an activity diagram.

A point in an activity diagram where alternative paths are chosen based on conditions.

Independent parallel execution paths in an activity diagram, often triggered by divisions.

A complex activity broken down into individual actions, which is further represented by a separate activity diagram.