Assessment Notification

Assessment Information
Course Year 12 Software Engineering
Number Assessment Task 3
Name Software Engineering Project (Curtain Call: The final act)
Date Thursday 26th June (Term 2, Week 9), 8:20am
Format Hand In Via Canvas
Weighting 30%
 If you require any variation to any of these details, see your Dean at least one week
before the task.
 You will be penalised if you are absent on the day of the task, or if you miss
timetabled activities on the day of the task, and you do not provide appropriate
documentation to explain your absence.
 If you are absent on the day of the task, you can expect to sit the task immediately
on your return to school.

Task Description
Task Description:
For this project, you will have the opportunity to develop your project management and
programming skills by creating your own software solution with accompanying
documentation. You will be provided with time in class to work on this assessment (1-2
lessons per week). In addition to the time given in class, you are expected to dedicate
time at home to complete the task.

This task will require the completion of three parts:

Part A: Documentation
 Define and prioritise requirements
 Structure Chart
 Data Dictionary
 Algorithms
 Evaluation & Maintenance
 Operating Instructions

Part B: Project Management

 Gantt Chart

Part C: Software Solution

 A software solution of your choice (teacher approval required) that
includes a user interface (UI)

NOTE: See Task Definition section for further detail on assessment content and
requirements.
Submission requirements:
Part A: will be submitted as a PDF file in canvas.
Part B: submitted as a PDF file(s) in canvas. You can submit the Gantt Chart as a
separate file(s).
Part C: will be submitted as a zip file with all project files.
1
Assessment Notification

Task Definition:

Part A: Documentation (35 marks)

Using AI for Learning Tasks: Student Hub

Use the following headings to help plan and present your documentation.

 A.1 - Pre Development: Define and prioritise requirements

o Project Summary (approx. 100-150 words)
 In your own words, provide an explanation of what the
program will do and how you will get it to do so.
o Project Requirements (approx. 200-300 words)
 Identify and specify the core requirements of the solution
using criterion-based objectives. These requirements
should be related to functionality (functional) and
performance (non-functional). You can present these in
table form.

Example

Requirement Type Criterion Based Priority (Essential

ID Requirement /Desirable/Optional)

01 Functional The system will Essential

allow users to log in
with valid credentials
and display a
welcome message
within 2 seconds.
02 Non-Functional The system will Desirable
respond to user
input within 2
seconds under a
load of 50
concurrent users.

 A.2 – Pre Development: Structure Chart

o Define modules and their hierarchy, the passing of parameters,
decisions and repetition.

2
Assessment Notification
 A.3 – Pre Development: Data Dictionary
o Choose TWO modules from your structure chart and complete a
planned data dictionary for each module. Refer to page 8 of the SE
Course Specifications Document for an example.
 A.4 – Pre Development: Planned Algorithms
o Create ONE high level algorithm in pseudocode depicting the
mainline of your software.
o Choose ONE module (subroutine) from your structure chart and
document the logic with a pseudocode algorithm. This subroutine
must have:
 Parameter(s) passed into it
 Parameter(s) returning out
 The manipulation of a data structure (e.g. Array (List), Array
of Records, Class, File etc).
 A.5 – Post Development: Evaluation & Maintenance
o Comparison of Final Project to Initial Requirements (approx.
300-350 words)
 Create an organised table comparing the final project to all
requirements listed in A.1.
 Indicate whether each requirement was met, partially met,
or not met, and include notes on why.
Example:
Requirement Met? (Yes/No) Justification
Users should be Yes Works with valid
able to log in credentials
System should No Responds in 3-4
respond in under seconds under heavy
2 seconds load

o Effectiveness of the Software Solution (approx. 300-350 words)

 Evaluate the solution based on the following:
 Requirements being met/not met.
 Usability
 Reliability
 Maintainability
 Identify areas for improvement for future development.
o Discussion of social, legal and ethical issues within your
project (approx. 300-400 words)
 Document at least ONE of each: social, legal and ethical
considerations that you deem to be significant for your
project during development and post implementation. Areas
to explore may include but not limited to:
 Copyright & Intellectual Property
 Security
 Ergonomics
 Inclusivity
 Privacy
