Frank,

Thanks for the links to some of the SOP documents on this. I managed to read through most of the flow charts and docs on the QA site and bumped around in BizDev project and looked at what was at the Marketing groups site also.  Actually I had done this months ago also, so last night was a quick review so probrably missed as much information as I got from them.

Following the admonition of the 'handling_RFEs.html' document I ram a report from IZ for all enhancements listed for the database access module. One can, with some effort, see much of what is being talked about there, there are some great ideas and many do relate to each other. In fact I think this is a good example of what I meant by using an issue tracking systems, alone,  being prone to losing sight of the forest for the trees, and great to see that the possible problem is already been thought about and a solution offered. I do have one small suggestion for the process described however. It is  not just RFEs that lead to requirements, defect reports can be indicators of missed requirements also. ( I suppose I should follow up on that thought at the QA list )

I suppose it is getting to be time to volunteer to help, then!

One question as I move along here - the User Experience tem? Is that an 'inside SUN' team or an OO.o team of people? (sorry if it was in the doc's above and I just missed it)If the later I might well be interested in helping, if the former...well my resume can be brought up to date rather quickly...*chuckling*...ok seriously .. just curious how one would interact with this team as they seem to be a major player when it comes to requirements. My first thought is that if one started to 'triage' these RFEs (and related Defect reports) looking to generate usable req. specifications just use the individual IZ entrys as a way to communicate. Is that it, or is there some mail list that this team uses separate from IssueTraker?

You are also correct in your comment that my focus is on Base specifically, and OO more broadly, as a development environment. Thinking of it as a large, high level, extensible widget set. But that is a discussion to be had over time, and hopefully with input from many more voices then just mine.

Thanks

Drew







 


Reply via email to