Highlights
Introduction:
This assessment requires learners to complete two scenarios:
• Scenario 1: Learners are required to design, write, document, and test a Python script based off of the given scenario below.
• Scenario 2: Learners are required to analyse, document, fix, and test a pre-written pseudocode and Python script set as given below.
Scenarios
Scenario 1: Port scanner
One of the TMC Networking team members has contacted the development team that you are a part of, requesting a port scanner so that they can perform lite reconnaissance on the network in hopes of reducing their threat surface. Your manager has tasked you with the design and development of this script and has given you a number of set requirements that have been passed to them.
Requirements:
• The script needs to incorporate both the Scapy module and the Sys module.
• The script must be run from the command prompt, with the main argument allowing the user to enter the IP address OR domain name OR address range.
• Your script needs to use appropriately filled out headers (an organisational template has been provided).
o This header should be displayed and then the script exited, if:
The user attempts to run the script from an IDE
If the user does not enter enough CLI arguments to sufficiently run the script
If the user adds a ‘-help’ argument when executing the script
• If the user adds a ‘-verbose’ argument while executing the script, it should show the process of sending and receiving for all packets.
• The ports to be scanned should be:
o 21 – FTP
o 22 – SSH
o 23 – Telnet
o 25 – SMTP
o 53 – DNS
o 80 – HTTP
o 110 – POP3
o 135 – Windows RPC
o 137 – Windows NetBIOS over TCP
o 138 – Windows NetBIOS over TCP
o 139 – Windows NetBIOS over TCP
o 443 – HTTPS
o 1433 – Microsoft SQL Server
o 1434 – Microsoft SQL Server
o 8080 – HTTP Alternative
• The packet crafted should have a randomised source port.
• The output should check for responses on the target address (or addresses) and give a list of the outputs; including the IP address being scanned, the port being scanned, and whether each port is open, closed, or filtered.
Scenario 2: Caesar cypher
TMC wants to create a Caesar cypher script that they can use to scramble messages or simple documents for internal use (sounds like one of the executives may have watched too many old spy movies). One of your colleagues, Joe Blog, took on the project and has created the script, however, they are having a number of issues trying to make it meet the requirements they were given and have asked for your help in the matter.
Requirements:
• The code should ask for a string of plain text characters from the user and then ask for the rotation key.
• The code should take the plain text and turn it into cyphertext by 'rotating' the character the same amount as the key and send it to a document on the computer (for easy sending). The file should be called EncryptedText.txt and ONLY hold the last message in it.
• The Caesar cypher process should be in a function.
• The key must only be between 0 and 25, else the user is asked again.
• The code should accept lowercase, uppercase, and numbers/symbols.
• Uppercase should be correctly rotated but stay uppercase.
• Lowercase should be correctly rotated but stay lowercase.
• Symbols (including spaces) and numbers should remain unchanged.
Part 1: Design
1) Based on the scenario and information provided, create pseudo-code that matches the logic needed to fulfil the requirements.
a) In a new empty text document, write your pseudo code for scenario 1 with a document editor of your choice. Save this file as “scenario1_pseudo”. [405E1.1-3, 3.1] [407E2.1]
b) This pseudo version will need to be titled as version one in the text document and any modifications needed to the pseudo-code later (as part of Task 4.c) will need to be saved as another version in the same text document with a description of why the changes were necessary. [405E1.1-3, 3.1-2] [407E2.2]
2) Review the pre-written pseudo code given to you in the “scenario2_psuedo” file. This has been written incorrectly with missing logic and errors.
a) Identify the missing logic and errors and make corrections to the pseudo-code in a new text document named “scenario2_pseudo_fixed”. [405E3.2] [407E2.2]
3) After reading the scenario, performing any research, and writing the initial pseudo code in the above tasks
a) Create a text document called “scenario1_requirements” and include the following information in it with explanations for each: [405E3.4, 5.1] [407E3.4]
i) The programming language/s you are going to use [407E1.1]
ii) The integrated development editor you are going to use [407E1.2]
iii) Pre-written classes: this includes native and 3rd party frameworks or modules you will use [407E1.2]
iv) Pre-written functions and methods you will use [407E1.1]
v) Any custom-made functions or methods that will be written by you [407E1.3]
vi) Any pre-written or custom-made variable names including what data type the variables are/will be [407E1.1]
vii) The network protocols (or other protocols) that will be used [407E1.3]
Part 2: Write and Review
4) For scenario 1, create a script called “Port_scanner.py” that follows the pseudo-code that you created for scenario 1. [405E3.3] [407E3.1]
a) Include completed headers at the top of the script using the TMC_Header template [405E5.2, PE3] [407E3.2]
b) Above every major block of code, include comments explaining what that block of code is doing. [405E5.1]
c) You will need to include a new version of your pseudo code from “task 1b” for any code changes that go outside the scope of your design. [405E3.2] [407E2.2]
5) Review the pre-written source code given to you in the “Caesar.py” file, using the corrected pseudo code from task 2 make any changes that are necessary to match the logic in the pseudo code and make it work correctly, save this as “caesar_fixed.py”. [405E3.2]
Part 3: Testing and Debugging
6) Use the TestPlanTemplate.docx document to create white box test plans for both scenario 1 and scenario 2, that contain information about the testing process for the working code. The test plans will need to include the following for both scenarios: [405E4.1-2, 5.1] [407E3.4]
a) Fully filled-out a test plan.
b) A completed functional testing table that includes columns for:
i) Test number
ii) Parameters and inputs used (stdin)
iii) Expected text output and outcome (stdout or stderr)
iv) Actual results of stdout or stderr as a screenshot.
v) Whether the test passed or failed.
Be sure to include a test for each input or parameter change including correct and incorrect values. In conclusion, for any failed tests, explain why they have failed and explain (in plain terms) what would need to be done to fix it.
c) Use debugging tools to show the code is working. [405E4.1]
i) Include screenshots of you using debugging tools on the running code, which contains your initials and student number.
d) Run the code outside of the IDE and in an expected real-world test. [405E4.1]
i) Include screenshots of you using the working code, which contains your initials and student number.
This 22334VIC: IT Assessment has been solved by our IT experts at My Uni Paper. Our Assignment Writing Experts are efficient to provide a fresh solution to this question. We are serving more than 10000+ Students in Australia, UK & US by helping them to score HD in their academics. Our experts are well trained to follow all marking rubrics & referencing style.
Be it a used or new solution, the quality of the work submitted by our assignment experts remains unhampered. You may continue to expect the same or even better quality with the used and new assignment solution files respectively. There’s one thing to be noticed that you could choose one between the two and acquire an HD either way. You could choose a new assignment solution file to get yourself an exclusive, plagiarism (with free Turnitin file), expert quality assignment or order an old solution file that was considered worthy of the highest distinction.
© Copyright 2026 My Uni Papers – Student Hustle Made Hassle Free. All rights reserved.