Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

I've been given a mess of applications that all touch various common files and data sources. (Retail IT environment so lots of generic sources of data that gets sliced and diced into various ways and shoved into other locations after modification.)

To help myself and the next guy after me I'm going to start capturing all the inputs and outputs for each application as they need code changes. Foo.4gl logs to foo.log.DATE, spits out a report /var/tmp/foo.report, and reads from database table BAR.

The wall I've hit is I can't figure out what's the best machine readable format to store that info. I want to at least start mapping the interdependencies but so far the "best" I can figure for portability is a text file with inputs and outputs in with the source code. Low tech but that way it's right there for the developer to see when they touch the code.

Anyone have any better recomendations? Open source solutions for capturing the interdependencies? Standard notation for representing those webs?

Troux isn't feasible due to cost and admin needs. This is legacy spaghetti applications so I'm having to start from scratch without much but my own efforts to work with.

share|improve this question
    
The only way to go is a text file, then you have the entire unix toolset at your disposal, you'll be able to do anything, even things you haven't thought of at first. But you'll have to clarify what you mean by capturing interdependencies. What exactly will you be doing? –  orion Feb 4 at 8:05

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.