How khyjb1995/mms2017fall works
Project type and purpose
• This is an academic “assignments” monorepo containing three independent coding exercises:
• Assignment 1 and Assignment 3: C++ console applications (built with Microsoft Visual C++/MSBuild).
• Assignment 2: A Java Swing audio tone generator (built with IntelliJ/Gradle or IDE-generated project structure).
• Purpose: each directory implements a standalone algorithm or functionality (e.g., audio signal generation, image processing), complete with source code, input data (audio .wav, PGM images), and build outputs.
File structure
• Top-level directories:
• Assignment 0, 1, 2, 3 – each a self-contained project.
• README.md at root: generic placeholder.
• For C++ assignments (1 & 3):
• Source: *.cpp, *.h, stdafx.* precompiled headers.
• MSBuild project files: .sln, .vcxproj, filters, and build logs under x64/Debug.
• Inputs and outputs (Assignment 3 uses i1.pgm, i2.pgm).
• For Java assignment (2):
• src/com/tonegenerator/Main.java + Main.form (UI layout).
• audio resources under audio/ and compiled classes under out/production.
• IntelliJ metadata (.iml).
• No shared libraries or cross-assignment dependencies—each module is independently buildable.
README for additional insights
• The README contains only placeholder paragraphs, lists, and a markdown table/image link—no architecture hints.
• This confirms there’s no overarching service or runtime: it’s strictly a collection of homework projects.
a. Main components
• “Assignment 1 Module” (C++ build pipeline + runtime)
• “Assignment 2 Module” (Java Swing application + audio resource loader)
• “Assignment 3 Module” (C++ image processing pipeline)
• “Shared Repository Structure” (version control layer)
• “External Tools” (MSBuild, Visual Studio, IntelliJ IDEA)
b. Relationships and interactions
• Developer → Git Repo → Checkout → Build Tools → Module Builds → Run
• Input resources (audio files, PGM images) are consumed by the respective modules at runtime.
• Outputs (executables, processed images) are produced and optionally committed.
c. Architectural patterns or design principles
• Monorepo pattern: multiple isolated subprojects sharing a top-level repo.
• Standard build pipelines per language (C++ MSBuild vs. Java IDE build).
• Resource folder for static inputs (audio/ in Assignment 2, .pgm in Assignment 3).
d. Key technologies and frameworks
• Microsoft Visual C++ (vcxproj, .sln) for Assignments 1 & 3
• Java Swing and IntelliJ IDEA project model for Assignment 2
• Git for version control