#SEQUENCE DIAGRAMS IF THEN ELSE HOW TO#

I didn’t get to see or hear the talk, but the slides and linked source code clued me in on the concept, which I found very compelling. #api360 /R3zWD0ApwN- Mike Amundsen September 29, 2018 Here are my slides from my 2018 talk 'Using Web Sequence Diagrams with your APIs' I'll post video and transcript when they are availble. While at Open FSharp this year, I read a tweet by Mike Amundsen linking to his talk from RESTFest: The latter part is often easier said than done, at least in my previous experience. Many of these issues can be solved by simply thinking through and documenting the desired flow and then implementing that flow within the software. Other cases - especially those where a specific sequence of steps should be followed - can lead to misuse, bugs, and lots of frustration. In many cases, this is a pretty good trade-off. Most people think it easier to expose all functionality to a user and provide documentation as to how the software should be used.

I’ve also experienced this from both perspectives as a producer and consumer of software library APIs.

#SEQUENCE DIAGRAMS IF THEN ELSE HOW TO#

I’ve built many systems where the user interaction design was either missing or delayed, both of which led to user frustration or confusion as to how to correctly interact with the software. I decided to choose something that cuts across all my various hobby projects through the years and in which I recently found inspiration and practical value when designing software systems, specifically those portions of software systems that want to expose and/or enforce a correct sequence of user actions. For years I’ve contributed here and there to a large number of projects, so it is hard to pick a topic. This post is my contribution to F# Advent 2018.

Sequence diagrams if then else