(Group 41)
These notes are rough because this is the extra stuff James said, but did not write down on the slides.
Group consensus → new people “don’t fit the culture”, don’t fit group consensus
Actual project could disaster → can still get 65+ if you evaluate why, prevention, discuss techniques
- Prioritise core requirements; first, run some sort of traffic simulation
- Balance between front-end & back-end
- Don’t shy away from tech aspects → client is techy
- Deadlines, setting goals
- Brainstorming session? → requirements
- If one person plagiarises, whole team is affected
Requirements
For each requirement:
- Meets customer request/need?
- Achievable? Well-defined? Justifiable?
- How to test?
(Read slides on requirements; make sure to organise and order them appropriately. Marking criteria weighted equally.)
Design - System Models
Don’t make diagrams that need massive zoom; readable. Only model key things.
Design - Methodology
- Some level of structure, organisation
Design - Testing & Validation
Unit Testing
- how often? when? before/after the code?
Planning and Design Document
- Appropriateness with Requirement document
- Equally weighted (each of the 5 marking criteria)
- Don’t need a contents page