<QUOTE> > Me too. But requirements and architecture/design docs are needed first.
Not always. When moving into virgin territory often the right answer is to code something to test a concept, knowing that it is expected to be discarded and rewritten. </QUOTE> Agreed. But this is sooo not virgin territory anymore. <QUOTE> > There are a number of us who've been asking for proper architecture and/or > design documentation for the software for years. Well, it doesn't appear to have been designed. It appears to have evolved. The first cut has been developed and everyone has learned from it. I think we should put together a loose framework document, if for no other reason than discussion purpose. After all, we need something to have a flame-war over at least once! ;-) </QUOTE> Yes, agreed. If by "loose framework document" you mean "product requirements and architecture document", I think that'd be a great idea. And valuable for all concerned. <QUOTE> That is fine when the application is clearly and finely defined. I see the SDR system for Flex as being a bit more out in the wilderness which makes the development iterative. </QUOTE> I don't agree that we're STILL out in the wilderness. Not at all. Do we not understand the product requirements? I'd argue that we do (or we can, at least pretty well). Do we not understand the constraints of the environment and the solution space? I contend that we do. Do we not understand the tools available to help build a solution to meet the requirements? Again, I say we do. So, really, this is no longer wide-open, unformed, space that requires ground-breaking innovation. Gerald and company have already DONE that, from vision to implementation, and what they've done has been damn impressive. Groundbreaking. Paradigm shifting, in fact. What we need now is the NEXT evolution of the software. And ensuring that software is world-class will require solid engineering discipline. <QUOTE> I would propose a separate architecture mailing list. It is useful to brainstorm on how the features would fit into the architecture. If the interface is placed in the right spot in the stack, the interface will exhibit an elegant simplicity. </QUOTE> That'd be cool. Or, how about a multi-day, live and in-person, architecture review (sorta like an IETF meeting)? Peter K1PGV _______________________________________________ Flexedge mailing list [email protected] http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for posting topics related to SDR software development and experimentalist who are using alpha and beta versions of the software.
