List view
Your first task is to demonstrate your progress on your Milestone 1 requirements. You or your group should be prepared to Demonstrate a working implementation of features addressing the Milestone 1 requirements Be prepared to discuss the design, implementation, and testing of these features To facilitate discussion of your design, you should be prepared to present a UML model of important aspects of your problem domain and system. In addition, you should document your individual contributions to the project. If you are working on an individual project, you don’t need to do anything special, since your commit history will be sufficient. If you are working on a team project, your commit history can be sufficient if most of your contributions are associated with your user identity. If some substantial fraction of your contributions are not associated with your user identity (for example, because you participated in pair programming, and most of your contributions were commited by a teammate), then you should keep a detailed log of your contributions and the associated code commits. Your second task is to document requirements to be addressed in Milestone 2. You should create a new milestone (i.e., for Milestone 2) in your issue tracker, document requirements as issues in the form of use cases or user stories, and associate the issues with Milestone 2.
Overdue by 3 year(s)•Due by March 2, 2022•3/3 issues closed- Overdue by 4 year(s)•Due by December 10, 2021•3/3 issues closed