15_Implementing_Architectures

15_Implementing_Architectures - Implementing Architectures

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. Implementing Architectures Software Architecture Lecture 15
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Foundations, Theory, and Practice Software Architecture Software Architecture Objectives Concepts Implementation as a mapping problem Architecture implementation frameworks Evaluating frameworks Relationships between middleware, frameworks,  component models Building new frameworks Concurrency and generative technologies Ensuring architecture-to-implementation consistency Examples Different frameworks for pipe-and-filter Different frameworks for the C2 style Application Implementing Lunar Lander in different frameworks
Background image of page 2
3 Foundations, Theory, and Practice Software Architecture Software Architecture Objectives Concepts Implementation as a mapping problem Architecture implementation frameworks Evaluating frameworks Relationships between middleware, frameworks,  component models Building new frameworks Concurrency and generative technologies Ensuring architecture-to-implementation consistency Examples Different frameworks for pipe-and-filter Different frameworks for the C2 style Application Implementing Lunar Lander in different frameworks
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Foundations, Theory, and Practice Software Architecture Software Architecture The Mapping Problem Implementation is the one phase of software engineering that is not  optional Architecture-based development provides a unique twist on the  classic problem It becomes, in large measure, a  mapping  activity Maintaining mapping means ensuring that our architectural intent is  reflected in our constructed systems Design Decisions Implementation Artifacts
Background image of page 4
5 Foundations, Theory, and Practice Software Architecture Software Architecture Common Element Mapping Components and Connectors Partitions of application computation and  communication functionality Modules, packages, libraries, classes, explicit  components/connectors in middleware Interfaces Programming-language level interfaces (e.g.,  APIs/function or method signatures) are common State machines or protocols are harder to map
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 Foundations, Theory, and Practice Software Architecture Software Architecture Common Element Mapping (cont’d) Configurations Interconnections, references, or dependencies  between functional partitions May be implicit in the implementation May be externally specified through a MIL and  enabled through middleware May involve use of reflection Design rationale Often does not appear directly in implementation Retained in comments and other documentation
Background image of page 6
7 Foundations, Theory, and Practice Software Architecture Software Architecture
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/24/2010 for the course CS 578 taught by Professor Staff during the Spring '08 term at USC.

Page1 / 31

15_Implementing_Architectures - Implementing Architectures

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online