Abstract: When going from specification to business architecture, then system architecture and implementation, the practitioner still has to face questions like: Can I keep my business logic isolated? How to prevent business process knowledge slipping into the applications or entities ? How to isolate business processes from the information? How to preserve evolution, and keep a neat separation of concerns, at code level? In these e-days, a new one appears, often un-seen: How to prevent duplication of process logic when one process serves multiple distribution channels ( e-service, re-tail, phone, Atm...). These techniques, 1 have been gathered and integrated in an architectural framework, exposed hereafter.