Marking Criteria

Topic
Requirements + constraints analysis	Are the functional and non-functional requirements designed with users in mind? Are the requirements thoughtful and insightful? Are the requirements conveyed via user stories, acceptance criteria or “done”? functional and non functional (security, performance) , correct user , user stories and acceptance criteria , logically group features , what competition looks like ……. Constraints -Assumptions , Technical Challenges
System design	Software Architecture Design Are all layers of the software architecture design thoughtfully chosen? Is the decision making process for each layer shown, with multiple options? (frameworks - comparison table , multiple comparisons, decision making process and reasoning) Sytem modelling, API design, api lifecycle Is the system modelled well via UMLs? Does the system modelling clearly show the flow of data/control? API lifecycle Was the API updated during later sprints?
Breadth and Depth of Implementation	Software Quality - testing - pylint / pytest percentage , style - docstrings , testing practices , continuous integration and testing - how it is being run and hosted , what peripheral systems are being hosted, decision making and reasoning , continuous deployment Front End Design - UX/UI, Figma , decision making process and reasoning , wireframes, user testing , use cases , system modelling , sketches
Project Management and Communications	Project Planning, refer to table - include the kanban method , scrums, agile etc etc, organise priority , table of comparison, deciosn making process and reasoning, organised GIT commits, git practices Team Roles - Strengths + weaknesses , team leader/ scrum / product owner / delivery manager , decision making process and reasoning
Report Structure	abstract, appendix , conclusion , no word limit , cover page , problem statement, Formatting, Future improvements, reflections