From: Trans Date: 2007-11-15T21:10:31+09:00 Subject: design timelines hi-- i'm doing a work on a large system and while i have no problems getting intot he bit and pieces of code, i'm finding it much more difficult to put together the "larger picture". i was hoping that it would sort of form organizically as I worked on variouis nuts and bolts, but even if plausible, i releaize that it's goinn to take too much time. so i'm thinking that i am going to have to just sit down for a spell and follow the systems execution thru, line by line. in doing so , it's seems a waste to be the only one who benefits from my drudger --it should be a good opportunity to do some documentation. but i wonder if i could go a step further, is there any precedence for creating "timeline" specifications? t.