Tag: architecture

It helps achieve proper fucntionality if the tasks are ordered

it is mandatory that the sequence added to a transaction must be the best execution sequence possible

The number of tasks to be executed affects the overall performance of a transaction

None of the above

Modifying a persistent object results in the instance update of the database

Only one persistent object can refer to an instance of a class at any given time

The transactional state of an object decides the response to an operation

None of the above

The model, view and the controller objects are independent of each other and can be easily used to integrate a new client's business logic

The new client can be coded into the controller as additional business logic for the enterprise data

The MVC pattern makes provisions for any new client at the time of development of the enterprise solution

The MVC Pattern provides for many models to be used by one controller, thus making it easy to incorporate a new client

Separation makes more space available for application and interface objects

Separation ensures independence of business logic

Separation is used for repeated testing of the code

Separation makes it easier for the model and the view to define roles in times of performance

The MVC pattern introduces extra classes due to the separation of the model,view and the controller components

The view component accesses the enterprise data through the model component

The model-view separation principle states that the application logic should not be put in the UI object method

The Model-View separation principle helps minimize the impact of requirement change in the interface on the controller layer

Provides a uniform interface to the subsystem

Defines a table for each persistent object class

Assigns an object identifier for each record

Makes a class resonsible for materialization

Provides a uniform interface to the subsystem

Assigns the responsibility for creating new class instance or object

Makes a class responsible for materialization

Makes the database mappers responsible for maintaining cache

Is a behavioral pattern that defines how a single class can be notified of a change

Consider the objects displaying the data and the objects containing the data as a single entity.

Is also known as the publish-subscribe model where an object can publish an event that has no subscribers

None of the above

Creates an abstract coupling between the subject and the observer

Allows the subject and observer to belong to different layers of abstraction

Supports notifications in the form of broadcasts

All of the above

At any given time only one algorithm is instantiated and active

The Strategy pattern encapsulates related classes that have different functionalities

The name of the message to the strategy object and the context object must be the same

None of the above