What to turn in
For the current lab's questions, point value, due date, and required deliverables, read its assignment on the course page and its D2L submission folder.
Prepare a report that shows what you did, what you observed, and why the evidence supports each answer. Submit the file type and any additional materials specified by that lab. Most labs ask for one PDF report.
Complete the work in the assigned environment, such as WolfCTF, and submit through D2L. Finishing the lab environment does not submit your report. If a lab handout gives a different format or evidence requirement, follow that lab's instructions.
File and page format
| Item | General guidance |
|---|---|
| Filename | Use Lastname_Firstname_LabN.pdf, replacing N with the lab number, unless the assignment specifies another name. |
| Submit one readable, non-password-protected PDF when a report is requested. Include other files only if the assignment asks for them. | |
| Length | Use enough space to answer every question and show readable evidence. Follow any page limit in the lab instructions. Put long supporting logs in an appendix rather than filling the main text with raw output. |
| Page setup | Use US Letter or A4 pages, consistent body text, clear headings, and page numbers. Keep screenshots, code, and diagrams large enough to read. |
| Figures and code | Number and caption figures/tables, refer to them in your explanation, and preserve line breaks in code and terminal output. |
Write in Word, Google Docs, LibreOffice, or LaTeX, then export a PDF. Open the exported PDF and check every page before submitting.
Report structure
1. Title information
Identify the lab number and title, CSC 472 Software Security, your name, student ID, instructor, and submission date. Include a separate title page if the lab requires one. Never include passwords, activation links, or session tokens.
2. Introduction
Explain the lab's objective in your own words and state what you investigated.
3. Environment and method
Describe the assigned workspace, relevant source or binary, tools and versions, commands or scripts, and the steps needed to reproduce your results. Include build settings, debugger state, or program inputs when they affect the answer.
4. Analysis and results
Use the question numbers and part names from the current lab. Answer every prompt and include all requested code, output, screenshots, and diagrams. For each answer, state the result, show evidence from your own run, and explain how that evidence supports the result.
“After [command or step], [specific output or observation] appeared in Figure [number] or Listing [number]. This supports [answer] because [reason].”
5. Discussion and conclusion
Summarize what the results established. Explain an unexpected result, limitation, or troubleshooting step when relevant. Report unresolved issues honestly.
6. References and assistance
Cite class materials and outside sources actually used. If AI helped explain or debug something, identify that help and show how you checked the resulting claim against your own experiment.
7. Appendix — if useful
Place long supporting transcripts or extra output here. Keep the evidence needed to understand each answer near that answer in the main report.
Evidence, code, and figures
- Use evidence from your own session. Include the relevant command or input, output, and program state. A screenshot alone does not explain a result.
- When the lab asks for a script or source code, include the complete relevant code and the output that shows what it did. Use a readable monospace font.
- When the lab asks for GDB or GEF evidence, capture the stop point, relevant registers or memory, and the command that produced the output. Explain the values you rely on.
- Include a diagram only when the assignment calls for one or when it makes your reasoning clearer. Label it with values from the same run and program point.
- Crop screenshots to the relevant area while keeping commands and results visible. Remove private information; do not alter observed values.
- Give each figure, table, or listing a descriptive caption, and refer to it in the text. Distinguish observations from guesses.
The lab assignment determines which evidence is required. Check every question against its requested deliverables before exporting the report.
How the report is graded
Check the current lab assignment and D2L rubric for its point value, question weights, and any special grading rules. These can differ between labs.
| Area | What to check |
|---|---|
| Technical content | Every required question is answered correctly and supported by evidence from your own work. |
| Organization | The objective, method, numbered answers, and conclusion are easy to find. |
| Presentation | The writing is clear, the PDF is complete, and sources and assistance are acknowledged. |
| Visual evidence | Code, output, screenshots, and diagrams are legible, labeled, and explained where used. |
Use the assignment's published rubric for exact weights and points.
Submit the PDF to D2L
Check the current lab's deadline in the course assignment and D2L folder. Allow time to correct an upload or file problem before the deadline.
- Export and check. Save the final PDF with the required filename. Open it locally and confirm that all pages, code, screenshots, and diagrams render correctly.
- Open the course. Sign in at WCU D2L and select your Fall 2026 CSC 472 course/section.
- Select the matching folder. Open Assignments and choose the folder for the lab number you completed. Check its due date, file rules, and instructions.
- Attach the file. Choose Add a File, select your final PDF, complete the upload, and check that the correct filename appears.
- Submit. Click Submit. Attaching a file without submitting it does not finish the D2L submission.
- Confirm. Look for the successful submission message. Reopen the submission/history area and verify the filename and recorded time. Open the submitted PDF if D2L allows it.
- Keep a receipt. Save the confirmation or history screenshot and retain your submitted PDF.
Submit the PDF file itself rather than a document-sharing link. If you need to replace it, use another submission only if the folder permits that, then verify the new record.
If the correct folder is missing, closed, rejects the required file, or shows a conflicting deadline, contact Dr. Chen at schen@wcupa.edu before the deadline with your course/section and a screenshot. Follow the syllabus and assignment for late-work rules.
Final checklist
- I used the correct lab number, filename, D2L folder, and deadline.
- I answered every question and included each required deliverable.
- My claims are tied to readable evidence from my own session.
- Required code, output, figures, and diagrams are complete, labeled, and explained.
- I acknowledged sources and assistance and removed passwords or tokens.
- I opened the exported PDF and checked every page.
- I clicked Submit in D2L and verified the recorded filename and time.