Browse Prior Art Database

Self-refining score and recommendation system for automation project

IP.com Disclosure Number: IPCOM000240121D
Publication Date: 2015-Jan-05
Document File: 7 page(s) / 192K

Publishing Venue

The IP.com Prior Art Database

Abstract

The System is used for automation project estimation, it uses multi-dimensional KPIs as inputs and based on a standard automation evaluation criteria for estimation, it will provide an improved solution after estimate a project. The system compare target project and current existing project. When existing project has similiar UI implementation, then information collection and evaluation could affort by current porject; When existing project do not have similiar implementation, the system extract UI technical information from auto-analysis repository, then process automation assessment program, from template reading to score calculation, and get final grade at last.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 01 of 7

Self

Self-

Software testing is being considered so important that organizations can allocate teams exclusively for testing activities in order to achieve more test efficiency and unbiased test results. In such situations, test teams should be able to estimate the required effort to perform their test activities on the schedule and to request more resources or negotiate deadlines when necessary. In the practice, the consequences of poor estimates are costly to the organization: scope reduction, schedule overrun and overtime.

-Several software development estimation models have been proposed over the years. COCOMO II is a well-known example of model used for estimating the effort to develop software products based on their characteristics (lines of code, function points, etc.). Regarding tests, Test Point Analysis is a model used for estimating the effort to define, develop and execute functional tests.

-However, these models do not estimate the effort to perform some specific testing activities (such as the execution of a given set of test cases), since their estimations are based on development complexity instead of test execution complexity. For this reason, estimates are usually made only based on expert judgment and historical data, which generally leads to a lack of precision.

-Related technologies and methods describes a tool that supports the measurement of test size and execution complexity, as well as the estimation of test execution effort. The tool was designed to be extended according to the customers needs, such as different estimation models, file formats of test specifications, parsers APIs, etc.
-
-In order to estimate the effort to exec...