Sharazone

Who is the targeted audience?

Any registered user

Tool administrator

Targetted goal(s)

Manage and control who has access to the test bed, how, and which features are available to each individual user.

Comply with local regulation in terms of privacy.

Expected benefit

Fine-tune the access to the Gazelle features.

Log who is performing actions with the test bed.

Offer advanced features to our users.

The user shall have access to an overview of the test runs for a given testing session whatever the current status of the related test cases

Priority

High - Major feature, it achieves a lot of work

Status

Draft

Customer

DG Santé

Business owner

Malo Toudic

Description

In Gazelle Test Management, the tests are executed from the Test execution page. This page also logs all the runs executed by the systems. The test runs are linked to the test case they relate to.

The test execution page shows only the test cases with a status set to "ready". As a consequence, if a test case is deprecated at some points, the SUT operator cannot access the test runs that were executed when the test case was "ready".

In the same way, the "All test runs" page displays only the test runs that relates to the "ready" test cases.

As a consequence, we experience a loss of information and that is not accessible neither from the SUT operator's or Testing Session Manager's point of view.

As a SUT Operator, I want to see all the test runs that have been executed by a system under test owned by my organisation, during a given testing session, at any time.
As a TSM, I want to see all the test runs that have been executed during a given testing session, at any time.
As a user, for each test run, I want to see the following details:
- Test run identifier
- Test case keyword (and a link access its details)
- Whether the test case is currently deprecated
- Last update date/time
- Test run status
- The role assigned to my SUT in this particular test run
- The other partners
- The status of the test run
- If a monitor is assigned, his first and last names
As a user, I want to be able to access the test run page for any test run (whatever the status of the test case is)
As a user, I want to be able to access the description of the test case.
As a user, I want to be able to filter on
- System (name/keyword)
- Test case keyword
- Monitor
- Type of test
- Domain
- Tested profile
- Tested actor
- Tested profile option
- Involved transactions
- Test run status
As a testing session manager or admin user, I want to be able to filter by Organisation (name/keyword)
As a user, I want the test runs to be grouped by tested SUT capabilities
As a user, for each SUT capabilities, I want to see the evaluation.
As a user, I want to be able to sort on test case and test status within each SUT capability.

What is/are the targeted context(s)?

Who is the targeted audience?

Monitor

SUT Owner

Targetted goal(s)

Allow the users to see all the test runs from a test session, regardless of the current status of the executed test cases.

Expected benefit

User will have access to a page that summarizes the outcome of their test campaign

Opportunities

We might also want to experience new widget/features on that page like displaying statistics.

Communication between management, participants, and monitors

Priority

Medium - Feature to be considered

Status

Draft

Customer

Renovation

Business owner

Anne-Gaëlle BERGE

Description

In the last years, the Projectathons have been held online as well as the two last European Connectathons. In that context, Rocket.chat has been used as a communication tool between the participants, with the test session managers, and with the monitors.

The SHARAZONE participants also use this tool for one-to-one communications. It is also the place where the SHARAZONE administrator broadcast information to the participants: new object available, tool maintenance, and so on.

All the involved parties agree that this tool is really useful and might also have an interest during onsite testing events.

What is/are the targeted context(s)?

Who is the targeted audience?

Targetted goal(s)

Main goal: allow participants to online events to communicate in a timely manner: find test partners, execute test cases, review test cases, share screen.

Secondary goals:

Support participants during the preparatory phase
facilitate the exchange of information (patient identifier, logs) during on-site events
be able to leave a message to an on-site participant (or monitor or TSM) when it is busy on another subject.

Expected benefit

Preparatory phase:

better support to the participants
create a place for exchange

Online:

make the test event happens

Onsite:

fasten the test execution and debugging

Documentation

As a Test Session Manager, I want to broadcast information to all the participants (text message / attachments).

As a Test Session Manager, I want to broadcast information to all the monitors (text message / attachments).

As a Test Session Manager, I want to hold calls with all the participants to the online event (video is optionnal).

As a Test Session Manager, I want to share my screen with all the participants when the event is online.

As a monitor, I want the participant to share his screen with me so that I can verify the outcome of the test even when working remotely.

As a SUT operator, I want to share information with my partners of the test instance.

As a monitor, I want to contact all the SUT operators of a particular test instance when we are working online.

As a SUT operator, I want to contact the management team when I have a question during an online event.

As a participant (SUT operator, monitor, test session manager), I want to receive all the notifications in one place.

As a test session manager, I want to enrol all the participants to the event in the communication tool.

As a participant, I want to use my Gazelle login to access the communication space.

As a test session manager, I want to offer one public channel per system or at least one public channel per organisation.

As a test session manager, I want to reuse the same "default" channels from an event to the other.

As a test session manager, I want to pin a message at the top of a given channel as a reminder to readers.

Split of responsibilities for SUT

Status

Draft

Customer

Renovation

Business owner

Anne-Gaëlle BERGE

Description

Gazelle Test Management requires an owner to be set for each SUT. However, the owner might be a person who does not attend the event. In that case, it is problematic for the other participants and the test session manager because there is no onsite contact point.

In addition, some companies regiter their SUT for a large amount of capabilities and they attend with more than 3/4 persons. In that case, it is also hard for the participants to know who to address testing inquiries.

This new need tries to solve (at least partially) this issue.

What is/are the targeted context(s)?

Who is the targeted audience?

Targetted goal(s)

Give an accurate single point of contact to test partners

Expected benefit

Ease the communication between participants

Target the correct person when looking for test partners

Documentation

As a SUT Operator, I want to know who to contact to test a particular profile with one of my possible test partners.

If a communication tool is set up for the event, I want to have a link to send a direct message to my contact.

Enhanced notifications

Status

Draft

Customer

