ITM305 Final Exam - System Analysis and Design

<p>Persistent classes (D)</p> Signup and view all the answers

<p>A dependency relationship between components (A)</p> Signup and view all the answers

<p>Its objects are designed to remain after the system shuts down. (B)</p> Signup and view all the answers

<p>Controller class (D)</p> Signup and view all the answers

<p>Use case diagram (D)</p> Signup and view all the answers

<p>The attribute can be accessed directly by other objects. (B)</p> Signup and view all the answers

<p>It acts as an interface between the entity and external users. (B)</p> Signup and view all the answers

<p>Use case driven design (D)</p> Signup and view all the answers

<p>To retrieve and send data to a database. (B)</p> Signup and view all the answers

<p>The characteristics of model elements. (C)</p> Signup and view all the answers

<p>To reduce coupling between the user interface and the domain layer (C)</p> Signup and view all the answers

<p>The duration when an object is executing a message (C)</p> Signup and view all the answers

<p>Determine all internal messages and flesh out each message with precision (D)</p> Signup and view all the answers

<p>Separating parts of the system that are not likely to change from those that will (D)</p> Signup and view all the answers

<p>Send a message to obtain required persistent data method (B)</p> Signup and view all the answers

<p>Input models such as activity diagrams, SSD, and classes (B)</p> Signup and view all the answers

<p>To show the origins and destinations of communication between objects (B)</p> Signup and view all the answers

<p>There is a perfect technology assumption (D)</p> Signup and view all the answers

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

<p>Dashed line with an arrow (A)</p> Signup and view all the answers

<p>Display electronic forms (A)</p> Signup and view all the answers

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

<p>Data Access Layer (B)</p> Signup and view all the answers

<p>They provide high-level operations triggered by external events. (A)</p> Signup and view all the answers

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

<p>Attribute is private and cannot be accessed outside the class. (C)</p> Signup and view all the answers

<p>System sequence diagram (SSD) (A)</p> Signup and view all the answers

<p>It retains its state even after the system shuts down. (A)</p> Signup and view all the answers

<p>Determining user interface design (B)</p> Signup and view all the answers

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

<p>As a domain model class diagram (A)</p> Signup and view all the answers

<p>Entity class (D)</p> Signup and view all the answers

<p>The interaction between an actor and the system for one use case scenario (A)</p> Signup and view all the answers

<p>Lowercase letters with no spaces, upper-case letters separate words (B)</p> Signup and view all the answers

<p>Repeating or looping of the message (D)</p> Signup and view all the answers

<p>It tests a condition that determines if a message is sent (A)</p> Signup and view all the answers

<p>Input to the use case and stored data (D)</p> Signup and view all the answers

<p>The complete system being treated as a single object (D)</p> Signup and view all the answers

<p>Every message must have an associated return value (C)</p> Signup and view all the answers

<p>A class that can be instantiated (C)</p> Signup and view all the answers

<p>Grouping classes into segregated packages or groups (A)</p> Signup and view all the answers

<p>It allows for easier system modifications and enhancements (C)</p> Signup and view all the answers

<p>The methods and responsibilities of the class are consistent (A)</p> Signup and view all the answers

<p>Isolating stable components from those likely to change (C)</p> Signup and view all the answers

<p>Bundling of data with relevant operations into a single unit (D)</p> Signup and view all the answers

<p>It has diverse and unrelated responsibilities (C)</p> Signup and view all the answers

<p>They share many associations and direct communications (C)</p> Signup and view all the answers

<p>Protection of data integrity by restricting access (B)</p> Signup and view all the answers

<p>Creating separate classes for different functionalities within a system (D)</p> Signup and view all the answers

<p>It reduces system complexity and increases robustness. (C)</p> Signup and view all the answers

<p>A base class that provides attributes and methods to subclasses. (D)</p> Signup and view all the answers

<p>To provide security and reduce coupling between classes. (A)</p> Signup and view all the answers

<p>The implementation of multiple methods with the same name and different parameters. (A)</p> Signup and view all the answers

<p>The class operates independently of other classes. (B)</p> Signup and view all the answers

<p>By directing messages through an intermediate class, similar to a firewall. (C)</p> Signup and view all the answers

<p>The name of the method along with its parameters. (D)</p> Signup and view all the answers

<p>It allows a class to inherit attributes and methods from another class. (C)</p> Signup and view all the answers

