Management Information SystemsCategory: Collaborative Objective Test & Team Performance (Role Play)
Type: Individual or Team
Two (2) parts: an objective test and interactive role play or presentation. A 60-minute objective test will be administered onsite at the NLC. Team competitors will take one (1) objective test collaboratively.
Objective Test Competencies: Systems Analysis & Design (Systems Development Life Cycle); Database Management and Modeling Concepts; Object Oriented Analysis and Design; User Interfaces; System Controls; Defining System and Business Requirements
Case: A decision-making problem outlining a small business’ environment and needs. Competitors will analyze the situation and recommend an information system solution to address the issues raised.
Skills: The ability to design and implement an information system solution to effectively manage vast amounts of information is a valuable skill that leads to the success of many business entities today. The use of technology to develop these information systems plays a crucial role in a business’ ability to compete in today’s business environment. This event provides recognition for FBLA members who demonstrate an understanding of and ability to apply these skills.
- Flip charts provided.
Performance Guidelines—Final Round
- Two (2) 4"x6" note cards will be provided to each competitor and may be used during event preparation and performance. Information may be written on both sides of the note cards. Note cards will be collected following the presentation.
- No additional reference materials allowed.
- Turn off all electronic devices.
- Individuals/teams should introduce themselves, describe the situation, make their recommendations, and summarize their cases.
- If participating as a team, all team members are expected to actively participate in the performance.
- All questions raised in the case must be addressed during the presentation.
- Objective test scores will be used to break a tie.
- Final performances are not open to conference attendees.
Penalty Points Deducted by Judges
- Five (5) points are deducted if competitors do not follow the dress code.
- Five (5) points may be deducted for not following guidelines.
Fifteen (15) competitors/teams—or an equal number from each section in the preliminary round—will advance to the final round. When there are more than five sections of preliminary performances for an event, two competitors/ teams from each section will advance to the final round.
In the case of team events, all team competitors are expected to actively participate in the performance.
Competitors cannot be replaced or substituted for prejudged events with the exception of the chapter events—American Enterprise Project, Community Service Project, and Partnership with Business Project.
All competitors must comply with the FBLA‑PBL dress code.
Prejudged materials and résumés will not be returned.
- The following will be provided for the final round of technology presentation events that allow viewing: screen, power, table, and projector. It is up to final round competitors to decide if they wish to use the provided technology.
- Competitors utilizing Apple products or other devices that do not have a VGA port or HDMI will need to provide their own adapters.
- Internet access will be provided for:
- 3-D Animation
- Coding & Programming
- Computer Game & Simulation Programming
- Digital Video Production
- Electronic Career Portfolio
- Mobile Application Development
- Public Service Announcement
- Social Media Campaign
- Website Design
- Internet access may not be WiFi, so competitors should plan appropriately when selecting laptops/tablets on which to present.
- Demonstrate excellent verbal communication.
- Display effective decision-making and problem-solving skills.
- Express self-confidence and poise.
- Work well as a team when applicable.
- Exhibit logic and systematic understanding.
- Conduct a professional business presentation.
- Answer questions effectively (when applicable).
Penalty Points Deducted by Judges
- Five (5) points are deducted if competitors do not follow the dress code.
- Five (5) points may be deducted for presentations over the allotted time.
- Five (5) points may be deducted for not following guidelines.
- Preliminary performances are not open to conference attendees.
- Final performances may be open to conference attendees, space permitting (with the exception of interview and prep/case events). Finalists may not view other competitors’ performances in their event.
- Recording performances is prohibited.
- All electronic devices must be turned off.
- All attendees must follow the dress code and wear their name badges.
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 FBLA national and state dues by 11:59 p.m. Eastern Time on March 1 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 four (4) entries in all events except LifeSmarts, Virtual Business Finance Challenge, and Virtual Business Management Challenge.
- Each competitor can only compete in one (1) individual/ team event and one (1) chapter event.
- 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 (American Enterprise Project, Community Service Project, and Partnership with Business 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.
- 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 (American Enterprise Project, Community Service Project, Local Chapter Annual Business Report, and Partnership with Business Project).
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.
Tips for Events Involving a Case Study or an Interactive/Role Play
- Students will be given a case study and/or role play scenario for review prior to the performance (EXCEPTION: Sales Presentation). Check the event guidelines for the practice time allotted in the particular event. Time varies for the events.
- Participants will be given note cards to write on during practice, and may use the note cards in the performance room.
- Do your homework and look at the performance rating sheet for your event. The judges will be using the rating sheet to score each individual or team.
- In an interactive/role-play event, the judges will interact during the presentation and still might ask questions at the end.
- Review the Performance Indicators when reading the case study or role play scenario.
- If competing as a team, all team members must participate in the presentation.
Sample Practice Materials
- Association of Computing Machinery
- Association for Information Systems
- Decision Science Institute
- IEEE - Advancing Technology for Humanity
- MIS Resources on the Internet
2. Demonstrate knowledge of the system life-cycle approach and identify and explain the steps in the systems development life cycle.
3. Identify the functions of systems analysts.
4. Select basic fact-gathering techniques to be used and conduct a preliminary investigation.
5. Record facts gathered through the system investigation.
6. Define the scope of the systems project.
7. Identify time, technology, and resource constraints.
8. Perform appropriate diagnostic tests
9. Investigate system alerts.
10. Design system output, system input, files, and processing.
11. Analyze the interaction of the operating system and hardware architecture.
12. Justify the communications selections for the system (e.g., single PCs, LANS, and/or WANS).
13. Identify the system components and their relationships.
14. Specify the workflow system.
15. Develop programming specifications and program the system.
16. Test and document the system..
17. Design a framework for evaluating information system function and individual applications.
18. Compare the capabilities of an application with the requirements it is intended to meet.
19. Identify alternative outcomes of the application verification process.
20. Evaluate processes and outcomes including the results and probabilities of errors.
21. Modify inputs, outputs, and processing to refine an application.
22. Determine needed follow-up actions including recommendations for new features or enhancements to existing tools.
2. Identify the uses of a DBMS in business organizations.
3. Demonstrate knowledge of how a DBMS ensures data integrity through transaction-control techniques.
4. Trace the evolution of DBMS models and their implementation.
5. Produce single- and multiple-level control break reports and subtotal and final totals.
6. Write programs that allow the user to make a menu choice, that require statements to be executed multiple times, and that access multiple files.
7. Design an information system within a database environment.
8. Build database applications and distribute data across a distributed DBMS.
9. Analyze/model organizations using Entity-Relationship and Object technologies.
10. Create/update and query a relational database using Structured Query Language.
11. Manage and monitor implementation of a database management system.
12. Identify and document problems and propose solutions that are congruent with application requirements.
13. Apply databases to actual situations and business problems.
14. Create conceptual data models.
15. Identify and select logical and physical structures appropriate for specific applications.
16. Create and normalize a logical data model in accordance with established company policy.
17. Plan, develop and normalize a database schema.
18. Explain the options for converting legacy records to electronic database management systems.
2. Describe the fundamental object-oriented principles and identify the characteristics and uses of object-oriented processing.
3. Describe the object-oriented software development process.
4. Explain the purpose, activities, and artifacts of the following Object-Oriented Software Development workflows: requirements gathering, requirements analysis, architecture, design, implementation, testing, and deployment.
5. Choose an object-oriented methodology that best suits the project.
6. Create a project vision document from the results of interviews and risk analysis.
7. Document the system in the System Requirements Specifications.
8. Create and refine the diagram for a software system based on the System Requirements Specifications.
9. Identify the key abstractions based on the analysis.
10. Describe the Analysis Model, the Architecture Model and the Component (Design) Model.
11. Construct the problem domain model.
12. Create the Analysis Model using Robustness analysis.
13. Distinguish between architecture and design.
14. Create the Architecture workflow artifacts.
15. Create the architecture model for presentation.
16. Create a solution model for GUI and Web UI application.
17. Refine the attributes, relationships, and methods of the Domain model.
18. Apply design patterns (e.g., composite, strategy, observer, and abstract factory) to the Solution Model.
19. Model complex object state using state chart diagrams
2. Describe interface techniques and standards.
3. Demonstrate knowledge of version management and interface control.
4. Assess the impact of changes that affect interfaces.
5. Integrate human factors and user interfaces in visual design.
6. Develop user interfaces.
7. Develop programs that interface with a data store
8. Understand the characteristics of potential users, their tasks, and their environments
9. Relate to the ways in which the users define themselves and their roles (e.g., jobs, tasks, and tools they use).
10. Conduct tasks analysis to review the workflow and other aspects of the user’s job.
11. Interpret the results of tasks analysis.
12. Select techniques that are appropriate to a project and the user’s environment.
13. Analyze and document data by creating representations such as work flows, task hierarchies, and task scenarios.
14. Reorganize results using such techniques as affinity diagrams and insight sheets to clarify relationships
15. Form the design using storyboarding, sketching, and video presentations
16. Test and document user interface usability.
2. Provide technical product support and facilitate the delivery of technical services.
3. Manage inventory and assets.
4. Participate in evaluation of the total system
5. Identify new application requirements within the system.
6. Document performance problems.
7. Analyze historical data to identify trends.
8. Formulate technical procedures.
9. Prepare documentation manuals.
10. Prepare required reports.
11. Apply data structure concepts to the storage and retrieval of data (e.g., map a model, create, and enter records and logical files).
12. Query a database and create reports and/or files from queries.
13. Transfer files between mid-range and microcomputer systems.
14. Implement hardware and software network security solutions (e.g., VPN, SSL, and firewall).
15. Maintain technical industry knowledge.
2. Define the role of Information Systems within strategic plan for the total company.
3. Develop a short-range Information System plan and a continuous improvement plan.
4. Determine functional structures (internal vs. outsourcing).
5. Establish goals and objectives for an Information System.
6. Define mission and critical success factors.
7. Formulate Information System operating procedures.
8. Identify hierarchical and flow models of the organization.
9. Define the roles and function of Information System personnel within the organization.
10. dentify drivers and inhibitors of information technology change in the organization.
11. Describe how information technology affects worker-management relationships.
12. Explain how information technology has contributed to worker productivity and teamwork.
- Information Technology
- Business Management & Administration
- Human Services
- Information Techology
- Law & Public Safety