Click here to Skip to main content

Karpov Andrey - Professional Profile

12,430
Author
195
Authority
114
Debator
94
Editor
50
Enquirer
81
Organiser
441
Participant
27 May 2011: Best C++/MFC article of April 2011
25 May 2009: Best C++/MFC article of April 2009
19 May 2007: Best C++/MFC article of Apr 2007

Andrey Karpov is technical manager of the OOO "Program Verification Systems" (Co Ltd) company developing the PVS-Studio tool which is a package of static code analyzers integrating into the Visual Studio development environment.

PVS-Studio is a static analyzer that detects errors in source code of C/C++ applications. There are 3 sets of rules included into PVS-Studio:

  1. Diagnosis of 64-bit errors (Viva64)
  2. Diagnosis of parallel errors (VivaMP)
  3. General-purpose diagnosis

Awards: MVP, Intel Black Belt

Andrey Karpov is also the author of many articles on the topic of 64-bit and parallel software development. To learn more about the PVS-Studio tool and sources concerning 64-bit and parallel software development, please visit the www.viva64.com site.

Best Articles:

My page on LinkedIn site: http://www.linkedin.com/pub/4/585/6a3

E-mail: karpov@viva64(dot)com

Member since Saturday, May 12, 2007 (5 years)

For more information on Reputation please see the FAQ.
 
You must Sign In to use this message board. (secure sign-in)
 
Search this forum  
  Refresh
GeneralDeveloping code testing and verification tools Pin
Monday, May 17, 2010 12:03 AM

OOO "Program Verification Systems" develops and maintains the PVS-Studio tool intended for detecting 64-bit and parallel errors in the code of C/C++ applications. The PVS-Studio package is a set of specialized static code analyzers that allow to perform verification of source code at the stage of program designing already and therefore significantly reduce costs on program debugging, testing and maintenance.

Our company is ready to develop and maintain specialized testing tools. We can implement the tasks of the following types:

1) Development of a specialized static analyzer for internal needs of the customer. We can implement a set of specialized diagnostic rules and integrate the tool into an existing software development cycle. In other words, we can create a tool to control the coding standard accepted in the customer's company.

2) We can develop a code analyzer accompanying solutions suggested by the customer and therefore support the customer's users. For example, the customer might develop a C/C++ compiler and a set of other development means for specialized processors. We can supplement the development set with a static analyzer customized specially for detecting the most relevant issues in user codes. Here is another example - we can develop a static analyzer that would check if a large and complex library is used correctly.

3) We can develop other solutions which are not connected with source code static analysis but require parsing the code of C/C++ programs. For example: tools to create documentation relying on the source code, tools to build dependencies between various units.

This is only a brief list of possible developments and other ways of cooperation are also possible. We are ready to provide you with additional information and answer all your questions.


Contacts

Site: http://www.viva64.com

E-Mail: support@viva64.com

Feedback Form: http://www.viva64.com/about/feedback/

Postbox: 300027, Russia, Tula, P.O. 1800.


General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   


Advertise | Privacy | Mobile
Web04 | 2.5.120528.1 | Last Updated 28 May 2012
Copyright © CodeProject, 1999-2012
All Rights Reserved. Terms of Use
Layout: fixed | fluid