School of Computing and Creative Media UOWM – Version 2.5 (28/03/2023)
Bachelor of Computer Science (Hons)
/ Bachelor of Software Engineering (Hons) / Bachelor of Game Development (Honours) / Bachelor of Information Systems
(Enterprise Information Systems) (Honours) /
Fundamentals of Programming / Application Development
XBCS1023N / XBGT1034N / XBCS1143N
Prepared by Bridget Merliza a/p Paul Christopher Archibald Semester July / September 2023
School of Computing and Creative Media UOWMKDU – Version 2.3 (23/12/2019)
Ticket Sales System
Course Title : Fundamentals of Programming / Application Development Course Code : XBCS1023N / XBGT1034N / XBCS1143N
Course Lecturer : Bridget Merliza a/p Paul Christopher Archibald : bridget.p@uow.edu.my
BRIEF
In this assignment, each team will be tasked to develop and implement a console based Ticket Sales System using C++. The Ticket Sales Systems is meant for the SCCA (School of Communication and Creative Arts) of UOW Malaysia. Each semester SCCA holds a theatre performance to showcase its students talents in performing arts. The performance is held in SCCA’s auditorium which has 15 rows of seats with 30 seats in each row. The program should display a screen that shows which seats are available and which are taken.
A sample chart depicting each seat in the theatre is shown below. Seats that are taken are represented by a # symbol and available seats are represented by @ symbol. Your team need not follow this representation.
REQUIREMENTS
A. Functionalities (5 marks)
• User Access : The program should have at least 2 separate users with different roles – Administrator and Manager. As this is a console based system, the patrons will not have access to the Ticket Sales System.
o The administrator will use the system to book the seats, view price list, view details of each booking with price, add details of payment and view payment details.
o The manager will use the system to view overall payments collected for each performance, view total number of seats sold and available at each performance.
• Price List : The program should have a list of prices for the seats according to the rows. Your team may assume the price list. This may be stored either in an array or in a file. The price list should be accessed based on the requirements of the specific users listed above.
• Book Seats: The program should show administrator the seating chart with the seats marked as available / taken. As seats are booked and payment is made, the seating chart will be updated accordingly.
School of Computing and Creative Media UOWMKDU – Version 2.3 (23/12/2019)
• Payment : The program will calculate the amount the patron / customer will have to pay for the total number of seats taken. Actual payment will not be made through the system, rather the details of the payment made is keyed in by the administrator.
• Outputs : All outputs according to the requirements based on user access will only be viewed on the console. Information / Data for the outputs should ideally be retrieved from the files (not database), vectors or arrays.
B. C++ Syntax (10 marks)
Your team should be able to demonstrate the proper use of C++ syntax and concepts to develop the Ticket Sales System. The program should be executable incorporating concepts of structured programming such as functions, selection and iterative control structures and basic programming. The team should observed appropriate naming conventions and use of appropriate C++ features with little redundancy in codes.
C. Additional Features: (5 marks)
• Your team is strongly encouraged to include additional features to enhance the functionality of your program, such as validation of inputs.
• You are also encouraged to include additional features related to the C++ syntax / features which was not covered in class. For these additional features, especially those taken from online sources and / or books, use proper intext references within the codes.
o Refer to the following link for guidance: https://tinyurl.com/mvzpvawb Submission Guidelines:
As this is a group assignment, each group is expected to submit at least one C++ source file. The group should submit header files if these were created by the team.
ASSESSMENT CRITERIA
Solution
o Functionalities : 5 marks o C++ Syntax : 10 marks o Additional Features : 5 marks
DUE DATE: 21 Nov 2023
School of Computing and Creative Media UOWM – Version 2.5 (28/03/2023)
ASSESSMENT RUBRIC (Fundamentals of Programming Sept 2023)
Group Name: ________________
Student Name: ___________________________ Student Id : _________
Student Name: ___________________________ Student Id : _________
Student Name: ___________________________ Student Id : _________
Student Name: ___________________________ Student Id : _________
Functionalities:
User Access Price List
Book Seats Outputs (No of outputs : ________________________)
Payment C++ Syntax:
o Selection control o Iterative control
o Structured programming o Functions
o Appropriate naming conventions o Arrays
Vectors Files
Structures Other features :
Criteria
(0)
Very Poor (1)
Poor (2)
Average (3)
Good (4)
Excellent (5) Functionalities
(5 marks)
Non submission
Only attempted 1 of the 5 functionalities.
Functionalities implemented but with
some major errors
Implemented 2 of the 5 functionalities.
Functionalities implemented but with
some major errors.
Implemented 3 of the 5 functionalities. All
functionalities implemented working with
some minor obvious errors.
Implemented 4 of the 5 functionalities. All
functionalities implemented working
with minor obvious errors.
Implemented all 5 functionalities. All functionalities working with no obvious errors.
School of Computing and Creative Media UOWMKDU – Version 2.3 (23/12/2019)
Criteria
(0)
Very Poor (1 – 3)
Poor (4)
Average (5)
Good (6 – 7)
Excellent (8 – 10)
C++ Syntax(10 marks)
Non submission
Incomplete program.
Error in compilation / execution.
Coded in mixture of C and C++.
Incorporated
Basic program in C++.
Only coded in main function. Repeated codes. Hardly used control structure.
Inappropriate naming conventions.
Basic program in C++.
Coded in functions besides the main function. Some repeated
codes. Some basic control structure. Some
inappropriate naming conventions.
Good use of C++ syntax.
Used one or more features such as vectors, files and
structures besides the functions and main function.
Some repeated codes. Some good use control structure.
Good naming conventions.
Excellent use of the C++
syntax. Used features such as vectors, files and
structures besides the functions and main function. Quite unique codes. Excellent use of control structure. Unique
yet appropriate naming conventions..
Criteria
(0)
Very Poor (1)
Poor (2)
Average (3)
Good (4)
Excellent (5) Additional Features
(5 marks)
No additional
features
At least one additional feature
included and documented.
At least two additional features included and
documented.
At least three additional and unique features
included and documented.
At least four additional and unique features included and
documented.
At least five additional and unique features
included and documented.
