Test
Sdp.3
Crea una cuenta gratis para terminar este test
Guarda tu progreso y consulta tu resultado final.
¿Ya tienes cuenta? Inicia sesión
Preguntas del test (30)
1All models in software design should be captured using UML diagrams
- AVerdadero
- BFalso
2Every project should document its architecture
- AVerdadero
- BFalso
3Architecture documents are abstractions of the system.
- AVerdadero
- BFalso
4All design decisions should be made before coding begins
- AVerdadero
- BFalso
5Different types of models are required in order to serve the needs of various stakeholders
- AVerdadero
- BFalso
6 A good set of architectural documents will completely describe the system
- AVerdadero
- BFalso
7A context diagram should include details related to quality concerns.
- AVerdadero
- BFalso
8A port is a point of interaction in a component diagram.
- AVerdadero
- BFalso
9A context diagram is similar to a snapshot in that the context is likely to change as the system runs.
- AVerdadero
- BFalso
10A view is a projection of a model that reveals select details
- AVerdadero
- BFalso
11An internals model can be used to identify boundary models of others.
- AVerdadero
- BFalso
12A master model is the one used by the architect to include information from all three viewtypes
- AVerdadero
- BFalso
13All systems are different and require different amounts of up front focus depending on how risky the project is.
- AVerdadero
- BFalso
14Presumptive architecture is a way of building systems within a specific domain, and using them will generally lead to a good solution within that domain.
- AVerdadero
- BFalso
15Architecture hoisting will ensure specific qualities or concerns are met
- AVerdadero
- BFalso
16A reference architecture is often an aspirational standard, while a presumptive architecture is a de facto standard
- AVerdadero
- BFalso
17Presumptive architectures succeed because the architecture is a good match for the common risks in the domain
- AVerdadero
- BFalso
18Component details in UML can be shown as text within a compartment of a component.
- AVerdadero
- BFalso
19Class diagrams can be generated directly from code
- AVerdadero
- BFalso
20The process of creating class diagrams is a valuable activity during design
- AVerdadero
- BFalso
21All class diagrams created during design of a system should be maintained as part of the project documentation.
- AVerdadero
- BFalso
22What architectural style is related to several design patterns, including the Document-View, Model-View-Controller (MVC), and Observer patterns?
- Ao Model-centered style
- Bo Mirrored style
- Co Rack style
- Do Server farm style
- Eo Pipe-and-filter style
23In what architectural style identical hardware is duplicated and run in parallel?
- Ao Model-centered style
- Bo Mirrored style
- Co Rack style
- Do Server farm style
- Eo Pipe-and-filter style
24In what architectural style commodity server computers are placed vertically to take up relatively little floor space?
- Ao Model-centered style
- Bo Mirrored style
- Co Rack style
- Do Server farm style
- Eo Pipe-and-filter style
25In what architectural style identical computers are located in the same room?
- Ao Model-centered style
- Bo Mirrored style
- Co Rack style
- Do Server farm style
- Eo Pipe-and-filter style
26What architectural style can be applied to the linguistic processing system?
- Ao Pipe-and-filter style
- Bo Model-centered style
- Co Mirrored style
- Do Rack style
- Eo Server farm style
27What Software Design Principle you can consider when writing your classes to make sure that when you need to extend their behavior you don’t have to change the class but to extend it
- Ao Open-Close Principle
- Bo Dependency Inversion Principle
- Co Interface Segregation Principle
- Do Single Responsibility Principle
- Eo Liskov’s Substitution Principle
28What Software Design Principle states that we should decouple high level modules from low level modules, introducing an abstraction layer between the high level classes and low level classes.
- Ao Open-Close Principle
- Bo Dependency Inversion Principle
- Co Interface Segregation Principle
- Do Single Responsibility Principle
- Eo Liskov’s Substitution Principle
29Clients should not be forced to depend upon interfaces that they don't use.
- Ao Interface Segregation Principle
- Bo Open-Close Principle
- Co Dependency Inversion Principle
- Do Single Responsibility Principle
- Eo Liskov’s Substitution Principle
30A class should have only one reason to change.
- Ao Single Responsibility Principle
- Bo Open-Close Principle
- Co Dependency Inversion Principle
- Do Interface Segregation Principle
- Eo Liskov’s Substitution Principle
Información
- Descripción
- God Philosophy Test sobre Sdp.3, creado por хомяк убийца el 23/05/2017.
- Autor
- хомяк убийца
- Idioma
- English
- Visitas
- 0
- Etiquetas
- Valoración
- Aún sin valoraciones Valora este test