Hi Jay, I will be writing about the technical details within the implementation stage of my report, but I wanted to write about the architecture in the design part of the report.
Thanks for your advice. John On 07/08/06, Jay Sprenkle <[EMAIL PROTECTED]> wrote:
On 8/7/06, John Newby <[EMAIL PROTECTED]> wrote: > Hi, this is probably a stupid question and it has nothing to do with SQlite > per se so I apologise in advance for hijacking the emails withmy question > plus I don't even know if this is the right place to ask the question. > > I have created a GUI to SQLite using VB.Net for my University project and it > interfaces with the SQLite .dll file. > > I have to now write about the architecture of my product but I am unsure as > what it would be, after reading this website I am even more confused :- > > http://www.javaworld.com/javaworld/jw-01-2000/jw-01-ssj-tiers.html Why is this particular guys method of dividing things up of particular interest? You can arbitrarily diving things up any way you like. IMHO if the paper is about the technical details of the implementation I would break it up into functional groupings of interest to the reader of the paper. Major functionality and/or which part comes from which library and what you wrote yourself to glue it together. As per usual, when people ask "What's the best xxxx?" I have to ask "For what?" If you're trying to plow snow a Porsche isn't useful. If you're trying to win a race a snow plow won't work too well.
