SWE4303 Computing Infrastructure Assessment 1 Guide: Network Design, Subnetting and Packet Tracer Proof of Concept

Published on: November 16, 2026 | Students Assignment Help UK Editorial Team | 10 views

To score well in SWE4303 Assessment 1, work out your personalised device counts and subnet sizes first, show the VLSM split of your 10.0.XY.0/24 network in a table, and only then build a Packet Tracer proof of concept that matches those numbers exactly. Markers reward a design where the report, the addressing table and the Packet Tracer file all agree. This guide explains how to plan the 2,200-word report, which service to configure and the mistakes that lose marks. If you want a second opinion on your own draft, our Cisco Packet Tracer assignment help page explains the support available.

What the assessment is really asking

The SWE4303 Computing Infrastructure Assessment 1 brief at the University of Bolton asks you to choose a business scenario, design a two-building network, justify your choices and prove the core of the design in Cisco Packet Tracer. The brief limits the report to 2,000 words plus 10%, and it is a category A assessment, so generative AI must not be used.

It tests two learning outcomes: justifying an infrastructure strategy for a brief, and applying networking principles and protocols to solve a problem. In practice, every design choice needs a reason, and every claim should be backed by evidence from your simulation.

Start with your personalised numbers

Your student ID digits X, Y and Z set the device counts, the growth allowance and the base network. Do this step before anything else, show the working in Appendix A and use the same numbers everywhere.

Seed item Rule from the brief What to show
Building A staff devices 20 + X The calculation and the result
Building B staff devices 10 + Y The calculation and the result
IT administration devices 5 + Z The calculation and the result
Growth allowance 20% + Y Each device count multiplied up and rounded up
Base network 10.0.XY.0/24 The derivation, dropping any leading zero

Round up every growth figure, add an address for the default gateway, and then choose the smallest subnet that fits. A /26 has 62 usable hosts, a /27 has 30, a /28 has 14 and a /30 has 2, which covers most small-site designs.

Want to see a worked layout? Our SWE4303 network design sample extract is for reference only and uses invented digits, so you cannot reuse its numbers.

A subnetting method that avoids mistakes

  1. Calculate hosts needed. Device count with growth, plus the gateway.
  2. Sort from largest to smallest. VLSM works best when big blocks are placed first.
  3. Choose the prefix. Find the smallest block where usable hosts are at least the requirement.
  4. Allocate in order. Each block starts where the previous one ended, aligned to its own size.
  5. Record everything. Network address, mask, usable range, broadcast and gateway in one table.
  6. Add the router link. A /30 between the two buildings, kept separate from the staff subnets.

Check your table by adding block sizes: the total must not exceed 256 addresses, and no two ranges may overlap. A single misaligned network address is the most common error markers find.

Choosing a service you can prove

The brief asks for at least one configured and tested network service. Pick the one you can finish properly rather than the most impressive one.

Service Why choose it Evidence to capture
DHCP Easy to demonstrate with several hosts and a relay Show ip dhcp binding, host IP configuration
DNS Shows name resolution to a company web page Server records, nslookup or ping by name
Web server Easy to visualise with a browser test Browser page from each building

Whichever you choose, add secure administration with SSH, a local user and a restricted access list, and keep your evidence in the same order as your report.

Packet Tracer evidence that earns marks

  • A clear topology screenshot with device names and addresses visible.
  • Show commands such as interface summaries and routing tables on each router.
  • Ping tests across the buildings, including one that fails for a reason you can explain.
  • Proof that SSH works from the administrator workstation and is blocked elsewhere.
  • Screenshots that are cropped, labelled and referred to in the report text.

For help with configuration problems, see our computer network assignment help page.

Justifying your design decisions

The brief rewards reasoning, so every choice needs a short because-clause. If you place a router in each building, say that it keeps broadcast traffic local and makes each site easier to secure. If you choose static routes, say that three subnets do not justify the extra complexity of a routing protocol, and that you would revisit the decision if the site grew.

Link choices back to the business scenario as well. A production and dispatch building may need reliable connectivity for stock systems, while an administration building may need more shared files and printing. Mentioning these differences shows that the design was shaped by the brief, not copied from a template.

Finally, be honest about limits. A single link between buildings is a single point of failure, and a short sentence explaining how you would add redundancy shows the maturity expected at this level without needing extra configuration.

Mark-maximising checklist

  • Your X, Y and Z derivation is in Appendix A and used consistently.
  • The scenario, services, users and reliability needs are stated as assumptions.
  • The VLSM table has network, mask, range, broadcast and gateway for every subnet.
  • The design explains why routers, switches and a given addressing plan were chosen.
  • At least one service is configured and tested.
  • Secure administration and basic service security are in place.
  • The report mentions growth and one limitation of the design.
  • The Packet Tracer file is the one you describe, and its addresses match the report.

Common mistakes to avoid

  • Using someone else’s example numbers instead of your own digits.
  • Forgetting to round growth figures up.
  • Leaving no space for the router link subnet.
  • Giving screenshots with no explanation.
  • Describing devices without explaining why they were chosen.
  • Configuring many services badly rather than one properly.

Common student worries

Many first-year students worry that they will run out of words. Use tables for addressing and evidence lists, and keep the written commentary for justification. Others find Packet Tracer frustrating: save a working version often, test one link at a time and keep a note of each command you enter.

If you are short of time, build the addressing table first, then a minimal working topology, then add the service. Read about our service to see how we can support planning and feedback.

FAQs

Which business scenario should I choose?

Choose the one you can describe confidently. All five scenarios have two buildings and the same technical requirements, so the choice mainly affects your wording and assumptions.

Do I need to use the exact 10.0.XY.0/24 network?

Yes. The brief asks you to derive it from your own student ID, show the derivation in Appendix A and use it consistently in the report and the Packet Tracer file.

How many services must I configure?

The brief requires at least one configured and tested network service, with evidence. A second service is optional and should not replace proper testing of the first.

Do the screenshots count towards the word limit?

Check the brief and module guidance. Generally, captions and explanatory text count, while images and appendices are treated separately, but confirm this with your tutor.

Can I use static routes?

Yes, if you justify them. For a small two-building site, static routes can be sufficient, and you can mention a routing protocol as a future option.

Is it acceptable to get help with an assignment like this?

This assessment is category A, so generative AI is not permitted. Planning guides and reference samples are study aids, and the work you submit must reflect your own understanding and follow your university’s rules.

For tailored feedback on your own design, submit your assignment details and our team will respond with options.

Written by
Students Assignment Help UK Editorial Team

Students Assignment Help UK Editorial Team

Our editorial team works with students in the UK and sees the questions they ask most often. This guide is built from those real queries: where students get stuck, what markers look for and how to plan the work step by step.

Latest Posts

UPTO 35% DISCOUNT

Get Your Assignment Completed At Lower Prices

Plagiarism Free Solutions
100% Original Work
24*7 Online Assistance
Native PhD Experts
Hire a Writer Now

Facing Issues with Assignments? Talk to Our Experts Now!Download Our App Now!

Have Questions About Our Services?
Download Our App!

Get the App Today!

QRcode