umple
Umple: Model-Oriented Programming - embed models in code and vice versa and generate complete systems. Save yourself lots of coding. Do it collaboratively online in UmpleOnline, in an IDE or on the command line.
Runssource: GitHubhomepageJavaMITcommit f721ae11a559
Java, MIT licensed. The project labels itself: class diagram, code generation, editor, low code, modeling, state machine, uml and umple.
umple runs. An Argusic agent installed it in 38 minutes and hit 5 errors on a clean machine with no GPU, and the whole session was recorded.
Umple first-build succeeds: the compiler jar (dist/umple-1.37.1.8672.ffc0b7ae3.jar) is built and generates correct Java code from Umple models, including class inheritance, attributes, and dependencies. The TXL/Python codegen step is skipped gracefully. Unit test template.test runs but most implementation tests fail due to pre-existing working-directory and version-mismatch issues.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Stable compiler jar (umple-1.37.1.8672.ffc0b7ae3) generates parser code referencing firstLineIndent and grammarResult attributes not declared in source .ump models12 minutes
- Java 17 JDK not pre-installed in container4 minutes
- txl (TXL source transformation compiler) not installed on container; needed for Python codegen beta2 minutes
- Apache Ant not pre-installed in container2 minutes
- Tests show 'Unable to locate umple file: dist/gradle/test/workingDir/...' failures (working directory mismatch) and expected-vs-actual warning code mismatches (901 vs 1510)
- Install time
- 38 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 5 hit, 4 fixed with no human help
- How the result was proved
- java -jar dist/umple.jar /tmp/final_test.ump processed successfully generating Person.java (with import java.util.List) and Student.java (extends Person), valid Java output
- Model tokens used
- 979,628
- Exact commit tested
- f721ae11a559
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
//------------------------ //Student Attributes private String studentNumber; //------------------------ // CONSTRUCTOR //------------------------ The compiler generates correct Java code for Umple models. Time to deliver the final report. **Elapsed time**: ~38 minutes. tokens used 979,628 The compiler generates correct Java code for Umple models. Time to deliver the final report. **Elapsed time**: ~38 minutes.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 38 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 5 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
class-diagramcode-generationeditorlow-codemodelingstate-machineumlumple
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/umple)Questions
- Does umple run?
- Yes. umple runs. Argusic installed and launched it on a clean machine in 38 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test umple?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f721ae11a559. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test umple?
- The run that produced this verdict cost $0.27: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does umple take to install?
- 38 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does umple need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing umple?
- 5 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for umple?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.