Question

Closed. This question is opinion-based. It is not currently accepting answers.

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 5 years ago.

Improve this question

As the years go by we get more and more applications. Figuring out if one application is using a feature from another application can be hard. If we change something in application A, will something in application B break?

We have been using MediaWiki for documentation, but it s hard to keep the data up-to-date.

I think what we need is some kind of visual map of everything. And the possibility to create some sort of reference integrity? Any ideas?

Answer 1

I m in the same boat and still trying to sell my peers on Enterprise Architect, a CASE tool. It s a round trip tool - code to diagrams to code is possible. It s a UML centric too - although it also supports other methods of notation that I m unfamiliar with...

Here are some things to consider when selecting a tool for documenting designs (be they inter-system communication, or just designing the internals of a single app):

Usability of the tool. That is, how easy is it to not only create, but also maintain the data you re interested in.
Familiarity with the notation.

A. The notation, such as UML, must be one your staff understands. If you try using a UML tool with a few people understanding how to use it properly you will get a big ball of confusion as some people document things incorrectly, and someone who understands what the UML says to implement either spots the error, or goes ahead and implements the erroneously documented item. Conversely more sophisticated notations used by the adept will confound the uninitiated.

B. Documentation isn t/shouldn t be created only for the documenters exclusive use. So those who will be reading the documentation must understand what they re reading. So getting a tool with flexible output options is always a good choice.
Cost. There are far more advanced tools than Enterprise Architect. My reasoning for using this one tool is that due to lack of UML familiarity and high pressure schedules, leaves little room to educate myself or my peers beyond using basic structure diagrams. This tool easily facilitates such a use and is more stable than say StarUML. (I tried both, StarUML died on the reverse engineering of masses of code -- millions of lines) For small projects I found StarUML adequate for home use, up until I got vista installed. Being opensource, it s also free.

With all that said, you will always have to document what uses what, that means maintaining the documentation! That task is one few companies see the value in despite its obvious value to those who get to do it. . .

友情链接