For the first four weeks of this course, we've been looking at options for representing the (relatively) static information of an application: the entities which would, in a previous era, have been captured in the form of files in a cabinet, entries in a ledger, etc.
It's time now to shift gears. As we begin the second part of this course, we're going to consider the more dynamic aspects of an application domain: the rules, algorithms, and workflows that transform a program from a mere filing system, to an active collaborator in coordinating human activities.
In week 5, we'll explore some basic building blocks for describing processes and making decisions in an object-oriented application. You'll see how to use Transaction Scripts to describe workflows without prematurely committing to a particular object design. And you'll learn how to use the Special Case and Null Object patterns to avoid spreading hard-coded business decisions throughout a codebase.
Report
There was a problem reporting this post.
Block Member?
Please confirm you want to block this member.
You will no longer be able to:
See blocked member's posts
Mention this member in posts
Please allow a few minutes for this process to complete.
Responses