Software Architecture or Component Frameworks? Alexander L. Wolf University of Colorado at Boulder

Slides:



Advertisements
Similar presentations
Vrije Universiteit amsterdamPostacademische Cursus Informatie Technologie Software architecture architecture -- components and boundaries case study --
Advertisements

Software Architecture Lecture 3
PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. Basic Concepts Software Architecture Lecture 3.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. Domain-Specific Software Architecture and Product Lines Software.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 43 Introduction to Software Engineering.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 3 – Building.
Shared Technical Architecture’s Role within the ECIO Organization “Arkansas Shared Technical Architecture”
Analysis of Software Architectures. What Is Architectural Analysis? Architectural analysis is the activity of discovering important system properties.
Distributed Software Architecture and Distributed Systems Middleware Eric M. Dashofy Department of Information and Computer Science University of California,
Domain-Specific Software Architecture and Product Lines
ECEN5053 SW Eng of Dist Systems, Arch Des Part 2, Univ of Colorado, Boulder1 Architectural Design of Distributed Systems, Part 2 ECEN5053 SW.
What is software engineering?
Sharing Systems and Resources ICRS: Where to start?
8-9 May 2000WESAS Experience with Software Architectures and Configured Software Descriptions Walt Scacchi James S. Choi Institute for Software Research.
1 Software Licenses, Open Source Components, and Open Architectures Thomas Alspaugh, Hazeline Asuncion, Walt Scacchi Institute for Software Research University.
Institute for Software Research©2001, University of California, Irvine Product-Line Architectures André van der Hoek Institute for Software Research University.
QoS-enabled middleware by Saltanat Mashirova. Distributed applications Distributed applications have distinctly different characteristics than conventional.
Problems with reuse – Increased maintenance costs; lack of tool support; not-invented- here syndrome; creating, maintaining, and using a component library.
INFO 355Week #61 Systems Analysis II Essentials of design INFO 355 Glenn Booker.
SOEN 6011 Software Engineering Processes
1 Refining Reliability Estimation of Mobile Software Systems The International Workshop on Software Architectures and Mobility, ICSE-SAM 2008, Leipzig,
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
Chapter 10 Architectural Design
DEEPAK BHIMARAJU; EDWARD ALLEN TEST CHALLENGES IN THE CLOUD.
4.x Performance Technology drivers – Exascale systems will consist of complex configurations with a huge number of potentially heterogeneous components.
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
Object-Oriented Analysis and Design OVERVIEW. Objectives  Describe Information Systems  Explain the role of a systems analyst  Introduce object-oriented.
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 12.
Patch Management Only part of the solution….. Bob Isaak Mar 04, 2004.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. Implementing Architectures Software Architecture.
CS480 Computer Science Seminar Introduction to Microsoft Solutions Framework (MSF)
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Modeling and Simulating Software Acquisition Process Architectures James Choi and Walt Scacchi Computer Science Dept. Institute for Software Research California.
Chapter 6 Architectural Design.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Systems Analysis and Design in a Changing World, Fourth Edition
Presented By Riyadh Mahmood 3/2/2010 Software Architecture Styles for Network-based Applications Original Paper by: Roy T. Fielding.
Process: A Generic View
Software Deployment and Mobility. Introduction Deployment is the placing of software on the hardware where it is supposed to run. Redeployment / migration.
Tolerating Intrusions Through Secure System Reconfiguration Dennis Heimbigner and Alexander Wolf University of Colorado at Boulder John Knight University.
Basic Concepts and Definitions
Improving System Availability in Distributed Environments Sam Malek with Marija Mikic-Rakic Nels.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 6 - Essentials of Design an the Design Activities.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
+ Informatics 122 Software Design II Lecture 13 Emily Navarro Duplication of course material for any commercial purpose without the explicit written permission.
P ERSONAL & TEAM PROCESS MODELS Lecture 05 Part -2.
The Software Lifecycle Stuart Faulk. Definition Software Life Cycle: evolution of a software development effort from concept to retirement Life Cycle.
Introduction to Systems Analysis and Design
Business System Development
Software Architecture Lecture 3
Software Architecture
Software Architecture Lecture 3
CS & CS Capstone Project & Software Development Project
Software Architecture Lecture 3
The Extensible Tool-chain for Evaluation of Architectural Models
Design Model Like a Pyramid Component Level Design i n t e r f a c d s
Implementing Architectures
Software Architecture Lecture 3
Software Architecture Lecture 3
Project Phases ‘98 ‘00 ‘02 ‘04 ‘06 Preparatory Phase
Exploiting Semantics for Event Detection Systems
Software Architecture Lecture 3
COMPONENT BASED SYSTEMS: A CLASSIFICATION OF ISSUES
Presentation transcript:

Software Architecture or Component Frameworks? Alexander L. Wolf University of Colorado at Boulder

What Have You Done for Me Lately? u Software architecture –prototype formal notations –prototype design environments –assessment practices u Component frameworks –inherently support distributed systems –compatible with popular OO methods –supported by commercial products u The “charitable” view –Component frameworks support only a specific architecture –Software architecture technology seeks to be general

Component Frameworks are Here Today From: “Experience with Software Architectures and Configured Software Descriptions” by Walt Scacchi, University of California, Irvine James S. Choi, California State University, Fullerton

Architecture vs. Component Frameworks u Reduced risk? u Predictability of scalability, reliability, deployability, maintainability? u Skill value? u Market interest?

One Attempt at Relating the Two Comp Middleware OS + NetworkOS + N Middleware 1 OS + Network OS + N Connector Middleware 2 Connector Comp Connector Process Boundaries Architectural Style? Architectural Style Process Boundaries From: “The Role of Middleware in Software Architectures” by Eric Dashofy, University of California, Irvine

Some Challenge Problems u Capturing and supporting a component framework as an architectural style u Modeling and analyzing component frameworks as software architectures u Providing a rigorous method to choose among alternative component frameworks (as architectures, not as products) u Showing how to integrate some software architecture technology into an existing component framework support system