Book a Demo

Author Topic: Model vs view  (Read 3766 times)

larsgk

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Model vs view
« on: June 29, 2006, 06:27:57 am »
I do get a bit confused about the terms 'model' and 'view'.
In EA, you can add a 'model' to the project at top level (e.g. clicking 'Add Model from Pattern' from the project context menu). But you can also add a 'view' by clicking the 'Add View...' item in the same context menu.
Looking in the online help, the top-level folders are referred to as 'views'.

The UML 2.0 standard gives the following definition of 'model': "A model captures a view of a physical system.  ... Different models can be defined for the same physical system, where each model represents a view of the physical system defined by its purpose and abstraction level."

OK, so the term 'view' has no semantic in UML, but 'model' does. I think EA (and not least the online help) should be a bit more accurate in their use of terminology.

jeshaw2

  • EA User
  • **
  • Posts: 701
  • Karma: +0/-0
  • I'm a Singleton, what pattern are you?
    • View Profile
Re: Model vs view
« Reply #1 on: June 29, 2006, 01:07:35 pm »
Can it be that the model exists in the repository and the view is just a presentation of the repository's content from an interesting perspective?  Perhaps I have this reversed??
Verbal Use Cases aren't worth the paper they are written upon.

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: Model vs view
« Reply #2 on: June 29, 2006, 04:20:39 pm »
IMO

EA's "view" is a (UML) model organization construct representing a (top level) collection point for some, user/usergroup defined, way of looking at the System.  I, for example, use 4 primary views loosely aligned to the RUP structurals.  Mine are "Requirements" view, "Analysis" view, "Design" view and "Deployment" view.  Others might use CIM, PIM, PSM views.  Its all horses for courses.

UML "models", in my interpretation, are a complete specification of a physical system from some particular aspect - maybe structural, maybe behavioral for instance.  A System may be composed of more than one system.

Adding a view in EA adds just the top level package element whereas adding a model firstly adds a (complete) prototype of a UML model - including substructures and occassionally sample elements.  Secondly, I believe that a model could/can be added at subsequent levels of the repository organizational heirarchy, depending n the needs of the analysts/designers.

So I actually find the terminology consistent.

bruce

"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.