Visual Expert
Jump to navigation
Jump to search
| VISUAL EXPERT | |
|---|---|
| Developer | Novalys |
| Initial release | 1995 |
| Stable release | Visual Expert 2025 [1]
|
| Repository |
|
| Written in | C# |
| Engine | |
| Operating system | Windows |
| Available in | English, Japanese, Spanish, French |
| Type | Code analysis tools |
| License | Subscription, Perpetual, Concurrent [2] |
| Website | www |
Visual Expert is a static code analysis tool, extracting design and technical information from software source code by reverse-engineering, used by programmers for software maintenance, modernization or optimization.
It is designed to parse several programming languages at the same time (PL/SQL, Transact-SQL, PowerBuilder...) and analyze cross-language dependencies, in addition to each language's source code.
Visual Expert checks source code against hundreds of code inspection rules for vulnerability assessment, bug fix, and maintenance issues.[3]
Features
[edit | edit source]- Cross-references exploration: Impact Analysis, E/R diagrams, call graphs, CRUD matrix, dependency graphs.
- Software documentation: a documentation generator produces technical documentation and low-level design descriptions.
- Inspect the code to detect bugs, security vulnerabilities and maintainability issues. Native integration with Jenkins.[4]
- Reports on duplicate code, unused objects and methods and naming conventions. Calculates software metrics and source lines of code.
- Code comparison: finds differences between several versions of the same code.
- Performance analysis: identifies code parts that slow down the application because of their syntax - it extracts statistics about code execution from the database and combines it with the static analysis of the code.
Usage
[edit | edit source]Visual Expert is used in several contexts:
- Change impact analysis: evaluating the consequences of a change in the code or in a database. Avoiding negative side effects when evolving a system.
- Static Application Security Testing (SAST): detecting and removing security issues.
- Continuous Integration / Continuous Inspection : adding a static code analysis job in a CI/CD workflow to automatically verify the quality and security of a new build when it is released.
- Program comprehension: helping programmers understand and maintain existing code, or modernize legacy systems. Transferring knowledge of the code, from one programmer to another.
- Software sizing: calculating the size of an application, or a piece of code, in order to estimate development efforts.
- Code review: improving the code by finding and removing code smells, dead code, code causing poor performances or violations of coding conventions.
Limitations
[edit | edit source]- As a static code analyzer, Visual Expert is limited to the programming languages supported by its code parsers - Oracle PL/SQL, SQL Server Transact-SQL, PowerBuilder.
- A preliminary reverse engineering is required. Visual Expert does it automatically, but its duration depends on the size of the code parsed. Users must wait for the parsing completion prior to using the features, or schedule it in advance. They must also allocate sufficient hardware resources to support their volume of code.
- Visual Expert is based on a client/server architecture: the code analysis is running on a Windows PC - preferably a server. The information extracted from the code is stored in a RDBMS, communicating with a client application installed on the programmer's computer - no web client is available. This requires that the code, the parsers, the RDBMS and the programmers’ computers are connected to the same LAN or VPN.
History
[edit | edit source]- 1995- 1998 - Prog and Doc - Initial version distributed on the French market [5]
- 2001 - Visual Expert 4.5
- 2003 - Visual Expert 5[6]
- 2007 - Visual Expert 5.7[7]
- 2010 - Visual Expert 6.0[8]
- 2015 - Visual Expert 2015 - Server component added to schedule code analyses[9][10]
- 2016 - Visual Expert 2016 - Oracle PL/SQL code parser, code inventory (lines of code, number of objects…)[11]
- 2017 - Visual Expert 2017 - SQL Server T-SQL code parser, Code comparison, CRUD matrix[12]
- 2018 - Visual Expert 2018 - DB Code Performance Analysis, integration with TFS
- 2019 - Visual Expert 2019 - Generation of E/R diagrams from the code
- 2020 - Visual Expert 2020 - Object dependency matrix, naming consistency verification, integration with GIT and SVN
- 2021 - Visual Expert 2021 - Continuous Code Inspection,[13] integration with Jenkins
- 2022 - Visual Expert 2022 - Support for cloud-based repositories and large volumes of code
- 2023 - Visual Expert 2023 - Performance tuning for PowerBuilder
- 2024 - Visual Expert 2024 - New web UI to simplify deployment and use among large teams.
- 2025 - Visual Expert 2025 - AI-based features to explain code, generate comments, and optimize queries
References
[edit | edit source]- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
- ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).