3460:421 Object-Oriented Programming (OOP) Spring 2021

News

• Finals Week Posted: Apr 30

  Announcements:

  • We do not have any activities during the University-scheduled Final Exam time. During Finals Week, the only thing you have to work on for this class is the XMLFramework project,
  • I do not have scheduled Office Hours during Finals Week. I am available by appointment. Contact me via Email, Discord, or Teams to schedule an appointment.
  • Remember that the XMLFramework project is due before Noon by 11:59:59 pm on Friday, May 7.

  XMLFramework

  • I fixed the CMake files in XMLFramework to better run on Windows and fixed some VC++ warnings on some of the provided code. If you already created the repository, these changes are in a pull request. This pull request will not change any of the files you are adding/changing.
  • Also regarding XMLFramework, you can add your refillBuffer.hpp and refillBuffer.cpp to the project if needed. The CMake build will take care of it automatically. Just make sure to verify that any files you add show up on GitHub. It is good to clone your project in another directory and build it to ensure any added files are in the repository.

  XML Framework and the Final Exam

  The in-person Final Exam was taken on Thursday, Apr 8, is Part I and consisted of 75 points. Part II of the Final Exam will come from your work on XML Framework. The questions in Part II:

  1. (5 points) Create a UML Class Diagram for the XMLFramework
  2. (5 points) Document the use of design patterns in the XMLFramework.
  3. (5 points) Fix the XMLFramework so that it has complete encapsulation and information hiding.
  4. (5 points) Document the software architectures used in the XMLFramework.
  5. (5 points) Add the C++ inheritance specifiers override and final and the C++ constructor specifiers explicit, mutable, default, and delete to the XMLFramework where appropriate.

  There is no report or questions to fill out. The answers to these come from your commits to XMLFramework.

• XMLFramework Project Posted: Apr 15

  The project is a critical part of your overall grade in the course. Parts of it count toward 25% of the questions on the Final Exam. Consider this as a take-home part of the Final Exam. No matter how you performed on the previous projects, you need to work on this project.

  The project is due by 11:59:59 pm on Friday, May 7. The XMLFramework counts as two projects, Projects 4 and 5. The project consists of:

  • Parsing XML with a variety of push and pull parsers
  • XPath evaluation - XPath is an addressing language for XML
  • XSLT transformation - XSLT is a transformation language for XML
  • Combining these operations as needed by the applications

  The open-layered architecture framework, XMLFramework, supports all this and includes:

  • Applications
    • Applications using the XMLFramework
    • xmlpipeline.cpp - CLI for using the framework
  • XMLFramework
    • As described above
  • XMLToolkit
    • Set of C++ classes for processing XML
    • Used to implement the XMLFramework, but can be used directly
    • Where your XMLParser lives
  • XMLLibrary
    • Set of C functions for processing XML
    • Used to implement the XMLToolkit, but can be used directly

  There is much code in the project already. The primary task is to finish the remaining @TODOs. Follow the following workflow:

  1. Decide on a // @TODO ... to complete
  2. Implement the // @TODO ...:
     1. Implement a part of the // @TODO ...
     2. Do not mention in your added code comments that you implemented an @TODO
     3. Note in the commit message what you added. Your commit message can mention the @TODO.
  3. When finished with a // @TODO ... item, remove the comment that contains the // @TODO .... When all finished, there should be no more @TODOs

  Note that at no time can a single commit change more than one of the // @TODO ...s. A @TODO may require multiple changes and commits. At all times, the code should build and run.

  The work involved is:

  • (60%) Complete any @TODOs
  • (10%) Fill in the @pattern and @role comments for all classes. A class can participate in multiple roles in multiple patterns.
  • (10%) Document the use of design patterns in the markdown file DESIGN.md. Each instance of a design pattern in XMLFramework must be listed, including the collaborators.
  • (10%) Document the architectures used in the XMLFramework in the markdown file ARCHITECTURE.md
  • (10%) Draw a UML diagram of the entire project in the file UML.pdf

  Notes:

  • The GitHub Classroom invitation link is on Brightspace.
  • Some of the work involves topics presented during the last weeks of class, including language features and design patterns. However, you can start right away as some of the work involves topics we have covered.
  • The answers to some questions on the Final Exam are from your work on this project. E.g., so instead of creating a UML diagram and uploading it during the Final Exam time, your UML diagram from this project is your Final Exam answer. You must do these parts as they also count toward the Final Exam.
  • The project has a complete CMake build. You are free to add files to the subdirectories, and the CMake build will handle them automatically. Any files in the apps directory are assumed to be single, executable files. Make sure that if you add files that you also commit and push the files to GitHub. Always verify at GitHub that the correct files are there.
  • In XMLFramework, the app, xmlpipeline, uses CLI11 for parsing command-line options. When you run cmake, the file downloads to the subdirectory external/. Depending on many settings in Windows, the download may be unsuccessful and quietly result in an empty file. As a work-around, directly download the file CLI11.hpp and save it in the build directory under external/.

  • To quickly find code, git grep works well. For all the lines of code that contain @TODO, enter the command git grep "@TODO" in the top directory of the project. To see only the filenames, git grep -l "@TODO". The command depends on the directory where you issue the command, e.g., if in the directory framework, the results are for that directory and its subdirectories. A command for a comprehensive report of which @TODOs are left: