What are some of the common architectural design patterns that are enforced/recommended by the tool?
Ben – Coverity Architecture Analyzer deals primarily with the dependencies of a software system. While not considered a design pattern, per se, it suggests an architecture that is layered (either strictly or not) and discourages cyclical dependencies (A depends on B depends on C depends on A). However, when thinking about automated analysis for design patterns as described in the literature, the key is to start with first a representation of the software system (the Software DNA Map) and then a picture of all the dependencies of the software system (as provided by Architecture Analyzer). From there, we feel it makes perfect sense to extend our work in the automated architecture analysis space to include some higher level design pattern analysis to help organizations understand precisely which design patterns they are using and how well they are using them. DZone – How do you see the ‘Agile Tools’ space evolving in the next 6 to 12 months and what are some of the new features/tools we c
Related Questions
- Does anyone know of any detailed architectural design patterns for organizing a web application with multiple servlets (and optionally, JSPs)?
- What are some of the common architectural design patterns that are enforced/recommended by the tool?
- Is the deShedding tool recommended for all shedding breeds of dogs and cats?
