Scribd
Upload
9 views2 pages

Assignment Checklist NETWORKING

The document outlines an assignment checklist for Unit 2 on Networking, detailing requirements for four deliverables: a formal presentation for a non-technical audience, an implementation plan for an internal technical team, a technical report for evaluators, and an evaluation report for executives. Each deliverable has specific content requirements, audience considerations, and academic standards, including the use of Harvard referencing. The checklist emphasizes the importance of clear communication, technical depth, and structured documentation.

Uploaded by

hihijibuhihi
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views2 pages

Assignment Checklist NETWORKING

The document outlines an assignment checklist for Unit 2 on Networking, detailing requirements for four deliverables: a formal presentation for a non-technical audience, an implementation plan for an internal technical team, a technical report for evaluators, and an evaluation report for executives. Each deliverable has specific content requirements, audience considerations, and academic standards, including the use of Harvard referencing. The checklist emphasizes the importance of clear communication, technical depth, and structured documentation.

Uploaded by

hihijibuhihi
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Assignment Checklist: Unit 2 – Networking

1. Formal Presentation (10–15 slides + speaker notes)


Audience: CEO & Senior Network Administrator (non-technical)
Purpose: Communicate investigation into networking principles, topologies, hardware, and
software

 [ ] Cover benefits & constraints of network types (wired, wireless, hybrid)


 [ ] Explain network standards (OSI, TCP/IP, 802.x) with pros/cons
 [ ] Illustrate impact of topologies (star, bus, ring, mesh, hybrid) on communication &
bandwidth
 [ ] Assess networking principles & protocols (IPv4, IPv6, HTTPS, etc.)
 [ ] Describe operating principles of devices & servers (routers, switches, firewalls,
file/domain servers)
 [ ] Show dependency between workstation hardware & networking software
 [ ] Use visuals, diagrams, and simplified language for non-technical audience
 [ ] Add speaker notes for each slide
 [ ] Include Harvard references and bibliography

2. Implementation Plan (Report, 1,000–1,500 words)


Audience: Internal technical team
Purpose: Design a networked solution for SBP Ltd

 [ ] Provide network design (hardware, software, addresses, devices, users, sub-domains,


physical layout)
 [ ] Detail device configuration & security considerations
 [ ] Create maintenance schedule for the network
 [ ] Develop test plan (actions, test data, expected results)
 [ ] Explain user feedback collection & analysis
 [ ] Document optimization improvements made to design
 [ ] Compare server types and recommend selection
 [ ] Justify choices with cost & performance optimization
 [ ] Structure with headings, sub-sections, Harvard referencing

3. Technical Report (1,500–2,000 words)


Audience: Technical evaluators
Purpose: Demonstrate implementation of the virtual network design

 [ ] Provide evidence of implementation (screenshots, configs, monitoring reports)


 [ ] Execute test plan and record results
 [ ] Analyze test results vs expected outcomes

1
 [ ] Recommend enhancements to the networked system
 [ ] Ensure technical depth & clarity for evaluators
 [ ] Support with Harvard references & bibliography

4. Evaluation Report (1,000–1,500 words)


Audience: CEO & Senior Network Administrator
Purpose: Reflective evaluation of topology, design, and implementation

 [ ] Evaluate selected topology & protocols for SBP scenario


 [ ] Show how they demonstrate efficient use of networking systems
 [ ] Provide critical reflection on final implementation & design decisions
 [ ] Reflect on enhancements made to improve solution
 [ ] Write in accessible language for non-technical audience
 [ ] Include Harvard referencing & bibliography

Academic Requirements (applies to all deliverables)


 [ ] Use headings, paragraphs, sub-sections appropriately
 [ ] Support all work with research & Harvard referencing
 [ ] Provide a Harvard-style bibliography
 [ ] Respect word limits (no penalty for exceeding)
 [ ] Maintain professional formatting & clarity

You might also like