Programming Assestment
Programming Assestment
Criteria
Unit code and name
ICTPRG302 – Apply introductory programming techniques (1)
Student details
Student number
881440194
Student name
Ryan Moller
Assessment declaration
Note: If you are an online student, you will be required to complete this declaration on the
TAFE NSW online learning platform when you upload your assessment.
written for me by any other person except where such collaboration has been
authorised by the Teacher/Assessor concerned.
Assessment overview The objective of this assessment is to assess your knowledge and
performance in creating simple programs using introductory
programming techniques.
Assessment event
2 of 2
number
Instructions for this This is a project-based assessment that assesses your knowledge
assessment and performance of the unit.
4. Testing
5. Program debugging
Assessment Checklist
What do I need to do To achieve a satisfactory result for this assessment you must
to achieve a answer all the questions correctly.
satisfactory result? If a resit is required to achieve a satisfactory result it will be
conducted at an agreed time after a suitable revision period.
What do I need to • TAFE NSW student account username and password. If you
provide? do not know your username and password, contact your
campus or service centre on 131601.
• Reference documents.
What the Access to this assessment and learning resources, including the
Teacher/Assessor will student workbook and any supporting documents or links.
provide Equipment/resources, including:
To complete this part of the assessment, you are required to evidence your participation in
an interactive role-play. This will be achieved by viewing an interactive video and then
capturing your responses in a recording.
Refer to the Observation Checklist to understand what skills you need to demonstrate in this
section of the assessment. This checklist outlines the assessment criteria your
Teacher/Assessor will be marking you on.
Once completed, the recorded evidence will be submitted via the online platform to the
Teacher/Assessor for marking.
This digital recording may be either an audio file (sound only) or video file (video and audio).
You may use your computer webcam and capture software or your mobile phone. Ensure
you have access to the required equipment and resources.
If space or bandwidth is limited, create an audio file rather than video. Video file uploads are
limited to 1Gb.
TIP: The following may be helpful: video recording instructions (pdf). This one-page
includes useful tips, links to resources, and a demonstration video.
Refer to the scenario outline and start with task 1.1 to complete this assessment part.
Login – for users who have previously registered. Username and password to be
checked for validity.
Register – create a new user account.
Passwords – new users given the option to enter their own password or generate
one.
Generated passwords – user given the option to choose the password character
types – numbers, symbols or letters. The default password length should be applied,
but users should also be allowed to choose how many characters
Save file – usernames and passwords should be saved to a text file accounts.txt
Exit – delay for 2 seconds before exit
View accounts – to display user account information from the accounts.txt file
(assuming that only admin have access to this program).
You will need to interview your supervisor, Christina Kaiser to get all of the information you
need and clarify the details of the project.
For the purpose of this assessment, an interactive conversation featuring Christina Kaiser has
been pre-recorded. Refer to Task 1.1 – interactive video roleplay.
To complete this task, you will need to access and view this interactive video.
Look at the partially completed software design document, so you know what details
are missing from the project brief.
You will need to ask Christina three questions regarding the project. Be clear and
specific in your request for each piece of information and use correct terminology – it
is not enough to say, 'what about passwords?' and assume they will know what you
mean.
See the table below for a list of what these questions should be about and in what
order you should ask them. As this is a pre-recorded video, you will need to ask the
questions in the same order as they appear in the table below.
Use this table to prepare and write down your questions to remind yourself of what to ask:
Table 2 Questions template
Confirm the format of the passwords What is the appropriate formal setting to
to be generated generate the password.
The interactive video will have three pause points where you will ask your questions to
Christina Kaiser. You may submit your three questions within one recording or separate
files. If in one recording, leave a 10 second gap between your questions so the assessor can
clearly identify your three different questions.
Recording process:
The video will play, Christina will speak, and a message will appear asking you to
record your question. Press pause on the video.
Use your device to start recording and proceed to record your first question.
Repeat this process until you have recorded all three questions.
At the end of the interactive roleplay, you have the opportunity to play back your recordings.
If you are not happy with your recordings, you can restart the interactive video and re-
record your questions.
If you are happy with your recordings, save the file(s), upload in the space provided and click
‘Submit’.
Once you have met with Christina and confirmed the requirements of the project, complete
the required sections of the Gelos Software Design Document.
Before commencing on your design, it’s a good idea to refresh your memory on the rules of
coding. In the space provided in the Gelos Software Design Document (Coding Rules), list five
basic rules for the programming language you are using to complete this project. Include a
brief explanation of each rule (approximately 20-30 words each).
You will need to use variables in your application. In the space provided in the Gelos
Software Design Document (Data Library Variables), list all of the variables needed for your
design and identify how these variables will be used.
For each of the operators and expressions to be used in your program, nominate the scope
for that variable. Record these details in the space provided in the Gelos Software Design
Document (Variable Scope). For example: global, username.
To enable testing of the program once it has been created, a data file containing test data
has been provided. Inspect the file accounts.txt to familiarise yourself with this data. These
details have already been recorded in the Gelos Software Design Document (Program Test
Data).
1. Iterate through the accounts.txt file to read each record. Use a logical
operator in the iteration, either when entering or exiting the loop.
2. Use a logical operator to allow the users to select a menu option using either
upper-case or lower-case characters (for example: a or A).
Paste a copy of the pseudocode or flowchart in the space provided in the Gelos Software
Design Document (Program Algorithm).
Code the algorithm in the programming language you are learning in this unit, using the
correct syntax, including:
1. A comment at the very top of the program that includes your name, date and
purpose of program.
4. For saving (write) and viewing (read) account details using file (accounts.txt),
make use of control structures (selection and iteration as required).
5. Use expressions, constructs and logical operators to display main menu, log in,
generate random password and create accounts. Remember to allow the users to
select a menu option using either upper-case or lower-case characters (for
example: a or A).
Paste a copy of the program code (or blueprints) into the Gelos Software Design Document
(Program Code).
Now that you have designed and created the program, you will need to present it to your
supervisor for feedback and approval. Submit these assessment pages and your Gelos
Software Design Document via the online learning platform and await feedback before
proceeding with the testing.
Table 3: Feedback
Once you receive the feedback, make any changes or modifications that were recommended
and update your Gelos Program Design Document (Changes Required from Feedback) to
record the changes made.
Note to student – if you have some spare time while awaiting feedback, you can complete
the small programming task in Part 5 of this assessment.
Test and record the results of your testing in the Software Test Report section of the Gelos
Software Design Document. Be sure to include tests for all four menu options, as well as for
menu options that do not exist, for example, try entering Q and test the results.
For each test, take a screenshot and save the image using a suitable file name. Record the
filename in the Screenshot Filename column of the Software Test Report table.
When all testing is complete, create a zip file containing all of your screenshot images. Name
this file YourName_Testing.jpg for inclusion in your final submission.
Now that you have completed your program and testing, you will need to evaluate your
solution and ensure it meets the specifications requested by the client. In the Software
Evaluation section of the Gelos Software Design Document, complete the table with the
specification and the evaluation of your solution.
Complete the programmer’s checklist in the Gelos Software Design Document to ensure you
have completed all tasks.
The trainee was asked to create an application that determines the average mark for a
student based on their marks from five different subjects (see code below).
• Ask the user to input the marks for the five subjects in a list/array.
• The program must ensure that the marks are between 0 and 100
• Display the list/array of marks entered.
• Find the sum of all the marks in the list (all five subjects) and display the output
as:
- The sum of your marks is: [sum]
• Find the average of all the marks in the list (all five subjects) and display the
output as:
- The average of your marks is: [average mark]
#read 5 inputs
print(marksList)
sumOfMarks = sum(marksList)
averageOfMarks = sum(marksList)/5
#display results
Expected Expected
mark1 mark2 mark3 mark4 mark5 Comments
sum average
10 12 16 14 18 70 14
Exception
A B D A C n/a n/a error on
input
17 17 199 20 -17 90 18
2. Use debugging and problem-solving techniques to detect and correct errors in the
code (use the test cases to confirm the design specifications). This must include
examining the contents of the variables. Document the changes you made by
including comments in the code, using the correct syntax.
Table 6: Corrected code for marks program
Debugging screenshots
Submission
Now that you are all done, you need to submit your files, including:
TASK/ Instructions
STEP S U/S Assessor Comments
#
TASK/STEP
Instructions S U/S Assessor Comments
#
Date of Observation:
Student identified
Assessors are to record their observations in enough detail to
Part 2 programming standards and
☐ ☐ demonstrate their judgement of the student's performance
Task 2.1 guidelines according to task
against the criteria.
requirements
syntax in sequence,
selection and iteration
constructs
Student created code using
language data types,
Part 3
operators and expressions ☐ ☐
Task 3.1
and developed application to
meet program specification
1. Student added comment to
top of code with name,
☐ ☐
date and purpose of
program
2. Student used appropriate
☐ ☐
library functions
3. Student clarified meaning
of code using commenting ☐ ☐
techniques
4. Student used selection and
iteration constructs using
☐ ☐
logical operators and made
use of control structures.
☐ ☐
5. Student creates expressions
in selection and iteration
constructs using logical
Part 4 ☐ ☐
The student used debugging
Assessment outcome
Satisfactory
Unsatisfactory
Assessor feedback
Has the assessment declaration for this assessment event been signed and dated by the
student?
Are you assured that the evidence presented for assessment is the student’s own work?
Comments: