ITECH1400 Fundamentals of Programming

Learning Outcomes Assessed

The following course learning outcomes are assessed by completing this assessment:

Knowledge:

K1. Identify and use the correct syntax of a common programming language.

K2. Recall and use typical programming constructs to design and implement simple software solutions.

K4. Explain the importance of programming style concepts (documentation, mnemonic names, indentation).

Skills:

S1. Utilise pseudocode and/or algorithms as a major program design technique.

S2. Write and implement a solution algorithm using basic programming constructs.

S4. Describe program functionality based on analysis of given program code. Application of knowledge and skills:

A1. Develop self-reliance and judgement in adapting algorithms to diverse contexts.

A2. Design and write program solutions to identified problems using accepted design constructs.

Assessment Details

The Federation University Australia Robot Wars are about to commence! The competitors are busy training and now it’s time to prepare to sell spectator tickets.
Your task is to design, develop and test a small application for purchasing and recording ticket sales to this event
The assignment is broken up into three main components:

1) Design and model two classes: Ticket and Checkout
2) Create an activity chart which describes the behavior of the ticket sales system
3) Create a computer program that allows a user to interactively purchase a number of tickets, then provides an opportunity to enter some (fake) credit card information to pay for the tickets, and finally, prints out a receipt for the user (to the screen, not on paper). Finally, the program should backup all the transactions into a text file

Part 1: Design and Model Two Classes

This stage requires you to prepare documentation that describes the function of the program and how it is to be tested. There is no coding or code testing involved in this stage.
Requirements:

1) Read all of this assignment sheet first!!!
2) Write an algorithm that describes how the program will operate.
a. All program requirements must be included, even if you do not end up including all these requirements in your program code.
b. The algorithm must be structured logically so that the program would function correctly.
3) Create class diagrams for the Ticket and Checkout classes
Add everything to your Word document.

Part 2: Activity Flowchart

Using either the online website https://draw.io (preferred), or the applications Visio or PowerPoint –create an activity diagram of how the program should operate to successfully purchase one or more tickets, accept payment, print a receipt for the user and backup the transaction to a text file.
Make sure to use the correct symbols in your diagram for starting, processes, decisions/branches, and ending the process.
Remember to do some (fake) checks when the user enters their credit card details e.g. that enough numbers have been entered.
Once you have completed your activity flowchart, add it to your Word document.

Part 3: Computer Program

You are free to design and implement the software however you see fit. Here are some requirements that must be incorporated into your program
1. You must display a welcome message when the program starts. At a minimum, this message should contain the name of your program, the name of the program developer and your student ID.
2. The welcome message should also have a row of asterisks at the top and the bottom, just long enough to extend over the text. Hint: Use a For loop for this.
3. When the user goes to purchase tickets, they should be able to purchase a child, adult, senior or concession ticket(s). Each ticket category should cost a different amount; it’s up to you to choose how much each ticket costs. They should be able to purchase as many tickets (across all categories) as they like
4. When the user goes to finalise their order, the total cost should display on screen. Your program should then ask the user to enter their (fake) credit card details, check the credit card details and, if ‘valid’, display a final receipt.