Transcript of weekly SDAST meeting Friday November 6 1998

Those participating: Peter Kretschmar, Juhani Huovelin, Carol Anne Oxborrow

On the agenda: Plans for DDD and updating ADD

*** IRC session log started at Fri Nov  6 10:05:43 1998.
#jemxadr> Hello, out there in SDAST land!
#jemxadr> Sorry, I'm late, I forgot how to get onto jemxadr
H oxborrow     #jemxadr 0 Carol Anne Oxborrow          ~oxborrow@tenma.dsri.dk
H huovelin     #jemxadr 0 *real name unknown*   ~huovelin@us.astro.helsinki.fi
H Peter@       #jemxadr 0 KRETSCHMAR Peter         ~pkretsch@isdcul10.unige.ch
315 apollo.dsri.dk * End of /WHO list.      
#jemxadr> I'm the only one here at DSRI: Allan's in the States and NJW is AWOL until
+ 10.30 END
<huovelin:#jemxadr> I also keep forgetting (Alzheimer !!!)
<Peter:#jemxadr> What should I say, I need that mail too, and I think I am younger t
+han you ...
#jemxadr> I hope it's not that serious, Juhani!! Do you have children? That destroys
+ braincells quicker than you can replace them! END
<huovelin:#jemxadr> I just started printing out the new and shiny ADD  END
#jemxadr> Me too. The other printer clients hate me! END
#jemxadr> Shall we get down to business? END
<Peter:#jemxadr> Why not. You wanted to talk about the DDD
#jemxadr> First I want to say thanks to both of you for providing replacement files 
+after my machine went ahead and ate some last monday END
<Peter:#jemxadr> You're welcome
#jemxadr> Next, about the DDD. After much discussion with TIM LOCK we have decided t
+o go with his concept of DDD 
#jemxadr> Namely that the ADD acts as a guide to a host of smaller DDDs, presumably 
+one for each application. 
#jemxadr> A new ADD will be produced and updated with each delivery of software, and
+ with the release of that application's DDD. Any questions so far? END
<Peter:#jemxadr> With application meaning one of our larger building blocks? END
<Peter:#jemxadr> Like e.g. JDataBinning? END
#jemxadr> Yes the applications are JDataPrep, JDataBinning, JGainCalculation, JScien
+tificAnalysis etc. There are 11 in all END
<Peter:#jemxadr> OK. Sounds reasonable to me. 
<huovelin:#jemxadr> How do we avoid repeating things in these two documents ? END
#jemxadr> It makes sense to release each DDD and updated ADD with each software deli
+very, because we're all working to different schedules now END
#jemxadr> That's a good question Juhani. Basically, I keep track of everything. What
+ever's already covered in ADD is ADD stuff, and will just be updated according to a
+ny changes in the architecture. Everything else, which is more detailed, will belon
<Peter:#jemxadr> IMHO we can not avoid repetition completely for the sake of readabi
+lity. But the question is justified how we minimize it. END
#jemxadr> g in a specific DDD. END
#jemxadr> I foresee all the individual DDDs being integrated into one document, righ
+t at the end of the integration period. END
<Peter:#jemxadr> The line might still be sometimes difficult to draw, look e.g. at a
+ll the processing descriptions we already have. Are they ADD or DDD stuff? END
#jemxadr> ESA PSS-005-0 sets out quite clearly what is needed in DDDs, or at least w
+hich things belong there, so there shouldn't be too much overlap. END
<huovelin:#jemxadr> So, we agree on the general approach. I understood from what Tim
+ Lock ...
<huovelin:#jemxadr> expalined, that the combination of ADD and DDD is more important
+ in the sense ...
#jemxadr> What we have by way of processing pseudocode is clearly only at the AD lev
+el, while the kind of annotated real code you'll be expected to produce for the DDD
+ will be very different, not just a rough guide but a blow by blow account. END
<huovelin:#jemxadr> of being "complete" than each of the two separately END
#jemxadr> Yes, that's what I understand too. END
<huovelin:#jemxadr> We dont seem to have big problems in adjusting the documents, si
+nce ...
#jemxadr> I've already made a ddd.sty file which is quite complicated because I was 
+imagining quite a complex single document. END
<huovelin:#jemxadr> we can improve them little by little, in the process of writing 
+the ...
<huovelin:#jemxadr> actual code END
#jemxadr> That's exactly right. The DDD grows naturally out of the code developement
+. END
<Peter:#jemxadr> OK. I assume we will soon get a ddd.sty and template files from our
+ infatiguable Carol Anne, right?
#jemxadr> The separate DDD approach means that each group is responsible for produci
+ng their own DDD. END
#jemxadr> Yes, I have ddd.sty ready, and a sort of manual with examples, so it shoul
+d be easy to use.
#jemxadr> I will stress, however that it's quite detailed and other people may not w
+ant to use all my features, which is fine since you're 
#jemxadr> responsible for your own documents now. END
#jemxadr> I've tried to incorporate as much of CTS in the ddd.sty as possible. END
<Peter:#jemxadr> We will see - and we should strive to keep some consistency between
+ the different documents in style as well. Makes for better readability. END
#jemxadr> Okay, I'll send the style file out next week, and you can use which bits y
+ou like. Tim's suggestions sound quite modest in comparison with what I've produced
+, for example he said that a complete listing may be enough for a DDD. END
<Peter:#jemxadr> Sounds good to me. Any other issues for the Agenda?
#jemxadr> Do you think our plans conform to what Tim hopes for, Peter? END
<huovelin:#jemxadr> I dont have anything else END
<Peter:#jemxadr> To CAO: I hope so. Probably we will find out in time that he put le
+ss importance on something we did and wanted more emphasis on something we neglecte
+d but all in all I feel we're on agood track.
<Peter:#jemxadr> We are the only team with whom Tim can actually have this kind of
<Peter:#jemxadr> discussion already END
#jemxadr> Well, then I think we all ought to get on with the DD phase ! END
<huovelin:#jemxadr> About the usage of the DD sty : It might help , if Carol Anne wo
+uld make ...
<Peter:#jemxadr> Almost - I first have to finish the QLA ADD (due on Monday but don'
+t hold your breath)
#jemxadr> I'll write to Tim and explain our plans, so that he knows what we're doing
+. END
<huovelin:#jemxadr> a sort of "example" on it END
#jemxadr> There are already examples in the little manual. END
<huovelin:#jemxadr> OK , thats good ! END
<Peter:#jemxadr> Fine END
#jemxadr> `See' you all next week? END
<huovelin:#jemxadr> OK, have a nice weekend END
#jemxadr> You too, Juhani. Thanks for a productive chat! END
<huovelin:#jemxadr> By bye END
<huovelin:#jemxadr> I meant "Bye bye" END
*** Signoff: huovelin ()
#jemxadr> Thanks for your help Peter. I hope this helps with Tim to get it all strai
+ght now. END
<Peter:#jemxadr> I'm optimistic. Have a productive working day and a nice & restful 
+weekend! END
#jemxadr> Thanks, have a good weekend too! END
<Peter:#jemxadr> 'See' you next week
<Peter:#jemxadr> Bye
*** Error: Closing Link: oxborrow[~oxborrow@tenma.dsri.dk] () 
*** IRC session log ended at Fri Nov  6 10:36:34 1998.
