USITCC South Central Regional

Advancing IT Education & Competition

Connecting students, faculty, and industry leaders.

Explore Past Events

The USITCC South Central Regional Student Conference typically offers several technical competitions for participants to test their skills against the best and brightest IT students in the Region.

Note: Specific rules, tools, and requirements may vary slightly each year. The following descriptions provide a general overview based on past events. For historical details from the Nov 2024 event, please see the 2024 Contest Archive.


Application Development

Showcase your object-oriented design and coding skills in this contest. You'll be asked to build an enterprise-quality solution to a complex coding situation. The world needs you because the world needs talented developers.

Team Composition

Teams may typically be made up of 1–2 people.

Skills and Resources

Successful teams will be skilled at languages like Java, C#, or VB.net and Object-Oriented Principles. Overall teams should generally have knowledge of:

  • Multiple GUI forms, including menu creation
  • User input validation
  • Exception handling
  • Data formats (e.g., JSON)
  • Documenting Code
  • Unit Testing
  • Object-Oriented Principles (ex. encapsulation, inheritance, polymorphism)

Specific allowed IDEs (like Visual Studio Community Edition, Eclipse) and language versions (like Java SE 11) may be specified each year. Check official rules for the specific event.

Protocol

Teams are typically given the problem statement at the beginning of the contest time. Time may be allowed to read the problem statement and ask questions in a common session. Once the Q&A time closes, no further questions may be answered. Each team submits their solution for judging prior to the contest closing time.

Database Design

Databases are at the core of virtually all critical information systems. In this competition, you will flex your database design and SQL muscles to show you’ve got the right stuff to make data work for you!

In this potentially two-part competition, teams are usually provided with a problem statement requiring them to design a database, create an entity relationship diagram (ERD) reflecting their design, and generate SQL code to query and modify the database. Teams may also be asked to construct additional SQL code (DQL/DML) and/or respond to questions about general database design and management issues.

ERDs should typically be created using diagramming software (e.g., Visio, LucidChart). SQL code must generally adhere to standard SQL and utilize specified database systems (like Oracle, MySQL, or MSSQL Server). Participants usually need to bring their own laptops with required software.

Team Composition

Teams may typically be made up of 1–2 people.

Skills and Resources

Successful teams will need skills in database design, entity-relationship modeling, and structured query language (SQL). Participants must generally use specified database systems (e.g., Oracle, MySQL, MS SQL Server). Development suites relying heavily on drag-and-drop may not be allowed. Standard SQL commands are preferred; application-specific commands might result in point deductions.

The competition may contain components like:

  1. Database Design: Submitting an ERD and relational schema (normalized to 3NF).
  2. Data Definition Language (DDL): Writing SQL to create the database structure.
  3. Data Query Language (DQL): Writing SELECT queries.
  4. Data Manipulation Language (DML): Writing INSERT, UPDATE, or DELETE statements.
  5. Knowledge demonstration: Multiple choice or other question formats on database/SQL concepts.
Protocol

Teams are typically given the problem statement at the beginning. A short time may be allowed for general questions about rules, but not specific problem or concept help. Once Q&A closes, no further questions are answered. Solutions must be submitted before the contest closing time.

Network Design

Fast and reliable data networks are the lifeblood of modern business. Prove that you have what it takes to tackle and solve thorny enterprise networking challenges by delivering a design that can accommodate a complex set of communication needs.

Teams typically create a proposal for a network design based on a given scenario. Elements often include LAN design, WAN connectivity, network components, protocols used, security issues, network architecture, and a budget.

Team Composition

Teams may typically be made up of 1–2 people.

Skills and Resources

Successful teams generally need a good understanding of internetworked systems, critical thinking for infrastructure design, budgeting skills, and the ability to create professional documentation (diagrams, written proposals).

No specific software is usually mandated, but diagramming tools (Visio, LucidChart), word processors (Word/PDF output), and internet access for research (specs, pricing) are helpful. Final documents usually need to be in standard formats like Word or PDF.

Protocol

Teams are typically given the problem statement at the beginning. Time may be allowed for general questions. Once Q&A closes, no further questions are answered. Solutions must be submitted before the contest closing time.

Microsoft Office Solutions

Today’s high-tech office environment calls for sophisticated solutions for analyzing and presenting business data. This unique event integrates database (Access), spreadsheet (Excel), presentation (PowerPoint), and word processing (Word) skills to create an end-to-end data management and presentation solution.

