CMIT 350 Assignment 2: Packet Tracer Task Instructions   As a network engineer for Kamehameha Institute, you will need to become familiar with the Packet Tracer simulation tool from Cisco

Subject:Computer SciencePrice:25.01 Bought8

Share With

CMIT 350 Assignment 2: Packet Tracer Task

Instructions

As a network engineer for Kamehameha Institute, you will need to become familiar with the Packet Tracer simulation tool from Cisco. Packet Tracer is used to simulate and test network configurations. This allows you to work out and improve upon the settings before implementing them. Using the diagram and configuration information from your first task, create a Packet Tracer simulation. How Will My Work Be Evaluated? 1.1.3: Present ideas in a clear, logical order appropriate to the task. 10.1.1: Identify the problem to be solved. 10.1.2: Gather project requirements to meet stakeholder needs. 10.1.3: Define the specifications of required technologies. 13.1.1: Create documentation appropriate to the stakeholder. 13.2.1: Evaluate vendor recommendations in the context of organization requirements. Submit your .pkt (Packet Tracer) file to the box below. Review the syllabus for information about late policies and resubmitted assignments.

Rubric Name: Deliverable 2: Packet Tracer Task

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

10.1.1: Identify the problem to be solved.

18 points

Presents a relevant IT problem clearly and specifically.

15.3 points

Presents an IT problem that requires a solution.

13.5 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.,/ 18

10.1.2: Gather project requirements to meet stakeholder needs.

18 points

Identifies IT project requirements in a thorough and clear manner to meet all stated stakeholder needs.

15.3 points

Identifies IT project requirements to meet stated stakeholder needs.

13.5 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.,/ 18

10.1.3: Define the specifications of required technologies.

18 points

Defines thoroughly and clearly the specifications of required technologies.

15.3 points

Defines the specifications of required technologies.

13.5 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.,/ 18

13.1.1: Create documentation appropriate to the stakeholder.

18 points

Creates thorough and accurate IT documentation that exceeds requirements.

15.3 points

Creates IT documentation that meets requirements.

13.5 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.,/ 18

13.2.1: Evaluate vendor recommendations in the context of organization requirements.

18 points

Evaluate and provides detailed justification for vendor recommendations in the context of organization requirements.

15.3 points

Evaluates vendor recommendations in the context of organization requirements.

13.5 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.,/ 18

Rubric Total ScoreTotal

/ 100