Communication Phase Meetings

[TelloViz]

---

Communication.

Before any technical work can commence, it is critically important to communicate and collaborate with the customer (and other stakeholders). The intent is to understand stakeholders’ objectives for the project and to gather requirements that help define software features and functions.

---

Communication Phase Meeting Topics

• [x] Simplest Viable Product Goal

  • Define the core features and initial goals of the project.

• [x] QT Basics

  • Overview of the framework and its components.

• [x] Discuss Process Workflow

  • Choose and agree on the workflow model (linear, iterative, etc.).

• [x] Discuss API Basics

  • Overview of RESTful APIs and how they will be used.

- [ ] CMAKE Overview - Explain its role in the build process.

- [ ] Git Conventions - Establish branch structures, commit practices, and review processes.

- [ ] Request and Manage API Keys - Discuss the acquisition and management of API keys for development.

[TelloViz]

Met on 9/10/24

Fulfilled this iteration of "Communication" phase of our process workflow.

We discussed:

• Understanding the "Problem"
  • Determined "Browse" functionality redundant with Search functionality covering its role.
• General Overview of how we can solve this "Problem
  • Why Python API has a Python SDK so interaction with the API is much easier than C++
  • Why QT Quick
    • Pairs well with Python in QT for rapid prototyping and GUI building.
    • Ease of use with connection front-end and backend.
• Minimum Viable Product
  • MVP will be the Search screen, and the Collection screen.
• Determined stretch goal features
  • 3D rotating card
• Determined Process Workflow
  • Iterative Workflow

Moving crossed out items in this card to the Planning Phase Card.