technical versus logical design

When I'm writing a schoolreport about something I made I often don't know what to put in logical and what to put in -technical design. In small projects I always end up putting the 2 together in 1 big chapter ( ;) ) I always get confused and don't know what goes where.

For example, where would you put these topics (in Logical ? or technical ?):

- An explanation of the design patterns I used and how I implemented them.
- An overview of my classes
- My Data model
- Comments and pictures of the GUI
- ...

Please don't bother me with a short foggy answer like "logical is the how and technical is the what" or stuff like that :) Hehe, I've heard that a 1000nd times and I still don't get it :D.

Thank you very very very much in advance.

BTW: It's quit important this time... because the last 2 months I have been working 45 hours/week on a big project and in about a month I'll need to hand over another report :cry:

I would think logical would have to do with the flow of the application. What it does, and how it works. While technical are things like its system requirements, issues pertaining to certain environments it may operate in (like if there are issues that need to be addressed with it working on windows 95 for example)

some may sort of cross over into both categories.. so you just need to feel out which one it leans to more, and put it in that one..

Quote:

---

Originally Posted by kleinma

... While technical are things like its system requirements, issues pertaining to certain environments it may operate in (like if there are issues that need to be addressed with it working on windows 95 for example)...

---

I think that is non-functional analysis, isn't it ?
*oi, a 3th category* :sick: