Demo Scenario

Purpose

This page is not an operating instruction. It defines the functional reference frame for manually setting up and checking the demo league.

The operational steps are described in the following chapters. During manual testing, work in those chapters and use this page only to look up which demo data and review cases are meant.

Use

• Use this page as a data and scenario reference.
• Do not create data directly from this page.
• Start the practical setup with Admin Context: Initial Setup.
• Document findings internally or in the matching work chapter, not on this reference page.

Naming Frame

• Product working title: LigaWerk
• Primary product domain: ligawerk.de
• Demo world: ZauberForest
• Demo association: ZauberForest Spielrunde

The demo world may be playful. The review scenarios stay functionally realistic: master data, team registration, player lists, license applications, game reports, review, communication and export are exercised like in real league operations.

Participating Roles

• Project team
• Administrator
• League administration
• Club managers
• Review office
• Game report recorder
• Referee

Canonical Demo Data

Association and Season

Leagues

Clubs

Teams

Venues

Test Accounts and People

Role Accounts

Demo Members and Team Players

The prepared demo state contains fictitious club members with public member images. Besides the first manually reviewed people, the dataset contains enough roster players for all demo teams. Not every member must later be copied into a league player list.

Prepared team-player records assign existing members to existing teams. They do not create teams or league registrations.

Demo Images

Demo images are synthetic, cartoon-like example images. They provide visual recognition in the test system and must not depict real people.

Target Scope for People and Licenses

The demo must cover enough people for club administration, league administration, review office, referees, officials, game report recorders, coaches and roster players.

Prepared Demo Scope for Schedule, Assignment and Game Registration

The demo schedule must include normal games, future assignments, submitted game reports, correction cases and final-review cases. Use game IDs such as WLD-001, WLD-003, WLD-004, WLD-006 and WLD-007 consistently in the later workflow chapters.

Review Scenarios

• Admin can create the association, clubs, access and first master data.
• League administration can create seasons, leagues, schedules and review registrations.
• Clubs can maintain master data, venues, people, teams and league registrations.
• Clubs can prepare player lists, referee registrations and team pages.
• Review office can decide license applications and created licenses are visible in the register.
• Referee assignment can assign people and send briefings.
• Game report recorder can record and submit a report.
• Referee can confirm or object to a submitted report.
• League administration can return a report for correction or mark it reviewed.
• Public pages show stable, understandable league, table, glossary and handbook content.

Demo Reset for the Project Team

Resetting demo data is an internal project-team task, not normal user work. Before resetting, clarify which host, database and uploaded assets are affected.

Boundary

This reference does not replace the operative chapters. It deliberately does not describe internal seed mechanics, deployment details or database reset commands for end users.