Home
Diagrams
Documentation
Changelog
How-to "NUML"
Privacy Policy
Datenschutzerklärung
Impressum

NUML - No Unified Modeling Language

Plan your software architecture ahead of time

Key features

insert_photo
Plan and communicate your solutions effectively
Do less, get more. Even compared to the code, write fewer definitions and get a diagram on top. The diagram supports communication in a team and is a part of the documentation.
code
Translate your diagrams into code
DRY - Don't repeat yourself! What is defined in the diagram already will resolve into code.
flag
Standardize the planning and development of your software
The standardization to use the layer model in all plannings will shorten the setting-in period of workmates of other teams.
sentiment_very_satisfied
KISS - Keep it simple stupid
The use of diagrams is reduced to the essential points of planning, the interacting parts

Build your first diagram today. A video will show you how to create professional diagrams easily. That will take only ~10 minutes. After that, you will save much time by not using overly complicated tools, Paint, PowerPoint, or similar.
Discover design errors before programming them. So you will not have to rewrite finished implementations or be locked in, in a bad architecture.
If you have written TypeScript or C# before, you will feel very confident with the used syntax. For defining a property, you write "Prop: Type", for a method, you write "MethodName(ParamType1, ParamType2): ReturnType". To adding Enums, Views, Classes/Interfaces, right-click in the diagram and add it. For adding dimensions, click the add button at the end of a dimension.

Planned features

insert_photo
Custom and further views
The user should be able to provide a file for views that will serve as a pattern for the export. Also, React, and Vue should be supported by the standard.
edit
Renaming Dependencies
So far, only the element that is being edited has been renamed. The possibility should be added that the objects that are dependent are also renamed.
layers
Collapsing Layers
For a better overview, it should be possible to minimize layers so that a better overview is possible for larger projects.
article
In code documentation
This should enable comments on members of the diagram. This should resolve into comments in the standard way of the respective languages. Thinking further, other tools can be used to generate technical documentation from the code.
fast_rewind
Step forward / back
Implement Ctrl + Z and Ctrl + Y
import_export
Own language imports
For example, if the return value of a function is "ICollection", the using directive is not set. The user can quickly fix this himself, but it would still be nice if such using directives were set automatically.
flag
Feature flags
Premium Feature
Enable and disable optional features
save
Save to the server
Premium Feature
The created diagrams are currently saved in the browser. I consider this to be not safe enough and therefore always recommend downloading a backup (Export -> Json). In case you delete your browser data.
timeline
GIT integration
Premium Feature
It is planned that a diagram can be generated using code. This can be changed, and these changes can be transferred into the code and checked in with GIT.

$ whoami

My name is Peer Nissen. Programming has become a passion for me. For me, code must be well structured because searching for classes or member of a project shouldn't be part of a developer's job. I think it's important to document, but I catch myself neglecting it.

I started programming in 2013 while studying business informatics at the Flensburg University of Applied Sciences. During my studies, I continued to educate myself more comprehensively than the curriculum provides. During my work at Portal Systems AG, it was always essential to write good and readable code. In short, the code of my work has always been important as a result to me. Not only should it meet the requirements, but I also have high demands on my code. Functions must be understood at once. Elements must be exchangeable without great effort.

When I'm not programming, I like to sail on the Alster or jog around the Alster. If I don't program and I'm not on the Alster, I want to go bouldering.