| CI tools |
No use of Git, or sparing usage (e.g. under 5 commits on a single main branch) or no team collaboration |
Git used with collaborators but with no FBM (e.g. main-dev). |
Git used with collaborators and an attempt at FBM (e.g. main, dev, 1-3 feature branches) |
Git used with competent FBM in a team (e.g. main, dev, variety of appropriately named feature branches) |
As (4), with more advanced practices (e.g. PRs, branch protection, versioning) |
| testing |
One of the following: no unit tests written; tests do not cover code; most tests fail or don't compile |
Full testing of one service/aspect of the application, or partial testing of two services/aspects. |
Full testing of two service/aspect of the application, or partial testing of three services/aspects. |
A large majority of the application is tested and tests are of an acceptable quality with no glaring deficiencies. |
The application is virtually fully tested and tests are of an acceptable quality with no glaring deficiencies. |
| agile |
No indication of Agile (e.g. Jira nonexistent or inaccessible, no documentation) or no collaboration. |
One of the following: Jira present but with incorrectly-formatted user stories; no story points; no Risk Assessment |
Jira present, but with incorrectly-formatted user stories or no story points. Risk Assessment present |
As (3), with user stories, story points & acceptance criteria correctly utilised |
As (4), with evidence of Jira user stories linking to GitHub |
| codebase |
The backend is non-functional, i.e., doesn't launch or has no working functionality. |
The backend supports a variety of CRUD operations (not necessarily all) on at least one table in MySQL or one document in MongoDB. |
The backend supports a variety of CRUD operations (not necessarily all) on at least two tables in MySQL or two document types in MongoDB. |
The backend supports a variety of CRUD operations for domains including but not limited to movies, bookings, and payment invoice storage required for business operations and by law for tax purposes. |
"As (4) but also supporting CRUD functionality for users and discussion boards. Search functionality must be implemented at a minimum for movies by title. and one of the following: Refactoring of backend code must be present. or The frontend is served statically, once built, from a static folder on the backend server. " |
| codebase |
The frontend is non-functional, i.e., doesn't launch or has no working functionality. |
The frontend meets at least 30% of the requirements checklist, it may contain a reasonable amount of bugs (10 or less non-major bugs and 1 or less major bugs). |
The frontend meets at least 50% of the requirements checklist, it may contain a handful (5 or less) bugs, with no major bugs. |
"As (3) but the frontend meets at least 70% of the requirements checklist, the following core functionality of the app must have been covered: Tickets, Movies, Bookings and payment invoice storage. Search functionality must have been attempted but is not required to have worked." |
"As (4), with refactoring of the frontend also present. Also present must be a working search functionality (at least by movie title) and a discussion forum. The frontend of the project (React) must be able to build to a static site successfully, with the produced static site free from bugs." |
| docs (Designs) |
No designs, or designs used without adherence to expected formats, or designs are wrong. As the documents in MongoDB reflect JSON, data designs are allowed to be more freeform then with SQL, but cardinality is still required to be specified. |
One simple design provided, but without expansion (e.g. one minimal data design without keys) |
"1 solid data design diagram or UML provided, following expected formats. Wireframe designs provided for the frontend." |
"2 solid data designs (before-and-after), or 1 solid data design diagram & 1 solid UML provided. Wireframe designs provided for the frontend." " |
Evidence of project evolution over time (e.g. multiple data designs & UML).Wireframe designs provided for the frontend." |
| docs (readme) |
No supporting documentation provided |
Documentation is incomplete, broken, or uninformative |
Documentation contains installation and deployment instructions |
As (3), with documentation containing testing instructions |
As (4), with documenation containing all relevant screenshots / supporting materials |
| testing |
"One of the following: no tests written; tests do not cover code; most tests fail or don't compile. If Istanbul is not present, add during marking to ascertain code coverage." |
Unit testing of one full service or partial testing of two services. |
Unit testing of two full services or partial testing (50% + coverage) of three services. |
"A large majority of the application is unit tested and tests are of an acceptable quality with no glaring deficiencies. At least 60% code coverage." |
"The application is virtually fully unit tested, with tests of an acceptable quality and no glaring deficiencies. Code coverage must reach at least 80%." |