Axivion Bauhaus Suite Technical Factsheet Inhalt 1 Integrated Solution for Stopping Software Erosion... 2 1.1 Build Process Integration... 2 1.2 Continuous Integration... 2 1.3 Web-Dashboard... 2 1.4 Clone Management System... 2 1.5 Data Format... 2 2 Automated Analyses... 3 2.1 Architecture Checking C,C++,C#,Java,Ada... 3 2.2 Clone Detection C,C++,C#,Java,Ada... 3 2.3 Style Checks C,C++... 3 2.4 Metrics C,C++,C#,Java,Ada... 3 2.5 Cycle Detection C,C++,C#,Java,Ada... 3 2.6 Dead Code Detection C,C++,C#,Java,Ada... 3 3 Adaptations and Enhancements... 4 4 Supported Programming Languages... 4 4.1 C/C++... 4 4.2 C#/.NET... 4 4.3 Java... 4 4.4 Ada 83/Ada 95... 4 5 System Requirements... 5 5.1 GNU/Linux... 5 5.2 Microsoft Windows... 5
Axivion Bauhaus Suite Technical Factsheet 1 Integrated Solution for Stopping Software Erosion 1.1 Build Process Integration Axivion Bauhaus Suite integrates into your existing processes and environments and automatically runs in the background. Developers can thus quickly take measures against the causes of erosion before the erosion takes hold. The language front-ends run as compilers or simply analyze the byte code. This makes it easy to integrate Axivion Bauhaus Suite into existing build environments and run automated analyses during nightly builds. Project files of various IDEs such as Microsoft Visual Studio Solution and Project Files and IAR Systems Workspace Project Files as well as other make processes using make files are supported. No external database is needed. 1.2 Continuous Integration Only a continuous monitoring of triggers for software erosion guarantees an effective and efficient protection. The continuous build system integration facility of the Axivion Bauhaus Suite enables the integration with existing version control systems to automatically check out, analyze and report new triggers of software erosion without always overloading developers with the complete list of violations (delta analysis). Any version control system with a command line interface can be integrated. For example: CVS Subversion MKS Source Integrity PTC Integrity Microsoft Team Foundation Server Microsoft Visual SourceSafe IBM Rational ClearCase Perforce Git Serena PVCS Serena Dimensions Fossil 1.3 Web-Dashboard The results are presented by an easy-to-use web dashboard that interfaces a webserver. Supported browsers are: Microsoft Internet Explorer (9.0 or higher) Firefox Opera Safari Google Chrome The database backend is SQLite. 1.4 Clone Management System The dashboard includes a clone management system that allows an overview on copy and paste duplicates in the source. You get a cross reference for cloned source code. This enables a consistent evolution of the software. 1.5 Data Format The data of the fact base, on the structural as well as on the syntactical level, is interchangeable between Microsoft Windows operating systems and GNU/Linux platforms in binary form. Specifications for the analyses, for example the specified architecture, can be saved as views in binary or XML format. These views can also be checked in to version control or configuration management systems. 2 of 5 Axivion GmbH 2014
Axivion Bauhaus Suite - Technical Factsheet 2 Automated Analyses 2.1 Architecture Checking C,C++,C#,Java,Ada Compares the "as is" architecture of the source code with the specified architecture: Detection of violations against the specified architecture Display of the violations in the dashboard as well as with the architecture browser Continuous monitoring of the level of compliance between specified and implemented architecture Allows for graphical or textual specifications to specify the desired architecture Hierarchical or flat specifications of any architectural structure are possible Mapping of elements in the source to elements in the specified architecture is entirely unrestricted and possible for any level of detail Portability of the specified architecture across different versions of the source Via a scripting interface and/or XML import, architecture specifications can be imported from other tools such as UML -based case tools (e.g. Enterprise Architect, IBM Rhapsody, Visual Paradigm for UML, etc.) or modeling tools (e.g. Microsoft Visio ). Whenever there is no specified architecture available, the architecture can be recovered incrementally. In addition to the information in the source code, information about other dependencies can be added via scripting or XML import. For example, dependencies by inter-process communication or information about data base accesses. 2.2 Clone Detection C,C++,C#,Java,Ada Detects duplicates within the source, often produced by copy and paste. Thereby, clones can be detected at the lexical and the syntactical level. Detection of all relevant clone categories: Type I clones: exact duplicates Type II clones: duplicates with renaming of identifiers and/or data types Type III clones: duplicates with insertions and omissions Various adaptations of parameters are possible (minimum length, similarity, weight of the syntax tree, ) Syntactic and lexical clone detection for C and C++ Lexical clone detection for C#, Java, Ada, Visual Basic, and Cobol Results can be imported into the architecture browser 2.3 Style Checks C,C++ The provided set of over 300 rules is geared to MISRA-C:2004. In addition to this, individual style checks can be implemented via the Python scripting interface. In doing so, the enriched AST can be queried. Scripts can either be implemented oneself or commissioned at Axivion. 2.4 Metrics C,C++,C#,Java,Ada In addition to standard metrics that are provided with Axivion Bauhaus Suite, individual metrics (based on structural and syntactical information) can be defined and collected via scripting. The results can be displayed in the dashboard and interactively be explored in the architecture browser which is especially interesting to look for correlations. It is furthermore possible to monitor trends of certain metrics over time. 2.5 Cycle Detection C,C++,C#,Java,Ada Detects cyclic dependencies between elements in the source code: Calculates cyclic dependencies Cycles in the call graph Cycles in the use relationships Cycles in the type dependencies Cycles in build dependencies, subdirectories and components 2.6 Dead Code Detection C,C++,C#,Java,Ada The detection of dead code is based on the graph accessibility. For C#/.NET and Java the byte code must not be optimized. Otherwise, dead code that is already removed by the compiler cannot be detected. Axivion GmbH 2014 3 of 5
Axivion Bauhaus Suite Technical Factsheet 3 Adaptations and Enhancements The fact base of Axivion Bauhaus Suite can be queried and manipulated via Python scripts. Among the various possibilities, one can: generate reports (batch processing is possible) integrate analysis results into the architecture browser query the Axivion Bauhaus Suite fact base (interactive use as well as batch processing is possible) implement individual analyses import external data implement Individual style checks on the syntactical level (C,C++) implement Individual metrics on the syntactical level (C,C++) implement Individual metrics on the structural level (C,C++,C#,Ada,Java) Scripts can either be implemented by oneself or commissioned at Axivion. 4 Supported Programming Languages 4.1 C/C++ The C/C++ front-end covers the following versions of C and C++: K&R C ANSI/ISO C/C++ ANSI X3.159-1989, ANSI C, C89 ISO/IEC 9899:1990, C90 ISO/IEC 9899:1999, C99 ISO/IEC 14882:1998, C++98 ISO/IEC 14882:2003, C++03 ISO/IEC 14882:2011, C++11 Profiles for additional dialects are included. For example many versions and variants of the following compiler families: Microsoft Visual Studio C++ Compiler (up to Microsoft Visual Studio 2013) GNU GCC and compilers based on GNU GCC Sun C++ compiler IAR C/C++ compiler TI Code Composer Studio C/C++ compilers Green Hills C/C++ compilers ARM Keil C/C++ compilers Renesas C/C++ Compiler Packages Tasking C/C++ compilers Wind River Diab Compiler Further dialects can be easily configured, please contact us for details. 4.2 C#/.NET The analyses make use of CIL byte code (ISO/IEC 23271:2006). Source code is needed for metrics calculation, clone detection and in order to get source positions. 4.3 Java The analyses make use of Java 1.4 und 1.5 byte code. Source code is needed for certain metrics and clone detection. 4.4 Ada 83/Ada 95 As tool partners of AdaCore, our front-end is based on the ASIS interface of the corresponding GNAT Pro compiler. 4 of 5 Axivion GmbH 2014
Axivion Bauhaus Suite - Technical Factsheet 5 System Requirements 5.1 GNU/Linux Axivion Bauhaus Suite runs on x86 and x86_64 GNU/Linux operating systems with glibc2.3 or later. For example: Red Hat Enterprise Linux 3, 4, and 5 or later SUSE LINUX Enterprise Server 9 and 10 or later Fedora Core 4, Core 5 or later Debian 3.1, 4.0 or later For the analyses of projects with more than 500 KLOC, we suggest the following: Processor: 3 GHz Intel Core or Intel Xeon Memory: 4 GB RAM Hard Drive: 300 MB for Axivion Bauhaus Suite, plus space for analyses results. 5.2 Microsoft Windows Axivion Bauhaus Suite runs on x86 and x86_64 Windows operating systems: Windows Server 2003 Windows Server 2008 Windows 7 Windows 8 Windows Server 2012 For the analyses of projects with more than 500 KLOC, we suggest the following: Processor: 3 GHz Intel Core or Intel Xeon Memory: 4 GB RAM Hard Drive: 300 MB for Axivion Bauhaus Suite, plus space for analyses results. Wind River and Diab are trademarks or registered trademarks of Wind River Systems, Inc. Renesas is a registered trademark of Renesas Electronics Corporation. Tasking is a registered trademark of Altium B.V. ARM and Keil are trademarks or registered trademarks of ARM Limited (or its subsidiaries) in the EU and/or elsewhere. All rights reserved. Green Hills is a trademark of Green Hills Software, Inc. Code Composer Studio is a trademark of Texas Instruments. Intel, Intel Core, and Intel Xeon are trademarks or registered trademarks of Intel Corporation in the U.S. and/or other countries. IBM, Rational, ClearCase, and Rhapsody are trademarks or registered trademarks of IBM Corporation. Microsoft, Windows, Windows Vista, Windows Server, Visio, Team Foundation Server, Visual SourceSafe, Internet Explorer, and Visual Studio are registered trademark of Microsoft Corporation in the United States and other countries. Firefox is a registered trademark of the Mozilla Foundation. UML is a registered trademark of Object Management Group, Inc. Visual Paradigm for UML is a registered trademark of Visual Paradigm. Sun and Java are registered trademarks of Oracle Corporation. Opera is a trademark of Opera Software ASA. Safari is a trademark of Apple Inc., registered in the U.S. and other countries. Google Chrome is a registered trademark of Google Inc. SUSE is a registered trademark of SUSE LLC in the United States and other countries. Red Hat, Red Hat Enterprise Linux, and Fedora are registered trademarks of Red Hat, Inc. Debian is a registered trademark of Software in the Public Interest, Inc. IAR Systems, IAR Embedded Workbench, and IAR C/C++ Compiler are trademarks or registered trademarks of IAR Systems AB. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. MISRA and MISRA C are registered trademarks of MIRA Ltd. Python is a registered trademark of the Python Software Foundation. MKS, MKS Source Integrity, and PTC Integrity are trademarks or registered trademarks of PTC, Inc. Perforce is a trademark of Perforce Software. Serena, PVCS, and Dimensions are registered trademarks of SERENA Software, Inc. SQLite is a registered trademark of Hipp, Wyrick & Company, Inc. All other marks are the property of their respective owners. Axivion GmbH 2014 5 of 5