Task 2 - Software Enterprise Project

Failure to submit/Illness/Misadventure - Failure to complete/submit the Assessment Task on the

due date may result in a zero mark. If students are absent for an assessment task, they need to
submit an illness/misadventure appeal form (found in your Assessment booklet) to the Head
Teacher, within 5 days of returning to school. If no form is submitted, a mark of zero will be received.
Students must still submit/complete the task to gain necessary feedback and to satisfy the
requirements of the course.
Malpractice - Students caught cheating may receive a zero mark and reattempt the task to satisfy
the requirements of the course. If a teacher believes the work is not that of the student, it is the
responsibility of the student to prove it is their own work. The undocumented use of AI will be treated
the same as plagiarism.

Outcomes being assessed:

A student:
▪ SE-12-01 justifies methods used to plan, develop, and engineer software solutions
▪ SE-12-02 applies structural elements to develop programming code
▪ SE-12-04 evaluates practices to safely and securely collect, use, and store data
▪ SE-12-06 justifies the selection and use of tools and resources to design, develop, manage,
and evaluate software
▪ SE-12-07 designs, develops, and implements safe and secure programming solutions
▪ SE-12-08 tests and evaluates language structures to refine code
▪ SE-12-09 applies methods to manage and document the development of a software project

Student name: ________________________

Weighting: 40% Due Date: 2nd of July 2026 by 3:15pm

Submission Details: Submit a Google Doc and a PDF version of the report.

Include all relevant project files (HTML, CSS, Database, Excel files, video, etc.) in a zipped folder and submit
via Google Classroom.
Task Description

You will develop a software project that addresses a real-world problem or opportunity, applying
the skills learned in Years 11 and 12. For this project, you are required to design and develop a
secure Progressive Web Application (PWA) for a client. The application should provide a
seamless, reliable, and user-friendly experience across devices, including offline functionality.
The solution must be developed using Python and the Flask framework to implement back-end
logic, server-side processing, and secure client–server communication. HTML and CSS should be
used to structure and style the user interface, while JavaScript should support interactivity, form
validation, and dynamic front-end behaviour. Additional libraries or APIs may be used where
appropriate, but their selection must be justified and documented.
The secure PWA must include features such as user authentication, secure and encrypted
data storage, and may incorporate push notifications to enhance user engagement. You must
also develop an intuitive, user-friendly interface that prioritizes accessibility and usability,
ensuring the application is easy to navigate for a wide range of users.
Throughout the development process, you must ensure the application follows security best
practices, including protection of user data and safe handling of user interactions. This project will
demonstrate your ability to apply software development skills to solve a practical problem while
meeting real-world security and usability requirements.

Project Requirements

Develop the software project, project documentation, and presentation within the following four key stages:

1. Identifying and Defining Requirements

2. Research and Planning
3. Producing and Implementing
4. Testing and Evaluating

Each stage has specific deliverables that must be addressed in detail.

Stage 1 - Identifying and Defining Requirements (20 marks)

1.1 Define the Problem and Requirements

● Identify the Opportunity or Problem:

○ Identify a real-world problem or opportunity that your software project will address.
○ Validate the problem by contacting and interviewing a client, and by analysing
relevant software engineering case studies, scenarios, and existing solutions.
● Investigate Implementation Methods:
 ○ Research and compare different types of software implementation methods (e.g.,
pilot, parallel) to determine which best aligns with the project’s objectives and the
needs of the stakeholders.
○ Justify the chosen implementation method based on applicable project-specific
factors .
● Who is Affected:
○ Clearly explain the impacted groups (e.g., businesses, schools, healthcare facilities)
and support your explanation with evidence from interviews and case studies.
● System Requirements:
○ Key Features & Functionalities: List the critical functions that the system must
perform.
○ Target Users & Stakeholders: Define who will use the system and who will benefit
from it, based on client and user input.
○ Data Management Requirements: Detail the need for databases, logs, analytics,
and other data-handling tools.
○ Scope Definition: Clearly outline what the system will include, such as its features,
functionalities, and any technical constraints. Additionally, define the system
boundaries by specifying what is outside the scope of the system, identifying the
limits of the problem or system to be developed

