Jump to content

Wikipedia:Articles for deletion/Virtual Forge CodeProfiler

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Psychonaut (talk | contribs) at 12:53, 7 June 2013 (Creating deletion discussion page for Virtual Forge CodeProfiler. (TW)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
Virtual Forge CodeProfiler (edit | talk | history | protect | delete | links | watch | logs | views) – (View log · Stats)
(Find sources: Google (books · news · scholar · free images · WP refs· FENS · JSTOR · TWL)

The software hasn't become notable since this article was last deleted in 2008. There are currently 5 references, of which the first and fifth are primary sources, the fourth is a blog post and therefore not reliable. The remaining two are passing mentions in two books, and therefore don't amount to significant coverage. (The entirety of what Chuprunov's second, 557-page book has to say about CodeProfiler is the following: "In order to detect inconsistencies and differences to the target state in advance, tools for static code analysis, such as Virtual Forge CodeProfiler, can be integrated into the SAP Transport Management System (TMS) of SAP… This tool can also scan all ABAP code in the live system for a large variety of security and compliance violations…". The first book says even less: "In order to detect inconsistencies and differences to the target state in advance, tools for static code analysis, such as Virtual Forge CodeProfiler, can be integrated into the SAP correction and transport process." (my translation from the original German)) Contrary to the article's claims, neither book specifically "recommends" CodeProfiler; it's only given as an example of a static code analysis tool which can be used. Psychonaut (talk) 12:53, 7 June 2013 (UTC)[reply]