Lofi Sketch for Messages Page and accompanying New Message Page:

Login Page

Lofi Sketch for view Relevant Faculty Members:

Lofi Sketch for new Student Checklist:

Sprint2 Summary: At the end of sprint 2, we completed most of our features, minus a few. Some of the reasons we were not able to finish all of them was because of some unseen time circumstances revolving around Thanksgiving Break as well as some of the features we were working on having blockers that we had not intended or predicted. We had some features that would require a feature that was taken during this sprint to be completed, which meant that feature could not be started until later in the sprint when the previous feature is completed.

One of the major issues we ran into was merging some of the features when they were related to similar other features. For example, there was a change to a database table (Account) in one of the current features, but another feature being developed also used this table, so it caused a lot of issues getting them put together since all of the data creation needed to be changed and edited to fix every occurrence. We also had an issue with our migrations that were autogenerated by rails overlapping with other features autogenerated migrations, which caused some more merging errors. To try and help fix this, we are going to do our best to improve communication when working with overlapping features and possibly feature-breaking changes. Some of these errors are just going to happen inevitably and will have to be dealt with as they show up.

We also decided that we would implement a pull request template so that they would provide more information and be easier to understand for whoever was trying to review it. So far it has been helpful in making our pull requests look much cleaner and more useful.

We did have some major successes this sprint. The pipeline that was implemented has saved a lot of trouble trying to make sure that everything is in working order, and has been an ongoing process to update and keep in the best condition. Because of this, we have been updating the pipeline over the course of this sprint and hope it is in perfect form for sprint 3, as we have fixed every issue with it we have encountered. We have also started using chores and bugs more heavily in pivotal tracker, making it easier for us to see what has to be done and fixed. Our updated points seemed to be quite a bit more closely in line with what we expected. We have also made improvements to our testing of features from sprint 1, and have very good coverage on our features.