Master the characteristics of scientific CS research, problem formulation, research questions vs. hypotheses, and core motivations. Click "Reveal Model Answer" to test your readiness.
Part 1: Research Characteristics & Definition
M1-Q01[DEFEND & COMPARE]
Define scientific research in Computer Science and state why standard software programming or building a website alone does NOT constitute research.
NUST Model Answer [5 Marks]:
Research in CS is a controlled, empirical, critical, and systematic inquiry designed to solve an identified problem and generate new, generalizable knowledge.
Why mere coding is not research:
Lack of Generalizability: Building a custom website solves an isolated engineering task, whereas research must yield generalizable insights, models, or algorithms applicable beyond a single application instance.
Absence of Systematic Methodological Evaluation: Software development focuses on execution; research requires controlled experimentation, baseline comparison, and critical evaluation of trade-offs.
⚠️ Examiner Trap Alert: Never confuse a software engineering tool artifact with the research contribution. The tool is merely the instrument used to test a research hypothesis or evaluate a model.
M1-Q02[APPLY & SOLVE]
State and explain the SIX core characteristics that qualify a process as valid Computer Science research. Give a concrete CS benchmarking example for "Controlled".
NUST Model Answer [6 Marks]:
1. Controlled: Extraneous variables are isolated. CS Example: When benchmarking execution time of a new Rust media player vs. a C++ player, CPU hardware, RAM, OS background processes, and input file sizes must be held strictly constant.
2. Valid and Verifiable: Conclusions follow logically from evidence, and independent researchers can replicate the experiment environment to get identical results.
3. Empirical: Conclusions are anchored in hard, observable data collected from real-world execution or empirical trials, not gut feelings.
Distinguish between a Research Problem Statement, a Research Aim, and Research Objectives. Provide a CS example of each for an Educational Behavioral Firewall project.
NUST Model Answer [6 Marks]:
Problem Statement (1 paragraph): A clear statement of a specific gap or failure in existing solutions. CS Example: "Existing static perimeter firewalls fail to dynamically detect and suppress packet loop anomalies generated by unauthorized student peer-to-peer proxy scripts in university networks, resulting in bandwidth congestion."
Aim (1 sentence - The "What"): Broad ultimate destination. CS Example: "The aim of this research is to design, implement, and evaluate a dynamic behavioral network firewall for educational institution LANs."
Objectives (3-4 bullet points - The "How"): Measurable steps starting with action verbs (Design, Implement, Measure, Evaluate, Compare).
1. To analyze network traffic patterns and identify signature metrics of unauthorized student proxy scripts.
2. To design a behavioral inspection algorithm that dynamically flags packet loop anomalies.
3. To evaluate the latency impact and detection accuracy of the proposed firewall against standard Snort IDS baselines.
M1-Q04[DEFEND & COMPARE]
Compare a Research Hypothesis with a Research Question (RQ). When is a Hypothesis appropriate versus a Research Question in CS research?
NUST Model Answer [5 Marks]:
Hypothesis: A tentative, testable prediction about the directional relationship between variables (typically used in quantitative experimental research).
Structure: "If [Independent Variable], then [Dependent Variable]."
CS Example: "Implementing dynamic memory compression in the Linux kernel scheduler will reduce cache miss rates by at least 25% under high workload."
Research Question (RQ): An open-ended inquiry used when exploring a novel area where prior empirical data is insufficient to formulate a directional prediction (qualitative or exploratory research).
CS Example: "What are the primary architectural bottlenecks experienced by developers deploying microservices on serverless platforms?"
M1-Q05[CRITIQUE & AUDIT]
EXAM TRAP AUDIT: Identify 3 critical mistakes in this draft problem statement and rewrite it to pass NUST examination standards:
"Our aim is to write a fast Flutter app with a Firebase database because current student mobile portals are slow and boring."
NUST Model Answer [6 Marks]:
3 Flaws Identified:
Framed as an engineering task rather than a research inquiry: "Write a fast Flutter app" is a software task, not a research gap.
Unscientific / Subjective language: Terms like "boring" are non-empirical and unacceptable in academic writing.
Lack of quantitative evidence or metrics: "Slow" is undefined; no baseline metrics or specific bottlenecks are cited.
Corrected NUST-Standard Problem Statement:
"Existing mobile student portals suffer from unoptimized client-side data serialization, resulting in latency spikes exceeding 4.2 seconds during peak registration periods (Moyo & Ncube, 2024). Current caching architectures fail to maintain offline state synchronization without causing data inconsistency across concurrent user sessions."