Continuous Business Process Improvement (BPI) is necessary in order to maintain and develop the enterprise competitiveness. However, achieving a level of software development performance that matches enterprise needs in terms of producing noticeable results within small amounts of time is a persnickety task, mainly because most available methods do not deliver full software architectures that can be directly used for in-house software development without iterations between implementation and design, as produced specifications are too close to the user interface, or too close to business regulations and domain modeling. Our approach applies a method that structures business processes, business rules and domain concepts, and uses this information in order to identify user tasks (use cases) and interaction spaces, and by means of their detail, methodically specify the software architecture for a particular BPI, bridging business and software using cross-consistent concepts. We present a theoretical example, and the validation of our method.