3
Assessment Notification
 A.6 – Post Development: Operating Instructions

Provide instructions to the user to operate your software/system. This

should be in video form. Some things to include:
o step novice users through the operation of the program
o provide step by step instructions on accessing and operating your
software/system.
o demonstrate key functionality of the program with step by step
instructions.

Part B: Project Management (5 marks)

Using AI for Learning Tasks: Student Hub

 B.1 – Gantt Chart

o Show the difference between your planned and actual timings of
the project in your Gantt Chart.

Part C: Software Solution (60 marks)

Using AI for Learning Tasks: Student Hub

You have freedom to create a software solution of your choice using a general
purpose programming language (GPL).

Before starting, your proposal must be approved by your teacher. Additionally, you
need to set up a working folder for your code and preferably implement distributed
version control (e.g. GitHub).

C.1 - Source Code:

You have limited time to develop your software solution, so careful planning and
scoping are essential. The best solutions are not necessarily the longest but are
well-structured, efficient, and meet the needs of users. Your software solution will
need to:

4
Assessment Notification
 use structured programming techniques:

o Deliberate and thoughtful modular coding design

o Elegant and structured coding design.
o Thoughtful development using an OOP approach (e.g. appropriate
use of class design)
o Effective internal and intrinsic documentation
o Secure code practices that minimise vulnerabilities where
appropriate
o Anticipating errors and using exception management to gracefully
handle errors.
o Effectives use of libraries
o Effective design and use of self-designed/custom functions

 include complex data types and data structures

o The use of at least TWO appropriate complex data structures (e.g.
2D arrays, lists, stacks, trees, dictionaries)
o Use of files (sequential and/or relative) demonstrating reading and
writing.

C.2 – Running Program:

 software is intuitive and easy to run

C.3 – Interface and the experience

 ease of use
 consistent placement of screen elements
 use of menus
 navigation between screens
 appropriate for target audience
 satisfies screen design principles
 appropriate use of graphics

Syllabus Outcomes
 applies structural elements to develop programming code SE-12-03
 explains the social, ethical and legal implications of software engineering on the
individual, society and the environment SE-12-05
 justifies the selection and use of tools and resources to design, develop, manage and
evaluate software SE-12-06
 designs, develops and implements safe and secure programming solutions SE-12-07
 tests and evaluates language structures to refine code SE-12-08
 applies methods to manage and document the development of a software project SE-
12-09

5
 Assessment Notification
Part A: Documentation: (35 marks)

0 1 2 3 4 5
Define and  N/A ❑ Provides a brief or ❑ Provides a reasonable ❑ Provides a clear,
Prioritise unclear explanation explanation of the comprehensive, and logically
Requirements of the program’s program’s purpose and structured explanation of the
purpose and operation, but with minor program’s purpose and
operation. Lacks gaps in clarity or depth. operation, including how it
detail or logic in Explanation of how it will will be achieved.
describing how it will be achieved is present but
be achieved. not fully detailed.
 N/A ❑ Identifies some ❑ Identifies most core ❑ Accurately identifies and
functional and non- functional and non- specifies all core functional
functional functional requirements and non-functional
requirements, but using criterion-based requirements using precise
with noticeable gaps objectives. Minor gaps in criterion-based objectives.
in accuracy, clarity, or clarity or relevance of Requirements are clearly
relevance. requirements. linked to the program’s
intended functionality.
0 1 2 3 4 5
Structure  N/A ❑ Structure chart ❑ Structure chart shows ❑ Structure chart shows ❑ Structure chart shows ❑ Structure chart shows
Chart shows little to no limited decomposition into moderate decomposition mostly logical evidence of thoughtful
evidence of modules, with several into reusable modules, but decomposition into decomposition into
decomposition into modules handling multiple some modules may handle reusable modules, with reusable modules, with
logical modules. tasks or lacking clear multiple tasks or overlap. most modules performing each module performing a
Parameter passing is purpose. Parameter passing Parameter passing is present a single, well-defined single, well-defined task
incorrect or missing. but inconsistent or task. Parameter passing is (achieves one task per
is limited or inconsistent,
Decisions and incomplete. Some key mostly logical, but there subroutine). Parameter
with missing or unclear
repetition structures decisions and repetition may be minor gaps or passing is logical and
are absent or entirely return values. Few key structures are shown, but inconsistencies in includes the returning of
inaccurate. decisions and repetition with gaps or unclear logic. returning values. Most values where appropriate.
structures are shown, and key decisions and Key decisions and
logic is unclear or flawed. repetition structures are repetition structures are
shown with minor clearly represented and
inaccuracies. accurately integrated.

