Additional Questions – Test Strategy
Additional Questions – Analysis Strategy Table of Contents 1Purpose3 2About Added Questions3 3Requirements4 3. 1As-Is and New AQ Features4 AQ As-Is Affection from V14 AQ Added / Added Affection for V24 ?Create AQ anatomic Component4 ?AQ FCA affiliated to Scoring FCA4 ?Create AQ Accident by artful an absolute accident (closed, open, abstract & archived)4 ? Allure Supplier4 3. 2AQ Aerial Akin Functionality and Account of User Stories5 Table beneath gives the mapping of User Belief adjoin the As-Is AQ Functionality5 Table beneath gives the mapping of User Belief adjoin the New AQ Functionality5 4Additional Questions Development6 . 1AQ Affection Development in Releases6 4. 2In Sprint Testing (Blue are new AQ features)6 4. 3System Testing7 4. 4In Sprint Testing Dependencies7 4. 5System Testing Dependencies8 1 Purpose The purpose of this certificate is to accord the overview of the Analysis Strategy (Approach) for Added Questions Affection which will be developed and Implemented for V2. This certificate briefs about AQ functionality and its requirements, the development approach, this certificate additionally altercate about the assorted levels of testing AQ as its actuality developed & the dependencies for testing. About Added Questions Added Question is an absolute functionality of V1 Accelerate application, appropriately it’s accepted as As-Is affection for V2. And additionally accept some additional/enhanced appearance for V2. This Added Questions (AQ) is a client axial functionality and in V1 AQ is not a accepted affection which is accessible for all Buyers. It’s a Bolt-On feature, area a Client organisation can opt for this affection by authoritative added payment. AQ functionality has been developed and implemented in V1 in a way it can be configured for any Client Organisation.
AQ provides an added bend to Client Organisation area they can ask their advised Questions to a specific set of suppliers of their own absorption and abbreviate account them aloft their response. Appliance this affection affiliate of a Client Organisation, who is accepting permissions to AQ can actualize an AQ Accident which comprises of a arrangement with questions, and the affiliate can chase for suppliers and allure them all or a specific set of suppliers to acknowledgment the questions, on or afore a asleep band date set for the accurate AQ accident by the member.
Buyer user can actualize AQ Contest and save it for affection purpose, absolute AQ accident can be acclimated by some alternative Client Organisation affiliate and the affiliate can use it as it is or can do some changes afore agreeable the suppliers. Even the arrive AQ contest can be reused. Client User will be able to add or abolish questions to an AQ event. A. Q arbitrary is the aftermost date of abstract accident in which the user can examination the accomplished accident and additionally analysis it afore sending it to the supplier users. Supplier needs to acknowledge to AQ and client will amount supplier according.
Scoring agent will advice AQ to amount Supplier. AQ artefact needs to be configured by C3 user with all appropriate features. AQ will be added as a basic which will be affiliated by adolescent artefact (community). * 3 Requirements Requirements developed as User Belief and advised by Products & Services aggregation and approved. Both the absolute appearance (As-Is) and the new V2 specific added / added appearance are additionally covered in user stories. The beneath table will accord the bifurcation of Absolute and New appearance of Added Questions. . 1 As-Is and New AQ Appearance * AQ As-Is Affection from V1| * AQ Added / Added Affection for V2| * Actualize AQ Arrangement | * Actualize AQ anatomic Component| * Actualize AQ Abstract accident & analysis of AQ| * AQ FCA affiliated to Scoring FCA| * Actualize AQ Accident appliance AQ Template| * Permission to C3 User for AQ| * Actualize AQ Accident by artful an absolute accident (closed, open, abstract & archived)| * Actualize & use AQ Library * | * Allure Supplier| * Accent Abutment to AQ| AQ appearance for GBO | * Client assigns scoring to AQ Event| * AQ appearance for Buyer| * Scoring can be chiral or automated * | * AQ appearance for Supplier| * AQ active to client back Current Date + 7 >= End Date| * Modification to AQ Accessible Accident | * Reminder email to supplier who has not responded| * Categorisation of AQ Accessible Accident (Responded, Not Responded, Not Interested)| * Clarification asked by Client on AQ supplier acknowledgment | * AQ Reports| * AQ scoring for anniversary supplier| * | * Comparison of AQ with account to supplier| * | * Client amount & email to supplier on AQ Close Event| * 4. 2 AQ Aerial Akin Functionality and Account of User Belief * Table beneath gives the mapping of User Belief adjoin the As-Is AQ Functionality Area| Functionality| User Story| GBO| | | | | | | | | Buyer| | | | | | | | | | | | Supplier| | | | | | | | | * Table beneath gives the mapping of User Belief adjoin the New AQ Functionality Area| Functionality| User Story| GBO | | | | | | | | | Buyer| | | | | | | | | | | | Supplier| | | | | | | | | * 4 V2 Development Strategy 5. 3 Development Admission V2 development is a mix of both Avalanche and Active development framework.
The Development of requirements follows waterfall, area as the absolute cipher development will appear in active methodology. Aboriginal all the User Belief will be written, advised and active off by the pale holders. Development will chase the aerial akin anniversary plan, which comprises of centralized releases and Demo Release. Date| 1/Dec/12| 1/Jan/13| 15/Jan/13| 29/Jan/13| 1/Feb/13| 1/Mar/13| 15/Mar/13| 29/Mar/13| Release| Alpha 0. 1| Alpha 0. 2| Alpha 0. 3| Alpha 1. 0| Alpha 1. 1| Alpha 1. 2| Alpha 1. 3| Alpha 2. 0| Purpose| Internal| Internal| Internal| Board| Internal| Internal| Internal| Board|
As mentioned aloft anniversary and every centralized absolution has assorted Iterations for development and the user belief will be allocated to these iterations for development. Aural these iterations all the allocated user belief will be developed and activated In-Sprint Testing. 5. 4 AQ Affection Development in Releases As explained above, AQ as affection to be developed for V2 will additionally chase the aforementioned development methodology, All User Belief belongs to AQ will aboriginal written, advised and active off, and again developed in assorted releases in assorted iterations.
The table beneath will accord us the account of AQ Development in Absolution and Abundance wise. The Main purpose of the beneath table is to accord bright account of Back AQ affection development will be started and in which absolution it will developed and delivered 100%. Table beneath will not accord the Start and End dates of either anniversary and every absolution or Iterations, these dates are accessible with the development aggregation and ion their plan. Release| Iteration| User Story| Functionality / Area| Centralized Absolution Alpha 0. 1| Abundance 1| | | | Abundance 2| | | | Abundance 3| | | Abundance 4| | | Centralized Absolution Alpha 0. 2| Abundance 1| | | | Abundance 2| | | | Abundance 3| | | | Abundance 4| | | Centralized Absolution Alpha 0. 3| Abundance 1| | | | Abundance 2| | | | Abundance 3| | | | Abundance 4| | | Demo Absolution 1. 0| Abundance 1| | | | Abundance 2| | | | Abundance 3| | | | Abundance 4| | | Centralized Absolution Alpha 1. 1| Abundance 1| | | | Abundance 2| | | | Abundance 3| | | | Abundance 4| | | Centralized Absolution Alpha 1. 2| Abundance 1| | | | Abundance 2| | | | Abundance 3| | | | Abundance 4| | | Centralized Absolution Alpha 1. 3| Abundance 1| | | Abundance 2| | | | Abundance 3| | | | Abundance 4| | | Demo Absolution 2. 0| Abundance 1| | | | Abundance 2| | | | Abundance 3| | | | Abundance 4| | | 5 AQ Analysis Admission This area describes the analysis admission for Added Question by answer the following. * Testing Ambit of Added Questions * Annex with alternative analytical V2 functionalities * Affiliation with Third Party Appliance Appearance * Levels of Testing * Analysis Architecture & Beheading * Analysis Data Requirements * Anatomic Automation Testing * Non Anatomic Testing Ambit 6. 5 Ambit of Added Questions
Additional Question as affection it advance beyond all the above areas of V2 application, admitting it’s Client axial affection it’s accepting ambit in C3 (Configuration Ascendancy Center), GBO (Global Back Office), SCC (Standard Company Concept) Client & Supplier. End to End Angle From an end to end angle the AQ functionality testing needs to be started from C3 (may be agreement of AQ – charge added advice to complete it) and again SCC-Buyer can actualize AQ Contest and allure Suppliers and again SCC- Suppliers can acknowledge for AQ events.
From GBO-User angle AQ needs to be activated for AQ Dashboard, AQ Reports, etc... (need added advice to complete this section) Non Anatomic Angle – Performance Few AQ Appearance needs to be activated for Performance * AQ arrangement conception with added Questions * Agreeable assorted suppliers * Acknowledgment time of examination AQ responses * AQ Report Generation for SCC-Buyer & GBO User Multilingual Angle As Added Question can be configured for any arrangement / community, and we accept communities which abutment added than one language, AQ needs to be activated in all applicative languages.
Cross Browser Angle As Client organisation associates and Suppliers can use any browser to admission the application, Added Questions appearance needs to be activated in assorted browser combinations. Association Specific Added Questions can be configured for specific communities and as we already accept few communities finer appliance AQ, all such communities needs to be activated thoroughly AQ feature. Supplier Angle AQ needs to be thoroughly activated with * Newly Registered Suppliers * Migrated Suppliers 6. 6 Added Questions Annex with alternative Features. Additional
Questions is one of the affection in V2 application, this affection has some affiliation / annex with some alternative appearance of V2 application. This area describes the AQ annex with such alternative appearance of V2. This annex may comedy a analytical role in AQ testing at anatomic akin and at end to end testing, we may accept a assignment about to bypass the dependency, area as some affection charge be accessible to analysis AQ. AQ Feature| Dependent Feature| Annex level| Back This Affection will be Ready| Do we accept Assignment Around| Assignment Around| Effectiveness of Assignment Around| Allure Supplier| Search| Actual High| ? ? | | ? | | Email Generation| Actual High| ? | ? | | ? | | Absolute / Migrated Suppliers| High| ? | ? | | ? | All such dependencies for all AQ appearance needs to be captured in a abstracted excel area and absorbed to this document. And the Dependencies needs to be discussed with Development team, as we may charge their advice for some assignment about or the affection needs to be developed in a priority. This annex is actual analytical for analysis execution. 6. 7 Affiliation with Third Party Appliance Appearance This area needs to be abounding in 6. 8 Levels of Testing
Additional Questions will be activated at In-Sprint Testing and Arrangement Testing, this area describes what will be covered in In-Sprint Testing and Arrangement Testing. In-Sprint Testing In-Sprint Testing is allotment of development, In-Sprint testing aggregation will assignment forth with Development aggregation for Absolution and Iterations, user belief assigned to iterations is the ambit for development and testing, while development teams starts coding In-Sprint testing aggregation starts analysis design, back the affection is developed and accessible for testing, In-Sprint analysis aggregation will analysis the affection and accord the result.
In-Sprint analysis aggregation covers Unit, Integration, Connected Affiliation and Regression Testing. In-Sprint Assemblage Testing In assemblage testing, aggregation checks for the afterward appliance Checklists * Field Akin Validation of all controls * Boundary Value, Equivalence Partitioning * Page Navigation on Links * Messages (information on ascendancy validation, Tool Tips, etc... ) * Page Templates, Company Logo, T&C’s, Copy Right, etc... * Cross Browser – All UI architecture needs to be accurate with all applicative browser combinations
In-Sprint Affiliation Testing Aggregation analysis the appearance developed chip with preceded and afterward appearance of a affection belongs to aforementioned bore (Group of requirements, belongs to one user story) aural the abundance as the appearance actuality developed in iterations. And additionally the affiliation of accumulation of requirements developed (one User story) with addition accumulation of requirements (another User Story) as abundance is accepting assorted User stories. In-Sprint analysis aggregation will address anatomic analysis cases to analysis this affiliation of features.
In-Sprint Connected Affiliation Testing Aggregation tests the affiliation of appearance developed in assorted iterations, as the appearance developed beyond assorted iterations of any absolution are actuality continuously chip together. Aggregation may address abstracted set of affiliation analysis cases for this abroad they will enhance their absolute affiliation analysis cases to analysis this, in an addition admission aggregation can accumulation set of alone affiliation analysis cases and assassinate them in an adjustment which covers this connected integration.
In-Sprint Regression Testing Analysis aggregation executes all the analysis cases which belongs to beforehand absolution for any alternating release, this is to ensure that the new absolution appearance are not arrest the absolute appearance already developed and activated and additionally ensures the affiliation of appearance in amid two alternating absolution is alive fine. Table beneath gives a account of Unit, Integration, Connected Affiliation & Regression testing for Releases and Iterations.
Release| Iteration| User Story| Feature| Testing| | | | | Unit| Integration| Connected Integration| Regression| Absolution 1| Abundance 1| User Adventure 1| Affection 1| Y| Affiliation of affection 1+2+3+4| Connected Affiliation of User Adventure 1 + 2+ 3| Absolution 1 TC's Regression Suite for Absolution 2| | | | Affection 2| Y| | | | | | | Affection 3| Y| | | | | | | Affection 4| Y| | | | | | User Adventure 2| Affection 5| Y| Affiliation of affection 5+6+7+8| | | | | | Affection 6| Y| | | | | | | Affection 7| Y| | | | | | | Affection 8| Y| | | | | User Adventure 3| Affection 9| Y| Affiliation of affection 9+10| | | | | | Affection 10| Y| | | | | Abundance 2| User Adventure 4| Affection 11| Y| Affiliation of affection 11+12+13+14| Connected Affiliation of User Adventure 1 + 2+ 3+4+5+6| | | | | Affection 12| Y| | | | | | | Affection 13| Y| | | | | | | Affection 14| Y| | | | | | User Adventure 5| Affection 15| Y| Affiliation of affection 15+16+17+18| | | | | | Affection 16| Y| | | | | | | Affection 17| Y| | | | | | | Affection 18| Y| | | | | | User Adventure 6| Affection 19| Y| Affiliation of affection 19+20| | | | | | Affection 20| Y| | | |
Release 2| Abundance 3| User Adventure 7| Affection 21| Y| Y| Y| Absolution 1 + Absolution 2 TC's Regression Suite for Absolution 3| | | | Affection 22| Y| | | | | | | Affection 23| Y| | | | | | | Affection 24| Y| | | | | | User Adventure 8| Affection 25| Y| Y| | | | | | Affection 26| Y| | | | | | | Affection 27| Y| | | | | | | Affection 28| Y| | | | | | User Adventure 9| Affection 29| Y| Y| | | | | | Affection 30| Y| | | | | Abundance 4| User Adventure 10| Affection 31| Y| Y| Y| | | | | Affection 32| Y| | | | | | | Affection 33| Y| | | | | | | Affection 34| Y| | | | | | User Adventure 11| Affection 35| Y| Y| | | | | Affection 36| Y| | | | | | | Affection 37| Y| | | | | | | Affection 38| Y| | | | | | User Adventure 12| Affection 39| Y| Y| | | | | | Affection 40| Y| | | | Arrangement Testing Arrangement testing will be accomplished by Arrangement Testing team, Arrangement analysis architecture and beheading will be done as End to End level. In Arrangement analysis architecture we will address Analysis Scenarios and Prepare Analysis Data to assassinate the Arrangement Testing. Analysis Scenarios will awning assorted functionalities with all about-face and aggregate of functionalities to analysis all accessible absolute time end to end scenarios.
System testing will additionally awning the end to end scenarios for best cardinal of suppliers, for archetype Arrangement testing will be accomplished for agreeable 500 suppliers for an AQ event, creating an AQ accident with 100 Questions. And to assassinate the end to end testing for such aerial aggregate of suppliers we charge abutment from Automation, because as the V2 appliance actuality developed appropriate from the scratch, absolute suppliers not accessible in the system, appropriately we charge to aboriginal annals for 100 of suppliers, registering 100 of suppliers will crave aerial ability calculation and it’s about not possible.
And additionally acknowledge to an AQ accident beatific for 100 of suppliers it booty time and resource, if it needs to be done manually, in such book we charge Automation calligraphy to complete the task. 6. 9 Analysis Architecture 6. 10 Analysis Data Requirements 6. 11 Anatomic Automation Testing 6. 12 Non Anatomic Testing Scope
Order a unique copy of this paper