1.2 Justify Tools and Resources

● Development Tools & Technologies:

o Programming Languages & Frameworks: Identify languages and frameworks that
align with the project’s functional needs and the complexity of the problem.
o Database Management Tools: Choose tools that facilitate efficient, secure, and
scalable data management.
o Development Environments & IDEs: Select environments that support rapid
development and debugging, while fitting the team’s workflow.
o Collaboration & Version Control Tools: Outline how tools like Git or similar
platforms will support teamwork and iterative development.
● Justification:
o Base your choices on how each tool meets project requirements, ensuring efficiency
and scalability.
 o Incorporate insights from client interviews and case studies to validate that your
selected tools and resources are the best fit for solving the identified problem.

Stage 2 - Research and Planning (20 marks)

2.1 Collaboration and Management

● Collaboration Tools:
○ Identify and justify the use of collaboration tools to support team communication
and document management.
● Team Roles & Responsibilities:
○ Define the roles and responsibilities of each team member (if applicable) to ensure
clarity in task assignments.
● Management Practices:
○ Explain how tasks, documents, and project progress will be managed using the
selected tools.
○ Conduct and document regular, at least three-minute, meetings using the provided
Meeting Minutes template to record key decisions, discussions, and action points.
● Development Approaches
○ Research and justify various software development approaches, including
Waterfall, Agile, and WAgile, that are applicable to your project.
● Quality Assurance Focus:
○ Briefly describe how communication methods and collaborative efforts will support
quality assurance processes throughout the project.

2.2 Project Planning

● Gantt Chart & Timeline:

○ Develop a Gantt Chart outlining project tasks, start/end dates, and dependencies
to provide a clear project timeline.
● Budgeting:
○ Prepare a budget estimating costs for software tools, training, hosting services,
and any other necessary resources.
● Project Management Skills:
 ○ Apply project management techniques to plan and conduct the development and
implementation of the software engineering solution.
● Risk & Quality Management:
○ Incorporate risk management strategies and quality assurance practices to ensure
the project meets its objectives and maintains high standards.

2.3 System Modelling

● Modeling Tools & Techniques:

○ Create system models that include:
■ Data Flow Diagrams (DFDs): Illustrate how data moves through the system.
■ System Flowcharts: Show the logical process flows within the system.
■ Wireframes: Plan the user interface and user interactions.
● Back-End Engineering Contribution:
○ Explain how back-end engineering supports the overall ease and success of the
software development process.
● Quality Assurance in Modelling:
○ Demonstrate how the use of modelling tools contributes to the quality assurance of
the software engineering solution by ensuring that system components are well-
defined and integrated.

Stage 3 - Producing and Implementing (35 marks)

3.1 Design and Development

System Design and Development:

● Front-end: Develop and implement a user-friendly interface (UI) that supports secure and
intuitive data input and interaction..
● Back-end: Implement the system logic, data processing, and storage components (e.g.
databases and server-side functions), ensuring data integrity and security.
● Architecture: Present a clear system architecture (e.g. client-server model) that outlines
how components interact and where data flows.
● Algorithm Documentation: Annotate your code and interface to show how they reflect
the design developed in Stage 2.3. Where design decisions evolved, justify the changes.
 ● Version Control: Utilise version control systems (e.g., Git) to track changes and manage
code revisions.

3.2 Implementation and Integration

● System Integration: Explain how the system will achieve hardware/software

compatibility and integrate with APIs or third-party services if applicable.
● External Documentation: Develop user manuals or tutorials that are appropriate.

3.3 Risk Analysis and Cybersecurity

● Cybersecurity Risks: List and briefly explain the potential security threats that your
proposed system could face.
● Write a Security Summary Report: In your report, show your understanding of web
vulnerabilities and explain how your system protects against them. Your report should:
1. Identify vulnerabilities you considered in your login system.
2. Explain the techniques you used to protect against them (e.g., hashing
passwords, sanitising input) and show evidence.
3. Justify your approach by explaining why your chosen techniques are effective and
appropriate for your system.
● Mitigation Strategies: Outline specific actions and best practices you applied to reduce
risks.

