UML Concepts and Methodologies Quiz

False (B)

Object Management Technology, Booch’s methodology, Object-Oriented Software Engineering

<p>black-box</p> Signup and view all the answers

<p>User's view = Functionalities available to users Structural view = System's organization and components Behavioral view = Dynamic interactions of the system Implementation view = Technical aspects of the system Environmental view = System's surroundings and dependencies</p> Signup and view all the answers

<p>9 (C)</p> Signup and view all the answers

<p>The input validation branch (A)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>To capture aspects important for some application while abstracting the rest.</p> Signup and view all the answers

<p>User's view</p> Signup and view all the answers

<p>transform-centred</p> Signup and view all the answers

<p>Afferent Branch = Input validation Efferent Branch = Output Central Transform = Data processing Transaction = A meaningful piece of work</p> Signup and view all the answers

<p>To create graphical models (D)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>The bubbles are all traversed during the same transaction.</p> Signup and view all the answers

<p>To capture alternate paths or scenarios (C)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>The highest level is called the context diagram. Its focus is on the application context and emphasizes the system's limits.</p> Signup and view all the answers

Signup and view all the answers

<p>Behavioral model (C)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>The different ways in which a system can be used by the users.</p> Signup and view all the answers

<p>occurring</p> Signup and view all the answers

<p>To define a piece of coherent behaviour without revealing the internal structure of the system (A)</p> Signup and view all the answers

<p>Structural view = Defines the types of objects and their relations Behavioural view = Captures object interactions Implementation view = Captures the components of the system and their dependencies Environmental view = Models component implementation on different hardware</p> Signup and view all the answers

<p>Static model (A)</p> Signup and view all the answers

<p>What the users can do using the system?</p> Signup and view all the answers

<p>extends</p> Signup and view all the answers

<p>Residence address, telephone number, and driving license number (A)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>A 22 caret gold coin</p> Signup and view all the answers

<p>day</p> Signup and view all the answers

<p>register-customer = Customer becomes registered register-sales = Purchase transaction is recorded select-winners = Identify prize winners reset-entries = Clear yearly purchase data</p> Signup and view all the answers

<p>The system displays a message indicating they have already registered (C)</p> Signup and view all the answers

<p>True (A)</p> Signup and view all the answers

<p>Customer Number (CN)</p> Signup and view all the answers

<p>To implement a login system for security (C)</p> Signup and view all the answers

<p>False (B)</p> Signup and view all the answers

<p>To inherit behavior from a similar parent use case.</p> Signup and view all the answers

<p>optional</p> Signup and view all the answers

<p>To make interaction diagrams easier to manage (B)</p> Signup and view all the answers

<p>Generalization, extends.</p> Signup and view all the answers

<p>variation</p> Signup and view all the answers

A set of principles and notations for modeling software systems.

A view that focuses on the functionalities offered to users, without revealing internal details.

A view that describes the structure of the system, including classes, objects, and their relationships.

A view that focuses on how the system behaves over time, such as interactions between objects.

A view that focuses on the implementation details of the system, such as programming languages and data structures.

A view that shows how the system interacts with its environment, including external systems and data.

An organization that promotes the use of UML as a standard.

A design model that takes a user-centric view of the application.

A graphical representation of a system's functions and data flow, showing how data is transformed and moved through the system.

The first level of a DFD, showing the main functions of the system.

The part of a DFD that receives input data from the outside world.

The part of a DFD that sends output data to the outside world.

The central part of a DFD that performs the main transformations on the data.

A method for analyzing a system by identifying and grouping related functions that process similar input data.

A graphical representation of a system's structure, showing the relationships between modules and their hierarchy.

A simplified representation of a real-world entity, capturing important aspects relevant to a specific application.

A way to organize use cases in a hierarchical structure, where high-level use cases are broken down into smaller, more detailed sub-use cases.

A use case that encompasses a broader scope and can be decomposed into more specific use cases.

A use case that is a refinement of a more general use case, focusing on a specific aspect or scenario.

The topmost level of the use case hierarchy, focusing on the overall context of the system and its interactions with external actors.

A use case level specifying the functionalities provided by specific subsystems within the system.

A description of how a user interacts with a system to achieve a specific goal. It represents a high-level functional requirement.

A set of use cases that collectively describe the functions and capabilities of a system.

The most common sequence of interactions within a use case, representing normal system behavior.

Variations or alternative paths in a use case, representing different scenarios or exceptions.

A real-world entity that interacts with the system, such as a customer or a cashier.

A graphical representation of actors and use cases, showing how they interact within the system.

A detailed, step-by-step description of how a use case is executed, outlining actions and responses between the actor and the system.

A unique identification number assigned to a customer to track their purchase history.

The act of recording a customer's purchase information against their unique customer number.

The process of selecting the winners of a prize scheme based on their total annual purchase value.

The process of resetting each customer's purchase value to zero at the start of a new year, after prizes are awarded.

Breaking down a complex use case into smaller, simpler ones to make it easier to understand and implement.

A relationship between two use cases where the second use case extends the functionality of the first one under specific conditions.

A relationship between two use cases where the second use case inherits all the features of the first one and adds additional functionality.

A point in a use case where an extension can be added, allowing optional behavior to be triggered based on specific conditions.

A way to represent the behavior of a system, showing how different elements (actors, objects) interact to achieve a goal.

Common behavior shared across multiple use cases, which can be factored out to avoid duplication.