<p>Constructors that initialize instances of a class. (D)</p> Signup and view all the answers

High-level operations offered by a system in response to external events.

Designing objects and methods for a use case, one use case at a time.

A class whose objects exist even after the system shuts down.

Represents a problem domain class, often persistent.

A class representing the system's interface (e.g., input forms).

Mediates between boundary and entity classes.

Handles data retrieval and storage.

A way of categorizing model elements by their characteristics.

A diagram used to group and organize classes or packages for better understanding, or to formally define subsystems.

A relationship between packages or classes where a change in one component may require a change in another dependent component.

The layer responsible for displaying information and handling user input to the application.

The layer responsible for business logic and data processing within the application.

The layer responsible for interacting with the database, fetching and storing data.

A controller acts as an intermediary between user interfaces and the application's domain logic. It decouples the view from the domain layer.

A dashed line representing an object in a sequence diagram, showing its existence throughout the interaction.

A vertical box on a lifeline, indicating when an object is actively processing a message.

A sequence diagram that includes multiple layers, such as view, domain, and data layers, reflecting the system's architecture.

The part of a system that handles data storage and retrieval, like reading or updating persistent objects.

Creating a new object in memory and having it retrieve its persistence data.

To design and model a real-world activity by considering the required inputs, creating the required outputs and possible ways of connecting these inputs and the outputs

Separating parts of a system that are likely to change from those that are unlikely to change, thus making the system more adaptable.

A description of how a user interacts with a system to achieve a specific goal.

A diagram that shows the classes in a system, their attributes, methods, and relationships.

A diagram that shows the interaction between an actor and the system for a specific use case scenario. It outlines the messages sent and received by the system, including actors and external systems, along with their sequence.

A system sequence diagram (SSD) primarily focuses on the content and structure of the system's input, showing what information the system expects to receive for a successful interaction.

The format for messages in SSD follows the UML convention: message name followed by a parameter list in parentheses. Names use lowercase letters, no spaces, and uppercase letters separate words. Parameter names are separated by commas even if empty.

These are messages sent by the system in response to an input. They can be responses completing events or requests to external systems requiring actions and replies.

A message notation [true/false condition] return-value := message-name (parameter-list) is used in SSD. It shows conditional messages, return values, message names and parameter lists with repetition marked by '*' and parameter list without parentheses for return messages.

The SSD should reveal what the system needs (input) to properly process a specific action and provide an appropriate response.

The SSD should show all system outputs (responses) to each input, including conditional outputs and output messages to other systems.

A class that can be instantiated, meaning you can create objects (instances) from it.

The principle that objects should be responsible for carrying out tasks within a system.

Dividing a system's functionality into distinct classes or packages, each handling specific tasks.

A design principle that safeguards stable parts of a system from changes in other parts.

A measure of how interconnected classes are, with 'tight' coupling meaning lots of dependencies and 'loose' coupling meaning fewer.

A measure of how focused a class's responsibilities are, with 'high' cohesion meaning tasks relate to the class's purpose and 'low' cohesion meaning tasks are unrelated.

Combining data and methods that operate on that data within a single class, hiding internal workings.

Classes heavily rely on each other, requiring many interactions and making changes difficult.

Classes are independent, interacting minimally, allowing for easier changes.

A class focuses on a specific set of related tasks, enhancing its purpose and clarity.

A relationship between packages or classes where a change in one component may require a change in another dependent component.

A diagram illustrating the three layers of a system: View, Domain, and Data Access.

The layer responsible for displaying information and handling user input to the application.

The layer responsible for business logic and data processing within the application.

Creating a new class (subclass) based on an existing class (superclass), inheriting its attributes and methods without needing to redefine them. This allows for code reuse and creating hierarchies of related classes.

An intermediate class acts as a go-between, decoupling two other classes while still linking them. This promotes flexibility and reduces direct dependencies.

The ability of a single method name to have multiple implementations, each with different parameters. This lets you handle different situations with the same method name.

A special method that creates a new instance of a class in memory when an object is instantiated. It initializes the object's state.

The unique combination of a method's name and its parameters (number and types). Different signatures allow for method overloading.

A benefit of encapsulation where limiting access to internal data and methods simplifies interactions among software components, improving robustness and maintainability.

The ability of a system to handle unexpected inputs and situations without crashing or producing incorrect results.

Indirection can enhance security by directing messages through an intermediate class, like a firewall, protecting sensitive information.