DRAKON blog

How icons in a DRAKON chart relate to real-time. Which icons block execution, which icons wait for an event.

Read more

Professionals use DRAKON to solve complex technical and organizational problems. Nevertheless, learning the basics of DRAKON does not take much time.

This is how to make a DRAKON flowchart... Read more

24 May 2018. DRAKON Editor Web got a new name—DrakonHub

DRAKON Editor Web has moved to the new address: drakonhub.com

All diagrams and projects remain safe.

Software requirements start with a problem statement. A precise problem statement is a mandatory input for creating requirements. If the client has not provided a problem statement, write one and get the client to approve it.

The problem statement should be... Read more

It is useful to have acceptance tests before writing the code. At least, creating acceptance tests helps us understand at an early stage whether the future program is needed at all.

A DRAKON flowchart contains all use cases in a... Read more

Give the DRAKON flowchart a proper name that reflects its purpose.

The name should not be too long, just long enough to convey the meaning.

If the name is too short, it will be difficult to figure out what the algorithm does. Also, it will be hard to find the diagram later on, if the name does not... Read more

Feedback: support@drakonhub.com

DRAKON Labs

Løkentoppen 21, Kolsås 1352, Norway

Telephone: +47 407 63 992

Terms of service

To the top