Bautista, Flores


Java for implementation
+ eliminated the smaller classes, merged them
+ coordination of work
+ conflict checking
- no updated documentation
- big OOP classes, but recognized it.
+ constant communication
+ prioritization
+ dealt with a setback – loss of a teammate

dependend on cliff’s notes
test data
needs to improve on the OOP principles
can recognize when code gets too big
mostly structured, some methods
adapted original design, hard to think about
hanapan ng errors
scheduling for the problem fixing, not too good
+ recognized dependencies based on the design and planned around that

mahirap pala yung print
pair debugging

Essential use cases finished, but features/nice-to-haves not really