Software Diagnostics Studio is a tool for project managers, team leaders, and software engineers who want to visually monitor and effectively steer software development processes. In a sense it serves as a “software tomograph”, bridging the communication gap between management and developers, improving maintenance performance for complex IT solutions and ensuring their sustainable evolution.
Software Diagnostics Studio is based on fast software visualization and precise data mining technology that directly extracts facts from software development environments such as source code repositories and configuration management systems (e.g., CVS, subversion, Perforce) and analyzes the source code base. It visualizes structure and components of the implemented architecture by means of “software maps”, which allow you to get insight into the actual structure of complex IT system implementations.
Software Diagnostics Studio also ensures that you are always informed about actual development activities: Watch where and when your developers create or modify the code base by projecting that information onto the software maps. You get a powerful “early warning system” that helps to effectively identify problematic development situations. With a single click you get answers on questions such as: - On which parts of the code is developer X working right now?
- Which developers currently modify a certain module?
- Which parts of the system remained unchanged in the last release?
The tool delivers the capabilities you need to effectively uncover quality problem, to review code metrics, to manage tests and test coverage, to review bug fixing measures, to improve performance, and to speed up software development to keep time and budget.
Without having to dig into code, essential questions in software development processes can be answered. Examples: - Why was most of the time spent on changing the “network” module during implementation of the “chart export” feature?
- Are there quality problems with the “network” module?
- Is the interface of the “network” module badly designed?
- Are there bugs in the “network” module? Which ones? What else do they affect?
- Why were there so many changes in the database layer the last 3 months?
- Has the data model been changed multiple times? Why?
- Why do changes in the application layer impact the database layer? Do we need a better interface protect the layers from change impacts?
|
3rd-party lib is exchanged in Google Chrome.
New features in Google Chrome’s media player implemented.
Refactoring in the Software Diagnostics code base.
28 days of development activity in the Software Diagnostics code base (400kLOC).
