Domain,Design,Development
Conceptual,Design,Code
Conceptual,Architecture,Development
Domain,Design,Code
None of the above
A type that appears in one model also appears in another
Defines the correspondence between two models to show consistency
Allows one to carry constraints from one model to another
Both a and c
Both b and c
Models of design
Different perspectives
Very high-level representations of the system
Both a and b
Both a and c
The domain is too simple to bother modeling
Domain modeling is open-ended and is a never-ending analysis task
The domain is irrelevant to your architecture choices
The best way to learn the domain is incrementally
It’s someone else’s job to do requirements
True
False
True
False
True
False
True
False
True
False
It takes too long to create the diagrams
Good UML tools are too expensive
It is not a language known by most non-developers
It’s use is incompatible with the goals of domain modeling
The diagrams require you to include too much detail
Can be used to model the structure of a system
Is similar to natural language in its support for modeling systems
Can be used to model the relationships in the domain
Is a language that is understood by most non-technical people
Is good for describing invariants in a model
Structure
Behavior
The way people will use the system
Both a and b
Both a and c
A deployment view shows where process will run and how they will interact
A deployment view shows how the system interacts with its environment
A deployment view shows how the system is installed in the target environment
Both a and b
Both a and c
Components describe units of code
Connectors are pathways of runtime interaction
A module is associated with exactly one component
Design decisions are clearly identifiable in views
Views always describe subsystem
Describe how the software being created interacts with elements in its environment
Can be based on a use case diagram
Might show the Internet
Describe what is in and what is outside the scope of the software project
All of a-d
Only a and d
Component and Connector,Designation and Module
Runtime,Documentation and Miscellaneous
Component,Module,Deployment
Component,Allocation,Module
Runtime,Allocation,Module
Built in the pipe and filter style
Is designed to allow new Code to be inserted easily
Was designed with few constraints to support the system’s performance goals
A web server
Was designed around the goal of modifiability
True
False
True
False
True
False
True
False
True
False
True
False
Something to worry about
A cause of failure
A chance of failure
A primary driver of architecture
An internals diagram
A context diagram
A sequence diagram
A functionality scenario