Our approaches forth the UML's behavior model as a premise, because defined events of an object in a sequence diagram orderly mean user scenarios with functional requirements, which can be managed for later engineered works. Therefore, we'll construct the meta architecture for a mathematical basis with various levels of abstraction in requirements, and then propose the process model that defines the connectivity between behavior models in the UML for easiness of management, reusability, also agility of extension. The proposed meta model can be extended to better refined model with refactoring like push down/pull up mechanism. Finally, all the materials from the meta model are configured and laid out by using XSLT/FOA including adjusted behaviors and generated at runtime dynamically.