Table of Contents
2About Additional Questions3
3.1As-Is and New AQ Features4
AQ As-Is Feature from V14
AQ Additional / Enhanced Feature for V24
Create AQ functional Component4
AQ FCA linked to Scoring FCA4
Create AQ Event by copying an existing event (closed, open, draft & archived)4 Invite Supplier4
3.2AQ High Level Functionality and List of User Stories5
Table below gives the mapping of User Stories against the As-Is AQ Functionality5
Table below gives the mapping of User Stories against the New AQ Functionality5 4Additional Questions Development6
4.1AQ Feature Development in Releases6
4.2In Sprint Testing (Blue are new AQ features)6
4.4In Sprint Testing Dependencies7
4.5System Testing Dependencies8
The purpose of this document is to give the overview of the Test Strategy (Approach) for Additional Questions Feature which will be developed and Implemented for V2. This document briefs about AQ functionality and its requirements, the development approach, this document also discuss about the various levels of testing AQ as its being developed & the dependencies for testing.
2 About Additional Questions
Additional Question is an existing functionality of V1 Accelerate application, hence it’s known as As-Is feature for V2. And also have some additional/enhanced features for V2.
This Additional Questions (AQ) is a buyer centric functionality and in V1 AQ is not a common feature which is available for all Buyers. It’s a Bolt-On feature, where a Buyer organisation can opt for this feature by making additional payment. AQ functionality has been developed and implemented in V1 in a way it can be configured for any Buyer Organisation.
AQ provides an additional edge to Buyer Organisation where they can ask their intended Questions to a specific set of suppliers of their own interest and short list them upon their response.
Using this feature member of a Buyer Organisation, who is having permissions to AQ can create an AQ Event which comprises of a template with questions, and the member can search for suppliers and invite them all or a specific set of suppliers to answer the questions, on or before a dead line date set for the particular AQ event by the member.
Buyer user can create AQ Events and save it for feature purpose, existing AQ event can be used by some other Buyer Organisation member and the member can use it as it is or can do some changes before inviting the suppliers. Even the invited AQ events can be reused.
Buyer User will be able to add or remove questions to an AQ event. A.Q summary is the last stage of draft event in which the user can preview the whole event and also review it before sending it to the supplier users. Supplier needs to respond to AQ and buyer will rate supplier according. Scoring engine will help AQ to rate Supplier.
AQ product needs to be configured by C3 user with all required features. AQ will be added as a component which will be inherited by child product (community).
Requirements developed as User Stories and reviewed by Products & Services team and approved. Both the existing features (As-Is) and the new V2 specific additional / enhanced features are also covered in user stories. The below table will give the bifurcation of Existing and New features of Additional Questions. 4.1 As-Is and New AQ Features
* AQ As-Is Feature from V1| * AQ Additional / Enhanced Feature for V2| * Create AQ Template | * Create AQ functional Component| * Create AQ Draft event & review of AQ| * AQ FCA linked to Scoring FCA| * Create AQ Event using AQ Template| * Permission to C3 User for AQ| * Create AQ Event by copying an existing event (closed, open, draft & archived)| * Create & use AQ Library * | *...