• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part II: web framework

 
Francesco Ioli
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In Cade/Sheil study guide, cap 9, there is this sentence:

"The class diagram remains web framework agnostic. Any web framework (within reason) is an acceptable choice—we merely assume a standard MVC separation of concerns"

I have some doubts related to what this sentence means..I read some previous posts and I came to some conclusions.. but I still have some doubts:

1)It's up to us to decide whether or not to use a webframework. They are both accetable decisions. Are you agree?

2)If we decide to use it, MUST the class diagram remain web framework agnostic or can we show some classes in the class diagram?

3)If the class diagram MUST remain web framework agnostic, how and where we have to communicate that we use a webframework ? In a decision list or in some other diagram?

What do you think?
Which is the experience of those who have already passed the exam?

Thanks in advantage

Ciao
Francesco
 
Krzysztof Grajek
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1. Yes, I guess you dont' have to use a web framework but that wouldn't be wise in my opionion, why reinvent the wheel, choose one web framework which best suits your needs.
2. Try to keep your diagram web framework agnostic, just show a controller + web pages if you want (like in cade's book), I have described some classes with appropriate stereotypes, stating what role they play in the web framework i will use, not sure if this is the right way but its harmless in my opinion.
3. You can always add notes to your diagram, you can add comments below your diagrams in the submission too, and you can add it to the assumption list as well - at least that's what I've done (dont' have my results yet )
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic