Skip to main content

Sequence Diagramming Tool Thingumy-bob

I've used a variety of tools to produce sequence diagrams over the years, many of them very poor, some of them satisfactory, none of them what you'd call "good". Usually because they force you to do battle with a plastic mouse for several hours to make anything other than the simplest of interactions come to life.

However, forced to ditch my old favourites (Rational Rose and Rational Software Architect) in favour of open-source alternatives (Papyrus), has not been as fruitful as I'd have liked. Papyrus does a good job but is just as bad as all the commercial variants at drawing sequence diagrams - resulting in micro mouse movements to get just the right connection in just the right position. I don't get it, sequence diagrams are more like code than any other diagram and it's easier to write them than it is to draw them... so with this in mind; and having tried websequencediagrams which is cool but doesn't seem to handle life-lines properly (and I'm not paying for the commercial version to find out), I knocked up my own means in a couple of lonely evenings just to see how bad it is...

Turns out a reasonable approximation isn't too hard and since I can make it do what I want to do with (relative) ease in the browser, so be it. Doesn't do a lot, but then I don't want it to do much. Anyway, try it out if you get some time at The Mighty sequence diagraming tool thingy... hummm...


Popular posts from this blog

An Observation

Much has changed in the past few years, hell, much has changed in the past few weeks, but that’s another story... and I’ve found a little time on my hands in which to tidy things up. The world of non-functionals has never been so important and yet remains irritatingly ignored by so many - in particular by product owners who seem to think NFRs are nothing more than a tech concern. So if your fancy new product collapses when you get get too many users, is that ok? It’s fair that the engineering team should be asking “how many users are we going to get?”,   or “how many failures can we tolerate?” but the only person who can really answer those questions is the product owner.   The dumb answer to these sort of question is “lots!”, or “none!” because at that point you’ve given carte-blanche to the engineering team to over engineer... and that most likely means it’ll take a hell of a lot longer to deliver and/or cost a hell of a lot more to run. The dumb answer is also “only a couple” and “

Inter-microservice Integrity

A central issue in a microservices environment is how to maintain transactional integrity between services. The scenario is fairly simple. Service A performs some operation which persists data and at the same time raises an event or notifies service B of this action. There's a couple of failure scenarios that raise a problem. Firstly, service B could be unavailable. Does service A rollback or unpick the transaction? What if it's already been committed in A? Do you notify the service consumer of a failure and trigger what could be a cascading failure across the entire service network? Or do you accept long term inconsistency between A & B? Secondly, if service B is available but you don't commit in service A before raising the event then you've told B about something that's not committed... What happens if you then try to commit in A and find you can't? Do you now need to have compensating transactions to tell service B "oops, ignore that previous messag

Equifax Data Breach Due to Failure to Install Patches

"the Equifax data compromise was due to their failure to install the security updates provided in a timely manner." Source: MEDIA ALERT: The Apache Software Foundation Confirms Equifax Data Breach Due to Failure to Install Patches Provided for Apache® Struts™ Exploit : The Apache Software Foundation Blog As simple as that apparently. Keep up to date with patching.