3.4 Logbook and Annotations

● Project Logbook: Maintain detailed documentation of project progress, challenges, and

solutions.
● Annotated Screenshots: Include annotated screenshots that showcase key system
features and development milestones where applicable.
Stage 4 - Testing and Evaluating (25 marks)

4.1 Testing and Validation

● Test Plan Development:

o Develop a comprehensive test plan that evaluates:
▪ Functionality: Verify that each feature behaves correctly.
▪ Usability: Ensure ease of navigation and a positive user experience.
▪ Data Accuracy: Confirm that data processing and outputs are correct.
▪ Path and Boundary Testing: Use test data derived from defined paths and
boundary conditions to cover all scenarios.
▪ Output Comparison: Systematically compare actual outputs with expected
outputs for all tests.
● Methodologies & Code Evaluation:
o Apply rigorous, language-dependent testing methodologies to evaluate and
optimise the code.
o Use language-dependent code optimization techniques to improve performance.
● Feedback Analysis:
o Collect, analyse, and respond to feedback from testing sessions to refine and
enhance the solution.
● Success Criteria Comparison:
o Compare the system’s performance against the success criteria outlined in the
problem definition and identified needs.

4.2 System Performance and Reflection

● Effectiveness Evaluation:
o Evaluate how effectively the system solves the identified problem by considering
both qualitative and quantitative metrics.
● Challenges and Solutions:
o Reflect on the challenges encountered during development, including issues
related to code performance, and document the strategies applied to overcome
these challenges.
● Future Enhancements:
o Propose improvements such as:
▪ Additional security features.
 ▪ UI/UX enhancements.
▪ Expanded system functionalities.
● Overall Impact:
o Summarise the overall effectiveness of the software engineering solution,
integrating insights from the testing phase and feedback received.

4.3 Final Presentation

● Final Presentation:
o Develop and deliver a 4-minute project video using presentation software that
includes:
▪ Introduction: An overview of the problem, objectives, and system design.
▪ System Demonstration: A demonstration of the developed solution,
showcasing key features including the user interface, core functionality,
underlying code, authentication processes, data handling, and implemented
security measures.
▪ Reflection: Discussion of project strengths, challenges faced, and future
improvements.

Marking Criteria

● Defining a real-world problem and identifying user needs

● Researching and justifying development methods

● Planning your project with tools like Gantt charts and budgets

● Designing a functional and user-friendly system

● Implementing front-end and back-end features with documentation

● Managing risks and cybersecurity considerations by implementing secure software architecture

practices.

● Testing your system thoroughly and using feedback to improve

● Reflecting on performance and suggesting enhancements

● Presenting your solution clearly in a short video

Project Sequence
Step/Section Week Completed Comment(Optional)

Stage 1 Week 2, Term 2

Stage 2 Week 4, Term 2

Stage 3 Week 8, Term 2

Stage 4 and Final Submission Week 11, Term 2

Marking Guidelines (Holistic)

Grade Marking guideline descriptors
A Demonstrates extensive understanding and application of software engineering
85-100 concepts. Shows strong problem-solving, innovative design, and effective project
planning. Implements all system components with clarity and detail. Evaluates
system performance critically. Communicates solutions professionally.
B Demonstrates thorough understanding with well-organised planning,
70-84 implementation, and documentation. Most system components function effectively.
Some innovation and evaluation are present. Communication is clear and mostly
complete.

C Demonstrates sound understanding with functional but basic implementation. The

50-69 project includes planning and documentation, but lacks depth. Evaluation and
innovation are limited. Communication is partially effective.

D Demonstrates basic understanding of software engineering. Planning is minimal,

35-49 and implementation is inconsistent or limited. Documentation lacks detail, and
evaluation is superficial.
E Demonstrates limited understanding. The project lacks coherence in planning,
34-0 development, and documentation. Significant gaps in knowledge, testing, and
communication.
 Marking Rubric(Analytic)

