Business Primitives in Software Development

Great introduction to Business Primitives when designing your applications:

http://codebetter.com/blogs/dru.sellers/archive/2010/01/27/business-primitives-1-2.aspx

The basic premise is to not only get you speaking the language of the business, but to make your method signatures easier to understand. For example, in a financial application that has a pricing class you might see a method signature similar to the following:

double getPrice(String)

Without diving into the source or docs, it's not immediately clear what the parameter represents. It could be a ticker, it could be a CUSIP. By creating a single value primitive such as Ticker, the method signature becomes:

double getPrice(Ticker)