Comprehensive Final Test and Project Report Guide

CMS Test Regulations and Room Etiquette

• Prohibited Electronic Devices and Personal Items:

  • Any device capable of communicating or storing hidden notes is strictly banned from being on your person during the test.

  • Prohibited equipment includes mobile phones, smartwatches, calculators, and smart glasses.

  • All prohibited items must be securely stowed inside a backpack, handbag, or chosen bag prior to entering the test venue.

  • Bags must be placed along the front of the lecture theater or lined against the perimeter walls, completely away from test-taking seating.

• Permitted Test Materials:

  • Students are permitted to bring only an official student ID card and a pen to their desks.

• Room Seating Procedure:

  • Seating follows a strict every-second-seat spacing model to maintain academic integrity and spatial separation.

  • The first individuals entering an aisle must move toward the center seats of the row rather than occupying end seats.

  • Subsequent arrivals must leave an empty seat between themselves and the next person, filling outward from the center.

  • Strict adherence to this seating protocol ensures rapid, orderly entry and exit from the testing facility.

• Arrival Logistics:

  • Students must arrive early to accommodate bag drop-offs, seating spacing, and ID verification without cutting into allocated exam time.

  • Due to preceding and subsequent testing sessions scheduled in the testing facilities, late entry risks a loss of test time.

Examination Scope and Second-Trimester Curriculum Review

• Scope Boundary:

  • The test assesses solely the content covered in the second half of the trimester, beginning at Lecture $10$.

  • Content covered prior to the mid-trimester break is excluded from this test.

• Lecture-by-Lecture Content Breakdown:

  • Lecture $10$ (Artificial Intelligence and Bias): Exploration of the ethical challenges of artificial intelligence, particularly the mechanisms through which machine learning models reinforce, amplify, and perpetuate systemic societal bias.

  • Lecture $11$ (Embodied and Autonomous AI): Guest lecture by Professor Judy Bowen analyzing embodied and autonomous AI systems, focusing on technical considerations, governance, and implications across everyday life, clinical healthcare, and educational environments.

  • Lecture $12$ (AI and Te Ao Māori): Session delivered by Te Taka detailing the intersection of artificial intelligence and Te Ao Māori (the Māori worldview) and the Māori language. Included demonstrations of emerging tools and critical frameworks regarding the ethical design and utilization of technologies for Māori and indigenous populations.

  • Lecture $13$ (International Data Sovereignty): Examination of international data sovereignty frameworks, focusing on the geographic location of data storage infrastructures, jurisdictional boundaries, legal cross-border access, and specialized legal terminology.

  • Lecture $14$ (Indigenous and Māori Data Sovereignty): Presentation by Te Taka focusing on indigenous data sovereignty, outlining specific principles, governance structures, and protocols regarding Māori data rights, ownership, and protection.

  • Lecture $15$ (Adversarial AI and Societal Impacts): Analysis of the broader societal impacts of artificial intelligence, including malicious or adversarial uses of technological tools and comparative global regulatory approaches.

  • Lecture $16$ (AI in Software Engineering Practice): Industry guest lecture by Dr. Ralph Heaser highlighting practical AI integration within modern software development workflows, the formation and operation of cross-functional micro-teams, and shifts in daily collaborative engineering practice.

  • Lecture $17$ (Teamwork Across Technical Disciplines): Lecture led by Te Taka exploring organizational teamwork dynamics specifically within computing, software engineering, mathematics, and data science.

  • Lecture $18$ (Professional Soft Skills and Safety Panel): Expert panel featuring four industry specialists discussing team dynamics, effective technical communication, psychological safety, and the essential role of soft skills in technical careers.

• Recommended Preparation Resources:

  • Comprehensive review of Lecture slides published on Moodle.

  • Targeted re-watching of lecture recordings for complex theoretical and practical concepts.

  • Active review of personal notes compiled across the second half of the trimester.

Test Structure, Question Types, and Examination Strategy

• Overall Grading Metrics:

  • The examination is scored out of a total of $50$ marks.

  • The structural breakdown is identical to the first mid-trimester test, divided into multiple-choice and long-form sections.

• Section 1: Multiple-Choice Questions (MCQs):

  • Located at the front of the examination script.

  • Contains $10$ questions, each worth $2$ marks, totaling $20$ marks.

  • Each question typically offers five potential answer options.

  • Test Strategy: No question should be left blank under any circumstance. An educated guess preserves a statistical probability of earning marks, whereas an omitted question automatically receives zero. Review all MCQ selections after finishing the long-form section.

• Section 2: Long-Form / Short-Answer Questions:

  • Contains $6$ structured analytical questions, each worth $5$ marks, totaling $30$ marks.

  • Requires detailed, multi-sentence or multi-paragraph responses demonstrating analytical depth; single-sentence answers are insufficient for full marks.

  • Test Strategy: Carefully dissect each prompt to ensure all sub-questions are answered.

