TheCommonComponentArchitectureandXCAT分析.pptVIP

The Common Component Architecture and XCAT Indiana University Extreme! Lab What is a Component Architecture? A systematic way of encapsulating special functionality and behaviors of a piece of software into reusable units. More than an object model. It defines the rules for the way objects can be instantiated and composed. It defines the environment of services that a component can use. It defines the way in which we discover how to interact with them. Isn’t this what a subroutine library does? Subroutine libraries or class libraries have well defined interfaces encapsulate functionality But are often hard to reuse because they often have complex resource requirements make conflicting assumptions about their operating environments. Subroutine libraries that follow very strict sets of design and use rules get reused. Above all else, a component architecture is framework of standard rules of behavior for objects. Standard Component Archtectures Examples: Microsoft COM/DCOM, COM++ the foundation of all Microsoft office products Java Beans Java standard for building user interfaces Enterprise Java Beans a standard for client-server applications in Java CORBA 3.0 The new component spec for CORBA. Look at One Design in Detail The U.S. Dept of Energy DOE2000 project The Common Component Architecture Lawrence Livermore National Lab Sandia Labs Argonne National Labs Los Alamos National Labs Universities: Utah, NCSA, Indiana A specification for component design for parallel and distributed applications Two parts to the CCA Architecture Components An encapsulated “object” defined by its public interfaces. Can be Java, C, Python, C++ or C++ and Fortran. Frameworks The software systems that provides basic services to components Used to compose components to make apps. Many implementations: Parallel and Distributed. Some Concepts in Detail Ports: the public interfaces of a component defines the different ways we can interact with a component and the ways the component uses se