Reference no: EM131950585
Assignemnt
You may consult any book, your notes, D2L discussions, and any other reference material, including online references. You may not discuss the examination with others, whether they are members of the class or not.
1. Explain the steps in a generic design process.
2. Carefully distinguish between architectural-design, mid-level design and low level design.
3. What are the two main techniques for evaluating architectural design alternatives? Carefully explain them.
4. Does the MVC style insulate the user interface from changes in the application domain? Justify your answer.
5. Explain how the Layered style supports reuse.
True or False
1. UML use case diagrams are dynamic models of all the use cases in a product.
2. Project Mission Statement Template includes "Business Requirements."
3. Architectural design is high-level software engineering design analysis.
4. A good architectural style supports all quality features.
5. Activity diagrams can represent any process and are useful throughout software design.
6. During the architectural design step we specify the internal details of each component.
7. Regarding activity diagrams, an activity is an atomic task or procedure that cannot be broken into parts.
8. Regarding activity diagrams, an initial node produces a token on each outgoing edge when an activity begins.
9. Software requirements specification (SRS) is the main input for the product design process.
10. With respect to product design principles,simplicity means: Adesign is acceptable only if it is simple and easy to understand.
11. A set of requirements is consistent if it includes every relevant requirement.
12. Every use case diagram must have at least one actor associated with each use case.
13. Postconditions must be true when the use case ends whether it is successful or not.
14. Use case models provide atomized requirements statements.
15. Product Design Principles include feasibility, usability, economy and changeability.
16. Only direct adjacent layers can invoke each other's methods in a layered architecture.
17. There is data sharing between all layers in a layered architecture.
18. A UML diagram must provide a complete view of the entire software system.
19. The MVC style should be used to separate an interactive interface from the remainder of a program, thus increasing user interface flexibility.
20. Among the advantages of layered architecture is "each layer is selected to be a set of related services; thus the architecture provides high degree of cohesion within the layer."
21. A resolution model is any representation of a design problem.
22. Architecture design is a problem-solving activity whose input is the SRS document and whose output is the SDD.
23. All architectural designs are the same in terms of their level of. abstraction.
24. Architectural Design better done as an individual first and then bring together all the individual architectural design suggestions.
25. Finalizing The Architectural Design step ensures that the selected architecture does satisfy the various functional and non-functional requirements (and possibly may delight the users) and is clearly documented.
26. In Low-Level Detailed Design PAID stands for Packaging, Algorithms, Interfaces, and Data structures.
27. In Layered architecture if any layer only uses the layer directly below it, then it is a Relaxed Layered Style.
28. In Layered architecture each layer may hide private information from other layers
29. In Pipe-Filter architecture Pipe is a mechanism that allows the flow of data.
30. Problems that fit Shared Data architecture includes real-time systems such as: airplane control, medical equipment monitor, home monitor,
31. In Model-View-Controller (MVC) architecture, Controller isthe portion that handles the data model and the logic related to the application functions.
32. In contrast to mid-level, low level detailed design fills in the details for programming purpose.
33. A program entity is visible at a point in a program if it can be "used" (read or change its value) at that point.
34. Regarding sequence diagrams, when an individual sends an asynchronous message, it blocks or suspends until the message returns.
35. State diagrams are a UML notation for describing finite automata.
36. Software architecture is crucial not only for satisfying a product's functional requirements, but also for satisfying its non-functional requirements.
37. Architectural design may begin during product design.
38. There is a clear boundary between architectural and detailed design.
39. Mid-level design must specify both static and dynamic aspects of components.
40. Hope you have done a good job up to this point. You get automatic credit for this one.
Attachment:- Lecture.zip