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:
- 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:
Comments