Logical Architecture and UML Package Diagrams

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

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
COMP1007 Introduction to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
October 23, 2001 Software Design-Layering and Packaging1 Architecture: Layers and Packages.
Chapter 9 Designing Systems for Diverse Environments.
March R McFadyen1 Architecture Architecture involves the set of significant decisions about the organization of a software system, decisions.
March R McFadyen1 Architecture Architecture involves the set of significant decisions about the organization of a software system, decisions.
Technical Architectures
© Lethbridge/Laganière 2001 Chapter 9: Architecting and designing software1 Layers Data from IBM-Rational and Craig Larman…
Object Oriented Analysis and Design
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
CMPT 370: Information Systems Design Instructor: Curtis Cartmill, Simon Fraser University – Summer 2003 Lecture Topic: Layered Architecture Class Exercise:
1 A Student Guide to Object- Orientated Development Chapter 9 Design.
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.
System Design Decomposing the System. Sequence diagram changes UML 2.x specifications tells that Sequence diagrams now support if-conditions, loops and.
Web Application Architecture: multi-tier (2-tier, 3-tier) & mvc
Objectives Design Class Diagrams Issues in system design Generalization Review UML papers.
Copyright © 2012 Accenture All Rights Reserved.Copyright © 2012 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are.
The Design Discipline.
Chapter 13 Starting Design: Logical Architecture and UML Package Diagrams.
Systems Analysis and Design in a Changing World, Fifth Edition
Logical Architecture and UML Package Diagrams 徐迎晓 复旦大学软件学院.
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.
4/2/03I-1 © 2001 T. Horton CS 494 Object-Oriented Analysis & Design Software Architecture and Design Readings: Ambler, Chap. 7 (Sections to start.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 11 Subsystem Design.
Requirements To Design--Iteratively Chapter 12 Applying UML and Patterns Craig Larman.
SOFTWARE DESIGN.
Chapter 9 Moving to Design
Object-Oriented Design Principles and Patterns. © 2005, James R. Vallino2 How Do You Design? What principles guide you when you create a design? What.
Chapter 13 Logical Architecture and UML Package Diagrams 1CS6359 Fall 2012 John Cole.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
What to remember from Chap 13 (Logical architecture)
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
1 CMPT 275 High Level Design Phase Modularization.
Chapter 10 Drawing System Sequence Diagrams
Patterns Roberto Damiani Mendes. Roteiro Definition; Definition; Architecture Patterns; Architecture Patterns; Design Patterns; Design Patterns; GRASP.
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.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Slide 1 What the business needs  How to build it Functional requirements  + Nonfunctional requirements Performance System environment issues Problem.
TK2023 Object-Oriented Software Engineering CHAPTER 8 LOGICAL ARCHITECTURE.
CSC 480 Software Engineering High Level Design. Topics Architectural Design Overview of Distributed Architectures User Interface Design Guidelines.
OOD OO Design. OOD-2 OO Development Requirements Use case analysis OO Analysis –Models from the domain and application OO Design –Mapping of model.
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.
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
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
UML Diagrams By Daniel Damaris Novarianto S..
OO Methodology OO Architecture.
UML dynamic Modeling (Behavior Diagram)
Chapter 13 Logical Architecture.
Figure 30.2 Layers in NextGen
Starting Design: Logical Architecture and UML Package Diagrams
Design and Implementation
Chapter 13 Logical Architecture.
An Introduction to Software Architecture
The Islamia University Bahawalpur
Design Yaodong Bi.
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Chapter 6: Architectural Design
Chapter 13 Logical Architecture.
Logical Architecture & UML Package Diagrams
Presentation transcript:

Logical Architecture and UML Package Diagrams Chapter 13 Applying UML and Patterns

Definition Software Architecture:There are various forms of it. But the common theme is that it has to do with large scale-the Big Ideas in the forces, organization, styles, patterns, responsibilities, collaborations, connections and motivations of a system and major subsystems.

Definition variance In software development, architecture is thought of as both noun and a verb. As a noun, the architecture includes the organization and structure of the major elements of the system. As a verb, architecture is part investigation and part design work.

Definition Architectural investigation: involves functional and non-functional requirements that have impact on system design. Some of these are: Market trends, performance, cost and points of evolution. Architectural Design: is the resolution of these requirements in the design of software.

Architectural Dimension and Views in UP The common dimensions are: The logical architecture, describes the system in terms of its conceptual organization in layers, packages, classes, interfaces and subsystems. The deployment architecture, describes the system in terms of the allocation of process to processing unit and network configurations.

What is a layer? “A layer is a coarse grained grouping of classes packages or subsystems that has cohesive responsibility for a major aspect of the system.” Higher layers call upon the services of lower layers.

Architectural Patterns and Pattern Categories Architectural patterns: Relates to large-scale design and typically applied during the early iterations(in elaboration phase). Design patterns: Relates to small and medium-scale design of objects and frameworks. Idioms: Relates to language or implementation-oriented low-level design solutions.

Architectural Pattern:Layers Idea behind Layer patterns: Organize the large-scale logical structure of a system into discrete layers of distinct, related responsibilities with a clean, cohesive separation of concerns such that the “lower” layers are low-level and general services, and the higher layers are more application specific. Collaboration and coupling is from higher to lower layers.

Inter-Layer and Inter-Package Coupling It is informative to include a diagram in the logical view that shows the coupling between the layers and packages. Following figure shows the coupling.

Partial coupling between Packages

Inter-Layer and Inter-Package Interaction Emphasizes the dynamics of how objects across the layers connect and communicate. The interaction diagram focuses on the logical view and on the collaborations between the layers and package boundaries.

Package Diagrams UML Package Diagrams are often used to show the contents of components, which are often packages in the Java sense. Each package represents a namespace. Packages, as components, can be nested inside other packages.

Package Diagram UI Domain Swing Web Sales

Logical vs. Process and Deployment of Architecture Architectural Layers are a logical view of the architecture They are not a deployment view of elements to process. Depending on platform, all layers could be deployed within the same process on same node. Or across many computers.

Terminology:Tier, Layers, and Partitions Tier relates to physical processing node or clusters of node, such as “client tier”. Layers of an architecture represent the vertical slices Partitions represents a horizontal division of relatively parallel subsystems of a layer.

  Layers and Partitions

How do we design application logic with objects? We could create one class and put all logic in it, but that violates the whole spirit of object orientation. We create software objects with names drawn from the real world, and assign application logic responsibilities to them. It takes a lot of skill and experience to do a good job of choosing objects and assigning responsibilities.

Domain Layer and Domain Model These are not the same thing. Domain model shows the real world, while the Domain layer shows the software architecture. But the Domain model inspires the Domain layer, and is the source of many of the concept, especially class names. Do not confuse the problem with the solution.

Information Systems In IS layered architecture was known as three-tier architecture. A three-tier architecture has interface, Application logic and a storage. The singular quality of 3-tier architecture is: Separation of the application logic into distinct logical middle tier of software. The interface tier is relatively free of application processing.

Information Systems(cont..) The middle tier communicates with the back-end storage layer. The following is an example of 3-tier architecture.

Example:

Two-tier Design In this design, the application logic is placed within window definitions, which read and writes directly to database. There is no middle tier that separates out the application logic.

The Model-View Separation Principle The principle states that model(domain) objects should not have direct knowledge of view(presentation) objects. Furthermore, the domain classes should encapsulate the information and behavior related to application logic.

Need for Model-View separation To support cohesive model definitions that focus on the domain process, rather than on interfaces. To allow separate development of the model and user interface layers. To minimize the impact of requirements changes in the interface upon the domain layer. To allow new views to be easily connected to an existing domain layer, without affecting the domain layer.

Continue.. To allow multiple simultaneous views on the same model object. To allow execution of the model layer independent of the user interface layer To allow easy porting of the model layer to another user interface framework.