architecture - Documenting Web Application Flow / Iteraction -
Whether artifacts / diagrams are used to move the flow of web applications to the account link between static pages and Dynamic visual component (HTML form, JSP, Ajax, etc.) interact with server-side components (servicelets, struts action, etc.)? Use UML Diagrams?
We used the UML class diagram using a variation of Conallen's essay. You will find that this essay has evolved and even a book has become.
I used the approach of my 2-tuck:
After Conallen's paper, we used to represent a new UML web page or part of a page (Orthodox ) So that we can separate server-side code (such as Java Servlet or JSP) from customer-side HTML / JavaScript / AJAX, for example: [page]>
There were new associations in:
< Ul>
- We've found that the ration roses icon extension which we see in the picture better than half.
Bad news:
- This approach was a lot of work - now we have twice as many institutions as a model since We were now modeling client-side institutions apart from server-side classes.
Conallen paper for Pict What I am talking about, but as I said, strictly not followed its approach - we only took those pieces we need We hope that it helps.
Comments
Post a Comment