Programming ConceptsCategory: Objective Test
60-minute test administered during the NLC.
Objective Test Competencies: Programming Development Concepts; Programming Structures ; Functions ; Databases ; Classes ; Strings ; Resources ; Randomization ; Arrays ; Refactoring
Objective Test Guidelines
- No materials may be brought to the testing site.
- Electronic devices must be turned off and out of sight.
- Financial calculators may be used for accounting, finance, and analysis & decision making events; calculators will be provided for all other events.
The general event guidelines below are applicable to all national competitive events. Please review and follow these guidelines when competing at the national level. When competing at the state level, check the state guidelines since they may differ.
- Dues: Competitors must have paid PBL national and state dues by 11:59 p.m. Eastern Time on April 15 of the current school year.
- NLC Registration: Participants must be registered for the NLC and pay the national conference registration fee in order to participate in competitive events.
- Deadlines: The state chair, or designee, must register each state competitor on the official online entry forms by 11:59 p.m. Eastern Time on the second Friday in May.
- Each state may submit three (3) individuals in all events requiring only objective tests and two (2) individuals or teams for all events that require a pre-judged or performance component.
- Each competitor can compete in two (2) events.
- Each competitor must compete in all parts of an event for award eligibility.
- A team shall consist of two or three members. Exceptions are Parliamentary Procedure which must be a team of four or five members, and LifeSmarts which must be a team of two members.
Competitors are not permitted to compete in an event more than once at the NLC unless one of the following circumstances applies:
- Modified Events: A competitor may compete in the same event when the event is modified. Note, if the only modification is a name change, competitors may not compete in the renamed event.
- Team Events: One (1) competitor of the team may have competed in the same event at one (1) previous NLC; however, they may not compete more than twice in the event at the national level.
- Chapter Events: Competitors may compete in a chapter event more than once (Community Service Project).
- Individual Entry: A competitor who competed as an individual entry in a team event at the national level may compete in the same event a second time as part of a team, but not a second time as an individual.
- Parliamentary Procedure: Two (2) competitors of the team may have competed in this event at a previous NLC; however, they may not compete more than twice at the national level.
- Pilot Event: Competition in a pilot event does not disqualify a competitor from competing in the same event if it becomes an official competitive event. The participant may compete in another event as well as a pilot event.
- Objective Tests: Ties are broken by comparing the correct number of answers to the last 10 questions on the exam. If a tie remains, the competitor who completed the test in a shorter amount of time will place higher. If this does not break the tie, answers to the last 20 questions will be reviewed and determine the winner.
- Objective and Production Tests: The production test scores will be used to break a tie.
- Objective Tests and Performances: The objective test score will be used to break a tie based on the tie-breaking criteria of objective tests.
- Reports/Projects and Performances: The report/project scores will be used to break a tie.
- Performances: Judges must break ties and all judges’ decisions are final.
- State chair/adviser must register all competitors for NLC competitive events online by 11:59 p.m. Eastern Time on the second Friday in May.
- All prejudged components (reports, websites, projects, statement of assurance) must be received by 11:59 p.m. Eastern Time on the second Friday in May.
- All prejudged projects and reports must be submitted electronically.
- All Statements of Assurance must be submitted online.
- All production tests must be received at FBLA-PBL by 11:59 p.m. Eastern Time on the third Friday in May.
- Desktop Publishing—two (2) copies of the finished product must be uploaded as PDF files by 11:59 p.m. Eastern Time on the third Friday in May.
- All production tests must be uploaded online.
- State chair/adviser may make name changes only (no additional entries) by 11:59 p.m. Eastern Time on the first Friday in June. Competitor drops are the only changes allowed after this date and onsite.
The number of competitors will determine the number of winners. The maximum number of winners for each competitive event is 10. Only one (1) award is given to the schools competing in chapter events (Community Service Project and Local Chapter Annual Business Report).
- Financial calculators may be brought to objective testing and used for any accounting, finance, or analysis & decision making events.
- Certain events may allow the use of additional materials. Please refer to event guidelines.
Americans with Disabilities Act (ADA)
FBLA‑PBL meets the criteria specified in the Americans with Disabilities Act for all participants who submit a special needs form.
Recording of Presentations
No unauthorized audio or video recording devices will be allowed in any competitive event. Participants in the performance events should be aware the national association reserves the right to record any performance for use in study or training materials.
Graduate students may compete in all PBL events.
2. Explain the difference between syntax errors and logic errors.
3. Develop the use of programming tools such as flowcharts, pseudocode, TOE charts, IPO charts, decision(truth) tables, & desk-checking.
4. Utilize and differentiate between the definition of a variable and a constant.
5. Demonstrate the knowledge of the rules for naming variables.
6. Utilize the scope and lifetime of named variables and constants.
7. Differentiate passing variable values ByRef and ByValue.
2. Evaluate and utilize the three major programming structures: sequence, selection(decision) & loop.
3. Develop how to avoid common loop mistakes and common decision mistakes.
4. Utilize a Priming Read within code.
5. Be able to utilize / manage / and identify Conditional, Structural, and Behavioral design patterns. (https://sourcemaking.com/design_patterns ).
2. Differentiate between arguments and parameters.
3. Utilize Getters & Setters (Accessors & Mutators).
2. Create queries, forms, reports, & modules for a relational database.
2. Utilize inheritance.