Renovation

Business owner

Anne-Gaëlle BERGE

Description

A lot of information are shared with the test event participant through the tool and they are available in various places. As a consequence, the participant has to regularly consult the various pages to check if a status changed or if a new information is available.

To inform the information in a timely manner, a notification system should be put in place.

What is/are the targeted context(s)?

Who is the targeted audience?

Targetted goal(s)

Inform the participant in a timely manner of any useful information through an instant messaging system.

Expected benefit

Improve the user experience;

Save time to the participant, he does not have to look in the tool to find the information.

Documentation

As a SUT Operator, I want to be notified when the status of a test instance changes.

As a SUT Operator, I want to be notified when my SUT is accepted to the session.

As a SUT Operator, I want to be informed when my SUT is graded.

As a SUT Operator, I want to be notified when someone posts a message in the chat window of a test run in which I am involved.

As a SUT Operator, I want to be notified when a milestone is reached: registration starts, registration ends, session starts...

SUT definition page

Status

Draft

Customer

Renovation

Business owner

Anne-Gaëlle BERGE

Description

The SUT edition page shall be reworked in order to make it clearer, and more complete, so that the participants to not have to jump in multiple locations to manage their systems.

Avoid using tabs and use a navigation bar instead.

What is/are the targeted context(s)?

Who is the targeted audience?

SUT Owner

Targetted goal(s)

Centralize the information about the SUT for the participant

Expected benefit

Reduce the number of pages to maintain

Ease the work of the SUT operator

Documentation

As a SUT operator, I want to set the name of my SUT.

As a SUT operator, I want to give a type for my SUT (Gateway, Workstation, PACS).

As a SUT operator, I want to communicate to my partners the links to my capability statements (HL7, IHE, DICOM, FHIR).

Do we really need a keyword ? It brings confusion because there is no consistency in the tool (names and keywords are used in several places)

As a SUT operator, I want to list the capabilities of my SUT that I want to test.

As a SUT operator, I want to be aware of the testing status of each AIPO (testable, not testable, at risk) when it has already been decided by the test session manager.

As a SUT operator, I want to know when a profile is not testable:

If it is already selected for my system, I need to be warned so that I am free to remove it from the list of capabilities;
If it is not selected, I shall not be allowed to select it (but the reason why I cannot select shall be clearly stated)

As a SUT operator, I want to ask the test session manager to allow me to test a capability as supportive.

As a SUT operator, I want to filter out the list of capabilities my system is registered for (filter on actor, profile, domain, option, supportive, result).

As a SUT operator, I want to see the result for each capability.

As a SUT operator, I want to see the notes from the domain manager on a given capability (if any).

As a SUT operator, I want to see where I have to sit in the room.

As a SUT operator, I want to access the communication channel dedicated to my system.

SUT management page for test session manager

Priority

Medium - Feature to be considered

Status

Draft

Customer

Renovation

Business owner

Anne-Gaëlle BERGE

Description

Especially during the registration period, the test session manager has to regularly access the list of registered SUT to perform several operations or simply to follow-up on the registration status.

Currently there are too many pages targetted to the test session manager that are redundant and none of them show a complete view. This need is aimed to simplify the SUT management pages for the test session manager.

What is/are the targeted context(s)?

Who is the targeted audience?

Targetted goal(s)

Offer to the test session manager a single page where to manage the SUT for the current test session.

Expected benefit

Ease the registration process for the test session manager and save him time.

Opportunities

Reduces the number of pages to be maintained in the future.

Documentation

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)

Use a standardized language

Status

Draft

Customer

Renovation

Business owner

Anne-Gaëlle BERGE

Description

In Gazelle, the wording is not always consistent with ISTQB and it is really Connectathon oriented. It leads to confusion to Gazelle users. The wording shall be adapted in several places to improve the user experience.

What is/are the targeted context(s)?

Who is the targeted audience?

Targetted goal(s)

Adapt the wording to the event supported by Gazelle TM.

Use a common language.

Expected benefit

Improve the user experience.

Opportunities

Sharazone, Inter-AMC and EPD projects will directly take advantage of this update.

Documentation

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:

Current term	New (English)	New (French)
TF	Interoperability model
Tests list	Tests	Tests
Test definition	Test cases	Cas de tests
MetaTest List
Configuration	SUT Configurations	Configurations des SUT
Network	Network details	Informations réseau
All configurations	SUT network configurations	Configurations réseau des SUT
Connectathon
PreConnectathon	Preparatory tests
Test instance	Test run
Testing session	Test session
system	SUT

Add dashboard for the TSM to follow-up with the registration and test execution

Status

Draft

Customer

Renovation

Business owner

Anne-Gaëlle BERGE

Description

During the registration and the execution of the event, the test session manager has to look into different places to find useful figures to manage the event. To ease the follow-up of the session, creating dashboard to quickly have a look to various indicators is necessary.

What is/are the targeted context(s)?

Who is the targeted audience?

Targetted goal(s)

Give an overview of the registration and the test execution to the test session manager.

Ease the report to the IHE T&T committee by provided the expected figures to the test session manager.

Expected benefit

Ease the work of the test session manager and save him time to support better the participants.

Documentation

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

Dashboards for the testing event participants

Status

Draft

Customer

Renovation

Business owner

Anne-Gaëlle BERGE

Description

In order to follow-up with their progresses during the event, the SUT operators need to access some graphics to show them their progresses in terms of:

SUT registration status (dropped, in progress, completed, accepted)
Approved vs unapproved network configuration (overall, per SUT)
Connectathon/Projectathon test statuses (overall, per SUT, per SUT per type: preparatory tests, group tests, no-peer, etc)
"AIPO" Results (overall, per SUT)

What is/are the targeted context(s)?

Who is the targeted audience?