Towards Component-based Systems Stephen E. Cross [email protected] 7 February 2000
19
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Sponsored by the U.S. Department of Defense 1 Towards Component-based Systems Stephen E. Cross [email protected] 7 February 2000
description
Towards Component-based Systems Stephen E. Cross [email protected] 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. - PowerPoint PPT Presentation
Transcript of Towards Component-based Systems Stephen E. Cross [email protected] 7 February 2000
Software Engineering InstituteCarnegie Mellon UniversityPittsburgh, PA 15213-3890
Sponsored by the U.S. Department of Defense
1
Towards Component-based Systems
Stephen E. [email protected]
7 February 2000
2
What I’d like to share with youBrief 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 InstituteDoD 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
Capability MaturityModel
Integration
Accelerating Software
Technology Adoption
COTS-Based Systems
Dependable Systems Upgrade
Architecture Tradeoff Analysis
Technical PracticeInitiatives
Team Software Process
Software Engineering
Measurement & Analysis
Survivable Systems
Product Line Practice
The right software delivered defect free, on time, every time
High confidence, evolvable,product lines
with predictable and improvedcost, schedule, and quality
Management PracticeInitiatives
6
SEI Technical Program
Management PracticeInitiatives
Capability MaturityModel
Integration
Accelerating Software
Technology Adoption
COTS-Based Systems
Dependable Systems Upgrade
Architecture Tradeoff Analysis
Technical PracticeInitiatives
Team Software Process
Software Engineering
Measurement & Analysis
Survivable Systems
Product Line Practice
Predictable Assembly
with Certifiable
Components
The right software delivered defect free, on time, every time
High confidence, evolvable,product lines
with predictable and improvedcost, schedule, and quality
7
The Unfinished RevolutionThe 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 SpaceSource 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
host-OS
Does the method assume a component virtual machine?
10
Commercial v. Custom Source
component-VM
host-OS
Does the method emphasize specification of components or assembly of preexisting components? (If preexisting then commercial source)
commercial custom
11
Application v. Infrastructure
infrastructure
applicationcomponent-VM
host-OS
customcommercial
Does the method focus on building applications or infrastructure?
12
Component/Method Space
component-VM
host-OS
customcommercial
application
infrastructure
Custom infrastructure: for all intents a black hole (projects that enter never escape)
13
Component/Method Space
component-VM
host-OS
customcommercial
application
infrastructure
UML Components & Component Factory both assume use of a framework and focus on component specification for business applications
14
Component/Method Space
application
customcommercial
component-VM
host-OS
Catalysis does not assume a framework but neither does it directly address enterprise system needs. It is application focused.infrastructure
15
Component/Method Space
component-VM
host-OS
customcommercial
application
infrastructure
The book I am writing with Hissam and Seacord focuses on design problems that are dominated by commercial software components
16
Component/Method Space
customcommercial
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
host-OS
infrastructure
component-VM
17
Component/Method Space
component-VM
host-OS
customcommercial
application
infrastructureThis area is still science fiction.There is research in “programmable middleware,” but this is a remote possibility for near-term commercial use.
18
Component/Method Space
component-VM
host-OS
application
infrastructure
customcommercial
