More or less, and it depends on the source code.

Consider what the terms "model", "view" and "controller" mean in this context.

"Model" is the business logic, so if you see a piece of code (be it class,
method or just a paragraph in a method), if it deals primarily with business
logic it's part of the "model".

"View" is the presentation, or the part with which the user interacts.
Typically this means the GUI (or command line), and the artifacts that
directly create the display and handle input. So if you see a form, dropdown,
button or the like that is part of the "view".

The "controller" has two main purposes - linking other components to each
other and managing navigation from screen to screen (or process flow module to
module). A controller component will invoke the correct model code in response
to a user input, say, or move the user from one page or screen to another.

Much real-world code intermingles these roles in a single code block or
artifact. You will probably encounter code that analyzes a screen input
(view), does some sort of business action such as a database update (model),
decides what screen to show next (controller) and moves the user to that
screen (view), all mixed together.

Well-written code will move these aspects into separate code blocks, usually
separate classes. For example, the Swing API includes JTable, a view
component, and TableModel, a model component. The JTable displays information
contained in the TableModel. One could display the information in some other
way than a JTable and still maintain its integrity as information in the
TableModel.

- Lew

Aned skrev:

At least in the View will be easily distinct from both Controller and
Model at source code level (which, by the way, is the only level on
which MVC operates; at least there's no MVC at execution level ... ok,
it may/could exist at distribution level, but this is secondary to
source code concerns). The View will be the only one with large amounts
of HTML or Swing or println()s.

Here's a test for you: look at a few random classes from the model,
view, and controller subpackages here and see if think you could spot
the primary concern from the code if you couldn't see the package
structure:

http://www.edmundkirwan.com/servlet/fractal/cs1/code/all-link0.html

.ed

--

www.EdmundKirwan.com - Home of The Fractal Class Composition