• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Design Pattern Question

 
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Which of the following design patterns is used to separate the task of writing the GUI screens and business logic?

Select 1 correct option.

A.View Logic
B.Front Controller
C.Model View Controller
D.Business View
E.Business Delegate

its both Front Controller and MVC right..
 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
MVC does this task along with separating data access. I think Front Controller would be more suitable answer to the given question.
 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I would rather say MVC is the appropriate answer. Front Controller deals with the allocation of the incoming request to the proper servlet (at least in our case). MVC separates the concerns of Model (business logic), View (GUI-presentation) and control,
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
MVC is the correct answer.

Reference: http://test.javaranch.com/peabody/PeabodyOnScwcdPatterns.doc
========================================================================
Model View Controller [aka MVC, aka Model 2 architecture]
* You want to keep Views/presentation, Controls/business logic, and Models/data access separate.
Consequences
Allows multiple view types for the same info
Decouples presentation, business logic, and data access components
Related Patterns
Front Controller

Front Controller
A centralized access point for presentation-tier request handling.
Forces
* You want to avoid duplicate control logic.
* You want to apply common logic to multiple requests. (IF)
* You want to separate system processing logic from the view. (MVC)
* You want to centralize controlled access points into your system. (IF)
Consequences
Centralizes control (IF)
Improves reusability
Related Patterns
Intercepting Filter
 
Chakravarthy Gogineni
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
More discussion on this question:

http://www.javaranch.com
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic