Projectathon

As a test session manager, I want to see the list of profiles selected for the current test session and, for each profile, I need the following information:

• What are the actors involved in the profile;
• What are the (non-dropped) SUT registered for each actor of this profile;
• Which ones of the SUT are already accepted to the session.

As a test session manager, I want to be able to give a status to each profile among: not testable, testable, at risk, not assessed yet.

As a test session manager, I want to decide when to make the list of profiles (along with their status) public to the test session participants.

As a test session manager, I want to be able to ask the tool to mark as "no peer" all the AIPOs when the profile's status is set to "not testable".

As a SUT operator, I shall not be able to add a "not testable" profile to my SUT. However, I want to see it in the list of profiles so that I understand why I cannot select it.

As a SUT operator, I shall not be able to start a test for a not testable profile also the actors appear in the test plan (with status = "no peer").

As a test session manager, I want to access the list of registered systems and see the following information for each of them:

• SUT name
• Organisation's name (+ ability to link it to more organisations)
• Main point of contact for the SUT (full name + link to send an email)
• Number of AIPO the SUT is registered for (allow to quickly see the dummy systems)
• Registration status (+ ability to change it)
• Whether the SUT is accepted or not to the session (and have the ability to change it)
• Whether a contract has been received for the organisation (when a contract is needed)
• The table where the system sits (+ ability to update it)

Dashboard

• Number of system registered per session + average
• Number of participants per session + average per system + average per AIPO
• Number of tested AIPO + results + drawings + average
• Number of different partners (organisation level / SUT level)

As a first action, we should make the current Connectathon menu agnostic of the type of test session:

• Use the "type" (from the testing session configuration) as display name in the menu bar where "Connectathon" is currently used.
• In case we do not merge the preparatory tests and test session tests:
  • The "Pre-Connectathon" sub menu might be renamed into "Preparatory tests"
  • The "Pre-Connectathon Tests" sub menu might be renamed into "List of preparatory tests"
  • The "Pre-connectathon results" sub menu shall be renamed into "Preparatory test results"
• The "Connectathon" sub menu might be renamed into "Testing"
• The "Connectathon" menu entry (lower level) could be renamed "Execute tests" (as well as the short cut in the top menu bar)
• The "Connectathon result" menu entry should be renamed "Test session results"
• The "Download connectathon report" menu entry should be renamed "Download test session report"

Then, everywhere in the tool, we should use the following vocabulary:

For a specific testing session:

• As a test session, I need to know how many profiles are offered for registration (overall, per domain)
• As a test session manager, I need to know how many organisations have registered SUTs and how many of them have downloaded their contract, and how many have sent it back;
• As a test session manager, I need to have an overview of the statuses of the SUTs (total + in progress, completed, dropped, accepted);
• As a test session manager, I need to have an overview of the number of participants (total + monitor vs vendor) and when (which days) they intend to attend to the event;
• As a test session manager, I need to have an overview of the status of the SUT network configurations (percentage of approved configurations, list of accepted systems with no approved configuration)
• Before the event starts, as a test session manager, I need to have an overview of the status of the preparatory tests.
• During the event, I need to have an overview of
  • the status of the test runs (running, waiting for validation, verified, passed etc)
  • list of organisations with no test
  • list of SUTs with no test
• After the event, I need to have an overview of the test session results:
  • How many AIPOs have been marked as Passed?
  • How many different profiles have been marked as Passed for at least one system?
  • Top 5 profiles in terms of Passed AIPO
  • How many different actor/profile pairs have been marked as Passed for at least one system?
  • How many different tests have been executed (overall and per test types: no-peer, peer-to-peer, group)
  • Average of test runs (verified, partially verified, failed) per monitors
  • Average of test runs (verified, partially verified, failed) per SUT
  • Percentage of not verified tests (to be verified/critical) on the overall number of completed tests (excl. running, aborted, paused)
  • List of domains where tests have been executed
• For each profile, the list of systems for each actor
  • Hide dropped systems
  • Highlight accepted systems
• Indicators when
  • Each actor is covered by at least 3 differents systems
  • A system acts as all the actors
  • Only systems from the same organisation are registered for the profile
  • No registration at all

As a test session manager, I want to give access to the documentation of the event on a landing page for the Connectathon/Projectathon. It also includes publishing the daily morning news during the Connectathon/Projectathon.

As a test session manager, I may want to send a notification to the participants to inform them that content has been added/updated.

One-click operations that shall be available to the user:

• As a SUT Operator, I shall see what are the upcoming events and when the registration starts/ends + the dates of the event;
• As a SUT Operator, I shall be able to access the results from the past events where my company attended, in Gazelle Test Management;
• As a SUT Operator, I shall be able to access the results from the past events where my company attended, in the connectathon result matrix;
• As a SUT Operator, I shall be able to download the test session report for a past event where my company attended.
• As an organisation owner, I shall be able to add a user for my company;
• As an organisation owner, I shall be able to grant access to the users who created an account by theirselves;
• When the registration for an event is open, I shall be able to add a SUT;
• When the registration for an event is open, I shall be able to update the SUTs owned by my organisation;
• As soon as my SUT is accepted, as a SUT operator, I shall be able to access the preparatory tests;
• As a company owner, I shall be able to review and download my contract (if needed for the event), until the contract is marked as received in the tool;
• As soon as my SUT is accepted,as a SUT operator, I shall be requested to fill out the network configuration for my SUTs;
• As soon as my SUT is accepted, as a SUT operator, I shall be able to access its test plan;
• As soon as my SUT is accepted, as a SUT operator, I shall be able to start the no-peer tests;
• As soon as the test event starts, as a SUT operator, I shall be able to access the list of peer-to-peer/group tests I have to execute;
• As a SUT operator, I shall be able to access the Product Registry.
• As a SUT operator, I shall be able to see the tools of interest with a link to access them (ie: this kind of page should be part of Gazelle TM: https://gazelle.ihe.net/connectathon.html).
• For on-site events, as a SUT operator, I shall be able to access the details to configure my SUT with a static IP address;
• As a SUT operator, I shall be able to access the network configuration of my potential partners.
• As a SUT operator, I shall be able to access the communication tool (if any set up for the event)