QUESTION 1
1.1 Similarities and Differences Between Classes and Use Cases
Similarity
Similarity- Classes and use cases both play essential roles in modeling systems. They are
used to define and detail different aspects of system requirements. Classes describe the
static structure of a system by specifying the data and methods associated with objects,
while use cases outline the functional interactions between users and the system (Booch
et al., 1999).
Difference
Difference- A class serves as a template for creating objects in object-oriented design,
focusing on internal data and behaviors. In contrast, a use case describes scenarios in
which users interact with the system to achieve specific goals. While classes are
concerned with the system’s structure and its components, use cases emphasize user
interactions and the system’s functionality (Jacobson et al., 1992).
1.2 Types of Questions in User Interviews
Open-Ended Questions
Purpose: These questions are designed to gather detailed insights into user experiences,
needs, and expectations. They encourage users to provide comprehensive responses that
reveal how they interact with the system and their business processes.
Example: "Can you walk me through the steps you follow when handling a customer
complaint from start to finish?"
Closed-Ended Questions
Purpose-These questions aim to obtain specific, quantifiable answers to confirm
particular details or facts. They are useful for verifying information and making clear
comparisons.
Example- "Do you utilize the system’s reporting feature daily? Yes or no?"
These question types help analysts collect both qualitative and quantitative data to
comprehensively understand business functions and rules (Sommerville, 2011).
1.3 System Design vs. System Analysis
, Question Answered- While system analysis addresses the "what" of a system—what the
system should do—system design answers the "how"—how the system will fulfill those
requirements. System design involves defining how the system will be constructed,
including architecture, components, and interfaces (Pressman, 2014).
Elaboration-System design takes the requirements identified during the analysis phase and
outlines the detailed plans for implementing these requirements. It includes specifying the
system’s architecture, data structures, and how different components will interact (Schach,
2011).
Question 2
2.1 Use Cases on Car Manufacturer Websites
When visiting car manufacturer websites such as those of VW, BMW, Mercedes, or Toyota,
potential buyers might find the following use cases:
Vehicle Search- Users can look for vehicles based on various criteria like make, model,
or features.
Vehicle Comparison-Users can compare different models to evaluate their specifications
and features side by side.
Request a Quote- Users can request pricing details for specific vehicles.
Schedule a Test Drive-Users can book appointments to test drive vehicles at local
dealerships.
Find a Dealership- Users can locate nearby dealerships or service centers.
These use cases align with typical goals of potential buyers seeking to research, compare, and
purchase vehicles (Osterweil et al., 2011).
2.2 Key Components of a Database Management System
The primary components of a Database Management System (DBMS) are:
1. Database Engine- Manages the storage, retrieval, and manipulation of data, handling
query execution and transactions.
2. Database Schema- Defines the organization of the database, including tables, fields, and
relationships.
3. Query Processor-Interprets and executes database queries, converting them into
operations on the database.
4. Transaction Manager- Ensures that transactions are processed reliably, maintaining
ACID (Atomicity, Consistency, Isolation, Durability) properties (Elmasri & Navathe,
2016).