6
 Assessment Notification
0 1 2 3
Data  N/A ❑ Data dictionaries ❑ Data dictionaries for both
Dictionary show limited or modules follow the NESA
inconsistent format accurately, with
adherence to the clear and consistent
NESA format. structure.
 N/A ❑ Variables and data ❑ Variables and data
structures are mostly structures are well planned,
appropriate but may appropriate for the task,
lack depth or and clearly linked to module
consistency. Most functionality. All fields (e.g.,
fields are correctly name, type, purpose, range)
completed with are correctly completed
generally accurate with accurate details.
details.
0 1 2 3 4 5
Algorithms  N/A ❑ High-level ❑ High-level algorithm ❑ High-level algorithm is
algorithm is depicts the mainline flow of well-structured and logical,
incomplete or the software with minor clearly depicting the mainline
contains major logical gaps or inconsistencies in flow of the software. Control
flaws. Control logic. Most control structures (sequence,
structures are used structures are used selection, iteration) are
incorrectly or correctly used. Pseudocode
correctly. Pseudocode
missing. Pseudocode is clear, follows NESA
mostly follows NESA
does not follow NESA standards, and is easy to
standards or is standards but may have follow.
unclear. minor formatting issues.

 N/A ❑ Subroutine ❑ Subroutine algorithm is ❑ Subroutine algorithm is

algorithm is logical but may have minor well-structured and logical.
incomplete or contains gaps or inconsistencies in Parameters are passed in and
major logical flaws. returned correctly. The
parameter handling or data
Parameter handling or chosen data structure is
structure use. Pseudocode
data structure use is appropriate and effectively
incorrect or missing. mostly follows NESA
used. Pseudocode follows
Pseudocode is unclear standards with minor
NESA standards and is easy
or does not follow formatting issues.
to follow.
NESA standards.

7
 Assessment Notification
0 1 2 3
Evaluation &  N/A ❑ Completes a table ❑ Completes a table ❑ Completes a clear and
Maintenance comparing some comparing functional and well-organised table
requirements from non-functional comparing functional and
A.1 but with some requirements from A.1. non-functional requirements
gaps or inaccuracies. Indicates whether each from A.1. Accurately
Notes are provided indicates whether each
requirement was met,
but may lack depth or requirement was met,
partially met, or not met,
relevance. partially met, or not met,
with relevant notes.
with clear and relevant
notes.
 N/A ❑ Evaluation is brief ❑ Evaluates the solution ❑ Thoroughly evaluates the
or incomplete. Few based on most criteria, but solution based on all five
criteria are with minor gaps or criteria (functionality,
addressed, and areas inaccuracies. Some areas performance, usability,
for improvement are for improvement are reliability, maintainability).
unclear or not Clearly identifies specific
identified but may lack
identified. areas for improvement or
detail.
future development.
 N/A ❑ Provides a brief or ❑ Provides a reasonable ❑ Provides a thoughtful and
