Architectural Design Decisions

This quiz covers the fundamentals of architectural design decisions, including the purpose of software architecture, levels of abstraction, key design questions, and the influence of non-functional requirements on architectural choices

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

more_vert More

QUESTION OF

volume_mute Read quiz aloud

Views #: 223

Questions #: 13

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

What is Architectural Design?

1 pts

volume_mute

Which of the following best describes what architectural design is concerned with?

Understanding how a system should be organized and designing its overall structure

Documenting user requirements in a specification

Writing detailed code for individual modules

Testing software components for defects

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Architecture and Requirements Engineering

1 pts

volume_mute

Architectural design is described as the critical link between which two activities?

Project management and budgeting

Design and requirements engineering

Testing and deployment

Coding and documentation

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Architecture in the Small vs. Large

1 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Level

Architecture in the large

Architecture in the small

Description

Concerned with the architecture of individual programs and how they are decomposed into components

Concerned with complex enterprise systems distributed across different computers, possibly owned by different companies

Match each level of architectural abstraction with its correct description.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three Advantages of Documenting Architecture

1 pts

volume_mute

Which THREE of the following are recognized advantages of explicitly designing and documenting a software architecture?

Reduced testing effort - architecture documentation eliminates the need for unit tests

Large-scale reuse - the architecture can be reused across systems with similar requirements

Faster coding - developers write code more quickly with a documented architecture

System analysis - early architectural design requires analysis and reveals whether requirements can be met

Stakeholder communication - the architecture provides a high-level presentation for discussion

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Packing Robot Architecture

1 pts

volume_mute

Consider the architecture diagram for a packing robot control system shown below. Which component is responsible for identifying the type of object on the conveyor and selecting the appropriate packaging?

Object Identification System

Conveyor Controller

Packaging Selection System

Vision System

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Key Architectural Design Questions

1 pts

volume_mute

During the architectural design process, system architects must consider a number of fundamental questions. Which of the following are among those key questions? Select ALL that apply.

What strategy will be used to control the operation of components in the system?

What architectural patterns or styles might be used?

Which programming language will be used for implementation?

How will the architectural design be evaluated?

Is there a generic application architecture that can act as a template for the system?

How will the system be distributed across a number of cores or processors?

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Architecture and Agile Development

1 pts

volume_mute

Which statement best describes the relationship between architectural design and agile development processes?

An early stage of agile development should establish an overall system architecture, since refactoring a system architecture is likely to be expensive

Architecture is not relevant in agile methods because components are refactored continuously

Agile processes never consider architecture, leaving it entirely to the implementation phase

Agile processes fully specify the architecture before writing any code

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Non-Functional Requirements and Architecture

1 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Non-Functional Requirement

Security

Performance

Safety

Maintainability

Availability

Architectural Strategy

Localize critical operations in a small number of components, deployed together on the same computer

Use a layered structure with the most critical assets protected in the innermost layers

Locate safety-related operations in a single component or a small number of components

Include redundant components so components can be replaced and updated without stopping the system

Use fine-grain, self-contained components where producers of data are separated from consumers

Match each non-functional requirement with the architectural strategy it demands.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Conflicting Architectural Requirements

1 pts

volume_mute

A system has both high performance and high maintainability as critical non-functional requirements. Why do these requirements create an architectural conflict?

There is no conflict — performance and maintainability always use the same architectural approach

Performance requires large components deployed together, while maintainability requires fine-grain, self-contained components — these are opposites

Performance and maintainability both require layered architectures, making it impossible to satisfy either

Performance requires distributed components, while maintainability requires a single monolithic component

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Block Diagrams as Architectural Models

1 pts

volume_mute

In a system architecture block diagram, what do arrows between boxes typically represent?

Inheritance relationships between classes

Ownership relationships between subsystems

Data and/or control signals passed from one component to another in the direction of the arrows

Temporal ordering of component development

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Two Uses of an Architectural Model

1 pts

volume_mute

There are two distinct ways in which an architectural model of a program is used. Drag the correct purpose into each placeholder.

An architectural model can be used (1) — where a high-level view aids stakeholder communication and project planning without excessive detail. It can also be used (2) — where the aim is to produce a complete model showing all components, their interfaces, and their connections.

Please drag and drop the selected option in the right place or type it instead

as a way of facilitating discussion about the system design

as a substitute for writing requirements

as a way of documenting an architecture that has been designed

as a tool for performance benchmarking

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Architectural Decisions as a Creative Process

1 pts

volume_mute

Why is it more accurate to think of architectural design as a series of decisions rather than a sequence of activities?

Because architectural design follows a strict waterfall process with defined stages

Because the activities within the process depend on the type of system, the architect's background, and the specific requirements — making it inherently creative rather than procedural

Because decisions are made only once at the start of a project and never revisited

Because architectural design is fully automated by CASE tools

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Evaluating an Architectural Design

1 pts

volume_mute

Which of the following statements about evaluating an architectural design are TRUE? Select ALL that apply.

Bosch's description of non-functional characteristics of architectural patterns can help with architectural evaluation

The true test of an architecture is how well the system meets its functional and non-functional requirements when in use

You can do some evaluation by comparing the design against reference architectures or generic architectural patterns

An architecture can be fully validated by static code analysis tools before implementation

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Undergraduate Professional

What is Architectural Design?

Correct Answer

Explanation

Architecture and Requirements Engineering

Correct Answer

Explanation

Architecture in the Small vs. Large

Level

Description

Correct Answer

Explanation

Three Advantages of Documenting Architecture

Correct Answer

Explanation

Packing Robot Architecture

Correct Answer

Explanation

Key Architectural Design Questions

Correct Answer

Explanation

Architecture and Agile Development

Correct Answer

Explanation

Non-Functional Requirements and Architecture

Non-Functional Requirement

Architectural Strategy

Correct Answer

Explanation

Conflicting Architectural Requirements

Correct Answer

Explanation

Block Diagrams as Architectural Models

Correct Answer

Explanation

Two Uses of an Architectural Model

Correct Answer

Explanation

Architectural Decisions as a Creative Process

Correct Answer

Explanation

Evaluating an Architectural Design

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: