Kamehameha Institute Case Study
Background:
| Kamehameha Institute is an organization that provides educational offerings to non-traditional students. The organization has tailored its unique educational offerings into the groups shown in Table 1 below: Table 1. Kamehameha Educational Offerings. Group Offering Kamehameha Branded Focused on the general public/provides services directly to its students Co-Branded Provides the same services as Kamehameha Branded but resold by a third party and labeled as “…. Kamehameha Strong” White Label Branded While the service offering is the same, these services are labeled solely with the third parties’ information 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 separate the three group offerings in Table 1 and 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: Each of the facilities has three floors:The first and second floor of each building requires 150 network connections each The third floor of each building houses a data center and requires 75 network connectionsThe Honolulu location requires additional network connections for failover purposes The Hilo location will be the primary data center and house redundant database serversThe Lihue location will serve as a failover data center and house the primary web servers (including the primary application and primary database servers)A constant connection between the three locations, carrying at least 75 Mbps of dataAll servers at all locations must have redundancy Protection from intrusions is required and should be documentedA plan to verify security and failover measures is required Submission: Using the free tool, daw.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 ant necessary interconnections. Figure 1 shows the draw.io ‘new network diagram’ dialog window: Project #1 Network Diagram Student Name: Name Any necessary hardwareSite-to-Site (WAN) connections (e.g., leased line connectivity, satellite, etc.)Annotate the following values for each of the Sites:Network IDUseable RangeSubnet MaskCIDR ValueBroadcast AddressAll devices require hostnames complying with the following naming conventions:Routers: Rx; where x is the site number incremented by a value of 1 for each routerSwitches: Sx; where x is the site number incremented by a value of 1 for each switchServers: SRVx where x is the server number incremented by a value of 1 for each serverFor each site router, implement a private ip addressing scheme using a range suitable for corporate infrastructure and include the following:management vlanproduction vlanHigh availability 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!) andsubmit it to the Assignment folder. Figure 2 demonstrates how to export your draw.io diagram as a PDF document: |
Hide Rubrics
Rubric Name: Deliverable 1: Network Infrastructure Design Diagramming
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.
/ 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.
/ 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.
/ 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.
/ 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.
/ 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.
/ 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.
/ 16
Rubric Total ScoreTotal
/ 100
Overall Score
Overall Score
Level 427 points minimum
Level 320 points minimum
Level 213 points minimum
Level 10 points minimum
| Associated Learning Objectives | |
| 1.1.3: Present ideas in a clear, logical order appropriate to the task. | |
| Assessment Method: Score on Criteria – 1.1.3: Present ideas in a clear, logical order appropriate to the task. | |
| Required Performance: Meets | |
| 10.1.1: Identify the problem to be solved. | |
| Assessment Method: Score on Criteria – 10.1.1: Identify the problem to be solved. | |
| Required Performance: Meets | |
| 10.1.2: Gather project requirements to meet stakeholder needs. | |
| Assessment Method: Score on Criteria – 10.1.2: Gather project requirements to meet stakeholder needs. | |
| Required Performance: Meets | |
| 10.1.3: Define the specifications of required technologies. | |
| Assessment Method: Score on Criteria – 10.1.3: Define the specifications of required technologies. | |
| Required Performance: Meets | |
| 13.1.1: Create documentation appropriate to the stakeholder. | |
| Assessment Method: Score on Criteria – 13.1.1: Create documentation appropriate to the stakeholder. | |
| Required Performance: Meets | |
| 13.2.1: Evaluate vendor recommendations in the context of organization requirements. | |
| Assessment Method: Score on Criteria – 13.2.1: Evaluate vendor recommendations in the context of organization requirements. | |
| Required Performance: Meets | |
| 2.2.2: Evaluate sources of information on a topic for relevance and credibility. | |
| Assessment Method: Score on Criteria – 2.2.2: Evaluate sources of information on a topic for relevance and credibility. | |
| Required Performance: Meets |
Bottom of Form
