Source Code Analysis Reverse engineering and visualization of source code lead to improved program comprehension. Speeds: Learning Unfamiliar Code Change Impact Analysis Integration of Open Source Code Code Reuse Software Maintenance Static Analysis & Metrics Quality checks identify problems in variable usage, task interaction and concurrency. And software metrics help assess code quality. Improves: Verification of Real-Time Behavior Code Review Preparations Assessment of 3rd Party Code Tracking Development Progress
The best starting point for learning about Imagix 4D and its capabilities is to take its built-in tour. The tour demonstrates the tool's features, and shows you how to use them to solve typical development problems. You're introduced to the display windows, and are able to experime with them while being guided through their use. The tour is also a useful reference resource, enabling you to review particular aspects of Imagix 4D's user interface once you've started using the tool. Complementing the tour, the User Guide provides detailed information about managing projects and data collection, a description of the tool's underlying data model, and an overview of the display windows demonstrated in the tutorial. A Getting Started section walks you, step by step, through the process of loading your code into the tool. The User Guide is included electronically through the user interface and also as a .pdf document. In addition, Imagix 4D's Help System includes both Tool Tips (Balloon Help) and a much more detailed Context Sensitive Help. You may soon determine that the full Tool Tips is unnecessary, and limit tool tip displays to just icons and possibly control widgets. But you'll find that the Context Sensitive Help, which is available through the F1 key for all windows, remains very useful even as you become more experienced with Imagix 4D. Software Document Generation Working in software development, software maintenance or quality assurance, one of your least desirable and least rewarding tasks is creating documentation. Whether it's for code you're creating, a change you're contemplating, or a problem that you're trying to resolve, the actual task of documentation is often dull and unimaginative. And under tight schedules, there seem to be better uses of your time. Yet detailed, accurate, up-to-date documentation is of enormous value. It helps insure that changes made to the source code don't create unforeseen problems. It speeds and focuses peer code review efforts. It lowers the likelihood of misunderstandings among developers and quality assurance teams. It alleviates the need to spend time hand-holding new engineers as they get up to speed.