Network design is as much of an art as it is a science. One of the necessary skills as a network designer includes creating diagrams, specifically, logical, physical, and wireless diagrams. For this exercise, each individual student is to develop their organization’s logical diagram (described in the case for the Network Proposal) using Microsoft Visio and develop appropriate narrative.
So, what constitutes a good quality logical diagram? Well, there are several characteristics:
- All diagrams, figures, tables and so on should have appropriate narrative describing in plain English what the diagram is trying to communicate
- Start the diagram itself with the cloud in the top-left (we read left to right, top to bottom)
- Appropriate use of color (designate secured and unsecured networks; VLANs, etc.)
- Consistent use of icons (colors, sizes, etc.)
- Recommended configuration information (IP addresses, gateways, DNS server, etc.)
- Logical flow of icons with limited overlapping lines (grouping appropriately, aligning, etc.)
- etc.
As an introduction, you need to identify the current situation and the issues with the existing system that need to be addressed as well as the steps necessary to provide a solution for the issue. Now, you can begin to develop the narrative for the logical design. Why did you make some of the design choices that you made? Why are you subnetting using multiple routers? Why are you segmenting using VLANs? What is the logical topology of your network and what does that mean to a business leader/decision maker? Describe in plain English/business terms how your recommended design addresses the business needs stated in the case. Do not explain what can be seen in the diagram. The diagram can be observed and a lot of useful information comes from it. But, the diagram does not tell the reader why design choices were made. That is your job as the professional and the narrative is how you convey that information. Once complete, insert your narrative before the diagram. Tables and figures such as your diagram should never be introduced first. Rather, they should be referenced (i.e. as in “…see Figure 1: Logical Diagram) in the narrative and then introduced after the first paragraph in which they are mentioned or at the top of the next page.
NOTE: This is the first part of an assignment that continues to build. In other words, for the next assignment, you do not need to create a new document. Rather, you simply need to post the same document that have continued to build. So, treat this as a formal proposal. Include a cover page, headings, etc.
For more helpful hints, review the following websites:
http://schuesslerphd.blogspot.com/2015/06/logical-…
https://docs.google.com/document/d/1R2jFrQHTRAR-kY… (Chapter Two)
http://schuesslerphd.blogspot.com/2015/04/valuatio…
http://schuesslerphd.blogspot.com/2015/06/logical-…
******This assignment is part of a semester project so more work will be needed to as the semester continues.******
I also attached the case study for the overall project but right now, just the Logical Design is needed.
| Criteria | Ratings | Pts | |||
|---|---|---|---|---|---|
|
This criterion is linked to a Learning OutcomeSO1: Students will design a logical network design to meet business objectives.threshold: 1.4 pts |
|
2.0 pts |
|||
|
This criterion is linked to a Learning OutcomeNarrativeShould be used to communicate concepts that are difficult/impossible to capture in the diagram itself. Used to explain design decisions including but not limited to segmentation, IP addressing scheme, VLAN scheme, etc. |
|
2.0 pts |
|||
|
This criterion is linked to a Learning OutcomeFlowThe cloud should be in the upper left corner of the diagram and the diagram should generally flow from the top left to the bottom right. |
|
2.0 pts |
|||
|
This criterion is linked to a Learning OutcomeColorThe diagram should make use of color to indicate logical segments of the network (different VLANs and/or different subnets). |
|
2.0 pts |
|||
|
This criterion is linked to a Learning OutcomeIconsConsistent and appropriate use of icons are used. |
|
2.0 pts |
|||
|
This criterion is linked to a Learning OutcomeConfiguration InformationAppropriate configuration information is included in the diagram. |
|
2.0 pts |
|||
|
This criterion is linked to a Learning OutcomeInitial SubmissionSubmission of Semester Project draft was made on or before the Sunday before the discussion was due. |
|
1.0 pts |
|||
|
This criterion is linked to a Learning OutcomeEarly Meaningful PostStudent made at least one meaningful post on or before Wednesday of the Peer Review week in which the DB post was due. |
|
1.0 pts |
|||
|
This criterion is linked to a Learning OutcomeLate Meaningful PostStudent created at least one meaningful post on or after Thursday of the Peer Review week in which the DB post was due. |
|
1.0 pts |
|||
|
This criterion is linked to a Learning OutcomeReflective PostStudent created meaningful reflective post on Sunday of the Peer Review week in which the DB post was due. |
|
3.0 pts |
|||
|
This criterion is linked to a Learning OutcomeInitial submission was a hyperlink to student’s Semester ProjectThis should be the same link for each DB post, with each DB including additional information added. You should NOT create a new document. Rather, continue to build on the old document, making corrections and updates as we progress throughout the semester. |
|
