Fortran Programming Language :: Software structure analysis


	Software structure analysis Hi, I don't know if this is the right ng for this question, but here goes : I am to take over the dev and maintenance of a fortran 77 code that's been developping by at least a dozen people over about 30 years. The code is a mess and I need to see how it works. Doing it by hand is going to be ... interesting. So, I have been looking on the W but no luck so far. What I need is a way to know how each program (about 30) and each subroutine is connected to what. This would give me the info flow structure. Note this is NOT a flowchart, which shows how the logic goes. And free is always better... Thanks for any help. G Have you looked at the Fortran: Tools: Code Analysis section of the Open Directory http://dmoz.org/Computers/Programming/Languages/Fortran/Tools/Code_An... and also the parent category? On 22 mei, 14:19, "G.T." <m@b.com> wrote: - Hide quoted text - > Hi, > I don't know if this is the right ng for this question, but here goes : > I am to take over the dev and maintenance of a fortran 77 code that's been > developping by at least a dozen people over about 30 years. > The code is a mess and I need to see how it works. > Doing it by hand is going to be ... interesting. > So, I have been looking on the W but no luck so far. > What I need is a way to know how each program (about 30) and each > subroutine is connected to what. This would give me the info flow > structure. Note this is NOT a flowchart, which shows how the logic > goes. > And free is always better... > Thanks for any help. > G There was another thread not too long ago about something similar. I do not know the various tools that were offered, but I suggest you look it up ... should not be too hard (no more than three weeks ago) Regards, Arjen On 22 mei, 14:19, "G.T." <m@b.com> wrote: - Hide quoted text - > Hi, > I don't know if this is the right ng for this question, but here goes : > I am to take over the dev and maintenance of a fortran 77 code that's been > developping by at least a dozen people over about 30 years. > The code is a mess and I need to see how it works. > Doing it by hand is going to be ... interesting. > So, I have been looking on the W but no luck so far. > What I need is a way to know how each program (about 30) and each > subroutine is connected to what. This would give me the info flow > structure. Note this is NOT a flowchart, which shows how the logic > goes. > And free is always better... > Thanks for any help. > G There was another thread not too long ago about something similar. I do not know the various tools that were offered, but I suggest you look it up ... should not be too hard (no more than three weeks ago) Regards, Arjen On May 22, 12:02 pm, Arjen Markus <arjen.mar@wldelft.nl> wrote: - Hide quoted text - > On 22 mei, 14:19, "G.T." <m@b.com> wrote: > > Hi, > > I don't know if this is the right ng for this question, but here goes : > > I am to take over the dev and maintenance of a fortran 77 code that's been > > developping by at least a dozen people over about 30 years. > > The code is a mess and I need to see how it works. > > Doing it by hand is going to be ... interesting. > > So, I have been looking on the W but no luck so far. > > What I need is a way to know how each program (about 30) and each > > subroutine is connected to what. This would give me the info flow > > structure. Note this is NOT a flowchart, which shows how the logic > > goes. > > And free is always better... > > Thanks for any help. > > G > There was another thread not too long ago about something > similar. I do not know the various tools that were offered, > but I suggest you look it up ... should not be too hard > (no more than three weeks ago) Maybe you are referring to the thread "Looking for some Fortran analysis tools" http://groups.google.com/group/comp.lang.fortran/browse_frm/thread/ba... . On 23 mei, 15:08, Beliavsky <beliav@aol.com> wrote: - Hide quoted text - > On May 22, 12:02 pm, Arjen Markus <arjen.mar@wldelft.nl> wrote: > > On 22 mei, 14:19, "G.T." <m@b.com> wrote: > > > Hi, > > > I don't know if this is the right ng for this question, but here goes : > > > I am to take over the dev and maintenance of a fortran 77 code that's been > > > developping by at least a dozen people over about 30 years. > > > The code is a mess and I need to see how it works. > > > Doing it by hand is going to be ... interesting. > > > So, I have been looking on the W but no luck so far. > > > What I need is a way to know how each program (about 30) and each > > > subroutine is connected to what. This would give me the info flow > > > structure. Note this is NOT a flowchart, which shows how the logic > > > goes. > > > And free is always better... > > > Thanks for any help. > > > G > > There was another thread not too long ago about something > > similar. I do not know the various tools that were offered, > > but I suggest you look it up ... should not be too hard > > (no more than three weeks ago) > Maybe you are referring to the thread "Looking for some Fortran > analysis tools"http://groups.google.com/group/comp.lang.fortran/browse_frm/thread/ba... > .- Tekst uit oorspronkelijk bericht niet weergeven - > - Tekst uit oorspronkelijk bericht weergeven - Ah, that is the one! Regards, Arjen Arjen I wrote a small program to use on 200 F77 source programs of ours. First I copied ALL the programs to one single file "ALL" using copy .for ALL <ret> The the program I mentioned read file "ALL: and noted each use of "PROGRAM" and wrote it to a file then every CALL something(parameters) and wrote that something name. Then every internal SUBROUTINE() and FUNCTION() met was also written out. Then the progam reads the listing file and notes as a report all the references to subroutines and funtions by program name. Of course this misses some inherent functions but they should all be fortran ones; but to be on the same side I could also include the names present in our library of called ASM modules by using LIB and listing the names. - Hide quoted text - Terence wrote: > Arjen > I wrote a small program to use on 200 F77 source programs of ours. > First I copied ALL the programs to one single file "ALL" using > copy .for ALL <ret> > The the program I mentioned read file "ALL: and noted each use of > "PROGRAM" and wrote it to a file then every CALL something(parameters) > and wrote that something name. > Then every internal SUBROUTINE() and FUNCTION() met was also written > out. > Then the progam reads the listing file and notes as a report all the > references to subroutines and funtions by program name. > Of course this misses some inherent functions but they should all be > fortran ones; but to be on the same side I could also include the > names present in our library of called ASM modules by using LIB and > listing the names. This brings to mind a similar approach that might actually be available more directly, but only if you are working on a system with a well-featured library function. Thus at least one system library has the feature of being able to provide one or other of two cross tabulations showing, for each object in the library, what other objects it calls or is called by. This would mean that you could start by putting your entire program into a library, and so on.