Exam Paper PDF

(2 MARKS) [Chapter-Page] 1. System Analysis [1-1] System Analysis means understanding and specifying in detail what the information system should do. 2. System Design [1-1] System Design means specifying in detail how the various components of the information system should be physically implemented...

(2 MARKS) [Chapter-Page] 1. System Analysis [1-1] System Analysis means understanding and specifying in detail what the information system should do. 2. System Design [1-1] System Design means specifying in detail how the various components of the information system should be physically implemented. 3. Information System [1-1] An Information System is a collection of interrelated components that collect, process, store, and provide the information needed as output to complete a business task. 4. Project [3-1] A project is planned undertaking that has a beginning and an end, and which produces a predetermined result or product. 5. Project Management [3-1] Project management is the organizing and directing of other people to achieve a planned result within a predetermined schedule and budget. (3 MARKS) 1. Two main principles of structured design [2-5] Two main principles of structured design are that program modules should be designed so that they are loosely coupled and highly cohesive. Loosely coupled means each module is as independent of the other modules as possible, which allows each module to be designed and later modified without interfering with the performance of the other modules. Highly cohesive means each module accomplishes one clear task. 1 Page 2. The critical path in project schedule [3-3] The longest path, from the first task to the last task, of dependent tasks is called the critical path because if any of the tasks on that path slip, then the entire project schedule will slip. 3. List three types of Information System [1-5] 1) Executive Information Systems (EIS) 2) Management Information Systems (MIS) 3) Transaction Processing Systems (TPS) (4 MARKS) 1. Differences between a Use Case Diagram and an Activity Diagram [7-9] Use Case Diagram: Shows a static view of the system functions and their static relationships with both external entities and with one another. Activity Diagram: Describes a dynamic view of those functions. In particular, it can specify the time-sequencing of the functions relative to one another, or the time-ordering of the steps required to carry out an individual function. 2. The advantages of storyboard [4-9] The advantages of storyboarding are: 1. Extremely inexpensive 2. User friendly, informal, and interactive 3. Provide an early review of the user interfaces of the system 4. Easy to create and easy to modify 3. Differences between a class and an object [8-16] [8-18] Definition: Class: A class is a description for a set of objects that shares the same attributes, and has similar operations, relationships, behaviors and semantics. Object: An object is an instance of a class. An object can be viewed as an entity at a particular point in time with a specific value and as a holder of identity that has different values over time. Memory Allocation: Class: No memory is allocated when a class is defined. 2 Object: Memory is allocated when an object is created. Page Nature: Class: A class is a logical entity. Object: An object is a physical entity. Example: Class: ❖ Consider a class ‘Student’. ❖ Attributes: name, student_id, major, GPA ❖ Methods: study(), attend_class(), submit_assignment() Object: ❖ Object 1: An object of the class ‘Student’ could be ‘student1’, which has specific values for name (e.g., Alice), student_id (e.g., 12345), major (e.g., Computer Science)and GPA (e.g., 3.8). ❖ Object 2: An object of the class ‘Student’ could be ‘student2’, which has specific values for name (e.g., Bob), student_id (e.g., 67890), major (e.g., Mathematics)and GPA (e.g., 4.6). (5 MARKS) 1. The phases of waterfall model [2-8] The waterfall model development proceeds linearly from 1) requirements analysis 2) design 3) code and unit testing 4) subsystem testing 5) system testing. 2. Differences between Model and Tool [2-2] Models A model is a representation of some important aspect of the real world. Consider a model of an airplane. Different types of models, such as 3D shapes, cross-sectional drawings, or mathematical characteristics, can be used depending on what aspect of the object needs to be understood. In system development, models represent various elements like inputs, outputs, processes, and object interactions, typically through graphical representations using standardized symbols. 3 Page Tools A tool in the context of system development is software support that helps create models or other components required in the project. Tool may be simple drawing programs for creating diagrams. They might include a database application that stores information about the project. The most advanced tools for system developers are known as CASE (Computer-Aided System Engineering) tools. CASE tools assist analysts in developing system models, ensuring their completeness and compatibility, and can even automatically generate program code based on these models. 3. What is Inheritance? Give Some Examples of Inheritance. [6-11] Inheritance Inheritance is an operational result of specialization. A child (subclass) inherits all attributes, associations, and operations of its parent (superclass). For example, the Automobile class inherits the VehicleID attribute from Vehicle. As a result, when the automobile object is created, it will have all the properties of both vehicle and automobile. Figure: The Class Specialization Relationship 4 Page (6 Marks) 1. For steps of the development project schedule [3-2] Developing a project schedule is a four-step process. In the first step, the project members identify all of the individual tasks for each activity as well as those activities that are unique to the specific project. The second step is to estimate the size of the task. This means estimating the number of human resources, the person-days required, the calendar time required and any other special resources that may be needed. The third step is to determine the sequence for the identified tasks. The team accomplishes this step by determining which tasks are predecessors for a given task. The final step is to schedule the tasks themselves, taking into account that resources cannot be double-scheduled. Although the scheduling of the tasks is not always simple, techniques and tools are available to help create a project schedule. 2. Three-tiered Architecture [9-1] A common layered system organization is the three-tiered architecture shown below. The user interacts with the top tier, the presentation layer, which contains the user interface. The presentation layer makes requests to the application layer, which contains the business logic. This layer loads and stores items in persistent storage (file, database, etc.), using a set of data services provided by the persistence layer. Presentation Layer GUI, etc. Business Logic Application Layer Data Repositories and Services Persistence Layer Figure: A Three-Tiered Architecture 5 Page Diagram for Practice 1. Draw ER Diagram 2. Modify Diagram (Possibility => Use Case Diagram) ER Diagram [ Sample Questions ] 1. Construct an E-R diagram for a car-insurance company whose customers own one or more cars each. Customer is listed with name, address and driver id. Car contains model, year, license and each car has associated with it zero to any number of recorded accidents. Accident is recorded with report_number, location and date. 2. A Bookstore has six branches in Yangon. Each staff works in a branch and registered customers can place the order online at website. Every order will have to delivery by a staff. 6 Page 3. United Direct Artists (UDA) is an insurance broker that specialise in insuring paintings for galleries. You are required to design a database for this company. The database must store painters, paintings, and galleries information. Painters have a unique number, Name, and phone number Paintings have unique number, title and price Galleries have unique number, owner, phone number, commission rate and address A painting is painted by a particular artist, and that painting is exhibited in a particular gallery. A gallery can exhibit many paintings, but each painting can be exhibited in only one gallery. Similarly, a painting is painted by a single painter, but each painter can paint many paintings. 7 Page 4. The database must store book, author, publisher and warehouse information. For every book you must capture the title, isbn, year and price information. The ISBN value is unique for a book. For every author you must store an id, name, address and the URL of their homepage. Each author can write many books, and each book can have many authors, for example. For every publisher you must store an id, name, address, phone number and an URL of their website. Books are stored at several warehouses, each of which has a code, address and phone number. ØA book has only one publisher. The warehouse stocks many different books. A book may be stocked at multiple warehouses. The database records the number of copies of a book stocked at various warehouses. Design an ER diagram for such a bookstore. Your ER diagram must show entities, attributes and the relationships between entities. 8 Page