1. COP 4009 4 th Lecture September 26, 2005 COP 4009 Component-Based Software Engineering Fall 2005 Instructor: Masoud Sadjadi http://www.cs.fiu.edu/~sadjadi/Teaching/COP-4009-Fall-2005/index.html Introduction to CBSE: Definitions, Concepts, and Principles

2. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 2 Acknowledgements  Dr. George T. Heineman –This course is based on the “CS 509 Design of Software Systems - Spring 2005” by Dr. Heineman with some adjustments to become appropriate for undergraduate students. Dr. Heineman has generously offered his course material (including the slides) and his help during preparation of this course. I am very grateful to him. –The original slides and the course material can be found at:  http://www.cs.wpi.edu/~heineman/html/teaching_/CS509/index.html  Dr. William Councill and other authors of the main textbook  Dr. Clemens Szyperski  Drs. Betty Cheng, Peter Clarke, Bernd Bruegge, and Allen Dutoit

3. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 3 Agenda  Component Based Software Engineering  Definitions  Component Infrastructure  Component Model  Tasks and Responsibilities

4. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 4 Other Engineering Fields  Every other engineering profession – divides problems into sub-problems  Ready-made solutions  Sub-contracted to conform to specifications – conforms to standards – self-imposed industrial regulation – certification regiment for engineers  But not Software Engineering…

5. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 5 Some Excuses  Software is different from hardware  My software needs are unique  We don’t trust software written elsewhere  Users can live with defective software  We want something better…

6. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 6 CBSE Methodology  At its core, CBSE is a methodology that: – constructs applications from software units – supports vendors in producing reusable software units – develops core technologies that support the run-time execution of these units – defines agreed-upon standards – engenders trust among participants We will participate in most of these tasks during this semester

7. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 7 Agenda  Component Based Software Engineering  Definitions  Component Infrastructure  Component Model  Tasks and Responsibilities

8. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 8 Software Component A Software Component is  a software element  that conforms to a component model  and can be independently deployed  and can be composed without modification  all above according to a composition standard

9. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 9 Component Model A Component Model defines specific interaction and composition standards. An interaction standard is the mandatory requirements employed and enforced to enable software elements to directly and indirectly interact with other software elements. Component interface Software Entity supply manage consume

10. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 10 comp Interaction Standard  Based on the concept of an interface – “An abstraction of the behavior of a component”  Provided interface – component implements the interface  Required interface – component interactions with other software elements are captured  Context Dependency in out

11. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 11 Composition Standard  Composition – the combination of two or more software components yielding a new component behavior  Defines several important concepts – PackagingInstallingInstantiating – DeployingConfiguring

12. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 12 CMI A Component Model Implementation is  the dedicated set of executable software elements  required to support the execution of components  that conform to the model  The “Plumbing” that enables components to connect and interact with each other

13. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 13 Agenda  Component Based Software Engineering  Definitions  Component Infrastructure  Component Model  Tasks and Responsibilities

14. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 14 Big Picture Decompose problem into projects and subprojects Design logical component infrastructure Problem to be Solved Select suitable component model Provided by vendor; or, if a proprietary component model, must be implemented. Legend Subproject Project Performance Requirements Evaluate Success of Software System Master Software Development Plan

15. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 15 Increasingly detailed refinement of design leads to an implemented component infrastructure Evaluate Success of Software System Analyze component infrastructure from multiple viewpoints Legend Interaction Component Logical Component Infrastructure Component Model Implementation Component Infrastructure

16. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 16 Component Infrastructure  A software component infrastructure is –a set of interacting software components  The infrastructure is designed to ensure that a software system constructed using those components will satisfy clearly defined performance requirements

17. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 17 Designing a Component Infrastructure  The Component Infrastructure is layered  Layering is a strategy for decomposing complex structures

18. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 18 Four Layers  User  Workflow and Process Control  Business Services  Data and Operating System Services

19. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 19 User  User components provide the external interface –graphical user interfaces (GUI), Web-based, or batch- oriented  Understand user interactions  Request services from other components in response to commands issued by the user

20. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 20 Workflow and Process Control  Workflow and process control components manage complex, automated business processes that interact with (potentially) many business services

21. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 21 Business Services  Business service and legacy wrapping components provide the implementation of the business rules and the operational activity  This is accomplished using internal business object implementations, or by wrapping legacy systems behind the component interface

22. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 22 Design Layers and Designers User Business Services & Legacy Wrapping Data/Operating System Services Workflow and Process Control Solution Component Designers Business Component Designers Data/Infrastructure Component Designers Supply Consume Supply Consume

23. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 23 Agenda  Component Based Software Engineering  Definitions  Component Infrastructure  Component Model  Tasks and Responsibilities

24. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 24 Component Model  Interfaces Naming Meta data Composition Customization Interoperability Evolution Support Packaging & Deployment Specification of component behavior and properties Definition of Interface Description Language (IDL)

25. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 25 Component Model Interfaces  Naming Meta data Composition Customization Interoperability Evolution Support Packaging & Deployment Global unique names for interfaces and components Interface Y Component X

26. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 26 Component Model Interfaces Naming  Meta data Composition Customization Interoperability Evolution Support Packaging & Deployment Information about components, interfaces, and their relationships Interfaces to services providing such information Interface Y Component X X Meta data Y Meta data

27. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 27 Component Model Interfaces Naming Meta data  Composition Customization Interoperability Evolution Support Packaging & Deployment Interfaces and rules for combining components to create larger structures and for substituting and adding components to existing structures Interface Y Component X Component Z ???

28. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 28 Component Model Interfaces Naming Meta data Composition  Customization Interoperability Evolution Support Packaging & Deployment Interfaces for customizing components User-friendly customization tools will use these interfaces Interface Y Component X CustomizationAPI Interface Y Component X’

29. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 29 Component Model Interfaces Naming Meta data Composition Customization  Interoperability Evolution Support Packaging & Deployment Communication and data exchange among components from different vendors, implemented in different languages Interface Y Component X VB Impl. Component Z Java Impl. ???

30. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 30 Component Model Interfaces Naming Meta data Composition Customization Interoperability  Evolution Support Packaging & Deployment Rules and services for replacing components or interfaces by newer versions Interface Y Component X X Meta data Version 1 Version 1.1 Y Meta data Version 1.0 Version 2.0

31. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 31 Component Model Interfaces Naming Meta data Composition Customization Interoperability Evolution Support  Packaging & Deployment Packaging implementation and resources needed for installing and configuring a component Interface Y Component X X Meta data Y Meta data

32. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 32 Agenda  Component Based Software Engineering  Definitions  Component Infrastructure  Component Model  Tasks and Responsibilities

33. Fourth Lecture on September 26, 2005COP-4009: Component-Based Software Engineering 33 Tasks and Responsibilities  Component Factory – Three primary groups (AD, CD, CMID) Tasks and Responsibilities Application Development Provides CD with component requests and designs Provides CMID with requirements for infrastructure services Component Development Builds components to specification and provides to AD Provides feedback on CMI and its services Component Model Implementation Development Provides AD with a component model implementation that satisfies application criteria Provides CD with suitable tools and an environment for component development Tasks and Responsibilities Application Development Provides CD with component requests and designs Provides CMID with requirements for infrastructure services Component Development Builds components to specification and provides to AD Provides feedback on CMI and its services Component Model Implementation Development Provides AD with a component model implementation that satisfies application criteria Provides CD with suitable tools and an environment for component development