54204_PP11_Chap11PPT_Modified

54204_PP11_Chap11PPT_Modified - Chapter 11 COMPONENT-BASED...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 11 COMPONENT-BASED SOFTWARE ARCHITECTURE
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Objectives Introduce concepts of the software components Discuss UML notations for component- based architectures Introduce principles of component-based design Introduce quality attributes of component- based design
Background image of page 2
Overview The component-based software architecture divides the problem into sub-problems each associated with component partitions. The interfaces of the components play important roles in the component-based design. The main motivation behind component-based design is component reusability ; a component encapsulates functionality and behaviours of a software element into a reusable and self- deployable binary unit .
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Designs can make use of existing reusable components commercial off the shelf (COTS) or in house-developed, and they may produce reusable components for future reuse. This increases overall system reliability since the reliability of each individual component enhances the reliability of the whole system via reuse .
Background image of page 4
There are many standard component frameworks such as COM/DCOM, JavaBean, EJB, CORBA, .NET, Web services, and Grid services. These target component technologies are widely adopted in local desktop GUI application design such as graphic JavabBean components, MS ActiveX components, and COM components which you can reuse them by simply drag and drop .
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Many components are invisible , especially those distributed in enterprise business applications and Internet Web applications such as Enterprise JavaBean (EJB), .NET components, and CORBA components . The combination of service-oriented and component technologies is getting more attention today; these include of course Web and Grid services.
Background image of page 6
A component is a deployable software package that can provide services to its clients ; it may also itself require services from other components, and son on . A component should be self-contained and substitutable as long as its interface is unchanged .
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
A component-oriented design is at a higher level of abstraction than an equivalent object- oriented design; the former defines components and connections between them instead of classes and connections between classes. A component is a higher-level concept, usually
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 41

54204_PP11_Chap11PPT_Modified - Chapter 11 COMPONENT-BASED...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online