Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: zyx on February 11, 2016, 04:47:27 am
-
Hello all,
It is valid to represent boundary, control and entity classes in a same model or it is mandatory to represent each kind of class in a separate model?
-
Please define "Model"?
But anyhow, I don't see why it would be invalid for those classes to be in anything that could be considered a model (an actual model, a diagram, a package,...)
Geert
-
If you intended to say Diagram rather than Model (which is why Geert asked) then yes, you can do that. If you really meant Model, then you live in a different world than me.
q.
-
Right, I mean diagram, but if we are applying the MVC pattern, there are 3 layers, so is it still valid to mix boundary, control and entity classes in a specific diagram?
-
UML allows that. If it conveys your thoughts then its legal anyway.
q.
-
Well zyx, the answer is easy: YES!
Assuming you have a (business-) DOM build from entity classes. The attributes contain business rules and data types that are valid at any time and company-wide (and usually implemented in the data base).
Next you have a control class model representing rules (incl. methods, aggregations aso.) concerning multiple attributes in one or more classes.
Next you have a boundary model, ideally connected with EAs user interface wireframes. Here you have rules concerning the UI only if other than above.
Then it’s a good idea to put all items of a topic in one diagram to do some talking and clarifying with your business SMEs, architects and developers.
-
Thank you, but I am not right what you mean by "DOM"... What does it means?
-
Domain Object Model
The ERM model the business specialists should understand