Lecture 3 System Architecture

Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)

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

View Full Document Right Arrow Icon
Copyright W. Howden 1 Lecture 3: Elaboration and System Architecture
Background image of page 1

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

View Full DocumentRight Arrow Icon
Copyright W. Howden 2 Topics • System design oriented software architecture concepts – component structures • UML and the representation of architecture – components • Java and architectural components –fo
Background image of page 2
Copyright W. Howden 3 Why Now? • System Architecture is often considered design, not requirements/elaboration • Personal past experience – Have a ready system metaphor we can use • Industry past experience – Study other experiences to get some insight • Examine technology to see what it will support
Background image of page 3

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

View Full DocumentRight Arrow Icon
Copyright W. Howden 4 System Architecture • Basic Pieces of the system – Components, Modules, Subsystems • Structure of the System – Relationships between pieces • Solution Strategies for System – Is this Architecture? – E.g. Analysis and Design Mechanisms
Background image of page 4
Copyright W. Howden 5 Mechanisms Analysis Design Implementation Persistency Relational DBMS JDBC Distribution Remote Method Invocation Java 2
Background image of page 5

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

View Full DocumentRight Arrow Icon
Copyright W. Howden 6 Tiers • Physical tiers – Separate machines, e.g. client/server • Logical tiers – Logical components, e.g. GUI, Business Logic, Data- Base • Refinements – E.g. • Thin client: presentation logic only • Fat client: presentation logic plus business logic
Background image of page 6
Copyright W. Howden 7 Layers • From OS – layers of progressively more abstract machines, each of which uses the services of lower levels • Logical Tiers and Layers GUI Business/Application/Domain Logic Data Base
Background image of page 7

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

View Full DocumentRight Arrow Icon
Copyright W. Howden 8 Model-View Separation • Layers model for GUI oriented application: View-GUI Model • View layer displays information known from model layer • Why? – Divide and conquer approach to development – Can make changes to GUI without touching the “guts” of the system
Background image of page 8
Copyright W. Howden 9 Model View Controller • View = graphics presentation • Model = Business Logic • Controller = respond to input from View by
Background image of page 9

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

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

This note was uploaded on 02/11/2008 for the course CSE 111 taught by Professor Howden during the Fall '07 term at UCSD.

Page1 / 30

Lecture 3 System Architecture - Lecture 3: Elaboration and...

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

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