Solve a multipart tournament scenario
Read every part before coding
A tournament report needs the stored scores, team totals and a winner. Decide which data is shared and which variables reset for each team. A later part may ask for a reusable function: keep its interface separate from the report's output.
Build a checklist
Your algorithm must read every score, reset each team's total, compare complete totals, preserve the first team on a tie, and print the requested values in order. All-negative totals mean the greatest value must be initialised from an actual team.
Review without a template
Attempt all three parts independently. Before checking, trace a single-team input and a tied result. On paper justify the 2-D array and your comparison operator. Review declarations, bounds, initialisation, state updates and output separately. These are original exam-style tasks, not past-paper transcriptions.
Up to four teams each have exactly three round scores. Choose 1D array, 2D array or single record to store the scores in a grid. Enter 1D, 2D or record.
Read N (1 to 4), then THREE integer round scores per team, team by team. Store a 2-D array, output each team total, then the first highest-scoring team index. Scores may be negative.
Cliquez sur Exécuter pour voir le résultat ici.
Write only FUNCTION Qualified(Total : INTEGER, Limit : INTEGER) RETURNS BOOLEAN. A team qualifies when Total is at least Limit.
Cliquez sur Exécuter pour voir le résultat ici.
Explain your choice of data structure and loop. Identify one boundary case and predict its result. For a subroutine, explain what is returned or changed in the caller.
Saved for this sitting on this browser. Review this yourself or with your teacher; these explanations are not automatically marked.
Review your explanation against these criteria
- My types and data structure match the data and the question.
- I justified the loop and checked its first and last iterations.
- Initial values and rejected operations preserve the intended state.
- My test includes input, purpose and expected result.
- I distinguished returning a value from printing and changing caller state.