Team Composition

Teams may typically be made up of 1–2 people.

Skills and Resources

Successful teams demonstrate creative problem-solving and in-depth knowledge of the MS Office suite. Key skills include:

Word:

  • Formatting text/margins/pages, using clip art/images.
  • Integrating information from other Office apps.
  • Creative writing/editing.

Excel:

  • Formatting worksheets, creating formulas (including nested).
  • Using built-in functions, applying security features.
  • Creating/modifying charts, organizing workbooks.

PowerPoint:

  • Creating/modifying presentations following basic design rules.
  • Adding animation and automating presentation options.

Access:

  • Designing databases (tables, relationships).
  • Importing data (from Excel, text files).
  • Creating forms, queries (static and calculated), and reports based on specifications.

Contestants usually need access to a functioning Microsoft Office suite, as well as Windows PC/Laptop (Not Microsoft Office Online).

Protocol

Teams are typically given the problem statement at the beginning. Time may be allowed for general questions. Once Q&A closes, no further questions are answered. Solutions must be submitted before the contest closing time.

PC Troubleshooting

Computers fail, and quick, knowledgeable help is essential. This competition tests your ability to diagnose and solve common PC issues.

The competition typically involves a knowledge exam covering hardware, software, networking, and security concepts relevant to PC technicians, often similar in style to popular certification exams (like CompTIA A+).

Team Composition

PC Troubleshooting is typically an individual event.

Skills and Resources

The competition focuses on a wide range of skills a PC Technician might encounter, potentially including:

  • Hardware identification and troubleshooting
  • Software installation and configuration
  • Operating system issues (Windows, macOS, Linux basics)
  • Basic networking concepts and troubleshooting
  • Security fundamentals
  • Mobile device concepts (Android/iOS)

The exam usually consists of multiple-choice questions delivered via a web browser. Access to reference materials or the internet is typically prohibited during the exam.

Security

Are you among the guardians of the modern IT galaxy? This competition tests your knowledge and practical skills in cybersecurity.

The event often consists of multiple rounds. A qualifying round might involve a knowledge exam (similar to Security+ or CEH concepts), while top scorers may advance to a hands-on Capture The Flag (CTF) round involving practical security challenges.

Team Composition

Security is typically an individual event.

Skills and Resources

The qualifying round exam may cover topics found on popular certification exams. Participants should be knowledgeable with topics and potentially tools such as (list is not exhaustive):

  • IP configuration and testing
  • Database/Web Server/Web Application Vulnerabilities
  • Social Engineering
  • Password Cracking Concepts
  • Penetration Testing Tools/Methodologies
  • Open Source Intelligence (OSINT)
  • Log Analysis / Network Traffic Analysis
  • Reconnaissance Techniques
  • Cryptography Basics
  • Vulnerability Identification and Exploitation Concepts
  • Security Regulations/Laws (e.g., PCI, HIPAA basics)
  • Physical security/access control concepts
  • Policy implementation basics (e.g., in Windows)

The CTF round requires practical application of these skills using various security tools and techniques. Internet access might be allowed during the CTF portion for research, but specific rules apply.

Systems Analysis & Design

Businesses need skilled analysts to understand complex problems and design effective solutions. Use traditional (structured) or modern (agile/object-oriented) tools to model your innovative solution to a given business scenario.

Teams are typically given a business problem statement and a timeframe to analyze the requirements and design a system. Any widely used methodology (e.g., Object-Oriented Analysis, Structured Analysis, Prototyping) may be allowed, but consistency is key.

Team Composition

Teams may typically be made up of 1–2 people.

Skills and Resources

The problem statement allows for multiple analysis and design methodologies, potentially including:

  • Structured analysis (DFDs, ERDs)
  • Object-oriented analysis (UML diagrams like Use Case, Class, Sequence)
  • Information engineering
  • Agile methodologies (User Stories, basic process flow)
  • Prototyping (mockups, wireframes)

Teams are generally expected to choose ONE primary approach and apply it consistently. Mixing components heavily (e.g., detailed DFDs with detailed UML Class diagrams) might be discouraged.

Teams usually must provide their own modeling software (CASE tools, diagramming software like Visio, LucidChart, draw.io, or specialized tools). Solutions are typically submitted as standard document files (Word, PDF).

Protocol

Teams are typically given the problem statement at the beginning. Time may be allowed for general questions. Once Q&A closes, no further questions are answered. Solutions must be submitted before the contest closing time.