Increase Code Quality with Architectural Review
Code degrades over time. Employees with differing skill levels, coding styles, and familiarity with the architecture will end up lowering the stability of a project. Maintain quality code and prevent architectural degredation with Architexa's integration into Subclipse and CVS.
Architexa integrates directly into Eclipse's History and Synchronize views and Eclipse's Team context menu. We support diagram creation for both SVN and CVS repositories. Our diagrams will allow you to simultaneously view changes across multiple files and even projects, realize their impacts or inconsistencies, and quickly document changes to critical components or architecture.
Review code before committing it
Under pressure to commit a critical component? Need to quickly check for bugs and inconsistencies before committing it or submitting it for review? Use Architexa to create a diagram of any outgoing changes straight from the synchronize view or the Team context menu. Create a class, sequence, or layered diagram to inspect changes from any angle. Learn How
Review old change sets
Agile team leads know that even with a disciplined team, it takes a lot of pouring over code in order to prevent bugs from cropping up. Simplify the review process by using Architexa when viewing revisions in Eclipse's History view. You can select any number of revisions to view the affected files and the impact of their modifications on the architecture. Find problem code visually: New dependencies/cycles in a layered diagram, Incorrect inheritance in a class diagram, or faulty logic in a sequence diagram. Learn How
Explore diffs in a diagram
Looking through old commits to find the source of a problem is never a fun task. Diffs can be helpful but it can take a lot of time to figure out where the problem lies. To speed up this process and make code maitence more intuitive, Architexa opens the text of the diff side by side with a visual representation. Learn How
Documentation review
In addition to making sure the quality of your project's code doesn't degrade over time, it is important to maintain the quality of your documentation. Reviewing the architecture as well as the code itself will ensure a better documented codebase. Developers are often biased to think that their own code is perfectly documented. Another set of eyes can make sure confusing code is documented before it is committed. Finding code that has similar functionality may be difficult without quality architectural documentation. Projects with limited or outdated architectural documentation are more susceptible to code erosion since developers may not be clear on what boundaries they are constrained by.
Document changes and new components
Has keeping documentation up-to-date become a tedious and time consuming hassle for your team? Using Architexa's team integration features will allow you to create up to date diagrams of critical code components as they are committed. With Architexa you can view, download, and explore existing diagrams and documentation. You can then update these diagrams with new code components. By integrating with Eclipse's History and Synchronize views this process becomes a streamlined step in the code review and committing phase of development. Learn How
