Table of Contents
1 Purpose 3
2 About Additional Questions 3
3 Requirements 4 3.1 As-Is and New AQ Features 4
AQ As-Is Feature from V1 4
AQ Additional / Enhanced Feature for V2 4
Create AQ functional Component 4
AQ FCA linked to Scoring FCA 4
Create AQ Event by copying an existing event (closed, open, draft & archived) 4
Invite Supplier 4 3.2 AQ High Level Functionality and List of User Stories 5 Table below gives the mapping of User Stories against the As-Is AQ Functionality 5 Table below gives the mapping of User Stories against the New AQ Functionality 5
4 Additional Questions Development 6 4.1 AQ Feature Development in Releases 6 4.2 In Sprint Testing (Blue are new AQ features) 6 4.3 System Testing 7 4.4 In Sprint Testing Dependencies 7 4.5 System Testing Dependencies 8
1 Purpose
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