Search

Thomas C Pavela

from Foster City, CA
Age ~74
Get Report
Also known as:
Thomas C Pazela, Thomas C Pauela
Phone and address:
706 Cayman Ln, San Mateo, CA 94404
(650) 349-3931
Related to:
Camille I BermudezPavela Aly, 32Shelley Pavela, 68Kimberly Pavela, 30Aly Pavela, 32Alyson Pavela, 32
Connected to:
Andrea Pavela, 35John R Pavelchak, 40Paula J Pavelcsyk, 76Amy E Pavelecky, 51Jeffrey R Paveleck, 60Ray R Pavelec, 77Richard M Pavelecky, 61Tomas Pavelek, 48Marianne V Paveletz, 60Jeffrey Pavelich, 55

Thomas Pavela Phones & Addresses

  • 706 Cayman Ln, Foster City, CA 94404 (650) 349-3931
  • 1640 Vista Del Sol, San Mateo, CA 94404
  • Sundance, UT

Industries

Information Technology and Services

Resumes

Resumes

Thomas Pavela Photo 1

Experienced High-Technology Executive

View page
Location:
San Francisco Bay Area
Industry:
Information Technology and Services

Business Records

Name / Title
Company / Classification
Phones & Addresses
Thomas C. Pavela
Director, President
OMNI-ID USA, INC
Business Consulting Services · Mfg Electrical Measuring Instruments
1065 E Hillsdale Blvd SUITE 400, San Mateo, CA 94404
(650) 571-6664

Publications

Us Patents

Graphical User Interface For Developing Test Cases Using A Test Object Library

View page
US Patent:
6421822, Jul 16, 2002
Filed:
Dec 28, 1998
Appl. No.:
09/222267
Inventors:
Thomas J. Pavela - San Jose CA
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 944
US Classification:
717125, 717109, 345771, 345970
Abstract:
A method, apparatus, article of manufacture, for generating a test code for an automatic procedure is disclosed. The method comprises the steps of presenting a visual representation of a library of executable code objects comprising a plurality of test objects to a user, accepting a selection of a first test object in the visual representation, presenting first test object options defining at least one test parameter, accepting a selection of a first test option, translating the first test option into at least one tag and at least one tag parameter, and storing the tag and the tag parameter in a source file. The article of manufacture comprises a data storage device tangibly embodying instructions to perform the method steps described above. The apparatus comprises computer with suitable program instructions for presenting a visual representation of a library of executable code objects to a user. The library of executable code objects includes a plurality of test object members, each of which define a set of instructions for performing a portion of the test procedure.

Method And Apparatus For Managing Code Test Coverage Data

View page
US Patent:
6536036, Mar 18, 2003
Filed:
Apr 6, 1999
Appl. No.:
09/286771
Inventors:
Thomas J. Pavela - San Jose CA
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 944
US Classification:
717125, 7071041
Abstract:
A method and apparatus for code coverage management is provided, wherein code coverage data, which may be stored in a database, is updated or resequenced with the code changes. This resequencing eliminates the need to freeze the program code while collecting the code coverage data. When a code change is incorporated into the system the resequencing routine makes the necessary adjustments to the code coverage data. Furthermore, building a table in a database to store code coverage data for every test case may not be feasible. Thus, in accordance with the present invention, the last column of the table may contain a pointer to a file. The file then contains the list of test cases that exceeded the table.

System And Method For Developing Test Cases Using A Test Object Library

View page
US Patent:
6978440, Dec 20, 2005
Filed:
Sep 19, 2001
Appl. No.:
09/955804
Inventors:
Thomas J. Pavela - San Jose CA, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F009/44
US Classification:
717125, 717106, 717123, 717135
Abstract:
A method, apparatus, article of manufacture, and a memory structure for generating a test code for an automatic procedure is disclosed. The method comprises the steps of defining a source file having a plurality of tags associated with a member of a library of executable code objects defining a set of instructions for performing a portion of the automatic test procedure, generating a test plan in a conventional language from the source file, and generating an automated test code for the automated test procedure from the source file. In one embodiment, a test index identifying system elements tested by the test code is generated and incorporated into the test plan, allowing the user to verify that all desired system elements are exercised by the automated test code. The article of manufacture comprises a data storage device tangibly embodying instructions to perform the method steps described above. The apparatus comprises means for defining a source file having a plurality of tags, wherein each tag is associated with a member of a library of executable code objects defining a set of instructions for performing a portion of an automatic test procedure, means for generating a test plan in a conversational language from the source file, and means for generating an automated test code for the automatic test procedure from the source file.

