FORM-2
THE PATENT ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003
PROVISIONAL SPECIFICATION
(See section 10 and Rule 13)
QUALITY ASSURANCE
TATA CONSULTANCY SERVICES MLIMITED
An Indian Company
of Bombay House, 24, Homi Mody Street, Mumbai-400 001,
Maharashtra, India
THE FOLLOWING SPECIFICATION DESCRIBES THE INVENTION
FORM-2
THE PATENT ACT, 1970

Field of invention:
This invention relates to Quality Assurance.
In particular, this invention relates to a system for determining the Quality Assurance of a product.
Background of the invention:
In any market driven economy, it is essential that products brought out in the market are well marketed and properly positioned in a particular product segment. It is also important that the product is of high quality and is able to meet a significant percentage of the overall requirements of customers in the segment. For successful launching, marketing and sale of products it is essential that a well-planned strategy be used. A well rounded Quality Assurance strategy will go a long way in establishing the product in the market. Such strategy necessarily includes various types of market analysis and research work before any product is launched into the market. Such analysis and research usually include market surveys, price band analysis, feasibility and marketability analysis and the like.
Quality assurance is a process of verifying or determining whether products or services meet or exceed customer expectations. Quality assurance is a process and a system driven approach with specific steps to help define and attain quality goals taking into considerations like design, development, production, and service.
2

Quality assurance involves all steps and processes, right from design and development of a product to marketing and selling strategies. Some of the steps involved in Quality Assurance of a product are as follows:
(i) Pre product design market survey: Such a survey helps assessing the kind of products, customers would like to purchase.
(ii) Product design: Depending on the reports of the survey a product for a
particular product segment is designed.
(iii) Post product design market survey: Such type of survey helps in assessing the product potential in a particular market and is especially important for product pricing.
(iv) Product production: After the market survey is done, the product is manufactured.
(v) Price determination: Depending on the result of the survey the product is priced competitively with regards to similar Other products in the market.
(vi) Marketing: After price determination a precise marketing strategy is developed for marketing the products in various markets.
(vii) Product promotion and Sales strategies: Elaborate promotion and sales strategies are then formulated which usually help in capturing the market.
(viii) Customer feedback and response: A check is always kept on customer response. If the customers respond favourably to the product launched, then based on these reports, various other policies and strategies are formulated. These and many other steps are involved in the process of Quality Assurance.
3

Prior Art:
The most popular tool used to determine quality assurance is the Shewhart Cycle, developed by Dr. W. Edwards Deming. This cycle for quality assurance consists of four steps: Plan, Do, Check, and Act. These steps are commonly abbreviated as PDCA.
The four quality assurance steps within the PDCA model stand for:
• Plan: Establish objectives and processes required to deliver the desired results.
• Do: Implement the process developed.
• Check: Monitor and evaluate the implemented process by testing the results against the predetermined objectives.
• Act: Apply actions necessary for improvement if the results require changes.
PDCA is an effective method for monitoring quality assurance because it analyzes existing conditions and methods used to provide the product or service customers. The goal is to ensure that excellence is inherent in every component of the process. Quality assurance also helps determine whether the steps used to provide the product or services are appropriate for the time and conditions. In addition, if the PDCA cycle is repeated throughout the lifetime of the product or service, it helps improve internal company efficiency.
Quality assurance demands a degree of detail in order to be fully implemented at every step. Planning, for example, may include investigation
4

into the quality of the raw materials used in manufacturing, the actual
assembly, or the inspection of processes used. The Checking step may include customer feedback, surveys, or other marketing vehicles to determine if customer needs are being exceeded. Acting may include a total revision in the manufacturing process in order to correct a technical or cosmetic flaw. Competition to provide specialized products and services results in breakthroughs as well as long-term growth and change. Quality assurance verifies that any customer offering, regardless if it is new or evolved, is produced and offered with the best possible materials, in the most comprehensive way, with the highest standards. The goal to exceed customer expectations in a measurable and accountable process is provided by quality assurance.
US Patent No. 6601017 discloses a process and system for quality assurance. The process includes developing a high-level quality assurance resource estimate and a high level quality assurance time estimate; producing a business analysis outline; and creating an acceptance test plan using an acceptance test plan template with the business analysis outline.
US Patent No. 6859781 discloses a business method for quality assurance of services. The quality of information technology services provided by an organization to a customer is assured. Assurance reviews of a first solution are performed and a second solution is defined to correct deficiencies. A third assurance review is performed. Customer commitment to the second solution is obtained. A readiness review, a project management review, and a deliverable readiness review are performed assuring customer need satisfaction.
5

