1 / 19

Towards Component-based Systems Stephen E. Cross sc@sei.cmu.edu 7 February 2000

Towards Component-based Systems Stephen E. Cross sc@sei.cmu.edu 7 February 2000. What I’d like to share with you. Brief SEI overview New challenges encountered with commercial components First steps: understanding the component/method space Summary.

pancho
Download Presentation

Towards Component-based Systems Stephen E. Cross sc@sei.cmu.edu 7 February 2000

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Towards Component-based SystemsStephen E. Crosssc@sei.cmu.edu7 February 2000

  2. What I’d like to share with you • Brief SEI overview • New challenges encountered with commercial components • First steps: understanding the component/method space • Summary

  3. Most of this talk is based a forthcoming book entitled Software Engineering with Commercial Components by Kurt Wallmau, Scott Hissam, and Robert Seacord. It will be published as part of the SEI-Addison Wesley Software Engineering Series later in 2001.

  4. Software Engineering Institute • DoD R&D laboratory federally funded research and development center (FFRDC) • Situated as a college level unit at Carnegie Mellon University, Pittsburgh PA • Mission is to provide leadership in software engineering and to transition new software engineering technology • Encouraged to support industry in precompetitive technology R&D and in technology transition activities

  5. SEI Technical Program The right software delivered defect free, on time, every time High confidence, evolvable, product lines with predictable and improved cost, schedule, and quality COTS-Based Systems Dependable Systems Upgrade Architecture Tradeoff Analysis Survivable Systems Product Line Practice Capability MaturityModelIntegration Accelerating SoftwareTechnology Adoption Team Software Process Software Engineering Measurement & Analysis Technical Practice Initiatives Management Practice Initiatives

  6. SEI Technical Program The right software delivered defect free, on time, every time High confidence, evolvable, product lines with predictable and improved cost, schedule, and quality COTS-Based Systems Dependable Systems Upgrade Architecture Tradeoff Analysis Survivable Systems Product Line Practice Predictable Assembly with Certifiable Components Capability MaturityModelIntegration Accelerating SoftwareTechnology Adoption Team Software Process Software Engineering Measurement & Analysis Technical Practice Initiatives Management Practice Initiatives

  7. The Unfinished Revolution • The first software crisis (the software factory regime) • The second crisis (the market regime) • system architecture reflects technology market • design for change • design supply chains • design in the face of misfits • design to technology competence • sustaining competence • design as exploration • accommodating the process singularity

  8. Component Space • Source of software components • Environments into which components are deployed and in which they are executed • Aspects of a system implemented by the components

  9. Framework v. Platform Host component-VM Does the method assume a component virtual machine? host-OS

  10. commercial custom Commercial v. Custom Source component-VM Does the method emphasize specification of components or assembly of preexisting components? (If preexisting then commercial source) host-OS

  11. Application v. Infrastructure component-VM application Does the method focus on building applications or infrastructure? commercial custom infrastructure host-OS

  12. component-VM commercial custom host-OS Component/Method Space application Custom infrastructure: for all intents a black hole (projects that enter never escape) infrastructure

  13. component-VM custom commercial host-OS Component/Method Space application UML Components & Component Factory both assume use of a framework and focus on component specification for business applications infrastructure

  14. component-VM commercial custom host-OS Component/Method Space application Catalysis does not assume a framework but neither does it directly address enterprise system needs. It is application focused. infrastructure

  15. component-VM commercial custom host-OS Component/Method Space application The book I am writing with Hissam and Seacord focuses on design problems that are dominated by commercial software components infrastructure

  16. commercial custom Component/Method Space component-VM application This is an area that is just emerging (e.g. component families for EJB™). No methods yet, but they will be needed soon; they share some characteristics of COTS components and e.g. UML Components infrastructure host-OS

  17. component-VM commercial custom host-OS Component/Method Space application This area is still science fiction.There is research in “programmable middleware,” but this is a remote possibility for near-term commercial use. infrastructure

  18. component-VM commercial custom host-OS Component/Method Space application infrastructure

  19. Visit Our Web Site For more information contact: Steve Cross sc@sei.cmu.edu 412-268-7740 http://www.sei.cmu.edu

More Related