Fill This Form To Receive Instant Help
Homework answers / question archive / CMIT 350 Assignment 1: Network Infrastructure Design Diagram Instructions Background: Kamehameha Institute is an organization that provides educational offerings to non-traditional students via the Institute's website in a three-tier web, application, and database configuration
CMIT 350 Assignment 1: Network Infrastructure Design Diagram
Instructions |
||||
Background: Kamehameha Institute is an organization that provides educational offerings to non-traditional students via the Institute's website in a three-tier web, application, and database configuration. The State of Hawai’i regulates the educational sector, driving the need to ensure Kamehameha follows the State’s strict security and regulatory requirements. Kamehameha's leadership is also very concerned with the threat posed by the online theft of their unique intellectual property. Additionally, the number of Hawai’ian entities breached by threat actors is on the rise. Thus, security, privacy, and compliance are all important considerations for the Kamehameha network architecture. Your boss, the Kamehameha Institute's Chief Operating Officer (COO) has tasked you to design a network infrastructure for three facilities located in the Hawaiian Islands of Honolulu, Hilo, and Lihue. The COO stipulated that you must provide for strengthened defenses to protect Kamehameha’s cultural heritage. After meeting with the COO, the two of you drafted the following set of requirements for your network design:
Submission: Using a network diagramming tool such as Microsoft Visio, or free tools such as LibreOffice Draw or Draw.io available at https://draw.io (no sign-in or registration required), create a network diagram (drawing) specific to the organization that encompasses the three facilities and also depicts any necessary interconnections. Figure 1 shows the draw.io ‘new network diagram’ dialog window: Figure 1. Draw.io New File Dialog Showing the Network Diagramming Templates Your diagram should include enough detail to show the topology interconnections. The viewer should be able to understand the Kamehameha Institute’s network environment and be able to implement the architecture you develop. Ensure that you properly cite any external sources. One of the keys to producing a viable network diagram is labeling the objects consistently and descriptively. Think about what you would want to know about a network device if you logged into it with little prior information. Consider location, floor number, or other pertinent information. At a minimum, include the following elements:
Example Network Diagram Callout Box.
When finished, export the diagram as a PDF document (Note: You will need to use this diagram again in Project 3, so ensure you save the xml source file!) and submit it to the Assignment folder. Figure 2 demonstrates how to export your draw.io diagram as a PDF document: Figure 2. Draw.io ‘Export’ as Function to PDF
When you are finished, upload your work to the dropbox below. Review the syllabus for information about late policies and resubmitted assignments. |
||||
This table lists criteria and criteria group name in the first column. The first row lists level names and includes scores if the rubric uses a numeric scoring method.Evaluation Criteria
Exceeds
Meets
Approaches
Does not Meet
Criterion Score
1.1.3: Present ideas in a clear, logical order appropriate to the task.
10 points
Presents a logical flow of ideas that is easily identifiable and completely appropriate to the task.
8.5 points
Presents ideas in a clear, logical order appropriate to the task.
7.5 points
Attempts to present ideas, but the logic is not clear and/or not appropriate to the task.
0 points
Does not present ideas in a clear, logical order appropriate to the task.
Score of 1.1.3: Present ideas in a clear, logical order appropriate to the task.,/ 10
2.2.2: Evaluate sources of information on a topic for relevance and credibility.
10 points
Evaluates sources of information thoroughly and appropriately on a topic for relevance and credibility.
8.5 points
Evaluates sources of information on a topic for relevance and credibility.
8.5 points
Attempts to evaluate sources of information on a topic for relevance and credibility, but there are gaps in the evaluation.
0 points
Does not evaluate sources of information on a topic for relevance and credibility.
Score of 2.2.2: Evaluate sources of information on a topic for relevance and credibility.,/ 10
10.1.1: Identify the problem to be solved.
16 points
Presents a relevant IT problem clearly and specifically.
13.6 points
Presents an IT problem that requires a solution.
12 points
Identifies an IT problem but may lack clarity and/or specificity regarding the need to be addressed.
0 points
Does not identify an IT problem to be solved.
Score of 10.1.1: Identify the problem to be solved.,/ 16
10.1.2: Gather project requirements to meet stakeholder needs.
16 points
Identifies IT project requirements in a thorough and clear manner to meet all stated stakeholder needs.
13.6 points
Identifies IT project requirements to meet stated stakeholder needs.
12 points
Attempts to identify project requirements to meet stakeholder needs, but there are gaps and/or lack of clarity.
0 points
Does not identify IT project requirements to meet stated stakeholder needs.
Score of 10.1.2: Gather project requirements to meet stakeholder needs.,/ 16
10.1.3: Define the specifications of required technologies.
16 points
Defines thoroughly and clearly the specifications of required technologies.
13.6 points
Defines the specifications of required technologies.
12 points
Attempts to define the specifications of required technologies, but there are gaps and/or lack of clarity.
0 points
Does not define the specifications of required technologies.
Score of 10.1.3: Define the specifications of required technologies.,/ 16
13.1.1: Create documentation appropriate to the stakeholder.
16 points
Creates thorough and accurate IT documentation that exceeds requirements.
13.6 points
Creates IT documentation that meets requirements.
12 points
Creates IT documentation that lacks detail and/or does not fully meet requirements.
0 points
Does not create appropriate IT documentation.
Score of 13.1.1: Create documentation appropriate to the stakeholder.,/ 16
13.2.1: Evaluate vendor recommendations in the context of organization requirements.
16 points
Evaluate and provides detailed justification for vendor recommendations in the context of organization requirements.
13.6 points
Evaluates vendor recommendations in the context of organization requirements.
12 points
Attempts to evaluate vendor recommendations in the context of organization requirements, but some recommendations lack detail or do not consider context.
0 points
Does not evaluate vendor recommendations in the context of organization requirements.
Score of 13.2.1: Evaluate vendor recommendations in the context of organization requirements.,/ 16
Rubric Total ScoreTotal
/ 100