Object-Oriented Software Engineering: Use Case Diagrams, Exercises of Computer Science

Download Object-Oriented Software Engineering: Use Case Diagrams and more Exercises Computer Science in PDF only on Docsity! Microlink Information Technology College Mid term mock exam – December 7, 2021 Degree Program: CS and SE Course Title: OOSE Course Code: CS-421 Teacher’s name: Terefe Feyisa Student’s name: School Id. No: Class: NA Semester: 1st Time duration: NA Total Marks: NA Exam Date: NA 1 Say TRUE or FALSE. 1. Software engineering is a process of analyzing user requirements and then designing, building, and testing software application which will satisfy those requirements. 2. Use case diagrams are a way to capture the system’s functionality and requirements in UML diagrams. 3. Views are used to address the problem: “The more information a model is supposed to give, the more complex and difficult it becomes”. 4. The focus of analysis in OOSAD is on finding and describing objects or concepts in the problem domain. 5. It captures the dynamic behavior of a live system. 6. An object technology is considered the best because, it avoids late delivery and over budget. 7. Analysis in OOSAD is an investigation of the problem and requirements, rather than searching for a solution. 8. An object technology enables users to manage their requirements in a manner that is easy to maintain and modify. 9. A use case represents a distinct functionality of a system, a component, a package, or a class. 10. An actor is an entity that initiates the use case from outside the scope of a use case. 11. The name of an actor or a use case must be meaningful and relevant to the system. OOSE Object Oriented Software Engineering — Use Case Diagrams Page 2 of 11 12. The focus of design in OOSAD is on defining software objects and how they collaborate to fulfill the requirements. 13. A purpose of use case diagram is to capture the core functionalities of a system. 14. reliability and scalability can be improved by means of object-oriented analysis and design application development. 15. System is a group of interacting or interrelated elements that act according to a set of rules to form a unified whole. 16. A use case diagram consists of a use case and an actor. 17. Design in OOSAD is a conceptual solution that fulfills the requirements, rather than its implementation. 18. A model is a simplified representation that is used to explain the workings of a real world system or event. 19. Code can be generated from models automatically. 20. The stages through which software goes from the time it’s first conceived to the time it’s retired from use are not the concern of UML. 21. A use case is a description of how a person who actually uses that process or system will accomplish a goal. 2 Explain the following concepts. System? System structure? System behavior? Object-Orientation? System Analysis? System Design? System Analysis and Design? Modeling? Requirements gathering? System requirements? Software life cycle? Waterfall models? Iterative models? Use case modeling? Use cases? Use case diagram? Design specification? Class diagrams? State machine diagrams? State? Activity diagrams? Activity? Communication diagrams? Sequence diagrams? 3 Essay questions. 1. How is a use case diagram different from a use case? Student’s name: Please go on to the next page… OOSE Object Oriented Software Engineering — Use Case Diagrams Page 5 of 11 (a) Association between an actor and a use case. (b) Generalization of an actor. (c) Extend relationship between two use cases. (d) Include relationship between two use cases. (e) Generalization of a use case. 16. Discuss UML as a Language. (One can visit: https://www.startertutorials.com/uml/overview-of-uml.html) (a) UML as a Language for Visualizing. (b) UML as a Language for Specifying. (c) UML as a Language for Constructing. (d) UML as a Language for Documenting. Student’s name: Please go on to the next page… OOSE Object Oriented Software Engineering — Use Case Diagrams Page 6 of 11 17. Discuss software development process. (One can visit: https://en.wikipedia.org/wiki/Software_development_process) 4 Fill in the blank questions by Matching Match the most appropriate term to each concept. Not all terms are used. No term is used twice. Software Dev’t Process Requirements Document Software Life Cycle UML The Waterfall Model Iterative Methodologies 1. specifies the purpose of a system and what it must do. 2. is the stages through which software goes from the time it’s first conceived to the time it’s retired from use. 3. is thus a standard language for software blueprints. 4. is the process of dividing software development work into smaller, parallel or sequential steps or subprocesses to improve design, product management. 5. is a sequential development approach, in which development is seen as flowing steadily downwards (like a waterfall) through several phases. 6. focus on limited project scope and expanding or improving products by multiple iterations. 5 Choose the best answer. 1. model the interactions among objects in a system with an emphasis on when these interactions occur. 4 marks A. Class diagrams B. Sequence diagrams C. Communication diagrams D. Activity diagrams 2. Which of the following choices lists stages of a typical software life cycle in sequential order? Student’s name: Please go on to the next page… OOSE Object Oriented Software Engineering — Use Case Diagrams Page 7 of 11 A. design, analysis, implementation, testing B. design, analysis, testing, implementation C. analysis, design, testing, implementation D. analysis, design, implementation, testing 3. Use cases can be in a relationship with other use cases. Which one of the following is TRUE about «include» relationships and «extend» relationships? A. If a use case A includes a use case B, represented as a dashed arrow from A to B labeled with the keyword «include», the behavior of B is integrated into the behavior of A. B. If a use case A includes a use case B, represented as a dashed arrow from A to B, A is referred to as the base use case and B as the included use case. C. The base use case always requires the behavior of the included use case to be able to offer its functionality. D. An included use case can be executed on its own. E. If a use case B is in an «extend» relationship with a use case A , then A can use the behavior of B but does not have to. F. An «extend» relationship is shown with a dashed arrow from the extending use case B to the base use case A. G. Both use cases, extending and base, can be executed independently of one another. 4. Which of the following is False about a model? It . A. provides a blueprint for some artefact. B. ensures standardization of a product. C. guaranties all requirements are met. D. permits to evaluate a design against a criteria. E. help to capture and record software design decisions. F. All are correct statements. G. All but C. 5. and are the most commonly used kinds of UML diagrams for use cases. A. use case diagrams, class diagrams B. sequence diagrams, package diagrams C. class diagrams, component diagrams D. use case diagrams, sequence diagrams Student’s name: Please go on to the next page… OOSE Object Oriented Software Engineering — Use Case Diagrams Page 10 of 11 7 Match the UML diagrams and terminologies. 1. Use case 2. Inheritance 3. Actor 4. Extension of a use case by another 5. Notes 6. System boundary 7. Include of a use case by another 8. Actor to use case association 8 Workouts. 1. Draw a use case diagram based on the following Bank Requirement Document. Requirements Document A local bank intends to install a new automated teller machine (ATM) to allow users (i.e.,bank customers) to perform basic financial transactions (see Fig.1). Each user can have only one account at the bank. ATM users should be able to view their account balance, withdraw cash (i.e., take money out of an account) and deposit funds (i.e., place money into an account). Suppose the system is also enabled a user of our ATM system to transfer money between two bank accounts. The user interface of the automated teller machine contains: Student’s name: Please go on to the next page… OOSE Object Oriented Software Engineering — Use Case Diagrams Page 11 of 11 • A screen that displays messages to the user. • A keypad that receives numeric input from the user. • A cash dispenser that dispenses cash to the user and • A deposit slot that receives deposits from the user. Figure 1: Automated teller machine user interface. 2. Draw a use case diagram based on the following document. Student Administration Requirement Document A student administration system is used by a professor to query student’s data, issue certificate and announce exam. 3. Draw a use case diagram based on the following (yet another) document. Student Administration Requirement Document A student administration system is used by a professor to reserve lecture halls and announce lectures. Whenever a new lecture is announced, the use case assign lecture must also be executed. The professor is involved in the execution of both use cases. When a new lecture is announced, it is possible (but not mandatory) to reserve a lecture hall. Student’s name: End of exam