California Future Business Leaders of America

Your Future Is Our Business


  • Category: Collaborative Objective Event & Team Presentation (Role Play)

    Type: Individual or Team (Section, State and National Competition)

    ELIGIBILITY: No more than one (1) team member may have competed in this event at a prior NLC or have competed more than two (2) years at the national level. A participant may compete as an individual their first year. However, if competing a second year, the participant must be part of a team.

    :  Each local chapter may enter one (1) individual or a team of two (2) or three (3) members. The top five (5) teams or eight (8) with the highest objective test score at SLC will compete in the role play presentation portion of the event. Number of finalists will be determined by December 31.

    NATIONAL: The top four (4) places in state competition will represent California at the National Leadership Conference. NOTE: Some SLC top-10 finalists will become eligible for the national conference as a result of drops. Make sure you get early approval from your parents to attend the National Conference so you will be in a position to say "yes" to your adviser if you are "bumped up".

    OVERVIEW: Two (2) parts: an objective test and interactive role play presentation. A 60-minute objective test will be administered onsite at the Section, State and National Conference. Team competitors will take one (1) objective test collaboratively. The role play part of this event consists of an open exchange between the competitor(s) and the judges throughout the presentation. Finalists will be given a case study and will have 20 minutes to prepare for the role play presentation.

    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.

    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. 
    • 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.

    FINALISTS: The top eight (8) individuals or teams will participate in the role play presentation. 


    Test: 1 hour 
    Prep: 20 min 
    Equipment Setup: N/A 
    Performance: 7 min 
    Warning: 6 min 
    Time Up: 7 min 
    Penalty Over Time: N/A 
    Q & A: N/A 

    JUDGING: Judges will play the role of the second party in the presentation and will refer to the case for specifics. All questions raised during the case must be addressed during the presentation. All competencies in the rating sheet will be addressed in grading.

    Rating Sheet (search for Management Information Systems)


    GUIDELINES: (It is highly recommended that competitors read all guidelines)
    Sequester Guidelines
    General Presentation

    General (All Events)
    General Competitive Event Tips


    Sample Practice Materials

    Sample Case Studies

    Practice Materials


    Format Guide
    Website Resources
    Systems Analysis & Design (Systems Development Life Cycle)
    1. Demonstrate knowledge of the key functions and subsystems of the network system.
    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.
    Database Management and Modeling Concepts
    1. Demonstrate knowledge of the features, functions, and architecture of a database management system.
    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.
    Object Oriented Analysis and Design
    1. Identify and define object-oriented programming terminology
    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
    User Interfaces
    1. Define hardware-software interface issues for a system.
    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.
    System Controls
    1. Set up/maintain user accounts on multiple systems.
    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.
    Defining System and Business Requirements
    1. Identify information technology needed to support given sets of tasks and activities for individuals, workgroups, and the organization.
    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.


    NBEA Standards
    • Communication
    • Information Technology
    • Management
    Career Clusters
    • Business Management & Administration
    • Finance
    • Human Services
    • Information Techology
    • Law & Public Safety