CSC 532 Term Paper Presentation Hybrid approach to component based Engineering  Introduction.  Component based development (CBD).  Pros and Cons of Component based Development.  Using hybrid approach.

CSC 532 Term Paper Presentation Introduction  Component - A software component is a unit of composition with contractually specified interface and explicit context dependencies only. A software component can be deployed independently and is subject to composition by third party's.

CSC 532 Term Paper Presentation Component Based Development and objectives  Definition: It is the creation and deployment of software-intensive systems assembled from components, as well as the development and harvesting of such components.  Objectives: Reuse components, lower development costs, lower maintenance costs and increase productivity.

CSC 532 Term Paper Presentation Differences between CBD and conventional reuse CharacteristicsConventionalCBD Architecturemonolithicmodular ComponentsImplementation and white box Interface and black box ProcessWater-fallEvolutional and concurrent MethodologyBuild from scratchComposition OrganizationMonolithicSpecialized component vendor, broker and integrator

CSC 532 Term Paper Presentation Differences between component and object  Specialization - a component is a specialization of an object. A Component is an object, but an object isn't necessarily a Component.  Scale - Components tend to encapsulate more than one object.  Functional Responsibilities - The container, or environment, within which the Component lives, may place certain responsibilities on it.  Functional Limitations - Again the container may impose restrictions on the functionality of the Component.

CSC 532 Term Paper Presentation Component based development Lifecycle Analysis Component –Oriented Design Component Composition Integration Test Component Acquisition System Test Fig 1: Lifecycle of component based development

CSC 532 Term Paper Presentation Component development and application development Component Development Application Domain Domain Analysis Modeling Component design and implementation Domain components Application Requirements Component based design methodology Component composition Application systems Component / application development support Component warehouse and broker Application requirements (component composition) Fig 2: component development and application development using components

CSC 532 Term Paper Presentation Components notation in UML > Canonical Form Elided Form

CSC 532 Term Paper Presentation Pros of CBD  Unit of maintenance and upgrade  Parallel development  Scalable  Infrastructure standardized.  Manageable and self contained units.  Higher level capabilities.  Reduces complexity.  Incremental testing.  Higher flexibility in meeting various requirements.

CSC 532 Term Paper Presentation Cons of CBD  Requires trusted components.  Requires component certification.  Composition predictability.  Rapidly changing standards.  Skilled people are required for developing.

CSC 532 Term Paper Presentation Using hybrid approach  Vertical framework – developing vertical components.  Horizontal framework – developing horizontal components.

CSC 532 Term Paper Presentation Vertical framework  services restricted to single domain such as Accounting, Manufacturing or Insurance Policy Management.

CSC 532 Term Paper Presentation Horizontal framework  services across the different verticals. E. g. Network security.

CSC 532 Term Paper Presentation Known Component Models  EJB  CORBA  COM+

CSC 532 Term Paper Presentation References  Ivica Crnkovic, “Component-based software engineering – New challenges in software development”, last visited 10/22/  Ivica Crnkovic and Magnus Larson, “Component- based software engineering – New Paradigm of software development”, last visited 10/22/  Ivica Crnkovic and Magnus Larson, “Demands on component-based Development”, Proc. 22nd International Conference on software Engineering, ACM Press, 2000