Faculty of Information Technology Department of SE Marking Scheme

Transcription

1 Philadelphia University Lecturer : Dr. Moayad A. Coordinator : Dr. Moayad A. Internal Examiner: Dr. Murad Mouash Software Design (721322) Date: zo" December Second Exam Section: 1 Faculty of Information Technology Department of SE Marking Scheme 1st semester Time: 50 Minutes Information for Candidates 1.This examination paper contains 4 questions. Question 1 carries 6 marks. Question 2 carries 6 marks. Question 3 carries 4. Question 4 carries 4. The total is The marks for parts of questions are shown in round brackets. I. Basic Notions Objectives: The aim of the question is to evaluate your knowledge and skills concerning with the basic concepts of Software Design-2. Question 1: (6 marks) (a) Which ofthe following is a design pattern? Explain your conclusion. [2 marks (0.5 mark for each branch)] 1- An object oriented design. (no) ~s.l4n cj~'3vl 2- The ability to varying the order in which a printt) method is applied to the elements of a vector. (no).\\;. J\u.t ~ ~e:fj(oci 3- Varying the order in which a prints} method is applied to the elements of a vector by introducing a class whose w\methods include a method like go'i'olilemenu), (yes) 4- Capturing the mutual behavior of a pair of objects of two classes by introducing a third class aggregating the two classes. (yes) (b) 1. Circle all of the correct answers for each problem: [4 marks (0.5 mark for each branch)] Graphically represents the processes that capture, manipulate, store and distribute data between a system and its environment and system components is: a. Conceptual data modeling. b. Class diagram. c. Process modeling. d. All of the above. 2- represents internal structure and functionality of process depicted on a DFD. a. Data Flow Diagram. b. Logical Modeling. c. Collaboration Diagram. d. None of the above. 3- Main goal of conceptual data modeling is to create accurate: a. Class Diagram. b. E_R Diagram. c. Use Case Diagram. d. Package Diagram. 4- only offers a modeling notation not a methodology for how to do modeling: a. DFD. b. E R. c. UML. d. OMG.

2 5- Parallel execution is possible and synchronization is representable when we are using: a. Interaction Diagram. b. State Diagram. c. Class Diagram. d. Activity Diagram. 6. Software Architecture illuminates the top level design decision: a. System is composed of interacting parts. b. Main pathways of interaction. c. Key properties of the parts. d. All of the above. 7. Components Contains a set of: a. Diagrams. b. Data bases. c. Collaborating Classes. d. Interfaces. 8. the single mindedness of a module. a. Coupling. b. Cohesion. c. Design Level. d. Interface. 11. Familiar Problems Solving Objectives: The aim of the question is to evaluate your basic knowledge of the key aspects of the lectures material and your ability to solve familiar problems. Question 2 (6 marks) (2 marks for each branch) A. For the following class: Account Balance Name Number JobPosition WithdrawO Createstatmentt) Changl'asswordt) I-Is it a cohesive class. (no) 2-Explain how if your answer is "yes or no". 3-Draw a cohesive one if your answer is no. Account Balance Name Number WithdrawO Changl'asswordt)

3 B. What are the basic Design Principles? The Open-Closed Principle (OCP). "A module [component] should be open for extension but closed for modification. The Liskov Substitution Principle (LSP). "Subclasses should be substitutable for their base classes. Dependency Inversion Principle (DIP). "Depend on abstractions. Do not depend on concretions." The Interface Segregation Principle (ISP). "Many client-specific interfaces are better than one general purpose interface. The Release Reuse Equivalency Principle (REP). "The granule of reuse is the granule of release." The Common Closure Principle (CCP). "Classes that change together belong together." The Common Reuse Principle (CRP). "Classes that aren't reused together should not be grouped together." C. Draw the module diagram for the procedural call of the programs: PI calls P4 and PS. P2 calls PS and P8. P3 calls P4. P4 calls P6. P6 calls P7, P8, and P9. Calculate the coupling factor for the design. If it is complex suggest your own solution. Cop. c Pi) J +3 :::.~ uf' (P3) ~ I + I + s s: 5' Cop. c P2-) ::: ~ CDP- C.f: W) -: {;+5 +.:1. = ~ _ """''''1'''- e <U\oI W\ etr;j e, ~ c1ft1d < j

4 Question 3 (4 marks) A) What are the levels for the following: [2 marks (1 mark each)] 1- Cohesion. a. Functional b. Layer c. Communicational d. Sequential e. Procedural f. Temporal g. utility 2- Coupling. a. Content b. Common c. Control d. Stamp e. Data f. Routine call g. Type use h. Inclusion or import i. External B) What is the functionality of the following methods? [2 marks (1 mark each)] 1- renderkitche(kitchenstyle) in abstract factory design pattern applied to Kitchen Viewer. rt i'~kerti Me--th.t!>J b build ~ '"rjj /;&UII!-L :t c Ite-e-&PIII [n,f-iu s.t!:j~ F~oUcaJej b J mu.l:tr;ii. bj c~t"~ "",:11ft.lc 3 el- WdiC",J,rl< ~6{)/ 71~ tj t-i4. sw:.&. c]toser1 ;;t f'lvi 1>, rn:e: 2-getSingletonOjMyClassO in singleton design pattern. A public static factory method of My Class, getsingletonojmyclasso, is defined that returns SingletonOjMyClass. Thus, to to get this one and only element of MyClass, we merely invoke MyClass.getSingletonOjMyClass

5 Ill. Unfamiliar Problems Solving Objectives: The aim of the question is to evaluate your knowledge of the key aspects of the lectures material and your ability to solve unfamiliar problems. Question 4 (4 marks) You are responsible for designing an inventory subsystem of a large application. It is expected that this subsystem will be eventually grow into a set of at least 10 classes. You must design the beginning of the subsystem in away that presents a compact, well-define interface for the rest of the application. You can assume the rest of the application is represented by a class Client. Through maint) in Client, your code should execute the following use case. 1.The application display introduction. 2.The application repeats the following until the user decides to quit The application displays the inventory items by names and prompts the user to choose one The user enters an item name The application displays information about the item The application prompts the user for a model number The user reports the inventory of that model and item. Draw' an UML class diagram for this subsystem, together with the Client class. /n ~C'I-~~qtJ I'n ~~~.t/-.:- () I ~VC"..nt-»t-:) ulf-ej of ito'"-'.