2. Organisation

Navigation

• 2.1 Repository Platform
• 2.2 Team Communication
• 2.3 Gantt Chat
• 2.4 Meeting Logs

2.1 Repository Platform

GitHub was selected as the primary platform for version control and as a code repository. Since several developers were working on different areas, branch protection was applied to the main branch to enforce separate workflows. Each pull request required approval from at least one member of the team; this approach fostered understanding and awareness among team members regarding the code changes being incorporated.

2.2 Team Communication

To facilitate effective communication with the client, Microsoft Teams was utilised as the primary collaboration tool for sharing ideas and addressing any issues. Weekly meetings were scheduled with the Microsoft supervisors to discuss blockers and track progress. The valuable feedback received from the supervisors was incorporated into the code, which allowed consistent progress. In between meetings, regular communication was maintained primarily through Teams to set up group meetings, discuss design ideas and best code practices.

2.3 Gantt Chart

Figure 1: Gantt Chart for planning the project.

Figure 1 shows the development timeline of Nexus. Each member of the group developed one aspect of Nexus. This approach facilitated the concurrent development of different functionality and allowed for common bugs/issues to be identified and solved efficiently without affecting other sections of the project. Additionally, the parallel development of multiple features allowed for a more comprehensive and robust product, incorporating a multitude of perspectives and skill sets, which ultimately contributed to its overall success.

2.4 Meeting Logs

Meeting Date	Meeting Log
9th May 2023	Platforms discussed: Blazor, ASP .NET, MAUI - Tutorials provided to learn them. Tutoral links shared for Azure Active Directory, Graph SDK, Azure OpenAI Code completion mini-deadline was set for 2 weeks before final deadline.
16th May 2023	Blocker regarding authentication raised and team urged to research MGT-providers for authentication. Supervisor provisioned Azure subscription for Web Site Hosting/Database/OpenAI and team to document Graph login Blocker documented by us. Graph Beta SDK discussed for additional functionality. Cosmos vs Mongo evaluated for backend data storage. Suggestions given for Blazor WASM or Blazor Server - Fluent UI suggested for improved app styling and accessibility.
23rd May 2023	AI usage in the application discussed. Prompts for AI interaction explored. Blocker from the previous week persisted. Scheduled session to address the blocker - issue resolved by adding custom provider and passing login token.
30th May 2023	First application preview presented to supervisor. Positive feedback on AI implementation. Supervisor suggested improvements to the UI for better user appeal. Blocker related to search bar functionality identified. Search bar not fully functional for certain queries.
6th June 2023	Blocker regarding saving summaries to OneNote brought up, this was due to a lack of documentation online. Supervisor found correct documentation on GitHub. Getting call transcripts was also an issue as it was a beta feature, so requested Microsoft supervisors for clarification on how to use it.
13th June 2023	The team wanted to deploy the application onto Microsoft Teams, however, there was an issue with the authentication on the Teams desktop because the SPA login screen was blocked on the desktop app. Currently no known workaround due to the lack of documentation about Blazor WASM Teams Apps. Instead, the Blazor app was deployed on the Teams Web App, where SPAs are not blocked.
20th June 2023	Leaflet feedback - needed a more unified colour scheme and brand/service logos.
27th June 2023	A final meeting discussed the issie of having to refresh the initial load for MGT toolkit to display information. This was due to the lack of a token when the dashboard appears with login. Also enquired about the blog format for the blog deliverable