Open-ended and Closed-ended Questions, Interviewing Users and Other Stakeholders, and Database Management System Concepts, Exams of Computer Science

The differences between open-ended and closed-ended questions and how they can be used to encourage discussion and obtain specific facts. It also explores the benefits of interviewing users and stakeholders to understand business functions and rules. Additionally, it covers concepts related to database management systems, such as managing multiple DBMS environments, protecting data and databases, and schema normalization. The document also explains the concepts of visibility, stereotypes, entity classes, class-level attributes, and methods.

Typology: Exams

2023/2024

Available from 10/25/2023

ClemBSC
ClemBSC 🇺🇸

3.8

(32)

1.6K documents

1 / 6

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
ICT2622 Semester 2
Assignment 2
2023
pf3
pf4
pf5

Partial preview of the text

Download Open-ended and Closed-ended Questions, Interviewing Users and Other Stakeholders, and Database Management System Concepts and more Exams Computer Science in PDF only on Docsity!

ICT2622 Semester 2

Assignment 2

  • ICT
  • Unique Number:
  1. Add any other required utility classes that are needed to the solution. For example, for a three- layer design, data access classes will be part of the solution. Usually, each persistent domain class will have a data access class to read and write to the database.

Question 3

3.1. A guiding philosophy and set of guidelines for developing information systems in an unknown, rapidly changing environment. 3.2. Value responding to change over following a plan. Value individuals and interactions over processes and tools. Value working software over comprehensive documentation. Value customer collaboration over contract negotiation 3.3. The Unified Process (UP) is an object-oriented system development methodology originally offered by Rational Software, which is now part of IBM. 3.4. Inception Phase - Develop an approximate vision of the system, make the business case, define the scope, and produce rough estimates for cost and schedule. Elaboration Phase - Define the vision, identify and describe all requirements, finalize the scope, design and implement the core architecture and functions, resolve high risks, and produce realistic estimates for cost and schedule. Construction Phase - Iteratively implement the remaining lower-risk, predictable, and easier elements and prepare for deployment. Transition Phase - Complete the beta test and deployment so users have a working system and are ready to benefit as expected.

Question 4

Internal Stakeholders - Persons within the organization who interact with the system or have a significant interest in its operation or success. External Stakeholders - Persons outside the organization’s control and influence who interact with the system or have a significant interest in its operation or success. Operational Stakeholders - Persons who regularly interact with a system in the course of their jobs or lives. Executive Stakeholders - Persons who don’t interact directly with the system but who either use information produced by the system or have a significant financial or other interest in its operation and success.

Open-ended Questions - Such as “How do you do this function?” - encourage discussion and explanation. Closed-ended Questions - Such as “How many forms a day do you process?” - are used to get specific facts. 4.3. Interviewing users and other stakeholders is an effective way to understand business functions and business rules.

Question 5

5.1. The person in charge of the safety and operation of the DBMS. 5.2. Managing a multiple DBMS environment. Protecting the data and database, including user authentication and attack prevention.

Question 6

Question 7

7.1. Visibility denotes whether other objects can directly access the attribute. (A plus sign indicates that an attribute is visible, or public; a minus sign indicates that it isn’t visible, or private.)