• Analytical Case Study / Representative Question Template:

  • Hypothetical Scenario: An organization based in New Zealand stores all operational data on servers physically situated within Aotearoa, but contracts its cloud infrastructure from a provider owned by a parent company in the United States.

  • Required Prompt Dissection: Explain the technical and legal distinctions between data residency and data sovereignty. Analyze why physical data storage within New Zealand may fail to guarantee New Zealand sovereign jurisdiction over that data.

  • Deconstruction of Required Response Components:

  • Part 1 (Data Residency vs. Data Sovereignty): Define data residency as the physical, geographic location where data is stored and processed. Define data sovereignty as the principle that digital data is subject to the legal frameworks, privacy regulations, and governance of the nation where it resides or to which the data subjects belong.

  • Part 2 (Jurisdictional Conflict and Extraterritoriality): Explain that foreign parentage (such as US corporate ownership) subjects the provider to extraterritorial statutory requirements (such as the US CLOUD Act). Under these extraterritorial mandates, foreign courts or law enforcement agencies can compel a US-based entity to disclose data under its custody and control, regardless of whether that data resides on physical hardware located in New Zealand. Consequently, physical residency in Aotearoa does not insulate data from foreign sovereign jurisdiction.

  • Response Depth: A complete response requires at least two distinct, detailed paragraphs addressing both the definitional distinctions and the legal implications of ownership.

Final Project Report Specifications and Cadmus Requirements

• Submission Deadline and Platform:

  • Submission is due on Friday, October 23, at $11:59\,\text{PM}$ ($1$ minute prior to midnight).

  • All work must be conducted and submitted live through Cadmus.

• Cadmus Usage and Academic Integrity Mandate:

  • Drafting outside of Cadmus (e.g., authoring within Microsoft Word or Google Docs) and pasting the resulting text into Cadmus is strictly prohibited.

  • Writing in Cadmus is an institutional requirement designed to ensure academic integrity, tracking individual contributions and mitigating the unapproved use of generative AI or external plagiarism.

  • Real-time multi-device collaboration is natively supported in Cadmus Live; all group members must be logged into their own accounts when contributing.

  • Contribution tracking verifies the individual inputs of each team member (e.g., individual tracking records for team members such as Nick, Anika, Te Taka, and Tim).

  • Non-Compliance Penalty: A mandatory $15\%$ penalty will be applied to the final report grade if analytics detect that text was authored externally and copied into Cadmus.

• Structural and Formal Report Requirements:

  • Format: The submission must be a formal, structured professional report, not an unstructured narrative essay or brain dump.

  • Estimated Length: Approximately $4$ to $5$ pages (standard A4 format equivalent).

  • Word Count Equivalence: Assuming a standard density of $500$ to $1000$ words per page, the baseline scope equates to roughly $5000$ words maximum, adjusting downward for figures and formatting.

  • Standard Structural Components: Title page or dedicated front matter listing group name and all group members, introduction, structured body with clear descriptive headings, summary, conclusion, and a formal reference list.

  • Visual Assets and Referencing: Incorporate visual data assets such as photographic evidence, charts, diagrams, or project timelines. All figures must include clear captions, formal figure number labels (e.g., Figure $1$), and explicit citations/analyses within the surrounding body text.

  • Individual Accountability and Reflection: Explicitly document internal division of labor, detailing who executed specific tasks, what methodologies were implemented, and what key technical or operational lessons were learned.

  • Iterative Learning: Integrate insights gained from observing other student presentations during the project showcase sessions, incorporating overlooked concepts into the final written reflection.

  • Assessment Rubric: Accessible directly within Cadmus, evaluating layout, structural design, presence of front matter, professional tone, and depth of analysis on a $5$-mark scale.

Questions and Discussion

• Examination Venues and Room Split:

  • Audience Inquiry: Clarification regarding testing locations, noting that the testing cohort was split across two venues during the first test.

  • Resolution: The examination will occur across two venues. Due to spatial constraints in the secondary room previously utilized alongside S Block, a larger, upgraded lecture theater was arranged by Tim. Venue assignments split by alphabetical surname ranges will be published directly on Moodle on the afternoon of the lecture.

• Marking Rubric Presentation in Cadmus:

  • Audience Inquiry: Observation regarding the tilted layout of the rubric preview within the lecture presentation slides, questioning its legibility.

  • Resolution: The slide preview was stylized at an angle intentionally to encourage students to consult the complete, uncropped rubric matrix hosted natively inside Cadmus rather than relying on slide excerpts.

• Cadmus Interface and Document Pagination:

  • Audience Inquiry: Clarification regarding the $4$ to $5$ page guideline given that Cadmus operates as a continuous scrolling web text interface rather than a paginated document processor.

  • Resolution: While initial setup assumptions presumed page-break visibility, page lengths should be gauged against standard word counts. Standard structured technical documents average between $500$ and $1000$ words per page depending on layout complexity, headings, and embedded graphic figures. Inclusion of a dedicated title page and expansive diagrams will naturally alter vertical scroll depth; hence, adhering to the equivalent semantic density of a $4$ to $5$ page document is the primary metric.

Feedback and Administrative Closeout

• Feedback Channels:

  • Internal Course Poll: A secondary informal feedback survey opened two weeks prior to the close of the trimester to evaluate course delivery and pedagogical effectiveness.

  • Official University Evaluation: Formal institutional feedback opened on October 5, accessible via the central notification banner situated at the top of the Moodle portal.

  • Completion of both evaluations is requested to refine instructional delivery, retain high-performing curriculum components, and correct operational deficiencies for future course iterations.

• Course Scope Context (SageMax 270):

  • Integrates core mathematical foundations, computing paradigms, and data analytics with advanced socio-ethical inquiries, legal frameworks, and indigenous knowledge paradigms.

  • Final project submission deadline remains Friday, October 23, at $11:59\,\text{PM}$.