DETAILS - "ITEMS" (with tentative evaluation points)

• ITEM 1: Wiki Documentation on GitHub: (keep the section titles ITEM1.A Team, etc for ease in understanding and peer reviewing)

• ITEM1.A Team (10 points) - list first and last name of all team members (as they appear in Canvas). Under each team member's name discuss their contribution.

  ITEM1.B: Updated Design Document (10 points):- updated Design Document -updated as necessary to show any changes since approval. Specifically highlight those changes.

  ITEM 1.C: Completion Discussion (10 points): discuss the state of completion or if there were changes from the approved design document, show the final Scrum/Kanban board (GitHub Project w/Issues + Milestones-for dates) which gives when and who did what tasks

  ITEM 1.D: CODE Design: UML Class Hierarchy Diagram (20 points): showing Hierarchy and Cardinality and Object Associations for this project.

   

  ITEM 1.E: JUnit Test Cases (20 points): show the results of running each JUnit Test Case and if errors discuss them. You should have JUnit test cases for each class in Java with the exception of any GUI/Interface class.

  ITEM 1.F: Issues Tracking Screen Shots + Presence on GitHub (20 points): using GitHub Project for your responsitory with Issues+Milestones(dates) create a Scrum/Kanban board and show screenshots of this board as it changes over time ---show towards the beginning of the project, the middle and the end.

  • NOTE you should create an Issue for Every Class in your code (and assign different group members to work on them), an issue for every deliverable of the project (javadoc, github pages, various video recordings, so on), and for every weekly meeting you have and to JUnit and Integration testing, and to any content you need to create for the app
  • You should make milestones for each week and associate these due dates with you issues you choose to do that week
  • You can also make milestones for each major deliverable like documentation, testing, etc. that you assign to your issues.
  • In your weekly meeting issue (which represents for your group 1 Scrum Cycle) you will want to add to it the following description AND RUN YOUR Meeting in this fashion.By doing this you are combining a Scrum "Standup"(item 1) and a Scrum "Code Review"(item 2+4) with a Scrum "Cycle Planning"(item 3) meeting in one. SEE EXAMPLE
  1. (10 minutes) Scrum Meeting Standup (each person quickly discusses what they did last week)
  2. Scrum Cycle/Code Review - Part A : Discuss/Present issues that are proposed for closure (meaning completed) by showing the code working, demoing or showing documentation of testing, etc. If approved move related issue to the "cLosed" column.
  3. Scrum Cycle Planning - Discuss what issues from the backlog should be worked on next week (next Scrum Cycle)
  4. Scrum Cycle/Code Review - PartB : Quickly have people who need help with something find someone to help (adjust anything necessary like reassignment of work on the issue board)
     
     
     

• ITEM 1.G: System Level Testing:

• ITEM 1.G.1 App Testing (15 points): Work Instance 1-X: Show screenshots of using the application COMPLETELY.

• ITEM 1.G.2 Database Testing (30 points) Shows the results of the database before and after changes from the Work Instance 1-X (from ITEM 1.F.1) that alter the database. It is required to do database as discussed in class (Firestore).
  
  

  
  

• ITEM 2: Code Documentation & commenting of code. (30 points): You should host your JavaDoc in your GitHub repository’s /docs folder and create a GitHub Pages site from it (read details here). Then post the Github Pages link inside your wiki in this section. Commenting should include:

• JavaDoc comments: before each class, before each class variable, before each method
  "In-code" comments: within each method to describe what is going on inside the methods

  
  
  

• ITEM 3:JUnit Testing Code(40 points)

• Unit testing code for EVERY class in your project except for GUI classes. Testing should be as rigorous as the class allows. Points evaluations per class = 40 points/#classes in your project. See ITEM1.C for how to provide the required documentation.

  NOTE: System level testing is demonstrated in ITEM 7.B
  

   

• ITEM 4: Code Styling (20 points)

  • Follow Code Styling guidelines stipulated in class and in Google Styling guide for Java

• ITEM 5: Collaboration (40 points)

  • Create a YouTube video showing a Scrum/Agile focused team meeting --where everyone does a standup and ALSO there is a code review session. Turn in URL here.

• ITEM 6: Functionality (100 points)
  

  • Points for completion of design + the application is currently fully functioning. Partial credit for lack of completion or run-time issues.
    
    

• ITEM 7: Presentation
  

• ITEM 7.A Class Presentation (25 points) :Your group will be called to present your work live
  ITEM7.B YouTube Presentation(25 points): YouTube video presentation of the application working with Audio narration discussing how the system runs and if there were any changes from design document or if there are any run-time issues.

   

• ITEM 8: Peer Evaluation (45 points)
  

  • peer evaluation of other groups performed. You will be assigned 3 groups to review. You earn up to 15 points per review depending on how complete and accurate your review is this will be evaluated by INSTRUCTOR.