How Much Detail Do You Need to Capture in UML for Code Development?

I had a mini-experiment to document my design in UML for a developer to write the corresponding code. The background and assumptions are:

  1. The application is an insurance quotation system
  2. Design is based on MVC, in particular, ASP.NET MVC
  3. Web caching is used
  4. The basic MVC application framework is in place (with sample codes)
  5. The developer is an intern from a local university
  6. 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:

image

image

The following UML Sequence Diagram depicts the sequence of events for subsequent access:

image

Finally the VOPC UML Class Diagram follows:

image

Comments

Popular posts from this blog

Understanding ITIL Service Management the UML way…

How to depict (Professional-Looking) Logical Network Diagrams in Astah