# Understanding the Software UI

### The Structure of the Biosignal Platform

The software is organised into several key "environments," each representing a step in conducting a quality assurance session.

The available "environments" are:

1. **Projects**: Create, open, or delete projects, setting up the foundation for your QA work. Testing: Connect devices, manage respondents (create, delete), select media for testing, and begin the QA tests.&#x20;
2. **Analysis**: Review individual respondent data, add annotations, create surveys, and log data from tests.&#x20;
3. **Results**: Normalise data to compare multiple respondents, making analysing trends and common reactions easier.
4. **Overview**: View an overall summary of the project, including graphical representations of survey results and data charts. Each of these environments is explained in detail on the following pages.

Main Navigation

For now, let's focus on the main navigation, found at the top of the software, disregarding the rest of the interface until later:

<figure><img src="/files/sV8dfHmyBbXrXK5TnPTO" alt=""><figcaption></figcaption></figure>

1. **Main Menu**: here, you can read the software license and open source licenses used. In the future, this area will be populated with more settings.
2. **Tab Menu**: navigate between different the different environments of the software, such as  Testing, Analysis, Results, and Overview.
3. **License Status:** displays the current status of your software license and expiration date.
4. **Save Indicator**: allows you to save your progress and view the last save time.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.cinematronic.dk/your-first-project/understanding-the-software-ui.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
