Section 1: Developing a Digital Outcome
- The complex processes used in the development of a digital outcome.
- The critical importance of systematic record-keeping and research.
- How to identify, address, and evaluate relevant implications throughout development.
1.1 Introduction & The Project Brief
A digital technologies outcome must be developed using complex processes to ensure it meets its intended purpose and is suitable for its target end users. The requirements, target audience, and constraints of an outcome are typically outlined in a brief.
If no written brief is provided, you must actively consult with the client or end users to establish the requirements, parameters, and specifications of the project.
1.2 Record Everything!
Comprehensive record-keeping is essential for demonstrating complex processes. Your documentation provides the necessary evidence to verify how decisions were made, trialled, and refined.
Keeping thorough records helps you to:
- Learn from mistakes and identify what needs to be adapted in future iterations.
- Identify successful techniques and formalise best practices for ongoing projects.
- Provide verifiable evidence for assessment criteria at Achieved, Merit, and Excellence levels.
Suitable forms of evidence collection include:
- Digital development logs (Google Docs, Notion, or dedicated project logs).
- Annotated wireframes, visual sketches, and UI screenshots showing design evolution.
- Audio notes or video logs (vlogs) explaining key technical decisions.
- Project management artefacts (Gantt charts, Kanban boards, sprint backlogs).
For Excellence, record-keeping is not just a passive diary. You must synthesise your entries to clearly justify why specific decisions were made over alternatives, citing precise trialling evidence and end-user feedback.
1.3 Using Research in Outcome Development
Research must actively inform every stage of the development process rather than being a standalone activity performed only at the start.
| Aspect of Development | How Research Informs the Outcome |
|---|---|
| Identifying Implications | Informs legal compliance (privacy laws, copyright), accessibility requirements (WCAG 2.1), and cultural appropriateness. |
| Planning | Helps determine logical component breakdowns, accurate time estimation, and selection of project management tools. |
| Trialling & Testing | Identifies optimal testing frameworks, user acceptance testing (UAT) methods, and comparative benchmark standards. |
1.4 Relevant Implications
When developing a digital outcome, you must address relevant implications throughout design, trialling, and implementation. Key implications include:
- Social and Cultural: Ensuring content, imagery, and language respect diverse cultural values (e.g., Tikanga MΔori considerations).
- Legal and Ethical: Adhering to relevant legislation such as the NZ Privacy Act 2020 and Copyright Act 1994.
- Intellectual Property: Respecting copyright, licensing terms (Creative Commons, MIT), and properly attributing assets.
- Privacy: Safeguarding personal user data, secure authentication, and data minimisation techniques.
- Accessibility: Designing for all users, including those with vision, hearing, motor, or cognitive impairments (WCAG guidelines).
- Aesthetics: Applying consistent visual design principles (contrast, alignment, visual hierarchy, typography).
- Usability: Ensuring intuitiveness, clear navigation, low cognitive load, and positive user experience (UX).
- Health and Safety: Minimising physical strain (ergonomics) and digital harm (reducing eye strain, dark mode options).
- End-user Requirements: Meeting explicit needs, expectations, and operational contexts of specified end users.
- Functionality: Ensuring code runs error-free, database queries return accurate data, and interfaces respond dynamically.
- Sustainability and Futureproofing: Writing clean, modular code and choosing scalable database structures to support future updates.
Learning Activity 1.1: Identify Suitable Research Sources
Identify five research sources that will inform your digital outcome and detail the specific information you expect to extract from each.
Learning Activity 1.2: Consider Relevant Implications
Select 3 critical implications for your outcome. Explain how you will explicitly address and evaluate each during development.
Topic 1 Knowledge Check
Test your understanding of outcome development and implications.
Section 2: Planning and Project Management
- Agile project management methodologies (Sprints, Backlogs, Iterative development).
- Deconstructing a complex outcome into logical component parts.
- Applying tools: Kanban boards, Gantt charts, wireframing, and milestone tracking.
- Drafting and evaluating practice project plans with explicit milestones.
2.1 Agile Project Management
Agile project management is an iterative approach to software and digital development. Rather than attempting to complete an entire project in one continuous linear process (Waterfall), Agile breaks the process into short cycles called Sprints.
- Flexibility: Allows continuous refinement based on end-user feedback and unexpected technical challenges.
- Iterative Trialling: Every cycle produces a working component or prototype that can be tested immediately.
- Risk Reduction: Flaws are identified early in development rather than right before release.
2.2 Deconstructing the Outcome into Components
To effectively manage complex outcomes, you must break the solution down into manageable component parts. For example:
- Web Development: Database schema design, backend API endpoints, navigation structure, UI wireframes, client-side validation, responsiveness.
- Software Development: Data structure selection, algorithm implementation, GUI layout, file I/O operations, error handling routines.
- Database Systems: Entity Relationship Diagrams (ERD), normalisation (1NF to 3NF), form interface design, query optimisation, report layouts.
2.3 Project Management Techniques & Tools
| Technique / Tool | Primary Purpose | Application in Digital Development |
|---|---|---|
| Kanban Board | Visual workflow management | Tracks tasks across stages: To Do, In Progress, Testing, Done. (e.g., Trello, GitHub Projects). |
| Gantt Chart | Timeline and dependency tracking | Maps out start dates, milestone targets, task durations, and critical paths. |
| Milestone Mapping | Key progress measurement | Defines fixed verification check points (e.g., "Database Schema Normalised", "User Auth Operational"). |
| Wireframing & Prototyping | Layout and workflow planning | Establishes UX/UI hierarchy prior to coding (e.g., Figma, Balsamiq). |
Learning Activity 2.1: Online Apps & Task Management
Describe how you will utilise an online project management application (e.g., Trello, GitHub Projects) to manage your component development workflow.
Learning Activity 2.2: Collaboration and Communication Apps
Explain how digital communication and collaboration tools will be used to capture stakeholder and end-user feedback during development.
Learning Activity 2.3: Practice Project Plan & Milestone Designer
Break down your digital project into distinct phases, specific tasks, and measurable project milestones. Add target dates and track dependencies.
| Milestone Name | Component Tasks / Sub-tasks | Target Date | Dependencies | Action |
|---|---|---|---|---|
Topic 2 Knowledge Check
Section 3: Trialling and Testing
- Distinguishing clearly between Trialling (exploring alternatives) and Testing (verifying correctness).
- Interactive Drag-and-Drop Activity: Categorising development activities.
- Systematic functional, usability, performance, and boundary testing procedures.
- Designing structured Test Cases with remediation tracking.
- Expanded Topic 3 Quiz (5 comprehensive items).
3.1 Trialling vs. Testing
It is vital to distinguish between trialling and testing in complex digital development:
| Process | Definition | Example Actions |
|---|---|---|
| Trialling | An exploratory, experimental process used to evaluate multiple options, algorithms, or prototypes before deciding on a final solution. | Comparing CSS Flexbox vs. Grid layouts; evaluating SQL vs. NoSQL databases; testing user preference between dark vs. light UI modes; benchmarking Python vs. Node.js execution speed. |
| Testing | A structured, systematic process used to verify that a specific component or complete outcome functions correctly against specifications. | Running automated unit tests; validating input field boundaries (Expected, Boundary, Invalid data); verifying cross-browser rendering and accessibility conformance. |
Learning Activity 3.1: Identify Suitable Trialling & Testing Techniques
Outline two specific trialling activities and two formal testing procedures you will carry out for your digital outcome.
Learning Activity 3.2: Interactive Categorisation (Drag & Drop)
Drag each development activity item below into either the Trialling Zone (Exploratory / Comparing Options) or the Testing Zone (Verification / Pass-Fail Validation).
TRIALLING (Comparing Alternatives)
TESTING (Validating Correctness)
3.2 Designing Test Cases & Boundary Value Analysis
Systematic testing requires running data sets through your software components across three primary categories:
- Normal (Expected) Data: Valid data that falls well within the allowed operational range (e.g., entering "John" in a name field).
- Boundary (Edge) Data: Data situated right at the absolute limits of acceptable inputs (e.g., entering an exact password length of 8 characters when min-length is 8).
- Invalid (Erroneous) Data: Inputs outside acceptable parameters designed to test error handling (e.g., entering -5 into an age field).
Learning Activity 3.3: Interactive Test Case Builder
Draft formal test cases for key features of your digital outcome. Log input types, expected responses, actual behaviour, and remediation steps.
| Test ID & Feature | Test Data Type | Expected Output | Actual Output & Result | Action Required |
|---|---|---|---|---|
Topic 3 Knowledge Check (Expanded)
Test your comprehensive understanding of trialling, testing, and quality assurance procedures.
Section 4: Final Review & Excellence Assessment Checklist
To achieve Excellence, you must prove that you used complex processes to develop a digital outcome effectively and efficiently. This means:
- Synthesis: You synthesised research, trialling outcomes, and stakeholder feedback to inform key development decisions.
- Justification: You rigorously justified your choice of tools, design decisions, and component architecture against alternative options.
- Optimisation: You actively refined and optimised the outcome's functionality, usability, and accessibility throughout the project lifecycle.
- Comprehensive Documentation: Your logs, project management boards, and test tables present clear, coherent evidence of complex processes.
Self-Assessment Checklist
Verify Your Readiness
Excellence Model Exemplar Reflection
Exemplar Written Response Analysis
Review the student justification response below and evaluate why it meets Excellence standards.
"During Sprint 2, I trialled two different navigation structures for the mobile view: an inline scrolling header versus a collapsible hamburger drawer. User testing with three members of our target end-user demographic revealed that 100% of participants accessed sub-pages faster with the hamburger drawer, registering an average task completion time of 3.2 seconds compared to 8.7 seconds for inline scrolling. Additionally, colour-contrast trialling using WebAIM contrast tools highlighted that my original accent blue (#00A88F on white) had a ratio of 3.1:1, failing WCAG AA standards for small text. I modified the accent colour to #005691 (contrast ratio 7.4:1), satisfying both accessibility requirements and visual clarity without compromising visual appeal."
Ka Rawe! Module Completed! π
You have successfully worked through the AS91907 (DT3.8) pre-learning module. You are now fully prepared to apply complex processes, structured planning, trialling, and testing to your digital outcome!