Component-based Architectures A non-trivial,nearly independent,and replaceable part of a system that fulfills a Definition of a (Software)Component clear function in the context of a well- A component conforms to and provides the defined architecture. physical realization of a set of interfaces. A physical,replaceable part of a system that packages implementation and conforms to and provides the realization of a set of interfaces. A component represents a physical piece of implementation of a system,including software code (source,binary or executable)or equivalents sueh as seripts or command files
Component-based Architectures Definition of a (Software) Component A component conforms to and provides the physical realization of a set of interfaces. A physical, replaceable part of a system that packages implementation and conforms to and provides the realization of a set of interfaces. A component represents a physical piece of implementation of a system, including software code (source, binary or executable) or equivalents such as scripts or command files. A non-trivial, nearly independent, and replaceable part of a system that fulfills a clear function in the context of a welldefined architecture
Component-based Architectures ▣Resilient √ Meets current and future requirements Improves extensibility √Enables reuse Encapsulates system dependencies ▣Component-based Reuse or customize components √ Select from commercially available components Evolve existing software incrementally
Component-based Architectures Resilient 9 Meets current and future requirements 9 Improves extensibility 9 Enables reuse 9 Encapsulates system dependencies Component-based 9 Reuse or customize components 9 Select from commercially available components 9 Evolve existing software incrementally
Model Visually Captures structure and behavion Shows how system elements fit together Keeps design and implementation consistent Hides or exposes details as appropriate Promotes unambiguous communication The UML provides one language for all practitioners
Model Visually Captures structure and behavior Shows how system elements fit together Keeps design and implementation consistent Hides or exposes details as appropriate Promotes unambiguous communication 9 The UML provides one language for all practitioners
Visual Modeling Using UML Diagrams Use-Case Diagram Statechart Class Diagram Diagram 公 Deployment Collaboration. Diagram Diagram 直有 Component Diagram Target System Forward and Sequence Reverse Diagram Engineering
Verify Quality Software problems are 100 to 1000 times more costly to find and repair after deployment Cost to Repair Software ◆ Cost of Lost Opportunities Cost Cost of Lost Customers Inception Elaboration Construction Transition
Verify Quality