Wednesday, August 10, 2022

Stickman Diagram

UML diagrams are often comes with critical details and can help to understand complex software designing problems beforehand.

I am not a big fan of UML diagrams but I agree that investing time in designing UML gives much benefit in longer run.

Have you ever started your software application designing with Stickman diagram?

I am sure the answer is YES in most of the cases but probably the term is not that famous.

STICKMAN Diagram : 

Like the name says, it starts with a stickman,
In UML terms  an Actor.

Furthermore, all the necessary very high level blocks drawn. Message exchange direction is important however content and specifications can be avoided. This diagram helps to list software application components and their dependencies.

Mainly following things need to be depicted-
1. How will system get Input 
2. What components are needed in the system for Happy Case Scenario.
3. What components are needed in the system for Sad Case Scenario.
4. How will system process Input to provide output.

In many cases we draw this diagram on whiteboard while discussing initial ideas with our team. Yes, those are the initial sticks which we draw on board just to picturise the application system is STICKMAN DIAGRAM.