TUM Hyperloop Project: Innovation Powered by
Sparx Systems Enterprise Architect

  1. Home
  2. Sparx Customer Stories
  3. TUM Hyperloop Case Study

The TUM Hyperloop program at the Technical University of Munich (TUM) leverages Enterprise Architect to model and develop its high-speed vacuum transport system.

The TUM Hyperloop Team, led by experts like Julian Demicoli, M.Sc., is pushing the limits of high-speed travel with a full-scale 24-meter Hyperloop demonstrator. Originating as part of SpaceX’s global competition, the project has grown in scope and complexity. With around 100 students working on different aspects—from mechanics to electronics—the team needed a robust method to document and manage their detailed work. Recognizing this, they turned to a professional modeling solution that mirrors industry practices.

Julian Demicoli, M.Sc., Head of the Electronics department of the Technical University of Munich (TUM) Hyperloop Team. (Source: TUM Hyperloop)

Challenge

(Source: TUM Hyperloop)

The team encountered several hurdles in their ambitious project:

  • Managing Complexity: With multiple specialized sub-teams (such as those handling mechanics, electronics, and infrastructure), keeping a unified overview of the project was difficult.
  • Inefficient Documentation: Initially, the team relied on a non-commercial tool for creating UML diagrams, which did not meet the rigorous demands of a high-profile engineering project.
  • Collaboration Across Disciplines: The need to share clear, understandable diagrams among experts and non-technical stakeholders highlighted the gap between technical modeling and effective communication.
  • Ensuring Real-World Alignment: The project demanded a tool that not only handled detailed technical documentation but also aligned with real-world industry practices for code generation and system modeling.

Solution

(Source: TUM Hyperloop)

To overcome these challenges, the team adopted the Sparx Systems Enterprise Architect. Julian Demicoli and his colleagues quickly discovered that Enterprise Architect offered a practical way to create intuitive UML diagrams and detailed system documentation. Here’s how it helped:

  • Intuitive and Comprehensive Modeling: Enterprise Architect enabled the team to build and refine an overall project model. The clear, guided diagram types made it easier for the team to document complex systems, allowing them to progress from a high-level overview to detailed sub-models.
  • Enhanced Collaboration: The tool’s ability to produce clear visual representations allowed for smooth communication between different sub-teams. This facilitated better coordination and ensured that everyone—from engineers to project managers—stayed on the same page.
  • Real-World Industry Practices: With its rich feature set for code generation and documentation, Enterprise Architect brought the team closer to industry standards. Julian Demicoli noted that switching to this professional tool helped bridge the gap between academic projects and real-world engineering demands.
  • Streamlined Processes: Instead of struggling with outdated tools, the team established a structured, evolving model that grew with the project. This not only boosted internal collaboration but also contributed significantly to the team’s success in competitions and in transitioning the project to a full-scale test track for magnetic levitation.