Wiki
Editing System Analyser

h3. Introduction Welcome to the System Analyser for Common Lisp home page. Here you can find different types of documentation and the source code of the applicaiton. I wrote the System Analyser to provide an automated means of detecting whether a system had developed unwanted characteristics within itself and also with it's coupling to other systems. These characteristics tend to become more prominent as the scale of the system increases and it's better to detect and address them before they get out of hand. The kind of characteristics you want to look for include: * unbalanced structure of the module relationships within a system * bloated dependencies between systems * circular dependencies (although modern system definition facilities should pick this up) * bloated modules/systems whose components have poor cohesion * insufficient decoupling of a module's interface and implementation For a more detailed introduction to System Analyser I recommend following the links below and reading the documentation, starting with "What Is It?". h3. Documentation * [[System Analyser - What Is It]] * [[System Analyser - Getting Started]] * [[System Analyser - Architectural Overview]] h3. Downloads |{background:#ddd}. *Version* |{background:#ddd}. *Source Code* |{background:#ddd}. *Release Notes* |{background:#ddd}. *API Reference* | | 0.2 | "package":../../distfiles/sys-analyser_0.2.tar.gz "public key":../../distfiles/sys-analyser_0.2.tar.gz.asc | n/a | "package":../../distfiles/sys-analyser-0.2-documentation.tar.gz "public key":../../distfiles/sys-analyser-0.2-documentation.tar.gz.asc | h3. License System Analyser is released under a BSD style license. See the LICENSE file in package for more details. h3. Roadmap At the moment I don't have an issue/defect tracking system setup. I still haven't decided on a suitable implementation. If anyone has some recommendations please let me know. Here is the current list of enhancements under consideration for upcoming releases: * todo: an abstraction for grouping analysis checks into a suite, similar to how unit tests are grouped into test suites * todo: a service for drawing the system definition into a visual graph using Graphviz * todo: write a developer's guide and/or tutorial * todo: support mk-defsystem system definitions Other more mundane house-cleaning tasks that need to be done for future releases: * todo: create a chained-condition under core/condition * todo: move item-not-found-error and already-exists-error to core/condition * todo: move the ASDF utililty functions in service/sys-graph to util/sysdef

as | Cancel (unlocks page)