General information
Title:
Designing/Documenting Discussion question
Environment versions
Network:
Windows 2008 Server
I'd like to hear others opinions on the subject of documenting applications from a programmers standpoint.
I ask this because I have seen a company who wrote and sold a fairly successful application get sold and have the key programmer leave (get a big payoff why work). The problem has become (I haven't seen their code) that the programmers taking over have had a very difficult time understanding the application. Remember I don't know the details.
In my case, I have developed a rather large commercial application (200+ tables) and there are several UML models that have been made to diagram the code. I feel that this is the proper way to do things, but when I go and look at the universities' course offerings there is no UML language course. We're a small shop and the use of the UML Language seems to me that it should be taught in software design 101.
So, after rambling my questions are:
Should I continue to document with UML with the thought that there are actually lots of programmers out there using UML that could utilize the models when I decide to hire or contact with other programmers?
Is there a tool to reverse engineer a VFP project (uses MMortals) into UML models?
Thanks
Jon
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only