SOFTware is HARD

I had a mini-experiment to document my design in UML for a developer to write the corresponding code. The background and assumptions are: The application is an insurance quotation system Design is based on MVC, in particular, ASP.NET MVC Web caching is used The basic MVC application framework is in place (with sample codes) The developer is an intern from a local university What is designed to be developed is one of the modules in the entire application – this particular module is a dashboard Without going into the details of the use case document, I created the basic tenets: certain basic sequence of events as well as the View-Of-Participating-Classes (VOPC). The mini-experiment proved to be a success to my surprise. The following UML Sequence Diagrams capture the basic flow for the initial web request: The following UML Sequence Diagram depicts the sequence of events for subsequent access: Finally the VOPC UML Class Diagram follows:

Sometime ago, I was reviewing the alerts and notifications sent from various applications and systems. We needed to capture and store the content of the messages. I took the opportunity to re-architect the entire landscape by documenting the as-is, as well as the to-be. The UML Communication Diagram – an unsung hero – was used for this purpose. The as-is integration mess: The to-be design – looking a lot better:

Recently, I had been dealing with other areas of IT including operations & governance. The following Activity Diagram documents how a typical institution might have to respond to security incidents.

A mindmap review of the powerful Bible study material. Flash version can be found  here