Method And Apparatus For Collecting Persistent Coverage Data Across Software Versions

View page
US Patent:
20030093716, May 15, 2003
Filed:
Nov 13, 2001
Appl. No.:
09/990802
Inventors:
Eitan Farchi - Pardes Hana, IL
Thomas Pavela - San Jose CA, US
Shmuel Ur - Shorashim, IL
Avi Ziv - Haifa, IL
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
H04B001/74
US Classification:
714/034000
Abstract:
A method, apparatus and article of manufacture for persistent code coverage data collection are provided. Initially, a program for which code coverage data should be collected is identified and divided into code coverage tasks (i.e. basic blocks) and each code coverage task is given a unique name. Coverage points are then inserted into the program source code at the beginning of each coverage task to produce an instrumented program. The instrumented program is then compiled and link-edited with an appropriate library to produce a program executable. A set of test cases to be run for a persistent code coverage data collection purposes is identified next. Then, the code coverage database is created using the identified code coverage tasks and the test cases. The program executable is loaded and run with the set of identified test cases to write coverage point information into an output file. The output file is then processed in order to populate the code coverage database with the code coverage data per each code coverage task. When the program is modified, the new and modified code coverage tasks and the new test cases identified and the code coverage database is updated accordingly. The code coverage data for the non-affected code coverage tasks is preserved for testing of the new version of the program eliminating the need for running the entire test bucket. The code coverage database may be queried to determine which test cases need to be rerun.

System And Method For Developing Test Cases Using A Test Object Library

View page
US Patent:
63322110, Dec 18, 2001
Filed:
Dec 28, 1998
Appl. No.:
9/221389
Inventors:
Thomas J. Pavela - San Jose CA
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 9445
US Classification:
717 2
Abstract:
A method, apparatus, article of manufacture, and a memory structure for generating a test code for an automatic procedure is disclosed. The method comprises the steps of defining a source file having a plurality of tags associated with a member of a library of executable code objects defining a set of instructions for performing a portion of the automatic test procedure, generating a test plan in a conventional language from the source file, and generating an automated test code for the automated test procedure from the source file. In one embodiment, a test index identifying system elements tested by the test code is generated and incorporated into the test plan, allowing the user to verify that all desired system elements are exercised by the automated test code. The article of manufacture comprises a data storage device tangibly embodying instructions to perform the method steps described above. The apparatus comprises means for defining a source file having a plurality of tags, wherein each tag is associated with a member of a library of executable code objects defining a set of instructions for performing a portion of an automatic test procedure, means for generating a test plan in a conversational language from the source file, and means for generating an automated test code for the automatic test procedure from the source file.

Predicting Software Product Quality

View page
US Patent:
20170091071, Mar 30, 2017
Filed:
Sep 25, 2015
Appl. No.:
14/865384
Inventors:
- Armonk NY, US
Catherine M. Cox - San Jose CA, US
Dario D'Angelo - Los Gatos CA, US
Xiyao Jiang - Shanghai, CN
Shahin Mohammadi-Rashedi - San Jose CA, US
Thomas J. Pavela - San Jose CA, US
Jeffrey S. Rhodes - San Jose CA, US
Marian E. Sadowski - Sunnyvale CA, US
International Classification:
G06F 11/36
Abstract:
Predicting software product quality. Real-time and historic software code metrics, software code defect data for the software product, and test case-related data for the software product are received. A feature predicted fallibility that estimates the number of code defects for a new feature of the software product, a product version projected fallibility that estimates the number of code defects for a new version of a software product, a test case related quality coefficient that estimates the likelihood of discovery of code defects in a new feature, a feature quality and a product quality indexes that are qualitative indications of quality of the new code of a feature and the new product version, are calculated. A report is then output that includes at least the calculated values, whereby developer resources are directed to features of the software product for which the calculated values indicate likelihoods of a high defect densities.
Control profile
Thomas C Pavela from Foster City, CA, age ~74 Get Report