Contact person: Simplified Java Document Search Engine

Phone:Show

Email:Show

Location: San Jose, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"1. Objective
The goal of this project is to design and implement a simplified document search engine in Java. The
system should integrate core data structures and algorithms, providing indexing, querying, ranking, and
navigation capabilities while also allowing for performance evaluation of different approaches.
2. Required Components
Your implementation must cover the following areas: - Linked Lists, Stacks, and Queues: Implement
a generic singly linked list with insertion, deletion, traversal, and size operations. Build a stack using
arrays and a queue using your linked list. Include a tokenizer that processes text files into words stored
in a linked list. - Sorting and Searching: Implement merge sort and quick sort for string arrays.
Provide runtime measurements for various input sizes. Implement linear search (unsorted) and binary
search (sorted) and compare performance both theoretically (Big-O) and empirically. - Trees and Hash
Tables: Implement a Binary Search Tree Map (BSTMap) mapping words to document IDs. Implement
a separate-chaining hash table (HashMap) and compare its performance with the BST. Extend the
design to include balanced trees (AVL and Red–Black), ensuring proper balance maintenance after
insertions. - Search Engine Assembly: Build an inverted index from a directory of text documents,
tracking word frequency and document associations. Implement query processing to retrieve ranked
results for both single and multi-term queries. Integrate back/forward navigation using your stack and
queue structures. - Performance Analysis: Conduct experiments to compare average search times
across BST, AVL, Red–Black, and Hash Tables. Include results on sorted vs. random data. Prepare a
concise report (tables/graphs) that summarizes findings and reflects on trade-offs between structures
and algorithms.
3. Deliverables
The final handover should include: - Java source code (modular, clean, documented). - JUnit or
equivalent tests demonstrating correctness and edge-case handling. - A report (2–3 pages) with
experiment results, graphs/tables, and a reflection on design trade-offs.
4. Work Quality Expectations
All code should follow standard Java conventions with clear class and method naming. Inline
comments should be provided to explain logic. Testing must confirm correctness, including handling of
edge cases. Documentation should be professional and concise.
5. Timeline & Completion
The entire scope should be completed within the agreed timeline. Final delivery must include all code,
test cases, and the written report packaged for submission" (client-provided description)