Grades

Sprint 4

Requirements Specification 5

Mockups & Storyboard 5

Documentation & Deployment 8

Codebase 27

Tests 20

Meetings and Demos 10

Wildcard 15

TOTAL 90

The comments from previous sprints, regarding use case specifications, have been addressed adequately.
UI mockups include screenshots and descriptions, improving the previous state of this document.
The deployment instructions could contain more detailed descriptions about setting up the environment, for example, specifying how to make the application available remotely.
I would have been desirable to include screenshots in the user manual.
The organization of the code improved, by grouping models in the same folder.
It would have been better if the forms and views are in their own folder.
Some models and forms don’t have good documentation.
In-code documentation does not follow standards to auto-generate project documentation.
Selenium tests were not included.
The application runs correctly, and no bugs were detected during my tests.
One validation error: end date can be before the start date.

Requirements Specification 3

UI Navigation 0

Detailed Design 10

Codebase 30

Tests 17

Meetings and Demos 10

Wildcard 15

TOTAL 85

Some comments made in the previous sprint regarding vague specifications are still present (e.g. “…for some period of time”, “a reasonable level of security”).
The UI mockups did not change to incorporate the suggestions from the previous sprint.
The architectural diagrams are clear and informative, but still the forms_*.py are not represented in the diagrams.
The organization of the code improved by splitting models into separate files, but still the folder structure can be improved.
The encoding inconsistencies were fixed and now the code is easier to read.
Most of the code has comments, but some of the files don’t have comments yet (e.g. filters.py, models_program.py).
The unit tests have been added, which cover most of the basic functionality. Edge cases are not tested thoroughly.
The performance of the team has improved considerably.
The issue tracker and meeting minutes are being updated constantly.
Although the aesthetics of the application can be improved, the application seems functional and does not crash with invalid inputs.
The commit count of Jonah was considerably lower than the rest of the team.

Requirements Specification 4

UI Navigation 17

Detailed Design 19

Codebase 25

Tests 0

Meetings and Demos 10

Wildcard 5

TOTAL 80

Some missing requirements from the previous sprint were added, such as importing data from a CSV file.
There are user stories with vague requirements, for example: “…for some period of time”, “a reasonable level of security”
Student 3.3 is not clear. Do you mean you will merge the documents automatically, or that the user has to submit only one document.
The UI mockups does not define which filters can be applied.
The UI mockups does not specify in detail the content of some views. Parts are being replaced by big labeled rectangles.
The forms must be associated in someway with other classes in the system, for example with some views, but the diagram does not depict those relationships.
The application consider form validations, and already implements some basic functionalities.
The organization of the code can be improved. The models, forms and views are all in the same subfolder.
There are encoding inconsistencies for new line characters that make the files hard to read (for example, models_coordinator.py is all in one line).
There are no automated tests implemented for the project.
The naming convention of issues was improved by including the title, and they have been closed as expected. There was a significant progress since the last TA meeting. In the future, the team should be more proactive.

Requirements Specification 15

UI Navigation 10

High-Level Design 10

Release Planning 15

Project Overview 15

Meetings and Demos 8

Wildcard 5

TOTAL 78

The description is clear and outlines the importance of the application.
The user stories are divided into detailed user stories, and cover most of the system’s functionality.
The user stories under System Role are actually details of other user stories.
There is no user story that can filter the applications.
The storyboard is not easy to follow. I think that using mockups with arrows (labelled by the user story) would be easier to understand for clients and managers. However, the transitions and screen elements are included in the document.
The component diagram depicts the typical Django application. The interactions among components are described.
The class diagram does not match the component diagram. For example, I couldn’t see the controllers and templates.
The Gantt chart is hard to read. The labels should have the user story. Likewise, the issues should have more descriptive titles.
The issues are assigned, and the organization seems reasonable.
The meetings are properly documented.
There are no closed issues so far.