US Patent No. 7003766 discloses suite of metrics for software quality, assurance and product development. Based on software developed with use-cases, a suite of metrics for the Product/Process (PP) complexity of software systems as well the PP complexity of each stage in the software development process analysis, design, and testing is provided.
Patent Application No. 20020138510 discloses a system, method, and program for providing a QA tool to organize all the QA processes and report the QA results in an efficient and organized manner. A main page and hyperlinks are automatically generated from a database of test cases and tested devices to connect the all of the QA documentation, test results, and test logs for a specific device, wherein the main page and subsequent linked pages are viewable by a web browser.
Patent application No. 20050021380 discloses a strategic level quality assurance procedure that is designed to identify and quantify major strategic pitfalls for businesses, isolate their root cause (of negative impact on business), and provide solutions. Furthermore, it provides a means to achieve a tactical increase in market dominance by the internal application of a quality system at the strategic level via packaging its own strategic abilities and success, independently from its own. product performance, which can then be parceled out and marketed as a commodity of corporate quality, linked directly to a company's financial success.
This invention seeks to overcome the limitations of the prior art
6

An object of this invention is to provide a system for quality assurance for assessing the quality of a product to be marketed in a competitive market.
Summary of the invention:
In accordance with this invention there is provided a system for quality assurance for marketing of a product in a competitive market. The system comprises at least one module/suite, typically said system having four modules, each of said modules/suites functioning independently or alternatively functioning in co-operation with each other; said four modules being:
(i) a strategizing module named Q-Strategize;
(ii) a planning module named Q-Plan;
(iii) a testing module named Q-Test; and
(iv) an automation module named Q-Automate.
Brief description of the accompanying drawings:
The invention will be described in detail with reference to a preferred
embodiment. Reference to this embodiment does not limit the scope of the
invention.
In the accompanying drawings:
Figure 1 illustrates a flowchart representing steps or processes of the
strategizing module;
Figure 2 illustrates a flowchart representing steps or processes of the
planning module;
Figure 3 illustrates a flowchart representing steps or processes of the testing
module; and
7

Figure 4 illustrates a flowchart representing step or processes of the automation module.
Detailed description of the accompanying drawings:
The invention will now be explained with reference to Figures 1 to 4 of the accompanying drawings.
Figure 1 illustrates a flowchart representing the typical steps or processes of the strategizing module. The I Block represents the Initiation of the strategizing module. The strategizing module (Q-Strategize) involves:
(i) A tool for QA Organization Level Assessment:
o The IC (Information Collection) block represents a tool for
understanding the Product Roadmap and Target Market segment.
o The GA (Gap Analysis) block represents a tool for studying the
existing QA Department of a Product Organization.
o The RF (Recommendation Formulation) block represents a tool for
articulating organizational QA goals.
o The TSF (Test Strategy Formulation) block represents a tool for using
questionnaires, standard analysis tools and group contribution techniques
to understand pain areas (NGT- Nominal Group Technique, SNAC-
Stakeholder Needs Analysis and Constraints, SWOT - Strength,
Weakness, Opportunities and Threats).
o The TSF block also represents a tool for studying the detailed
schedules for Product Major Release
o The CF (Consolidated Feedback from other Q-Suites) block and the
AF (Analyse Feedback and identify Revisions/Corrections to Test
8

Strategy) block represent an analyzing tool for various parameters such as:
? Global QA teams vs Localized QA teams.
? Automated vs manual testing.
? Existing Customer Feedback/ trends for the product.
? Shared QA infrastructure across departments vs. dedicated QA infrastructure.
? Mechanisms for catching defects early like having a Design Verification Process in place.
(ii) The GA block represents an identifying tool for identifying gaps wdth respect to the identified Organizational QA Goals.
(iii) The DTOS (Derive Test Organization Structure) block represents a
tool for deriving optimal QA Organization Structure.
(iv) The DTOS block also represents a tool for deriving Infrastructure
Requirements.
(v) The TSF block represents a solutions' tool for working out a QA
strategy roadmap.
(vi) The TSF block also represents a solutions' tool for working out a QA
Automation Strategy.
The following reports / documents constitute the three parts that are implemented using Q Strategize incorporated within the TSF block.
• Test Organizational Maturity Report
o A reporting tool for assessment of maturity of the Testing / QA team of the Product Organization.
9

