adplus-dvertising
frame-decoration

Question

What is the difference between MVC and the Document-View pattern?

a.

MVC is used in Smalltalk environment while the Document-View pattern is used in graphical user interface platforms.

b.

The Document-View pattern relaxes the distinction between the view and the controller.

c.

MVC is only applied in specific design situations.

d.

The Document-View pattern addresses a recurring design problem that arises in specific design situations.

Answer: (b).The Document-View pattern relaxes the distinction between the view and the controller. Explanation:In various graphical user interface platforms, a variant of MVC has been applied in which the distinction between the view and the controller has been relaxed and is called the Document-View pattern.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What is the difference between MVC and the Document-View pattern?

Similar Questions

Discover Related MCQs

Q. What is the purpose of patterns in software design?

Q. What is the main aim of MVC pattern in software design?

Q. What is the role of patterns in documenting software designs?

Q. What are the main entries of a schema used for describing patterns?

Q. What is the main goal of separating details in software applications?

Q. What are design patterns in software development?

Q. What are antipatterns in software development?

Q. What is the purpose of knowledge of antipatterns in software design?

Q. What is the purpose of refactoring in software design?

Q. What do design patterns provide for software design?

Q. What is the "God Class" antipattern in software design?

Q. What is "Lava flow" antipattern in software development?

Q. What is a "Poltergeist" antipattern in software development?

Q. What is the "Golden Hammer" antipattern in software development?

Q. What is the "Stovepipe" phenomenon in software development?

Q. What is the "Swiss Army Knife" antipattern in software development?

Q. Who needs information about the function and use of each component and its interfaces to other components in the design documentation?

Q. Who must know about algorithms to be used, data structures, and the kinds of interaction with other components in the design documentation?

Q. What is the purpose of the requirements specification in design documentation?

Q. What does IEEE Standard 1016 mainly address in the design documentation?