Part 1 - Identifying and Defining (20 marks)

Criteria Extensive (5) Thorough (4) Sound (3) Basic (2) Limited (1-0)
Identifies a real-world Identifies a relevant Describes a problem or Provides a vague or The problem is unclear
Defining the problem or opportunity problem or opportunity opportunity with minimal poorly supported or unrelated.
problem and clearly with strong using some supporting supporting evidence. problem. User or system Requirements are
requirements evidence (interviews, evidence. Defines clear Identifies users and gives requirements are basic missing, unrealistic, or
case studies, scenarios). but less specific user and general information or incomplete. copied. Lacks
Defines specific user and stakeholder needs. understanding of
stakeholder needs stakeholders.
clearly.

Criteria Extensive (5) Thorough (4) Sound (3) Basic (2) Limited (1-0)
Investigating Comprehensively Effectively compares Describes one or more Identifies an Little or no understanding
implementation investigates and suitable implementation methods with some implementation method of implementation
methods compares methods and explains comparison; justification with limited explanation. methods. The selection
implementation methods how the selected method is present but lacks Justification is minimal or lacks rationale or is
with clear links to project meets project needs and depth or clear linkage to partially relevant. inappropriate.
needs. The method is stakeholder the project or users.
expertly justified with expectations.
evidence of stakeholder
and project alignment.

Criteria Extensive (5) Thorough (4) Sound (3) Basic (2) Limited (1-0)
Identifying Clearly explains and Thoroughly identifies Identifies affected users Provides a limited or Fails to identify relevant
affected supports who is impacted who is affected and or groups with some vague mention of stakeholders, and the
stakeholders using direct evidence provides supporting relevant detail. The stakeholders with explanation is inaccurate
from interviews, case evidence. The analysis of explanation of impact is minimal explanation or or unsupported.
studies, and research. impact is mostly well basic. evidence.
The impact is analysed in developed.
depth.

Criteria Extensive (5) Thorough (4) Sound (3) Basic (2) Limited (1-0)
System Accurately outlines Thoroughly outlines Lists several system Identifies a few Requirements are
requirements critical features, system features and features and users with a requirements or users. missing or unrelated.
and scope functionalities, data users with defined general understanding of The scope is unclear or Lacks understanding of
requirements, users, and boundaries. Most the scope. Some underdeveloped. system scope and
system boundaries. The requirements are requirements are boundaries.
scope is well defined, appropriate and justified. relevant.
and constraints are
clearly justified.

Total Mark

Teacher You demonstrated proficiency in these areas:

Feedback

You need to work on these areas of assessment in future:

Some ideas to help achieve success in these areas include:

Part 2 - Researching and Planning (20 marks)

Criteria Extensive (5) Thorough (4) Sound (3) Basic (2) Limited (1-0)
 Clearly identifies and Selects appropriate tools Lists collaboration tools Mentions basic tools or Fails to identify tools or
Collaboration justifies appropriate tools and gives valid and team roles; some roles with minimal [Link] absent
and with clear reasoning for [Link] team justification is provided explanation and unclear or incorrect.
choice. Clearly defines roles and responsibilities but lacks detail or clarity. link to project needs. No clear management
Management
all team roles with clear, with minor [Link] Describes some Minimal explanation of plan or documented
effective responsibilities task/document management practices management and few or meetings.
aligned to project needs. management using and includes basic poorly detailed meeting Lacks understanding of
Explains and documents selected tools; meeting meeting records. minutes. approaches, ethics, or
effective task/document minutes included with Describes one or more Brief or vague mention of communication needs.
management; includes relevant decisions and development development method or
detailed, regular meeting [Link] approaches and ethics and minimal
minutes (3+), clearly development addresses basic ethical stakeholder engagement
outlining actions and key approaches and issues and plan.
[Link] discusses some communication
compares Waterfall, social/ethical concerns strategies.
Agile, WAgile; integrates and gives reasonable
relevant social/ethical strategies for
issues; outlines strong stakeholder
communication communication.
strategies and QA
contribution.

