Can your engineers readily find the information they’re looking for? Where did that data come from? Is it in kilometers or miles? Above sea level or ground level?

Will they find the same answers if they looked in the functional specifications as in the interface specification or the algorithm appendix? Did they need to look in all three to get the answers? Did the data have the same name in all three documents?

The use of CASE tools can help substantially in not only making your system engineering data readily available but also, when used properly as a single source, assuring that the information is consistent throughout the system documentation.

CASE has been part of engineering best practices since 1980. Today’s CASE tools provide significant capabilities and numerous options “right out of the box”. Trying to use too many capabilities will likely cause significant maintenance issues and unnecessary changes to your current processes.

Teragon can help you focus on the capabilities you really need, develop standards for your project, create customized reports to enforce your business rules, assure the quality and integrity of the data, or simply provide an administrator to resolve modeling issues and facilitate data entry.

Already using a CASE tool?

• Do you frequently need custom reports generated?
• How many engineers have had to become “tool gurus”?
• Considering centralizing model updates to maintain configuration control?
• Working on more than one Engineering Change Proposal concurrently?
• Using a Requirements Management tool too?