• Test Organization Structure (Standard Techniques for deriving
optimum Organization structure)
o A reporting tool for skills, Staffing, team Structure and training. o A reporting tool for QA Reporting and Communication.
• Test Strategy Document
o A reporting tool for Test Management & Metrics Strategy.
o A reporting tool for Test Environment, Change Control & Release
Strategy.
o A reporting tool for Defect Control, Tracking & Approach to Fixes.
o A reporting tool for Profiling and Analysis for Non Functional
Testing.
o A reporting tool for Completion Criteria.
Figure 2 illustrates a flowchart representing the typical steps or processes of the planning module in accordance with the system of this invention. The planning module (Q-Plan) can be defined using the following:
The reference symbol TS represents the Test Strategy block as shown in figure 2.
o The TS block encompasses the following steps in relation to QA Planning:
? Types of QA of relevance to the Product.
? DVT to QA/ QA to Alpha/ Alpha to Beta Gate Criteria.
? QA Schedules with respect to overall Product Schedules.
10

o The TS block also encompasses steps in relation to Estimation:
■ Test cycle time estimation.
The reference symbol TOS represents the Test Organisation Structure block as shown in figure 2.
o The TOS Block encompasses the following steps in relation to Test Environment:
? Test Bed Setup.
? Optimization of use of Hardware Infrastructure to reduce test cycle time. This may be achieved by minimizing the test infrastructure idle ant time.
? De-duplication of test cases across Products & Releases
o The TOS Block also encompasses the following steps in relation to Communications Plan:
? Reporting Plan.
? Interface criteria for interaction with cross functional group.
o The TOS Block also encompasses the following steps in relation to Test Design:
? Test Scenario Building
? Test Specifications.
11

? Pass/Fail criteria.
o The TOS Block also encompasses the following steps in relation to Define Entry/Exit Criteria:
? When to start testing criteria.
? When to stop testing criteria.
? Success criteria.
o The TOS Block also encompasses the following steps in relation to Establishing Test Traceability:
? Change Management.
o The TOS Block also encompasses steps in relation to Test Effectiveness Criteria.
o The TOS Block also encompasses steps in relation to Test change management:
? Version control.
o The TOS Block also encompasses the following steps in relation to Test Tools Selection.
? Checklist.
? Templates.
12

The reference symbol TP represents the Test Planning block as shown in figure 2.
o The TP block encompasses steps in relation to Multi-location Test Planning.
o The TP block also encompasses the following steps in relation to Defect Logging and Tracking Mechanism:
? Define priority level and severity level
? Define defect tagging rules for easy search.
? Define various states for defect.
The planning module also has a positive feedback engine [FE block] wherein test results from one test cycle act as a source of feedback for subsequent test cycles to identify and eliminate bottlenecks in testing processes, thereby enhancing test effectiveness. The reference symbol TA represents the Testing and Automation block as shown in figure 2. The block describes the improvements which can be classified into three broad categories:
o Short term improvements
■ To bring small improvements on short-term feedbacks from one test cycle. These are fed into subsequent test cycles. For instance, optimizing test cycle time by better automation coverage.
13

o Mid term improvements
■ To bring improvements at planning and testing level. For
instance, improvements that can increasingly detect hit
ratio, that can optimize test cycle or choose better testing
tools that can improve test execution productivity.
o Long term improvements
■ To bring improvements at strategy level. For instance,
feedbacks that help to establish an alternate team
organization to catch defects at the early stage for better
phase containment, thereby reducing overall costs.
Figure 3 illustrates a flowchart representing the typical steps or processes of the testing module (Q-Test) in accordance with the system of this invention. The artifacts that are produced during and at the end of the Test Execution [TCE block] (for a product release) under the testing module and some of the activities performed / information used coming up with the same include:
The reference symbol TCE represents the Test Case Execution block as shown in figure 3.
• The TCE block encompasses the following steps in relation to Test Data (if required):
o Create Data.
o Modify Data.
o Analyze Data Integrity of Existing Data.
14

