I hate to be stickler on this, but we should come to a consensus on the format. IEEE-830-1998 and IEEE-1016-1998 are industry standards. They are essentially lingua franca for nearly every developer that I've come across. From experience, I strongly feel that basic use of the concepts from 830, such as User Characteristics, Scope, Product Perspective, and Specific Requirements would be extremely beneficial for this project. I can't tell you how many times I've discovered overlooked aspects to something I was building by following those guidelines.
John Dean Michael Berris wrote: > Hi Guys, > > I've made a few changes to the SoftwareSpecifications page and > following John's structure for the page. I keep forgetting that you > can have more than one page on a Wiki to put information in. ;) > > Anyway, I also made a new page where the MessageRequirements are put. > However, note that this doesn't follow the same format that the > HTTPAPIRequirements page proposes. I have yet to flesh out the other > requirements pages, and I think these pages ought to be filled out by > "users" of the library (or at least representative users). For one, I > think I need to move the contents of MessageRequirements to > MessageDesignSpecifications looking at the content of that page... > > What do you think guys? Comments would be most appreciated. :) > > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Cpp-netlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
