Answer these quesions:(Only number question and correct answer without more details):

1. Software design describes the software architecture which in-turn describes: (a) how software is decomposed and organized into components and their interfaces (b) functional characteristics (c) functional and non-functional characteristics (d) how software is assembled and organized into a cohesive bundle

2. Software design consists of two activities that t between software requirements analysis and software construction: (a) Software architectural design and Software detailed design (b) Software component design and Software interface design (c) Software pattern design and Software verication (d) Software component design and Software verication

3. In the context of software design principles, cohesion is dened as (a) the degree of interface compatibility (b) a measure of the interdependence among modules in a computer program (c) a measure of the strength of association of the elements within a module (d) the degree of of both input/output and interface compatibility

4. In the context of software design principles, coupling is dened as (a) the degree of interface compatibility (b) a measure of the interdependence among modules in a computer program (c) a measure of the strength of association of the elements within a module (d) the degree of of both input/output and interface compatibility

5. Design for concurrency is concerned with dealing with issues related to (a) eciency, atomicity, synchronization, and scheduling (b) deadlocks, gridlocks, parametrization, and monitoring (c) speed, capacity, multi-threading, and resource allocation (d) All of the above

6. While there are various attributes that contribute to the quality of a software design, there is an interesting distinction between quality attributes discernible at (a) the high-level design phase and those discernible at the detailed design phase (b) run-time versus pre-loaded and those related to the architectures performance qualities

(c) run-time versus not run-time and those related to the architectures intrinsic qualities (d) the requirements analysis phase and those discernible at the architecture design phase

7. Fault-tree analysis and automated cross-checking are two types of (a) Design review analysis (b) Static analysis (c) Feasibility analysis (d) Prototyping analysis

8. Measures are classied in two broad categories: (a) function based measures and OO design measures (b) function based measures and cohesion measures (c) function based measures and coupling measures (d) function based measures and Agile design measures

9. A good design must (a) implement all explicit requirements from the analysis model and accommodate all implicit requirements desired by the user (b) be readable and understandable guide for those who generate code, test components, or support the system (c) provide a complete picture (data, function, behavior) of the software from an implementation perspective (d) All of the above

10. The FURPS Quality Factors are: (a) Functionality, Reliability, Performance and Stability (b) Feasibility, Usability, Robustness, Persistence and Supportability (c) Functionality, Usability, Reliability, Performance and Supportability (d) Feasibility, Reliability, Performance and Stability ____________________________________________________ 11. T / F This design issue concerned with how to handle long-lived data is called: data persistence. 12. T / F The MVC approach is an example of the Interaction and Presentation design issue concerned with structuring and organizing interactions with users and the presentation of information. 13. T / F Architectural styles and design patterns are design concepts that can be used to design families of programs (also known as product lines). 14. T / F A design pattern describes a solution that happens to be an exception but to a common problem in a given context. 15. T / F The data ow architectural style describes input data that is transformed by a series of computational or manipulative components into output data. 16. T / F An archetype is a class or pattern that represents a core abstraction critical to the design of an architecture for a core system. 17. T / F An archetype determine the dynamic elements of the architecture that tend to continuously change and will need to be implemented when the system is built. 18. T / F Archetypes are the abstract building blocks of an architectural design. 19. T / F In the context of design class characteristics, primitiveness describes the characteristic in which each class method focuses on providing one service. 20. T / F Functional independence is achieved by developing modules with single-minded purpose and an aversion to excessive interaction with other models.