Criteria Extensive (5) Thorough (4) Sound (3) Basic (2) Limited (1-0)
Project Planning Develops a detailed Provides a Gantt chart A Gantt chart includes The timeline or budget Incomplete or missing
Gantt chart with all tasks, with most tasks and main tasks and the lacks clarity or detail and Gantt chart and/or
accurate dates, and dependencies.A budget is basic with few dependencies are budget.
dependencies. reasonable and mostly some omissions. shown. Poor planning with little
Comprehensive budget complete budget. Shows understanding of Attempts planning but to no risk or QA
covering all potential Applies suitable project planning methods; lacks detail in risk or QA consideration.
costs. management strategies; includes basic risk/QA areas.
Applies advanced project risk and quality are considerations.
management techniques mostly considered.
and integrates risk
assessment and QA
planning seamlessly.

Criteria Extensive (10-9) Thorough (8-7) Sound (6-5) Basic (4-3) Limited (2-0)
Modelling Tools Creates accurate, Models are mostly Some modelling tools Limited use of modelling No meaningful modelling
detailed DFDs, system correct and complete, are used with a basic tools; diagrams may be or understanding is
flowcharts, and with a clear link to project structure and incomplete or unclear. shown.
wireframes clearly components. understanding. Vague or limited No explanation of the
aligned to system Describes the back-end Some understanding of explanation of the back- back-end role or QA.
functions. role and how modelling back-end contribution; end or QA link to
Explains how back-end aids QA with moderate mentions QA in basic modelling.
engineering contributes clarity. terms.
to overall project success
and QA; models support
integration and
refinement.

Total Mark
 Teacher You demonstrated proficiency in these areas:
Feedback

You need to work on these areas of assessment in future:

Some ideas to help achieve success in these areas include:

Part 3 - Producing and Implementing (35 marks)

Criteria Extensive (15-13) Thorough (12-10) Sound (9-7) Basic (6-4) Limited (3-0)

Design and Builds a well-designed Develops a functional Constructs a working Attempts a basic user Fails to develop or omits
Development and secure front-end and front-end and back-end interface and basic interface or backend core front-end or back-
back-end system with system with good system features. function. Limited end structure. Little or no
intuitive user interaction usability. Provides clear Architecture is present structure or poor evidence of architecture
and strong data integrity. architecture and partial but lacks clarity or implementation. Some or alignment with Stage
Presents a clear client- alignment with Stage 2.3. completeness. Some parts may not align with 2.3. No version control or
server style system Justifies some design reference to Stage 2.3. plans. Minimal use of Git just screenshots of
architecture. Annotations decisions. Version Minimal version control is or annotations.. code..
show how the build control is evident and used.
aligns with Stage 2.3 and mostly used effectively.
fully justify any design
changes. Strong use of
Git to show version
control

Criteria Extensive (5) Thorough (4) Sound (3) Basic (2) Limited (1-0)
System Clearly explains The integration and Basic explanation of Limited understanding of No clear plan for
Integration & integration with implementation method integration and some integration and/or vague integration or method of
Implementation hardware/APIS; selects was well discussed with justification of the deployment method. implementation.
and justifies appropriate minor gaps. implementation method.
deployment method
aligned to project
context.

Criteria Extensive (10-9) Thorough (8-7) Sound (6-5) Basic (4-3) Limited (2-0)

Risk Analysis Clearly identifies and Identifies and explains Describes some Lists basic threats but Fails to identify relevant
and explains multiple relevant relevant threats with common threats; provides minimal threats or provides
Cybersecurity and realistic security appropriate examples; explanation is generally explanation or shows inaccurate/missing
threats (e.g., XSS, SQL demonstrates solid correct but lacks depth or misunderstanding of [Link] little
injection). Shows deep understanding of risk [Link] [Link] or no understanding of
understanding of [Link] most vulnerabilities and some security concepts at a web vulnerabilities or
potential impact on relevant vulnerabilities protections but with basic level; includes [Link]
[Link] outlines and associated limited explanation or generic or partially justification or misleading
major web vulnerabilities protections; inconsistent links to correct explanations
and comprehensively demonstrates good system [Link] [Link] or [Link] to
explains techniques used understanding of web justification, though generic justification describe effective
to address them (e.g., security reasoning may be partial provided; lacks link to mitigation strategies.
input validation, [Link] or [Link] system [Link]
password hashing). justification for most general strategies, some a few strategies with
Links vulnerabilities techniques; rationale is of which are partially limited application or
directly to implemented mostly appropriate and applicable. detail.
[Link] the use relevant. Explains and
of each security measure applies multiple
with a clear rationale strategies that are
supported by industry appropriate and effective
practices or for risk reduction.
[Link] and
applies several effective
risk mitigation strategies
 and best practices (e.g.,
HTTPS, rate limiting,
code review). Strategies
are realistic and tailored
to the system.

