Open timothxy opened 1 year ago
We managed to come to a consensus on the class diagram, whether its correct is to be seen but I think its good that we confirm if it matches with everyone's understanding of the architecture.
1.3.5 Software Architecture Patterns
1.5.1 Introduction, Data Dictionary, Features and Requirements
1.6.7 Integrated Features Testing
1.6.8 D1 Prototype Release
Report Quality:
Team:
Class:
Although there were many iterations when we did the component diagram, the entire team remained patient throughout
The component diagram is up to standard after a few rounds of changes. The team also managed to integrate 1 feature together with the other team in the class to form a working application.
After each iteration of the component diagrams for respective groups, everyone was able to come to terms with their respective features and responsibilities. Although the class diagrams may not be perfect, we understand what our groups are responsible for in a large scale project like this.
Every group member is to insert their individual retrospection on what went well.