Decide on name for QualityByDesign

[benhepworth]

Related to Issue #3
QbD User Store PR for additional context

This is an extension of the original Quality Attenuation work, but not tied to a specific vendor. We chose the name Quality by Design with the idea that when an application is built, the application developer can design it in a way to ensure desired quality of experience.

On the TSC call some names were thrown out:

• Quality by Design (keep original name)
• Connectivity Insights Score
• Quality Action Score
• Quality Actions
• Quality Insights
• Application Quality Score
• Quality of Experience Insights

[benhepworth]

IMO the word Score shouldn't be in the name - it is much more than just providing a score

[Kevsy]

How about 'Quality Tracking'?

'Tracking' implies an ongoing process, and just like tracking a parcel online, suggests the actions that can be taken.

The distinction would then be:

Connectivity Insights: 'if they were to start a session now, what quality is this end user likely to experience?'
Quality Tracking: 'for this ongoing session, what quality does the application perceive, and can the network do anything about that?'

[benhepworth]

what about Application Quality Insights?

[benhepworth]

I also like Quality of Experience Insights.

[Kevsy]

My concern with the word "tracking" is that when put in the context of a network provider it could sound big brother-ish. What do you thinK?

Fair point! I hadn't thought of that...

what about Application Quality Insights?

I think that could be misinterpreted as assessing the Application's role in quality, namely how well the Application is coded for networking (e.g. whether if follows guidance in [GSMA's 'Best Practice for 5G Developers'] (https://event-assets.gsma.com/Las-Vegas/Presentations/Ed-Lambert_ATT.pdf) or equivalent for fixed/Wi-Fi/Satellite)

I also like Quality of Experience Insights.

Yes, I like that one. Or 'Session insights', in case there is another layer of 'Quality of Experience insights' which somehow includes end user feedback.

[benhepworth]

I like Session Insights...or what about Application Session Insights?

[Kevsy]

I like Session Insights...or what about Application Session Insights?

I'd be fine with either of those - slight leaning to Session Insights as I think the 'Application' is implied by 'session'.

[benhepworth]

In general, what are everyone's thoughts about using Insights as the last word to align with Connectivity Insights naming?

[shafayetkhan]

Great ideas @benhepworth and @Kevsy!

I think adding Insights would fit well. At first, I was leaning towards Quality Insights since it pulls from both Quality on Demand and Connectivity Insights. But I also want to suggest a new one: Service Insights.

[benhepworth]

I'm not sure about using the word Service @shafayetkhan - in many cases it implies a service call by a technician and could add confusion.

[Kevsy]

@shafayetkhan re Service Insights: I see what you mean, but as I understand it, 'Service' is a popular term used in North America to indicate coverage - so it could be misinterpreted as relating to e.g. signal strength, 4G or 5G etc.

[benhepworth]

hi @hdamker - on the Connectivity Insights call this morning the decision was made to go with "Session Insights" for the name of the repo instead of Quality by Design. What needs to happen next in the process?

[hdamker]

hi @hdamker - on the Connectivity Insights call this morning the decision was made to go with "Session Insights" for the name of the repo instead of Quality by Design. What needs to happen next in the process?

@benhepworth next step would be to create an issue with the request to rename (and some rational) within https://github.com/camaraproject/APIBacklog, including a PR on the original API Proposal. In addition it would be good to have the User Story done and merged (#7) and some minutes about the call this morning (I assume that the other Maintainers of ConnectivityInsights were involved in the decision). Technically changing the name is afterwards a small admin task.

[benhepworth]

New name has been decided upon: Session Insights
Link to meeting notes where this decision was made: https://lf-camaraproject.atlassian.net/wiki/x/mIDoAQ
Link to Issue in API Backlog to rename Quality by Design to Session Insights: camaraproject/APIBacklog#116
Link to PR in API Backlog to update original docs and to resolve Issue #116 in API Backlog: camaraproject/APIBacklog#117

@hdamker - ok, all of this has been done. The only outstanding thing now is to merge the two current open issues in the QualityByDesign repo (README updates and User Story). Upon approval from @Kevsy or @maheshc01 I will merge these (should have this hopefully this week). Then the rename can happen via the open Issue/PR in API Backlog. Thanks for your direction in this.