ITIS 6112 Design Patterns C.F.T.D.T.T
Terms in this set (19)
C.F.T.D.T.T - Come F*ck Tonight Don't Take Too Long - Command, Front Controller, Transaction Script, Domain Model, Table Model, Table Data Gateway
State the acronym in place to represent the second half of the Design Patterns you will be responsible for:
A Command Pattern encapsulates Request as Objects.
What does a Command Pattern encapsulate?
A controller object that handles all request for a website.
What is a Front Controller Pattern?
A Transaction Script Organizes business logic by procedures where each procedure handles a single request from the presentation tier.
A Transaction Script Pattern organizes business logic by:
An Object model of the domain that incorporates both behavior and data.
What is a Domain Model Pattern?
A single object that handles the business logic for all rows in a database table or view.
What is a Table Module Pattern?
An object that encapsulates access to a database table, where one instance handles all the rows in the table.
What is a Table Data Gateway Pattern?
When you want to parameterize objects with an operation to perform.
When is a Command Pattern most applicable?
A Command Pattern DECOUPLES the object that invokes the operation from the one that knows how to perform it.
What is a significant consequence of using a Command Pattern in larger design?
When Controller logic is COMPLEX.
When is a Front Controller Pattern most applicable?
Data manipulation and data presentation can vary independently.
What is a significant consequence of using a Front Controller Pattern?
When business logic is simple.
When is a Transaction Script Pattern most applicable?
Most of the time you will have one Transaction Script for each database Transaction.
What is a significant consequence of using a Transaction Script Pattern?
When your application has highlight complex, ever changing business logic.
When is a Domain Model Pattern most applicable?
Simple Domain models may have one Domain object per database.
What is a significant consequence of using a Domain Model Pattern in larger design?
When you have an awkward interface to a database.
When is a Table Data Gateway Pattern most applicable?
A Table Data Gateway is usually stateless.
What is a significant consequence of using a Table Data Gateway Pattern in larger design?
When your persistence tier is Table-oriented.
When is a Table Module Pattern most applicable?
Table Module has no notion of an identity for the objects it is manipulating.
What is a significant consequence of using a Table Module Pattern in larger design?
YOU MIGHT ALSO LIKE...
Academic Word Lists - AWL Sublists
Miranker Databases Final
OIM 297A Exam 1
OTHER SETS BY THIS CREATOR
ITIS 6112 Intro to Software Testing
ITIS 6112 Brief Intro to Software Process Improvement
ITIS 6112 Intro to Software Process Models
ITIS 6112 Design Patterns F.A.P.O.P