superficial analysis analysis of social and well-structured analysis of
with limited ethical considerations with social and ethical
connection to the clear links to the project. considerations directly
project. Discussion is Some insights into the related to the project.
vague or lacks impact on the project’s Discussion demonstrates a
meaningful insights deep understanding of the
design and use are
into the project's implications and how they
provided, but analysis may
design and use. affect the project’s design
lack depth. and use.
0 1 2 3 4 5
Operating  N/A ❑ Poorly structured ❑ Limited detail and ❑ Instructions are present ❑ Clear and mostly ❑ Clear, detailed, and well-
Instructions or incomplete. Little organisation. Instructions but incomplete. Video may organised. Instructions for organised. Step-by-step
to no guidance on are incomplete or unclear. not fully align with all installation and operation instructions for installation +
program functionality, the logic of the are mostly complete with operation are comprehensive
Video only demonstrates and easy to follow. Video
functionality. basic functionality. explanation is unclear or minor gaps. Video is relevant
effectively demonstrates how
makes assumptions. and supports most key to use all key functions.
functions.

8
 Assessment Notification

Part B: Project Management (5 marks)

0 1-2 3-4 5
Gantt Chart  N/A ❑ Gantt chart is incomplete or ❑ Gantt chart is mostly complete with ❑ Gantt chart is accurate, complete, and well-
contains major gaps (e.g., several minor gaps (e.g., missing 1–2 key stages). organised. Includes all key stages and clearly
missing stages). Planned vs actual Planned vs actual timelines are shown but distinguishes between planned vs actual
timelines are unclear or not may have minor inconsistencies. timelines. Logical sequencing and appropriate
included. task duration are shown.

Part C: Software Solution: 60 marks

 0 1-4 5-8 9-12 13-16 17-20

Programming  N/A ❑ Code is not ❑ Code is partially ❑ Code shows reasonable ❑ Code is mostly modular ❑ Code is highly modular
Techniques modular or modular but lacks modularity and structure. and well-structured. Most and well-structured. Each
structured. Modules consistent structure. Some modules perform modules perform a single task module performs a single,
are absent or poorly Modules are poorly multiple tasks or lack clear with clear organisation. Code well-defined task. Code is
defined. Code flow is organised or perform separation. Code follows demonstrates logical flow but elegantly designed with
unclear and multiple tasks. Code flow logical flow but with gaps in may have minor logical flow and consistent
inconsistent, making is inconsistent, leading to consistency or design. inconsistencies in structure or use of coding standards.
the solution difficult unclear logic. standards.
to follow.

❑ Code is ❑ Code is poorly ❑ Code includes reasonable ❑ Code is well-documented ❑ Code is consistently and
undocumented or documented. Few documentation, but some with clear comments clearly documented.
has minimal, unclear comments are present, areas lack clarity. Comments explaining most of the logic. Comments explain the
comments. Variable and they are unclear or cover general logic, but Variable and function names purpose and logic of each
and function names inconsistent. Naming some key parts are are mostly descriptive and module. Variable and
are inconsistent or conventions are weak. undocumented. consistent. function names are
irrelevant. descriptive and consistent.

❑ Code does not ❑ Code shows limited ❑ Code addresses some ❑Code minimises most ❑ Code minimises
address awareness of vulnerabilities but with vulnerabilities with minor vulnerabilities through
vulnerabilities. vulnerabilities. Exception noticeable gaps. Exception gaps. Exception handling is thoughtful coding practices.
Exception handling handling is weak or handling is implemented but present and generally Exception handling is robust
incomplete, leading to inconsistent, leaving some effective, but some errors and integrated, ensuring the

9
 Assessment Notification
is absent or unhandled errors and potential errors unhandled. may not be handled correctly. program handles errors
ineffective, causing possible program gracefully.
the program to fail instability.
unpredictably.
❑ Libraries and ❑ Libraries and custom ❑ Libraries and custom ❑ Libraries and custom ❑ Libraries and custom
custom functions functions are limited or functions are present but functions are used functions are effectively
are absent or poorly implemented. with noticeable gaps in appropriately with minor gaps integrated to enhance
incorrectly Code is repetitive or efficiency or consistency. in consistency or efficiency. program efficiency and
implemented, inefficient due to lack of Some custom functions are Custom functions are mostly functionality. Custom
leading to inefficient reuse. repetitive or not well- reusable and contribute to functions are well-designed,
or poorly structured integrated. code clarity. reusable, and improve code
code. clarity and maintainability

0 1-3 4-6 7-9 10-12 13-15