Criteria Extensive (5) Thorough (4) Sound (3) Basic (2) Limited (1-0)

Logbook and Maintains a detailed, Records regular log Provides logbook entries Submits minimal log Logbook is absent,
Annotated consistent logbook that entries with clear with key updates. entries with few or poorly maintained, or
Evidence documents all stages of explanations. Includes Includes some annotated unclear annotations or lacks relevant
development, including annotated screenshots screenshots, but they are screenshots. screenshots and
issues and solutions. that cover most major limited in number or annotations.
Presents well-annotated features of the system. clarity.
screenshots that clearly
demonstrate key
processes and decisions.

Total Mark

Teacher You demonstrated proficiency in these areas:

Feedback
You need to work on these areas of assessment in future:

Some ideas to help achieve success in these areas include:

Part 4 - Testing and Evaluating/Presentation (25 marks)

Criteria Extensive (10-9) Thorough (8-7) Sound (6-5) Basic (4-3) Limited (2-0)
Test Plan Designs and documents Constructs a detailed Outlines a test plan that Attempts a test plan with Demonstrates little or no
Development a comprehensive, test plan covering most addresses key functional minimal detail. Identifies evidence of testing. May
structured test plan that key areas. Applies and usability areas. a few testing aspects but mention feedback or
evaluates all aspects of appropriate testing Applies some testing lacks clarity and depth. testing superficially
functionality, usability, methods and makes techniques. Responds to feedback in without structure or
accuracy, boundary considered use of Acknowledges and uses a limited way. purpose.
conditions, and outputs. feedback to improve the feedback to a basic
Applies and justifies solution. degree.
testing methodologies
and optimisation
techniques. Incorporates
and responds to
feedback critically.

Criteria Extensive (10=9) Thorough (8-7) Sound (6-5) Basic (4-3) Limited (2-0)
System Analyses and evaluates Explains system Describes system Lists limited performance Provides minimal or no
Performance and system performance performance and effectiveness with some outcomes. Mentions evaluation. Fails to
Reflection using qualitative and evaluates effectiveness. supporting evidence. some issues or identify issues or
quantitative measures. Describe challenges and Identifies basic challenges without clear suggest meaningful
Identifies and explains improvements made. challenges and reflection. improvements.
key challenges. Justifies Suggests relevant proposes simple
applied solutions. enhancements. improvements.
Proposes thoughtful,
forward-looking
enhancements.

Criteria Extensive (5) Thorough (4) Sound (3) Basic (2) Limited (1-0)
Final Presentation Delivers a highly Presents a clear and Outlines the project and Attempts to present the Fails to communicate
engaging and well-organised video. key features with a basic project, but lacks clarity, key elements of the
professional video Communicates project explanation. structure, or detail. project. The presentation
(approx. 4 minutes). aims and system Demonstrates the Some features are is disjointed, unclear, or
Explains the problem features accurately. system but with limited shown but not clearly incomplete..
and design clearly. Includes relevant depth or clarity. explained.
Demonstrates the insights and some
system effectively using reflection.
visuals and narration.
Provides deep insights
and reflects thoughtfully
on the process.

Total Mark

Teacher You demonstrated proficiency in these areas:

Feedback
You need to work on these areas of assessment in future:

Some ideas to help achieve success in these areas include:

Student Reflection