Skip to content

Chris-B33/UL-Student-Record-System

Repository files navigation

UL-Student-Record-System Project Progress

GitHub forks GitHub Repo stars

Description

This is a project undertook by me and a few classmates tocreate a mock student record system.
This system would hold students transcripts, make them accessible and editable by teachers and allow for review by department heads.

Installation

Download this repository and run "Interpreter.java" from the command line.
From there you can choose to act as a student, teacher or department.
There is also full documentation inside of the "docs" folder.

Meeting Summaries

Meeting 1:

  • Collaboratively brainstormed UML diagrams.
  • Identified classes and objects, establishing potential relationships between them.
  • Provisionally defined relationships.
  • Color-coded classes/objects based on predicted difficulty/time consumption.

Meeting 2:

  • Established a GitHub repository for project management.
  • Deliberated project functionality and outlined the best approach.

Meeting 3

  • Created CRC diagrams, referencing the UML diagram and utilizing insights from the GradeBook tutorial.
  • Discussed data storage methods, opting for CSV files, and addressed memory management considerations.

Meeting 4:

  • Discussed method signatures for classes, refining the project structure.
  • Added UML and CRC diagrams to the GitHub repository.
  • Task assignment for the upcoming meeting.

Meeting 5:

  • Reviewed individual progress.
  • Shared useful classes and methods for collaborative advancement.
  • Discussed and resolved any arising issues.
  • Committed updated changes to GitHub.
  • Conducted a trial run to assess the interaction of classes/objects.

Meeting 6

  • Team members committed their respective codes to GitHub for collective analysis.
  • Collaboratively addressed and resolved errors, providing assistance to team members.
  • Discussed overall project progress and identified elements needing completion before the next meeting.
  • Established a provisional deadline for comprehensive testing and analysis of the entire project.

Meeting 7

  • In-depth discussion of code errors, pinpointing areas requiring modification or addition before the provisional deadline.
  • Analyzed and strategized for necessary code changes to meet project requirements.

Final Meeting

  • Successfully added comprehensive Javadoc comments to all code files, enhancing documentation and code readability.
  • Systematically finalized and resolved any issues identified during the testing phase, ensuring the project's robustness
  • Completed and finalized the UML diagrams, providing a comprehensive visual representation of the project structure.
  • Created and added a detailed project instruction file, offering clear guidelines for future reference.