How coltonc3/comp250 works
Project Type and Purpose
• The repository is not a single full-stack application; it is a collection of separate assignments covering topics such as KD Trees, implementing big integers, search engine functionalities with XML parsing, and a strategy game simulation.
• The README emphasizes the course’s focus on mathematical tools, fundamental data structures, algorithms (both recursive and non-recursive), and abstract data types.
• Each assignment (e.g., KDTrees, MyBigInteger, SearchEngines, StrategyGame) is implemented as a standalone project within the repository, with its own source files and test or assignment instructions (e.g., “A1.pdf”, “A2.pdf”, etc.).
File Structure
• Top-level directories (KDTrees, MyBigInteger, SearchEngines, StrategyGame) represent independent modules or assignments.
• Each directory’s “src” subfolder contains the primary Java source files that implement the key functionality.
• There are test or demo classes (e.g., TestAllCases.java, MiniTester.java, SyntaxTester.java) which indicate where unit tests or simulators are.
• The PDFs (A1.pdf, A2.pdf, etc.) likely contain assignment specifications that further detail expected design and functionality.
• Central Component: “COMP250 Coursework” – this is the overarching container. Underneath, list each assignment as a separate component.
• For KDTrees:
• Components: KDTree, Datum, and accompanying test classes (Tester.java, TestAllCases.java).
• Relationship: KDTree uses/operates on Datum objects; test classes validate functionality.
• For MyBigInteger:
• Components: MyBigInteger.java and TesterPosted.java.
• Relationship: The main arithmetic logic is encapsulated in MyBigInteger, while the tester exercises its methods.
• For SearchEngines:
• Components: SearchEngine, MyWebGraph, XmlParser, Sorting, and driver classes (GraderV2.java, MyTester.java).
• Relationships: Likely, the SearchEngine orchestrates interactions with MyWebGraph (for linking or indexing) and XmlParser (for interpreting XML test files). Sorting is a utility which might be used in indexing or query processing.
• For StrategyGame:
• Components: MilitaryUnit (base type) and its derived classes such as Archer, Warrior, Settler, Worker, and other supporting components like Tile and ListOfUnits.
• Relationship: The game simulation illustrates interactions among different units and terrain (Tile), with test classes (MiniTester.java, SyntaxTester.java) ensuring game rules and behavior.
Architectural Patterns / Design Principles
• Though these assignments are largely self-contained, you might note common Java object–oriented design principles (inheritance used in StrategyGame, encapsulation in MyBigInteger, modularization in SearchEngines).
• “utility” or “helper” modules (for instance, the XmlParser and Sorting in SearchEngines) that support core functionality.