Software Architecture Based On Xyz / E Description And Refinement Of Case Studies

As the size of software system increases, the algorithms and data structures of the computation no longer constitute the major design problems. when systems are constructed from many components, the organization of the overall system-the software architecture-presents a new set design problems. Design issues at this level include gross organization and control structure, assignment of functionality to computational units, and high-level interactions between these units.Unfortunately, most of current representations of software architecture are informal and ad hoc. While architecture concepts are often embodied infrastructure to support specific architecture styles and in the initial conceptualization of a system configuration, the lack of an explicit, independently-characterized architecture or architecture style significantly limits the benefits of software architecture design in current practice. Evidently, what is needed is a more rigorous basis for describing software architectures. At the very least we should be able to say precisely what is intended meaning of box-and line description of some system. Even, we should be able to check that the overall description is consistent in the sense that the parts fit together appropriately. Moreover, we would like a complete theory of architecture descriptions that allow us to reason about the behavior of the system as a whole.XYZ system is a SE system based on a temporal logic language (TLL) XYZ/E and a group of tools with the goal to enhance reliability, maintainability and productivity. As a first executable temporal logic language, it blends temporal logic operator with programming language. Consequently, It can represent static semantics and dynamic semantics in a unified frame and support stepwise refinement from abstract specification to executable program. We described several common software architecture styles based on XYZ/E and its refinement pattern. Formally, the software development process consists of a sequence of transitions from the interface to its corresponding architectures of the nested components and the transition from the specification of the component to itscorresponding architecture structure designed at that step can be formally validated. Finally, we demonstrate this method through a real practice.