Well, what I'm trying to figure out is why a "novice" is working on a project described for an IT Architect.
Possibly the only "novice" part of the project would be the internal network "This network should not be a flat network.", but conversely, that's almost a given for a network the size and physical topology as described.
Some of the requirements could be very involved, but specifics are undefined. For example "Secure/Protect the company Wireless Network." actually requires? Possibly, this just means authorized wireless connections but maybe even things like negating rogue APs. Further, there's a lot more that goes hand-in-hand with wireless having nothing, per se, dealing with security or protection but how well the wireless environment works and what standards it supports, etc.
So, for a real lead, you would need to first nail down all the actual requirements. Heck, we "know" the business operates in 4 states and there are two DCs, but how many locations, how many hosts at each location, kinds of hosts at the locations, bandwidth requirements, etc.
Remote users how many, kind of media available to them, etc.?
Again, though, just don't see how a "novice" can even begin to write up a paper on this, so rather difficult to direct you.
See, the situation is somewhat like saying "I'm a novice auto mechanic" but I have project to architect an automobile with the following requirements such as it must get 40 mpg, can do 0 to 60 in 6 seconds, can . . ., can . . ., and must not use non-radial tires.
I don't mean to sound harsh, but, to me, that's how your OP comes across (unintentionally, I'm sure), so for an automobile, how should we answer? Can you now see this as a possible reason for the lack of responses?
