Problem identification and literature survey notes — Unit 1

The Minor Project in the 7th semester is a critical bridge between academic theory and the major project in the final semester. It is the first formal opportunity to apply engineering principles to a substantial, self-directed problem.

⇒1.1 Key Objectives

• To identify a real-world problem or research gap.
• To systematically review existing solutions and literature.
• To propose a viable technical architecture or algorithm.
• To practice formal technical documentation and presentation skills.

A project succeeds or fails based on how well the problem is defined. A vague problem leads to a vague, un-evaluable solution.

⇒2.1 Characteristics of a Good Problem Statement

• Specific: It addresses a narrow, defined issue, not a broad field. ('Improving latency in IoT edge nodes' instead of 'Making IoT better').
• Measurable: The success of the solution can be quantified (e.g., measuring accuracy, execution time, or memory footprint).
• Relevant: It addresses a current technical or societal need.
• Feasible: It can be reasonably attempted within the constraints of a single academic semester and available resources.

Scope creep—the continuous, uncontrolled growth of a project's requirements—is the leading cause of project failure.

⇒3.1 Boundaries

Clearly defining what the project will not do is as important as defining what it will do. For example, if building a predictive healthcare model, the scope might explicitly state: 'This project focuses on model accuracy using static datasets and will not include a real-time web portal or HIPAA-compliant deployment.'

Before building a solution, you must understand what already exists. A literature survey is a comprehensive review of prior research, existing software, and technical papers related to your problem.

⇒4.1 Purpose of the Survey

• To ensure you are not 'reinventing the wheel'.
• To understand the current state-of-the-art algorithms or tools.
• To identify the specific gaps or flaws in existing systems that your project will address.
• To justify your choice of methodology by comparing it against others.

⇒5.1 Sourcing Credible Information

A technical literature review relies on peer-reviewed sources and official documentation, not random blog posts.

• Digital Libraries: IEEE Xplore, ACM Digital Library, SpringerLink, ScienceDirect.
• Search Engines: Google Scholar.
• Pre-print Archives: arXiv (especially for recent machine learning and computer science papers).

When reading a paper, focus on the Abstract, Methodology, and Conclusion to quickly determine relevance.

A literature review is not simply a list of summaries. It must synthesize the information.

⇒6.1 Synthesis and Comparison

Organize the review thematically or chronologically. Create comparison tables that contrast existing systems based on parameters like accuracy, speed, technology stack, and limitations.

The conclusion of your literature review should explicitly state: 'Based on this review, existing systems suffer from limitation X. This project proposes to solve limitation X using approach Y.'

After identifying the problem and reviewing the literature, you must prove the project is actually doable.

• Technical Feasibility: Do we have the required hardware, software licenses, and programming skills?
• Operational Feasibility: Will the proposed solution actually solve the user's problem in a practical way?
• Economic/Resource Feasibility: Can this be completed with a zero or minimal budget?
• Time Feasibility: Can the scope be completed within the 3-4 months of the semester?

• Problem Statement: Must be specific, measurable, and bounded by a clear scope to prevent feature creep.
• Literature Survey: Essential for understanding the state-of-the-art and identifying the specific gap your project fills.
• Sourcing: Rely on IEEE, ACM, and Google Scholar for credible, peer-reviewed research.
• Feasibility: A critical check to ensure the project can be executed technically and chronologically before any code is written.