Chapter 13 Logical Architecture.

Slides:



Advertisements
Similar presentations
Software Architecture Design Chapter 12 Part of Design Analysis Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
Advertisements

A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Object-Oriented Analysis and Design CHAPTERS 12-14: INTRODUCTION TO DESIGN 1.
March R McFadyen1 Architecture Architecture involves the set of significant decisions about the organization of a software system, decisions.
© Lethbridge/Laganière 2001 Chapter 9: Architecting and designing software1 Layers Data from IBM-Rational and Craig Larman…
1 © Wolfgang Pelz UML3 UML 3 Notations describe how to use reusable software. Package Component Deployment Node.
1 CS 426 Senior Projects Chapter 19: Interfaces and Components [Arlow & Neustadt 2005] February 28, 2008.
Oct. 9, 2003CS WPI1 CS 509 Design of Software Systems Lecture #6 Thursday, Oct. 9, 2003.
1 CS 691z / 791z Topics on Software Engineering Chapter 17: Interfaces and Subsystems [Arlow & Neustadt, 2002] March 6, 2007.
Logical Architecture and UML Package Diagrams
March R McFadyen1 Figure 30.2 Layers in NextGen They only have three layers in this architecture Each layer is shown as a UML Package No separate.
The Design Discipline.
Chapter 13 Starting Design: Logical Architecture and UML Package Diagrams.
Systems Analysis and Design in a Changing World, Fifth Edition
UML - Development Process 1 Software Development Process Using UML (2)
Logical Architecture and UML Package Diagrams 徐迎晓 复旦大学软件学院.
Requirement Analysis Functional & Non-Functional Requirements Scenarios Use cases: – View Fixtures – Manage Tournament – Register Team – Report Discrepancy.
An Introduction to Software Architecture
BTS430 Systems Analysis and Design using UML Domain Model Part 1—Finding Conceptual Classes.
12 Systems Analysis and Design in a Changing World, Fifth Edition.
Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman.
COMP 6471 Software Design Methodologies Winter 2006 Dr Greg Butler
Systems Analysis and Design in a Changing World, 3rd Edition
Chapter 13 Logical Architecture and UML Package Diagrams 1CS6359 Fall 2012 John Cole.
© 2005 Prentice Hall10-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
GRASP: Designing Objects with Responsibilities
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
What to remember from Chap 13 (Logical architecture)
Part VII: Design Continuous
Lecture 18: Object-Oriented Design
UML Package Diagrams. Package Diagrams UML Package Diagrams are often used to show the contents of components, which are often packages in the Java sense.
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
Chapter 19: Interfaces and Components [Arlow and Neustadt, 2005] University of Nevada, Reno Department of Computer Science & Engineering.
SOEN 343 Software Design Section H Fall 2006 Dr Greg Butler
Computer Science 340 Software Design & Testing Software Architecture.
TK2023 Object-Oriented Software Engineering CHAPTER 8 LOGICAL ARCHITECTURE.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
Object and Class Structuring Chapter 9 Part of Analysis Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
BTS430 Systems Analysis and Design using UML
Introduction. System Design Hardware/Software Platform Selection Software Architectures Database Design Human-Computer Interaction (HCI) Interface Object.
OBJECT ORIENTED VS STRUCTURED WHICH ONE IS YOUR CHOICE.
Copyright © Craig Larman All Rights Reserved Large-Scale System Partitioning.
Logical Architecture and UML Package Diagrams. The logical architecture is the large-scale organization of the software classes into packages, subsystems,
Design Concepts ch-8
GRASP – Designing Objects with Responsibilities
Architecture Brief Pepper
Layers Data from IBM-Rational and Craig Larman’s text integrated into these slides. These are great references… Slides from these sources have been modified.
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
OO Methodology OO Architecture.
BTS530: Major Project Planning and Design
Use Case Realization Describes a collaboration among analysis classes that shows how a specific use case is realized Consists of flow-of-events analysis,
Chapter 13 Logical Architecture.
Chapter 19: Interfaces and Components
Figure 30.2 Layers in NextGen
Object oriented analysis and design
Starting Design: Logical Architecture and UML Package Diagrams
An Introduction to Software Architecture
The Islamia University Bahawalpur
Chapter 19: Interfaces and Components
Chapter 19: Interfaces and Components
Software Analysis.
Design Yaodong Bi.
Interfaces and Components
Extending Interface Based Design
Chapter 19: Interfaces and Components
Chapter 13 Logical Architecture.
Logical Architecture & UML Package Diagrams
Presentation transcript:

Chapter 13 Logical Architecture

Logical Architecture Large-scale organization of classes Packages Subsystems Layers Tools - UML package diagrams

Layer Coarse grained Cohesive responsibility Strict or relaxed E.g. User Interface Strict or relaxed

Software Architecture Many definitions Key aspect: Large scale, big ideas Motivation Constraints Organization Patterns Responsibilities Connections

Design with Layers Organize layers using related responsibilities Collaboration and Coupling Layers Pattern Model view controller pattern

Why? Separation of concerns Encapsulate complexity Replaceable Reusable function Team organization

Domain layer vs. Application Layer Application layer organization Create domain object that encapsulate application logic (Domain Layer) Domain layer != Domain model However - many domain model concepts become domain layer classes

Terminology Tier - current usage: physical nodes Layers Partitions - parallel division of layers

SSD, System Operations, Layers When there is a UI layer: SSD shows operations to the UI Layer

Summary Separation into layers is a common first step In Architecture centric design, this flows from the software architecture