Complex data  N/A ❑ Data structures ❑ Uses only one data ❑ Uses at least two ❑ Uses at least two complex ❑ Uses at least two
types and structure or misuses complex data structures. data structures. Data
are absent or complex data structures
data them. structures are integrated and
incorrectly effectively. Data structures
structures contribute to program are well-integrated and
implemented. functionality. enhance program
functionality.

❑ File handling is limited ❑ File reading or writing is ❑File handling is mostly ❑ File reading and writing is
❑ File handling is
or unreliable. present with some correct and efficient, but implemented correctly and
absent or completely inconsistencies or there may be minor gaps or efficiently.
ineffective inaccuracies. inefficiencies.

❑ Data structures
❑Weak integration of ❑ Data structures and file ❑ Data structures and file ❑ Data structures and file
and file handling are data structures and file handling are present and handling are mostly well- handling are well-integrated
poorly integrated or handling. Code is somewhat integrated, but integrated. Code is efficient and enhance program
absent. inefficient or with noticeable and consistent but may have functionality. Code is
inconsistent inefficiencies and scalability minor scalability or error- scalable, efficient, and
is limited. handling gaps. consistent under various
inputs. The architecture
allows for easy modification
or expansion.

10
 Assessment Notification
0 1-2 3-4 5-6 7-8 9-10
Running  N/A ❑ Program rarely or ❑ Program produces ❑ Program produces ❑ Program produces correct ❑ Program consistently
Program never produces the correct output in limited correct output for basic output under most inputs and produces the correct output
correct output. cases but frequently fails cases but struggles with conditions, but may fail in under all expected and edge
Reliability is poor, or returns incorrect complex or edge cases. specific edge cases. Generally cases. Runs reliably across
with frequent failures results. Reliability is Reliability is inconsistent reliable but with minor all inputs and conditions
or crashes. under certain conditions. inconsistencies. without failures.
weak or inconsistent.

❑ Program runs
❑ Program is ❑ Program runs but with ❑ Program runs reliably ❑ Program runs smoothly
unstable and crashes inconsistently with occasional crashes or under most conditions but and consistently under all
consistently. Error frequent crashes or performance issues. Error may experience minor crashes expected conditions without
handling is absent or instability under normal handling is present but or performance issues under crashing. Handles errors
ineffective, causing input. Error handling is inconsistent. edge cases. Error handling is gracefully and recovers
repeated failures. weak or incomplete. mostly effective. effectively from failures.
0 1 4-6 7-9 10-12 13-15
Interface and  N/A ❑ Interface is ❑ Interface is difficult to ❑ Interface is functional but ❑ Interface is easy to use ❑ Interface is highly
the confusing or navigate. Screen not intuitive. Some with minor inconsistencies in intuitive and easy to use.
experience incomplete. elements are inconsistencies in screen screen element placement or Screen elements are
Navigation is unclear, inconsistently placed. element placement and navigation. Design is consistently placed and
screen elements are Design is not well- navigation. Design is appropriate for the target well-organised. Navigation is
poorly placed, and aligned with the target somewhat suitable for the audience. smooth and logical. Design
the design is audience. target audience. aligns perfectly with the
unsuitable for the target audience.
target audience.
❑ No meaningful ❑ Feedback is limited or ❑ Provides basic feedback ❑ Provides helpful feedback ❑ Provides clear, helpful,
feedback provided. unclear. Error messages for user actions and errors, for most user actions and and informative feedback
Error messages are are generic or not but it may be vague or errors. Error messages are for all user actions and
missing, misleading, informative. Little inconsistent. Some error mostly clear and informative errors. Error messages are
or confusing. Users guidance is provided for messages lack clarity or but may lack consistency or specific, actionable, and
are left without resolving issues. helpful suggestions. detail. consistent in format and
guidance when issues tone.
occur.
❑ Design shows no ❑ Design shows limited ❑ Design includes some ❑ Design is accessible for ❑ Design is appropriately
consideration of accessibility accessibility for users with users with different needs. inclusive and accessible for
accessibility different needs. users with different needs

11
Assessment Notification

This is a blank page

12