-
Notifications
You must be signed in to change notification settings - Fork 0
Sources Citations and AI Use
Software work is influenced by documentation, examples, tools, and other people. Keeping track of that help is a professional habit.
For Module Three, the current Assignment Guidelines and Rubric in D2L Brightspace is the authority for AI-use and acknowledgement requirements.
This Wiki page explains how the repository supports that requirement. It does not create a separate AI policy.
The Module Three assignment tells students who use generative AI tools to follow SNHU's student generative-AI guidance, acknowledge that use, and use the linked Shapiro Library guidance for citation.
Because institutional guidance can change, follow the current links and wording in D2L rather than relying on a copied policy statement in this Wiki.
Depending on what you actually use, outside assistance may include:
- websites or online documentation;
- code or pseudocode examples;
- books or articles outside the supplied course materials;
- another person who materially contributed to the solution;
- IDE-generated code suggestions; or
- a generative AI chat or coding tool.
Do not add a citation merely because a source exists. Acknowledge sources or assistance that actually influenced your work, following current course guidance.
The repository includes course-provided materials such as:
- README files;
- the SRS;
- the SDD;
- the SDW template;
- Draw.io reference tabs;
- starter pseudocode;
- optional Python scaffolding; and
- tests.
These materials are part of the course workflow. Follow the current assignment instructions for whether and how course-provided materials need to be cited in your submitted work.
The pseudocode template includes a References section so you have a place to record outside sources or assistance you actually used.
If current assignment guidance requires acknowledgement, use that section in a way consistent with the guidance.
If you used no outside source that needs acknowledgement, delete an unused reference TODO rather than inventing a reference.
The optional Python starter also includes a References section.
That section is an IT 140 course convention designed to build the habit of keeping sources and assistance visible with technical work. It is not a Python-language requirement.
The graded task is to design the program logic. The learning value comes from understanding the requirements, reasoning about the 40-hour boundary, and representing the solution yourself.
Even when an AI tool is permitted, you remain responsible for:
- understanding the submitted design;
- checking it against the assignment requirements;
- making sure the flowchart and pseudocode agree; and
- acknowledging AI use as required by current course guidance.
Do not rely on an AI-generated answer that you cannot explain or verify.
The optional SDW is designed to support your own thinking by asking you to explain requirements and design decisions in your own words.
That makes it useful even when other assistance is allowed: it helps you verify that you understand the work you are submitting.
When asking for help in GitHub Discussions, Issues, or another public location, avoid posting your completed graded flowchart or pseudocode.
Describe the problem without sharing the entire solution whenever possible.
If you are unsure whether a source, AI tool, or other assistance is allowed or how it should be acknowledged, ask your instructor and follow the current D2L assignment guidance.
Return to Home.