Business-driven development is an approach that focuses on automating the path from business understanding to IT solution. IBM's experiences with customers taking a business-driven approach to develop services-oriented solutions are highlighting a number of best practices that are important to share and discuss. This paper focuses on how companies adopting a service-oriented approach are assembling the appropriate environment to be successful. The paper identifies three design techniques for SOA and describes when each of them can be used in practice, depending on the business and IT drivers and the organization's maturity. We then highlight how to use structured enterprise models together with the tools and methods to automate the design of service-oriented solutions. These scenarios and examples are playing an important role in the development of future method content and tooling requirements for IBM Rational tools.

Many challenges face organizations as they describe their business domains from a services perspective and transform that understanding of their business into a specific realization targeting a solution infrastructure. However, one of the most pressing problems involves helping organizations to effectively transition to service-oriented design of applications. Great benefit could be gained by using a well-defined, repeatable approach to the modeling of business domains from a services perspective that supports the application of automated approaches to realize a service-based solution. In this paper we explore model-driven approaches to the realization of service-oriented solutions. We describe a services-oriented design approach that utilizes a UML profile for software services as the design notation for expressing the design of a services-oriented solution. We describe how a services model expressed in this UML profile can be transformed into a specific service implementation, and describe the design-to-implementation mapping. We then comment on how these technology elements play in an overall MDD approach for SOA.

This paper defines the fundamental concepts, key elements, and semantics of a metamodel that is being proposed as a response to the OMG's RFP for a Business Process Definition Metamodel [BPDM]. It also introduces notations that allow to view a process model at varying levels of detail, while maintaining consistency with the underlying model and semantics. A formal definition of the metamodel and its relationship with UML 2.0 [UML2] will be given in a forthcoming paper.

Many enterprises are implementing service-oriented architecture (SOA) using Web services, and are designing those services according to the principles of Model Driven Architecture (MDA). Because the UML used to express MDA lacks model elements for indicating the security needs of business processes, system architects are forced either to ignore security concerns in their models, or to indicate their intentions in ways that are implementation-specific. This paper proposes a candidate profile for UML that presents security-related intent elements as stereotypes that business users and software architects can apply to UML elements when working with business stakeholders to capture business requirements. Using a profile such as the one proposed here would allow architects to specify the business intent of security in their designs without violating the MDA prohibition against implementation-specific details in high-level, behavioral models.