o Analyze Data Sufficiency.
The reference symbol TCSR represents the Test Case and Scenario Refinement block as shown in figure 3.
• The TCSR block encompasses the following steps in relation to
Revised Test Cases - both Manual & Automated :
o Review and Refine Test Cases.
o Create additional test cases (if required).
o Fix broken test cases / suites.
• The TCSR block also encompasses the following steps in
relation to Defect Identification, Reporting & Tracking Log:
o Defect Identification, Reporting for the defects raised by the QA team during the test cycle.
The reference symbol TRAR represents the Test Result and Reporting block as shown in figure 3.
• The TRAR block encompasses the following steps in relation to
Test Progress reports:
o Status of defects (Defect distribution as per Severity,
Age, Area and the like).
o Test Health Monitor (Traffic Light System).
o Test Results (Test case wise pass / fail report).
15

• The TRAR block also encompasses the following steps in
relation to Test Report for the Release:
o List of Important Defects/Issues found.
o Priority Wise Test Case Distribution.
o Severity Wise Defect Distribution.
o Functional Area Wise Defect Distribution.
o Highlights and Lowlights.
o Risk Mitigation Strategy.
o Learning and Best Practices.
o Result Analysis.
o Feedback & QA Recommendations.
The results and reports assimilated from the above procedures / steps are also used to provide Small Improvements in the form of feedback and recommendations to other Q-Suites as represented by the SIQS Block.
Figure 4 illustrates a flowchart representing the typical steps or processes of the automation module (Q-Automate) in accordance with the system of this invention. The automation module has a framework named Q-Autoframe. All automation requirements are mapped to this framework. Based on the requirements of a specific customer, there are options of using existing tools/ products in the market and / or do fresh development for different parts of the framework. The various parts of the framework include but are not limited to the following:
• Trace-ability Matrix.
• Parallel Test Execution Controller.
• Automated Alerts Manager.
16

§ Hardware Resource
§ Manager. Test Case
§ Dependency Manager.
§ Workflow Engine.
§ Results Manager.
§ Test Simulators.
§ Test Configuration Manager.
The automation module or Q-Automate of this system performs the following activities:
• Test Requirements gathering.
• Gap analysis with Q-Autoframe.
• Solution Fitment.

Q-Automate has a Master QA Control System (MQCS) which helps maintain traceability. It implements a dashboard, which keeps track of life cycle of the test execution. The dashboard has several fields (only a simplified view is shown here)j which get populated during different stages of the test life cycle. Detailed steps of the test cycle with respect to MQCS are as follows:


• The master QA control System (MQCS) provides an encoder to encode test steps, test environment dependencies on other tests, constraints and the like in the form of a single file. Once encoded, scenarios are added to the dashboard for tracking. This enables the MQCS to learn about a test scenario first.
17

• MQCS also acts as an editor to provide options to add/delete/modify physical test beds to the available pool of test infrastructure.
• The functional tools perform the following tasks:
1) A parsing function:
o It implements a parser which can be triggered on demand. o Parser takes test scenario file as input, parses and extracts the
test infrastructure requirement from it. o It then searches and maps the requirements with the pool of
available test beds and tags the test scenario with suitable test
beds. o It populates other dashboard fields such as version of the
target product software release, test's own version and the
like.
2) Testing Function:
o MQCS provides a selective run of the test scenarios that have
gone through the parsing cycle,
o The dashboard is updated with the test execution status at
periodic intervals, once the run action is triggered
o Upon completion of execution, test result link is updated in
the dashboard for the end user analysis.
• In this way, MQCS maintains traceability from test planning
stage to test execution and result reporting stage.
18

While considerable emphasis has been placed herein on the various components of the preferred embodiment and the interrelationships between the component parts of the preferred embodiment, it will be appreciated that many alterations can be made and that many modifications can be made in the preferred embodiment without departing from the principles of this invention. These and other changes in the preferred embodiment as well as other embodiments of the invention will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the invention and not as a limitation.
19
Dated this 31st day of January, 2007.