Use case driven software development typically starts with abstract problem domain descriptions of how the users see themselves using the system being developed, and entails a series of iterative refinement steps that incrementally detail the user stories/use case model, in order to bring those descriptions to the solution domain. This process tends to produce overcrowded detailed use case models that are difficult to read, but that are essential to maintain a use case driven approach, during software construction/coding activities. Business applications typically comprise a set of functions that the users can make on the system. When a use case driven approach is used to develop business applications those typical business applications' functions pop-up as use case patterns. This paper presents a set of use case patterns that can be found in data-centered business applications, and proposes a use case pattern language that can be used together with standard UML use case language to facilitate the understanding of detailed use case models.

Traditional software applications are typically customized before being delivered to a client. This customization was a paid service delivered by software development organisations. With the growing demand of applications delivered with a SaaS model, software development organisations are increasingly responding with the migration of traditional applications to a multi-tenant SaaS deployment model. This makes them face themselves with the problem of customizing a shared application, with a shared database, for each tenant that subscribes their deployed service. After overviewing existing solutions for application customizability, this paper addresses the customization of the business logic layer of multi-tenant applications by proposing a solution, which has been used in a multi-tenant WMS application deployed with a SaaS service model.