Author Topic: Boundary, control and entity classes  (Read 3102 times)

zyx

  • EA User
  • **
  • Posts: 74
  • Karma: +1/-1
    • View Profile
Boundary, control and entity classes
« 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?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 8173
  • Karma: +193/-22
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Boundary, control and entity classes
« Reply #1 on: February 11, 2016, 05:03:24 am »
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

qwerty

  • EA Guru
  • *****
  • Posts: 9380
  • Karma: +146/-137
  • I'm no guru at all
    • View Profile
Re: Boundary, control and entity classes
« Reply #2 on: February 11, 2016, 05:31:34 am »
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.

zyx

  • EA User
  • **
  • Posts: 74
  • Karma: +1/-1
    • View Profile
Re: Boundary, control and entity classes
« Reply #3 on: February 11, 2016, 07:59:20 am »
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?

qwerty

  • EA Guru
  • *****
  • Posts: 9380
  • Karma: +146/-137
  • I'm no guru at all
    • View Profile
Re: Boundary, control and entity classes
« Reply #4 on: February 11, 2016, 08:44:01 am »
UML allows that. If it conveys your thoughts then its legal anyway.

q.

StefanPears

  • EA User
  • **
  • Posts: 119
  • Karma: +6/-0
  • Unwissenheit schützt vor Erkenntnis nicht
    • View Profile
Re: Boundary, control and entity classes
« Reply #5 on: February 11, 2016, 07:35:28 pm »
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.

zyx

  • EA User
  • **
  • Posts: 74
  • Karma: +1/-1
    • View Profile
Re: Boundary, control and entity classes
« Reply #6 on: February 12, 2016, 12:54:22 am »
Thank you, but I am not right what you mean by "DOM"... What does it means?

StefanPears

  • EA User
  • **
  • Posts: 119
  • Karma: +6/-0
  • Unwissenheit schützt vor Erkenntnis nicht
    • View Profile
Re: Boundary, control and entity classes
« Reply #7 on: February 12, 2016, 03:27:36 am »
Domain Object Model
The ERM model the business specialists should understand