Content deleted Content added
→Related Links: Reply |
|||
Line 39:
This section and the cited paper are not specific to static analysis so should either be moved to "program analysis" or removed.
[[Special:Contributions/218.212.205.1|218.212.205.1]] ([[User talk:218.212.205.1|talk]]) 05:33, 11 May 2015 (UTC)
:Agree, the whole section needs re-work. Sentences like "This document on "How to Deliver Resilient, Secure, Efficient, and Easily Changed IT Systems in Line with CISQ Recommendations" describes three levels of software analysis." are not ideal. If a document is used, it should be linked and and doesn't need explicit mentioning. CISQ comes from a Quality-type angle. The mentioned "levels" are very similar to a "V-model", but basically I have not seen a SCA-tool or method that works on the integration side of things. SCA at the core of things is on the module/unit level, checking the blank code if you want. A fraction of tools can do dependencies. I think this section needs re-working to put it into correct context. I might do it, but I would call this comment done if you don't mind. Yes agree, program analysis is the right home for this and program analysis article seems very poor under-developed too in terms of references. {{done}} --[[User:17387349L8764|17387349L8764]] ([[User talk:17387349L8764|talk]]) 08:29, 6 April 2021 (UTC)
== External links modified ==
| |||