To increase user acceptance of business software applications, software architects need to consider a type of quality attribute, in addition to the commonly used technical quality attributes, which is directed towards the human experience of the application user. The author defined a taxonomy of these new attributes--the human experience quality attributes--and corresponding criteria for measuring their inclusion in the applications. Furthermore, the author developed a pattern language, following concepts for patterns from Christopher Alexander, for early incorporation of these new attributes in the architecture of a business software application. Using an explanatory case study, the author evaluated the pattern language and concluded that it was accurate, sufficient, and useful for its purpose. That is, it was effective for eliciting, documenting, and communicating the information needed for architecting a business software application that possesses the newly defined human experience quality attributes.