WorksheetsSAAD 7
Total questions: 94
Worksheet time: 47mins
Name
Class
Date
1.
The slide distinguishes Requirement specification documents from later design artifacts. Which item is shown under Requirement specification documents?
a)
Use Case Specification
b)
Class Diagram
c)
State Machine Diagram
d)
Database Design
e)
Interface Design
2.
Within the Design Document structure shown, Interaction is a subcategory under Behavior. Which diagram is explicitly listed under Interaction?
a)
Sequence Diagram
b)
Use Case Diagram
c)
ER Diagram
d)
Package Diagram
e)
Deployment Diagram
3.
The slide juxtaposes two phrases to motivate the idea of architecture by analogy. Which pair of phrases is shown?
a)
Construction architecture and Software Architectures
b)
Construction management and Software Architectures
c)
Construction architecture and Software Requirements
d)
Construction design and Software Architectures
e)
Construction architecture and Software Testing
4.
On that slide, the term presented as the software-side counterpart of construction architecture is:
a)
Software Architectures
b)
Software Requirements
c)
Software Maintenance
d)
Software Management
e)
Software Deployment
5.
Which statement best matches the slide definition of software architecture?
a)
A set of decisions about the organization of software
b)
A full list of all classes and methods in the system
c)
A detailed step-by-step test plan for every feature
d)
A repository structure for storing source code files
e)
A schedule for assigning tasks to developers
6.
According to the slide, which activity is explicitly part of software architecture?
a)
Assembling structural and behavioral elements into subsystems
b)
Choosing variable names for each method parameter
c)
Writing unit tests for each branch condition
d)
Estimating project cost using earned value metrics
e)
Selecting a color palette for user interface themes
7.
Why does the slide argue an architecture document supports information exchange across groups?
a)
It gives a comprehensive overview without going into element-level detail
b)
It enumerates every code line so no interpretation is needed
c)
It replaces requirements so teams do not need meetings
d)
It contains hardware purchase orders and vendor contracts
e)
It only targets one specialist group, avoiding ambiguity
8.
The slide links architectural reuse to grouping elements by life cycle. What is the intended mechanism?
a)
Elements with similar life cycles are grouped, making them easier to reuse together
b)
Elements are randomly distributed to maximize parallel development
c)
Elements are duplicated across subsystems to avoid shared dependencies
d)
Elements are merged into one module to eliminate subsystem boundaries
e)
Elements are hidden from documentation to reduce maintenance costs
9.
In the slide list of perspectives, which perspective is described as focusing on hardware nodes and program code?
a)
System implementer perspective
b)
BA perspective
c)
Designer perspective
d)
Programmer perspective
e)
System operator perspective
10.
In the slide list of perspectives, which perspective is explicitly associated with processes?
a)
System operator perspective
b)
BA perspective
c)
Designer perspective
d)
Programmer perspective
e)
System implementer perspective
11.
In the 4+1 model diagram, performance, scalability, and throughput are concerns of which view?
a)
Process View
b)
Logical View
c)
Implementation View
d)
Deployment View
e)
Use-Case View
12.
In the 4+1 model diagram, which view is explicitly centered on end-user functionality?
a)
Use-Case View
b)
Deployment View
c)
Process View
d)
Implementation View
e)
Logical View
13.
Which question is aligned with the logical perspective as stated on the slide?
a)
What classes of objects does the system consist of, and how are they related?
b)
What physical nodes will host the deployed binaries?
c)
What protocol will be used on each network connection?
d)
How many operating system processes will be started at runtime?
e)
What installation scripts must be shipped to customers?
14.
Which question is aligned with the implementation perspective as stated on the slide?
a)
What executable or layout components are the source code components compiled or packaged into?
b)
What are the responsibilities of each domain object?
c)
What is the event flow of each use case?
d)
What are the states and transitions of an entity?
e)
What terms define strong cohesion inside a package?
15.
The slide distinguishes process and deployment perspectives. Which question belongs to the process perspective?
a)
How is the system executed on threads or processes?
b)
On which hardware nodes are components located?
c)
How are computing nodes connected to each other?
d)
What executable components are built from source code components?
e)
What classes belong together in a package hierarchy?
16.
The slide distinguishes process and deployment perspectives. Which question belongs to the deployment perspective?
a)
How are the layout components deployed on computing nodes and how are nodes connected?
b)
How do objects collaborate inside a use case event flow?
c)
How should classes be organized into packages for cohesion?
d)
What source code files are needed to compile a library?
e)
What interfaces does each component provide?
17.
When organizing classes into packages, which pair of principles is explicitly stated on the slide?
a)
Strong Cohesion and Weak Coupling
b)
Strong Coupling and Weak Cohesion
c)
Strong Inheritance and Weak Encapsulation
d)
Strong Performance and Weak Security
e)
Strong Deployment and Weak Implementation
18.
A package design aims to minimize dependencies across packages. Which description best matches the slide notion of weak coupling?
a)
Classes in different packages have limited static and message-exchange dependencies
b)
Classes in different packages share many bidirectional links and frequent message exchange
c)
Classes in different packages are forced into the same inheritance hierarchy
d)
Classes in different packages are duplicated to avoid referencing each other
e)
Classes in different packages are prohibited from using any interfaces
19.
Which statement about UML packages is explicitly stated on the slide?
a)
Packages can be hierarchical, where packages contain smaller packages
b)
Packages can only contain classes, not other packages
c)
Packages must be flat to avoid dependency cycles
d)
Packages are only used in deployment diagrams
e)
Packages represent runtime threads by default
20.
The slide lists multiple uses of packages across perspectives. Which mapping is explicitly listed?
a)
Grouping components is associated with the implementation perspective
b)
Grouping components is associated with the deployment perspective
c)
Grouping use cases is associated with the process perspective
d)
Grouping classes is associated with the deployment perspective
e)
Grouping documents is associated with the use-case perspective
21.
The slide explains strong cohesion within a package using multiple lenses. Which lens is explicitly mentioned?
a)
Purpose, where classes provide services of the same nature and share domain terms
b)
Network topology, where classes share the same subnet and IP range
c)
Storage format, where classes store data in the same file extension
d)
Programming language, where classes must be written in the same language version
e)
UI styling, where classes must render with the same font family
22.
The slide describes separating stable classes from frequently changing classes. Which separation is given as an example?
a)
Separating business classes from application classes into different subsystems
b)
Separating executable files from hardware devices into different packages
c)
Separating views from routers into different hardware nodes
d)
Separating deployment protocols from thread life cycles into different documents
e)
Separating tables from documents into different operating systems
23.
On the slide, package dependency is said to reflect which kinds of relationships between classes in the two packages?
a)
Both static relationships (inheritance, linkage) and dynamic relationships (message exchange)
b)
Only dynamic relationships (message exchange) and not static structure
c)
Only static relationships (inheritance, linkage) and not message exchange
d)
Only runtime CPU scheduling relationships between threads
e)
Only deployment-time placement relationships between nodes
24.
Which rule is explicitly stated to avoid weak correlation problems between packages?
a)
Avoid circular dependencies between packages
b)
Force every package to depend on at least two other packages
c)
Place each inheritance hierarchy across multiple packages
d)
Maximize leapfrog dependencies to reduce indirection
e)
Ensure every package has both UI and database classes
25.
How does the slide define a software architectural pattern?
a)
A generic, reusable solution to a common situation in a given context
b)
A detailed implementation blueprint for one specific system instance
c)
A set of coding conventions enforced by the compiler
d)
A complete set of database records for the application
e)
A fixed sequence of runtime process IDs for deployment
26.
Which option is listed on the slide as a common architectural pattern from a logical perspective?
a)
Event bus architecture
b)
Monolithic architecture
c)
Peer-to-peer architecture
d)
Client-only architecture
e)
File-per-class architecture
27.
In the layered architecture figure, which ordering matches the middle stack from top to bottom?
a)
UI, Application, Business, Data access, Data storage
b)
UI, Business, Application, Data access, Data storage
c)
Application, UI, Business, Data storage, Data access
d)
User services, Business services, Data services, Data access, Data storage
e)
Business, Application, UI, Data access, Data storage
28.
In the layered architecture figure, which ordering matches the left stack from top to bottom?
a)
User services, Business services, Data services
b)
User services, Data services, Business services
c)
Business services, User services, Data services
d)
Data services, Business services, User services
e)
UI, Application, Business
29.
The slide states that reverse dependencies are not allowed in layered architecture. What is the prohibited situation?
a)
A lower layer depends on an upper layer
b)
An upper layer depends on a lower layer
c)
Two layers have no dependency between them
d)
A utility package is referenced by multiple layers
e)
A layer is split into multiple packages
30.
The slide cautions against leapfrog dependencies. Which situation best matches a leapfrog dependency?
a)
Layer 3 directly depends on Layer 1 while Layer 2 exists in between
b)
Layer 2 depends on Layer 1 and Layer 3 depends on Layer 2
c)
Layer 1 depends on Layer 2 due to an inversion of control mechanism
d)
Utilities are referenced by both Layer 1 and Layer 3
e)
A layer contains multiple packages that reference each other
31.
Which rationale is explicitly listed as a reason to use layered architecture?
a)
Separation of abstraction levels
b)
Elimination of all dependencies between modules
c)
Guaranteeing constant-time performance for all operations
d)
Ensuring each layer is deployed on a separate hardware node
e)
Replacing the need for any interface design
32.
The slide mentions encapsulating changes as a reason for layered architecture. What action best matches that idea?
a)
Separating elements into different groups so a group can be changed with limited impact
b)
Merging all layers into a single package to reduce boundaries
c)
Forcing every layer to call every other layer for maximum flexibility
d)
Duplicating the same logic across layers to avoid shared code
e)
Removing documentation so implementations can change freely
33.
In the MVC diagram, which element is shown at the top receiving and routing a request/response path?
a)
Router
b)
Models
c)
Views
d)
Controllers
e)
Data access layer
34.
In the MVC diagram, the arrow labeled "Query" originates from Controllers and points to which package?
a)
Models
b)
Views
c)
Router
d)
Utilities
e)
Gateway
35.
Which responsibility is assigned to the View package according to the slide?
a)
Presentation and communication with users
b)
Receiving requests from users via the router
c)
Retrieving objects from Models
d)
Compiling source code components into executables
e)
Placing components on hardware nodes
36.
A Controller receives a user request via a router, retrieves objects from Models, and then creates or updates View objects. What advantage does the slide explicitly associate with MVC that supports this separation?
a)
Easy to assign development and testing due to separated roles
b)
Eliminates the need for any packaging or layering decisions
c)
Guarantees microservices can be deployed independently
d)
Forces all dependencies to be bidirectional for flexibility
e)
Requires all user interaction to occur via message buses
37.
In the microservices architecture figure, what component sits above the services and mediates interactions?
a)
Gateway
b)
Router
c)
EJB Container
d)
Deployment spec
e)
Utilities layer
38.
In the microservices architecture figure, each service is paired with its own data store (DB1, DB2, DBn). What structural property is being illustrated?
a)
Service-level data ownership where each service is coupled to its own database
b)
A single shared database used by all services through one schema
c)
A layered stack where UI directly depends on data storage
d)
A bus topology where services publish to channels and listeners react
e)
A deployment diagram where nodes are underlined instances
39.
According to the slide, microservices are designed, built, and deployed independently. Through what element do they interact with each other?
a)
Gateway
b)
Router
c)
EJB Container
d)
Database table
e)
Thread scheduler
40.
Which advantage is explicitly listed for microservices on the slide?
a)
Independence in deployment and integration
b)
Elimination of the need for any component diagrams
c)
Prohibition of replacing services once deployed
d)
Dependence on a single executable file for the whole system
e)
Tight coupling of services to simplify governance
41.
In the event-bus architecture figure, which layer sits between Sources and Listeners?
a)
Channels
b)
Gateway
c)
Controllers
d)
Models
e)
Deployment nodes
42.
The event-bus figure shows that a channel can dispatch to multiple listeners. Which description matches the depicted routing?
a)
A single channel can feed multiple listeners, enabling one-to-many event handling
b)
Each listener can write directly back into sources, creating a feedback loop
c)
Listeners must always publish back into the same channel they consume from
d)
Sources must be deployed on the same node as every listener
e)
Channels are compiled into executable files and cannot be shared
43.
The slide defines event-bus architecture as dividing a system into event-generating and event-handling layers. What are the names used for these roles?
a)
Source and listener
b)
Model and view
c)
Device and execution environment
d)
Executable and library
e)
Package and class
44.
Which advantage is explicitly listed for event-bus architecture on the slide?
a)
Separation between event-generating elements and event-handling elements
b)
Elimination of all channels to reduce communication cost
c)
Forcing a strict top-down call chain with no asynchronous flow
d)
Guaranteeing that every event has exactly one listener
e)
Replacing deployment diagrams with class diagrams
45.
In the implementation perspective, which question is explicitly raised about mapping from the logical view?
a)
What source code components are classes implemented into?
b)
What classes of objects does the system consist of?
c)
How are computing nodes connected to each other?
d)
How is the system executed on threads or processes?
e)
How should events be streamed through channels?
46.
In the implementation perspective, which question is explicitly raised about packaging?
a)
What layout components are applications packaged into?
b)
What are the non-functional requirements for the system?
c)
What is the use-case view for end-user functionality?
d)
What are the relationships between processes?
e)
What principles define strong cohesion within a package?
47.
The slide contrasts package diagrams with component diagrams. What is the main distinction stated?
a)
Component diagrams show the physical structure of installed software products
b)
Component diagrams replace use-case specifications in requirements documents
c)
Package diagrams only exist at runtime and not in design
d)
Component diagrams are primarily used to model hardware nodes
e)
Package diagrams are only for executable files and libraries
48.
On the slide, "physical" in component diagrams is clarified in a specific way. What does it mean there?
a)
Oriented toward software products that exist as installation artifacts
b)
Oriented toward the logical results of analysis and design
c)
Oriented toward hardware procurement and rack layout
d)
Oriented toward end-user task flows in use cases
e)
Oriented toward CPU scheduling and thread priorities
49.
Which description matches the UML definition of a component given on the slide?
a)
A physical and replaceable part that adapts and provides implementation for a set of interfaces
b)
A conceptual grouping used only to organize use cases
c)
A runtime operating system process that executes threads
d)
A hardware device such as a printer or kiosk
e)
A network protocol such as HTTP or JDBC
50.
The slide reframes a component as an implementation of logical elements. Which logical elements are explicitly mentioned as examples?
a)
Classes or collaborations
b)
Nodes or connections
c)
Threads or processes
d)
Protocols or templates
e)
Requirements or event flows
51.
The slide distinguishes deployment components, work product components, and execution components. Which item best fits the slide notion of a work product component?
a)
A source code file used to build deployment components
b)
A dynamic library (DLL) required at runtime
c)
An executable that runs on a node
d)
A packaged runtime component such as a JAR
e)
A communication protocol used by a node connection
52.
The slide lists a JAR as an example of which component type?
a)
Execution component
b)
Work product component
c)
Deployment component
d)
Logical component
e)
Use-case component
53.
Which stereotype is listed as a standard UML template for a component diagram?
a)
<<table>>
b)
<<gateway>>
c)
<<router>>
d)
<<controller>>
e)
<<process>>
54.
The slide states that non-standard templates can be used. Which option is listed as an example of such a non-standard template?
a)
<<infrastructure>>
b)
<<executable>>
c)
<<library>>
d)
<<file>>
e)
<<document>>
55.
The slide gives two ways to organize components. Which option is one of the two stated ways?
a)
Establish dependencies between components
b)
Replace all dependencies with inheritance relationships
c)
Underlining component names to indicate instances
d)
Enforce that all components live on one hardware node
e)
Convert all components into database tables
56.
According to the slide, the alternative to establishing dependencies is to:
a)
Group the components into packages
b)
Deploy the components onto devices and execution environments
c)
Assign the components to threads and processes
d)
Stream the components through channels
e)
Replace the components with use-case specifications
57.
The slide states a core purpose of a component diagram in the presence of different component types. What is that purpose?
a)
To describe what type of component it is
b)
To describe the full state machine of each class
c)
To list all non-functional requirements in detail
d)
To define the user interface layout of each screen
e)
To specify the CPU and memory limits of each process
58.
If a diagram uses stereotypes such as <<library>> and <<executable>>, what modeling goal from the slide is being directly served?
a)
Making the component type explicit in the diagram
b)
Documenting the exact event flow of each use case
c)
Showing underlined instance names for hardware resources
d)
Assigning objects to processes using composition only
e)
Avoiding the need to show any dependencies at all
59.
The slide states that if a system consists of only one executable file, component diagrams are not needed. What file type is explicitly used as the example?
a)
.EXE
b)
.JAR
c)
.INI
d)
.TBL
e)
.HLP
60.
According to the slide, component diagrams become useful when a system consists of multiple executables and libraries because they help document decisions about the:
a)
Physical system implementation and its dependencies
b)
Exact class method bodies and local variables
c)
End-user task flows in every scenario
d)
Cost model for hardware procurement
e)
Exact thread scheduling quantum values
61.
In the deployment components diagram, which component is marked as <<executable>>?
a)
animator.exe
b)
render.dll
c)
dlog.dll
d)
wrfrme.dll
e)
raytree.dll
62.
In the same diagram, if animator.exe depends on render.dll and render.dll depends on raytree.dll, which statement is most consistent with the depicted dependency chain?
a)
animator.exe has an indirect dependency on raytree.dll through render.dll
b)
raytree.dll has an indirect dependency on animator.exe through render.dll
c)
dlog.dll depends directly on raytree.dll via animator.exe
d)
wrfrme.dll is the only library required by animator.exe
e)
render.dll has no dependencies because it is a library component
63.
The slide notes that beyond executables and libraries, installation requires auxiliary layout components. Which item is explicitly listed as an example?
a)
Configuration parameter initialization files
b)
Process scheduling policies
c)
Inheritance hierarchies
d)
Use-case diagrams
e)
Class diagrams
64.
Why does the slide say modeling auxiliary components is important?
a)
It helps describe the state of the system needed for installation
b)
It replaces the need to model executable components and libraries
c)
It guarantees that hardware nodes are chosen automatically
d)
It ensures every event has exactly one listener
e)
It eliminates the need for any source code files
65.
In the diagram that adds tables, files, and documents, what stereotype is used for animator.hlp?
a)
<<document>>
b)
<<file>>
c)
<<table>>
d)
<<library>>
e)
<<executable>>
66.
In the same diagram, shapes.tbl is annotated with which stereotype?
a)
<<table>>
b)
<<document>>
c)
<<file>>
d)
<<library>>
e)
<<application>>
67.
The slide describes source code files as an intermediate step toward executable components. Which statement matches that role?
a)
Source code files contain details about logical elements and are used to create physical components
b)
Source code files only exist after the system is running and cannot be stored
c)
Source code files are themselves hardware nodes in a deployment diagram
d)
Source code files are network protocols used for node connections
e)
Source code files replace the need for any component diagram
68.
The slide notes that tool constraints can impose organization such as .h and .cpp files, and that dependencies reflect a compilation order. What is being modeled by these dependencies?
a)
The order implied by which source files must be available or processed before others compile
b)
The runtime message bus routing among processes
c)
The placement of executables onto hardware nodes
d)
The cohesion of business classes inside a package
e)
The end-user steps in a use-case flow
69.
In the source code modeling example, which file is shown as the central dependency target that multiple sources point to?
a)
render.h
b)
render.cpp
c)
rengine.h
d)
poly.h
e)
colortab.h
70.
In the same diagram, which file is annotated with version 5.3.7?
a)
render.cpp
b)
render.h
c)
rengine.h
d)
poly.h
e)
colortab.h
71.
The deployment perspective is framed by two guiding questions on the slide. Which one is explicitly listed?
a)
On which hardware nodes are the components located?
b)
What classes belong in the same inheritance hierarchy?
c)
What is the compilation order of source code files?
d)
How are use cases grouped into packages?
e)
What is the difference between strong cohesion and weak coupling?
72.
The second guiding question in the deployment perspective slide is about node interconnection. Which phrasing matches the slide?
a)
How do the hardware nodes communicate with each other?
b)
How do classes exchange messages within one package?
c)
How do controllers update views in MVC?
d)
How do services share a database schema in microservices?
e)
How do components get compiled into deployment artifacts?
73.
In the slide definition of deployment diagrams, a node is described as what kind of element?
a)
A physical element that exists at runtime and represents a computational resource
b)
A source code file that must be compiled before linking
c)
A class package used to group related domain entities
d)
A network protocol such as HTTP or JDBC
e)
A use-case scenario describing user functionality
74.
The slide distinguishes node naming conventions using underlining. What does an underlined node name indicate?
a)
An individual resource instance rather than a class of resources
b)
A package that contains other packages
c)
A component that is compiled from multiple source files
d)
A synchronous communication protocol between nodes
e)
A controller that routes requests to models
75.
The slide states two representation levels for deployment diagrams that correspond to class and object diagrams. Which pair matches the slide?
a)
Class level and instance level
b)
Logical level and use-case level
c)
Requirement level and design level
d)
Source level and binary level
e)
Synchronous level and asynchronous level
76.
The slide says a node can be a device or an execution environment. Which example matches the execution environment category listed on the slide?
a)
EJB Container
b)
Printer
c)
Kiosk
d)
Processor
e)
Console
77.
In the deployment diagram example slide, what is said about the WebServer node having no stereotype template?
a)
The developer has not decided yet; it could be a type of software or a physical device
b)
It must be an execution environment and cannot be hardware
c)
It must be underlined because it is always an instance
d)
It is a database table and should use the <<table>> template
e)
It is a source code file and should use the <<file>> template
78.
The example slide emphasizes that nodes can contain other nodes or software. Which nesting relationship is explicitly described?
a)
ApplicationServer contains an EJBContainer node, which in turn contains multiple software components
b)
WebServer contains JDBC connections, which in turn contain HTTP protocols
c)
DB Server contains process threads, which in turn contain controllers and views
d)
Mainframe contains packages, which in turn contain smaller packages at runtime
e)
Router contains channels, which in turn contain sources and listeners
79.
In deployment diagrams, what does the slide say connections represent?
a)
Communication relationships between pairs of nodes, physically represented by a transmission path
b)
Inheritance relationships between classes across packages
c)
Compilation dependencies between source files
d)
Data ownership relationships between microservices and databases
e)
Update notifications from controllers to views
80.
The slide states that each connection supports one or more communication protocols. What is the recommended way to specify them?
a)
Use appropriate templates (stereotypes) on the connection
b)
Underline the protocol name to indicate an instance
c)
Convert the protocol into a package and group nodes under it
d)
Model the protocol as a use-case event flow
e)
Replace the connection with a class diagram association only
81.
From the connection templates table, which option is defined as a Java technology for connecting to and accessing databases?
a)
JDBC
b)
ODBC
c)
HTTP
d)
RMI
e)
RPC
82.
From the connection templates table, which option is defined as a synchronous connection where the sender waits for the receiver response?
a)
Synchronous
b)
Asynchronous
c)
Web services
d)
HTTP
e)
Message bus
83.
The process perspective slide asks where the system is executed. What runtime unit is explicitly named in that question?
a)
Processes
b)
Packages
c)
Hardware nodes
d)
Database tables
e)
Channels
84.
Another question on the process perspective slide is about placement. What is being placed, according to the slide?
a)
System objects on processes
b)
Libraries on routers
c)
Channels on use cases
d)
Packages on protocols
e)
Deployment specs on class diagrams
85.
The slide states that processes can be modeled using active classes and objects, and also using components. Which stereotype is explicitly suggested for marking such processes?
a)
<<process>>
b)
<<table>>
c)
<<library>>
d)
<<document>>
e)
<<device>>
86.
According to the slide, how can relationships between processes be modeled?
a)
Using dependencies between the stereotyped process elements
b)
Only using inheritance between process classes
c)
Only by placing processes on hardware nodes
d)
Only by converting each process into a database table
e)
Only through MVC controller-to-view updates
87.
Which statement matches the slide description of a single-process architecture life cycle?
a)
The process is created when the application starts and destroyed when it ends
b)
Processes are spawned from a parent and can be destroyed independently
c)
Each external request creates a new process that persists forever
d)
Processes are created only after installation and never at runtime
e)
Processes are replaced by packages and do not exist at execution time
88.
Which statement matches the slide description of a multi-process architecture life cycle?
a)
Processes are usually created from a parent process and can be destroyed independently
b)
A single process is created once and cannot be destroyed until shutdown
c)
Processes exist only as deployment components such as DLLs
d)
Processes are identical to hardware nodes and must be underlined
e)
Processes are channels that stream events from sources to listeners
89.
The slide states that instances of a class need to be executed on at least one thread or process. What additional possibility is explicitly mentioned?
a)
They can be executed on multiple threads or processes
b)
They must be executed on exactly one process
c)
They can only execute on hardware devices, not processes
d)
They can only execute inside database tables
e)
They can only execute inside use-case views
90.
In the example on the slide, MainStudentForm and RegisterForCoursesForm are shown as being executed within which process?
a)
Student Application Process
b)
Course Catalog Process
c)
Database Process
d)
WebServer Process
e)
Gateway Process
91.
Which distribution strategy is described as grouping design elements that frequently interact in a control flow, then iterating toward a minimal set of processes?
a)
Inside-Out
b)
Outside-In
c)
Top-Down Layering
d)
MVC Routing
e)
Event Streaming
92.
Which distribution strategy is described as starting from independent flows for each external service request or external event, then grouping and reducing flows?
a)
Outside-In
b)
Inside-Out
c)
Bottom-Up Packaging
d)
Library Linking
e)
Database Normalization
93.
The slide states that relationships between processes must match relationships between design elements. Which mismatch best violates that rule?
a)
Two classes exchange messages frequently, but their processes have no communication relationship
b)
Two classes are in different packages, and their processes are deployed on different nodes
c)
A process supports multiple instances of a class, and the class is used by one subsystem
d)
A device node hosts an execution environment that contains components
e)
A utility package is referenced by multiple layers
94.
In the process relationship diagram, a process is connected to a class with a relationship labeled "supports". What is the most consistent interpretation with the slide context?
a)
The process provides an execution context for instances of that class
b)
The class physically contains the process as a nested node
c)
The class compiles the process from source code files
d)
The process is a network protocol used by the class
e)
The class replaces the need for the process at runtime
100 %
