Hi, I am Queenie Qiu, a robot enthusiast,
and creative thinker.

The design, development and implementation of the project was mainly done by me with assistance from CSCI 3081 instructor crew. The realization of the project was divided in steps throughout the entire semester.

Design Process: I used a UML diagram to visualize a system in all phases of software development life-cycle. View the UML

Iteration 1: The first iteration is focused on building domain entities and getting practiced in the software development process. Being supported by CSCI3081 team, I constructed classes of building domain entities for a transit system such as Bus, Route, Stop and Passenger. The code is organized such that simulation behavior (i.e. the model) is separate from the visualization (i.e. the view), which allows for automated unit testing using Google Test. Therefore, preliminary unit tests were conducted to test each domain entity to make sure they had accurate functionality. In addition, there have been a few entities that have been made into abstractions to allow for extension. The Simulator is the primary driver of the application. In iteration 1, the only implementation of this was the LocalSimulator which was relatively primitive. It was hard-coded with the campus's transit system in mind and displayed the simulation results on Terminal. Although I created an alternative simulator scenario that output the results in a file, there was no external control of the simulation; it could only be changed by modifying the code.

Iteration 2: While the hard-coded simulator is not ideal, I added additional structures in domain entities to realize the visualization of the simulation and created a new configuration simulator. The configuration simulator takes in the configuration file specified by the users and runs simulation on it. To verify the functionality, heavy unit tests and integration tests were constructed.

Iteration 3: I extended some abstract classes to implement regression tests on the program which is essential for further development of the project. I also refactored the program to make it into a clearer and more robust version.

Documentation: I used Doxygen compliant comments to comment on my code and then automatically generate code documentation. I also wrote a User Guide and a Developer Guide for potential program users.

Testing and code style checking: For testing, we adopted google tests for unit testing. For code style checking, we used the CSE-check-style tests which had developed by the Computer Science Department, University of Minnesota, Twin Cities. The whole project’s codes satisfied the Google coding style after the style check tests have been implemented.