1) Design is the Path from Concept to Problem
FALSE
2) The logical modeling transforms the logical artifacts into engineering blueprints
FALSE
3) Concrete modeling consists of logical and physical modeling activities
TRUE
4) Design must discover or create the components of the problem
FALSE
5) Usually more than one solution can satisfy the same problem. Therefore, design must select between alternate solutions.
TRUE
6) Design takes into account only functional requirements
FALSE
7) An architectural view of the solution is not important to designing a system
FALSE
8) Design must produce a builder's view of the system
TRUE
9) Design is a one-time job
FALSE
10) Analysis deals with HOW to build a system
FALSE
11) Logical modeling represents the solution without reference to a specific technology
TRUE
12) Physical modeling maps the logical modeling to specific technologies
TRUE
13) The same logical design can translate into many physical designs
TRUE
14) Transformation of logical design into physical design is a one-step activity
FALSE
15) Logical design does not need to take into account the existing technological paradigms
FALSE
16) Design modeling starts with identifying the generic components of the solution
TRUE
17) A component is NOT the same thing as a reusable software unit that provides services independent of particular applications
FALSE
18) Design objects are part of the problem domain but are not necessary for building the solution
FALSE
19) A layer is a collection of independent components
FALSE
20) UML notation cannot be stereotyped
FALSE
21) We may stereotype any and all modeling elements within UML, including actors, relationships, and use cases
TRUE
22) Packaging cannot contain use cases
FALSE
23) UML offers a set of mechanisms that allow modeling to be refined, extended, and adapted to specific needs
TRUE
24) It is a good idea to consider using UML extensions early in the development phase
FALSE
25) UML notes specify things like requirements, observations, reviews, and explanations
TRUE