1 / 6

Lab Course Scheduler: Robust File Handling and Custom Output Generation

The Lab Course Scheduler is a user-friendly program developed by Team Name, consisting of students 1, 2, 3, and 4. Users can specify input files, with the program adeptly handling any file format errors to ensure robust performance. The application generates an output file with lab courses organized into designated days and times, allowing customization of output name and location. Utilizing object-oriented design principles and tested thoroughly for reliability, this tool simplifies lab scheduling and enhances productivity.

arne
Download Presentation

Lab Course Scheduler: Robust File Handling and Custom Output Generation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Program Name Developed by Team Name Student1, Student2, Student3, Student4

  2. Demonstration • User can specify the input file, program reads in the file • Program deals robustly with any file format errors • Program produces an output file with all lab courses properly fitted into the assigned days and times • User is able to specify the output file name and location

  3. Object-Oriented Design • Insert UML class diagram here Reflections?

  4. Pattern(s) used • Pattern 1 used • Justification and advantages • Pattern 2 used • Justification and advantages Reflections?

  5. Testing • Program Stats • # classes, # methods, total lines of code • Unit testing Stats • # classes, # methods, total lines of test code • Unit testing code coverage % Reflections?

  6. Implementation • Repository stats • Number of revisions (use TortoiseSVN > show log) • Program style • NetBeans analyze Javadoc results • Conventions used and enforced (pmd) • Packaging and completion of Integration 1 status report

More Related