Date/Location: 7-April-2020 at 4:30 in Collaborate Ultra

Information Updates/Reminders

• Last week was about analysing the legacy code.
• This week is about converting and documenting the code
• Next week we will use an iteration over two weeks to fix bugs and extend the project. (No bug fixing or extensions yet!)
• Everyone should be able to use the team git repo, github wiki and Trello. Ask for help (tutor or team) if that’s a problem.
• Everyone should have used toggl.com to track their time last week. Also track time on tasks this week with Toggl.
• Tutor must be added to github, trello and toggl.
• The Programming Help Desk ATC620 is still available to help us with programming for this unit.

Decisions Needed

• (R1) What tool(s) is used to do the conversion, based on the report? Telerik Code Converter https://converter.telerik.com/ and Our Brains
• (R2) What coding standard will be used for C#, based on the report? Reinaldy
• (D1) Who will add tutor account to team tools? Josh and Jake
• (D2) Who will convert the VB code and fix the compile errors with the C# code? This can be shared by several team members. Jake
• (D3) Who is responsible for completing the missing documents? This can be shared by several team members. Everyone
• (D4) Who is responsible for validating the converted C# code? Hayden

General Items

• Add tutor account to team tools (github, wiki, toggle). See (D1)
• Code needs to be converted, and the converted code that compiles is committed to the repository. See (D2) == (Note – repository must have already contained VB code.) ==
• Converted code will need the appropriate SwinGame files to build and run the C# code. See (D2)
• Missing code documentation (identified by report) needs to be fixed in the converted code. Can be shared by several people. See (D3)
• Converted and running code functionality needs to be checked to make sure it is the same as before (Validation). Suggest a checklist (list of functions?) to document the before and after result. See (D4)
• There may be missing features, bugs or extension ideas that have not been identified and documented. This will be needed for the upcoming two-week iteration, so we should continue to look for these and note what they are. Everyone needs to contribute to this action and keep a record of their contributions.