|
|
|
- Elinor May
- 6 years ago
- Views:
Transcription
1 Software Engineering Sequence 3, /50 Software Engineering
2 Plan /50 Software Engineering
3 ground Evolution of Program 3/50 Software Engineering
4 Definition What is a design pattern Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice. [C. Alexander 77] 4/50 Software Engineering
5 Definition What is a design pattern Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice. [C. Alexander 77] The design patterns are descriptions of communicating objects and classes that are customized to solve a general design problem in a particular context.[e. Gamma 97] 4/50 Software Engineering
6 Definition Essential elements Pattern name: describes a design problem, its solutions, and consequences in a word or two Problem: describes when to apply the pattern Solution: describes the elements that make up the design, their relationship, responsibilities and collaborations Consequences: the results and trade-offs of applying the pattern 5/50 Software Engineering
7 Sources A Pattern Language: Towns, Buildings, Construction : Christopher Alexander, Sara Ishikawa and Murray Silverstein Design Patterns, Elements of Reusable Object-Oriented Software : Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides wikipedia: design patterns 6/50 Software Engineering
8 Categories Pattern can be divided into three categories with respect to their purpose. Creational patterns: the process of object creation Structural patterns: the composition of classes or objects Behavioral patterns: the ways in which classes or objects interact and distribute responsibility 7/50 Software Engineering
9 List Abstract Factory: provide an interface for creating families of related or dependent objects without specifying their concrete classes. Builder: separate the construction of a complex object from its representation. Prototype: specify the kinds of objects to create using a prototypical instance, and create new objects by copying this prototype. Singleton: ensure a class only has one instance, and provide a global point of access to it. 8/50 Software Engineering
10 Abstract factory Problem: create the group of objects without knowing their exact concrete class Example: program with a GUI Mac and Windows (manager the elements of graphic interface) Solution: the creation of the object is transferred to another specific class 9/50 Software Engineering
11 Abstract factory: structure 10/50 Software Engineering
12 User interface toolkit 11/50 Software Engineering
13 Factory code public abstract class Button { public abstract void paint(); public class WinButton extends Button { public void paint(){... public class MacButton extends Button { public void paint(){... 12/50 Software Engineering
14 Factory code public abstract class Button { public abstract void paint(); public class WinButton extends Button { public void paint(){... public class MacButton extends Button { public void paint(){... 12/50 Software Engineering
15 Factory code public abstract class ScrollBar { public abstract void paint(); public class WinScrollBar extends ScrollBar { public void paint(){... public class MacScrollBar extends ScrollBar { public void paint(){... 13/50 Software Engineering
16 Factory code public abstract class ScrollBar { public abstract void paint(); public class WinScrollBar extends ScrollBar { public void paint(){... public class MacScrollBar extends ScrollBar { public void paint(){... 13/50 Software Engineering
17 Factory code public abstract class GUIFactory { public Button createbutton(); public ScrollBar createscrollbar(); public class WinFactory extends GUIFactory { public Button createbutton(){ return new WinButton(); public ScrollBar createscrollbar(){ return new WinScrollBar(); public class MacFactory extends GUIFactory {... 14/50 Software Engineering
18 Factory code public abstract class GUIFactory { public Button createbutton(); public ScrollBar createscrollbar(); public class WinFactory extends GUIFactory { public Button createbutton(){ return new WinButton(); public ScrollBar createscrollbar(){ return new WinScrollBar(); public class MacFactory extends GUIFactory {... 14/50 Software Engineering
19 Factory code GUIFactory guifactory; Button button; ScrollBar scrollbar; if (ismac()) { guifactory=new MacFactory(); if (iswin()) { guifactory=new WinFactory(); button=guifactory.createbutton(); scrollbar=guifactory.createscrollbar(); 15/50 Software Engineering
20 Factory code GUIFactory guifactory; Button button; ScrollBar scrollbar; if (ismac()) { guifactory=new MacFactory(); if (iswin()) { guifactory=new WinFactory(); button=guifactory.createbutton(); scrollbar=guifactory.createscrollbar(); 15/50 Software Engineering
21 Factory code GUIFactory guifactory; Button button; ScrollBar scrollbar; if (ismac()) { guifactory=new MacFactory(); if (iswin()) { guifactory=new WinFactory(); button=guifactory.createbutton(); scrollbar=guifactory.createscrollbar(); 15/50 Software Engineering
22 Factory code GUIFactory guifactory; Button button; ScrollBar scrollbar; if (ismac()) { guifactory=new MacFactory(); if (iswin()) { guifactory=new WinFactory(); button=guifactory.createbutton(); scrollbar=guifactory.createscrollbar(); 15/50 Software Engineering
23 Abstract Factory 16/50 Software Engineering
24 Singleton 17/50 Software Engineering
25 Singleton Problem: guarantee that one class has only one instance; one unique and global access point to this instance Example: class represents the configuration of a system; class manipulates the window of one application Solution: intercept requests to create new objects; define a static method that returns the instance 18/50 Software Engineering
26 Singleton code public class Singleton { private static Singleton instance; private Singleton() { public static Singleton getinstance() { if (Singleton.instance==null) { Singleton.instance=new Singleton(); return Singleton.instance; Singleton s1=singleton.getinstance(); Singleton s2=singleton.getinstance(); System.out.println(s1==s2); 19/50 Software Engineering
27 List Adapter: convert the interface of a class into another interface clients expect. Bridge: decouple an abstraction from its implementation so that the two can vary independently. Composite: compose objects into tree structures to represent part-whole hierarchies. Decorator: attach additional responsibilities to an object dynamically to extend functionality. Facade: provide a unified interface to a set of interfaces in a subsystem. 20/50 Software Engineering
28 Composite Problem Represent the set of objects by the tree structure Let clients treat individual objects and compositions of objects uniformly. 21/50 Software Engineering
29 Composite Problem Represent the set of objects by the tree structure Let clients treat individual objects and compositions of objects uniformly. Example A draw application (a line and the set of lines should be treated in the same way) An arithmetic expression 21/50 Software Engineering
30 Composite Problem Represent the set of objects by the tree structure Let clients treat individual objects and compositions of objects uniformly. Example A draw application (a line and the set of lines should be treated in the same way) An arithmetic expression Solution an abstract class representing an object or a tree a child class representing the leafs a child class representing a node of the tree 21/50 Software Engineering
31 Composite: example 22/50 Software Engineering
32 Composite: example 22/50 Software Engineering
33 Composite: example 22/50 Software Engineering
34 Composite: structure 23/50 Software Engineering
35 Composite Pattern objects Component: interface for all objects in this pattern (interface or an abstract class with some methods common to all objects). Leaf: the behaviors for the primitive elements. It is the building block and implements base component. Composite: consists of leaf or composite elements (children) and implements the operations by calling those of its children. 24/50 Software Engineering
36 Composite code public interface Shape { public void draw (String fillcolor); public class Triangle implements Shape { public void draw(string fillcolor) { System.out.println("Drawing Triangle with color"+fillcolor); public class Circle implements Shape { public void draw(string fillcolor) { System.out.println("Drawing Circle with color"+fillcolor); 25/50 Software Engineering
37 Composite code public interface Shape { public void draw (String fillcolor); public class Triangle implements Shape { public void draw(string fillcolor) { System.out.println("Drawing Triangle with color"+fillcolor); public class Circle implements Shape { public void draw(string fillcolor) { System.out.println("Drawing Circle with color"+fillcolor); 25/50 Software Engineering
38 Composite code public class Drawing implements Shape { private List<Shape> shapes = new ArrayList<Shape>(); public void draw (String fillcolor) { for(shape sh : shapes) sh.draw(fillcolor); public void add (Shape s) { this.shapes.add(s); public void remove (Shape s) { shapes.remove(s); public void clear () { shapes.clear(); System.out.println("Clearing all shapes"); 26/50 Software Engineering
39 Composite code public class Drawing implements Shape { private List<Shape> shapes = new ArrayList<Shape>(); public void draw (String fillcolor) { for(shape sh : shapes) sh.draw(fillcolor); public void add (Shape s) { this.shapes.add(s); public void remove (Shape s) { shapes.remove(s); public void clear () { shapes.clear(); System.out.println("Clearing all shapes"); 26/50 Software Engineering
40 Composite code Shape tri = new Triangle(); Shape tri1 = new Triangle(); Shape cir = new Circle(); Drawing drawing = new Drawing(); drawing.add(tri); drawing.add(tri1); drawing.add(cir); drawing.draw( Red ); drawing.clear(); drawing.add(tri); drawing.add(cir); drawing.draw( Green ); 27/50 Software Engineering
41 Composite code Shape tri = new Triangle(); Shape tri1 = new Triangle(); Shape cir = new Circle(); Drawing drawing = new Drawing(); drawing.add(tri); drawing.add(tri1); drawing.add(cir); drawing.draw( Red ); drawing.clear(); drawing.add(tri); drawing.add(cir); drawing.draw( Green ); Results Drawing Triangle with color Red Drawing Triangle with color Red Drawing Circle with color Red Clearing all the shapes from drawing Drawing Triangle with color Green Drawing Circle with color Green 27/50 Software Engineering
42 Composite code Shape tri = new Triangle(); Shape tri1 = new Triangle(); Shape cir = new Circle(); Drawing drawing = new Drawing(); drawing.add(tri); drawing.add(tri1); drawing.add(cir); drawing.draw( Red ); drawing.clear(); drawing.add(tri); drawing.add(cir); drawing.draw( Green ); Results Drawing Triangle with color Red Drawing Triangle with color Red Drawing Circle with color Red Clearing all the shapes from drawing Drawing Triangle with color Green Drawing Circle with color Green 27/50 Software Engineering
43 Composite hierarchy 28/50 Software Engineering
44 Facade Problem unified interface by defining a higher-level interface that makes the subsystem easier to use. 29/50 Software Engineering
45 Facade Problem unified interface by defining a higher-level interface that makes the subsystem easier to use. Example recuperate old codes that are hard to be refactored several complex interfaces 29/50 Software Engineering
46 Facade Problem unified interface by defining a higher-level interface that makes the subsystem easier to use. Example recuperate old codes that are hard to be refactored several complex interfaces Solution one high-level class that reuses the useful functionalities 29/50 Software Engineering
47 Facade: goal 30/50 Software Engineering
48 Facade: structure 31/50 Software Engineering
49 Facade code class ComplexeA1{ public void actiona11 () {... public void actiona12 () {... class ComplexeA2{ public void actiona21 () {... public void actiona22 () {... class ComplexeB1 { public void actionb11 () {... public void actionb12 () {... class ComplexeB2 { public void actionb21 () {... public void actionb22 () {... 32/50 Software Engineering
50 Facade code class Facade { complexea1 a1; complexeb2 b2; Facade(){ a1=new ComplexeA1(); b2=new ComplexeB2(); void performactionsab1 () { a1.actiona11(); b2.actionb22(); void performactionsab2 () { a1.actiona11(); a1.actiona12(); b2.actionb21(); 33/50 Software Engineering
51 Facade code class Facade { complexea1 a1; complexeb2 b2; Facade(){ a1=new ComplexeA1(); b2=new ComplexeB2(); void performactionsab1 () { a1.actiona11(); b2.actionb22(); void performactionsab2 () { a1.actiona11(); a1.actiona12(); b2.actionb21(); Facade facade=new Facade(); facade.performactionab1(); 33/50 Software Engineering
52 List Command: an object is used to encapsulate all information needed to perform an action or trigger an event at a later time. Interpreter: define a representation for the grammar of a given language with an interpreter to interpret sentences in this language. Iterator: provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation. 34/50 Software Engineering
53 List Observer: define a one-to-many dependency between objects so that one object changes state, all its dependents are notified and updated automatically. State: allow an object to alter its behavior when its internal state changes. Strategy: define a family of algorithms such that they are interchangeable. Visitor: separate an algorithm from an object by defining a new operation without changing the classes of the elements on which it operates. 35/50 Software Engineering
54 Strategy Problem Allow different algorithms for the same object 36/50 Software Engineering
55 Strategy Problem Allow different algorithms for the same object Example Robots with different behaviors Different sorting algorithms 36/50 Software Engineering
56 Strategy Problem Allow different algorithms for the same object Example Robots with different behaviors Different sorting algorithms Solution The algorithms are encapsulated by classes. The class using the algorithm will have an instance of this class as attribute. 36/50 Software Engineering
57 Strategy: structure 37/50 Software Engineering
58 Strategy code abstract class SortStrategy { abstract void sort (List list); class Quick extends SortStrategy { void sort (List list) {... class Merge extends SortStrategy { void sort (List list) {... 38/50 Software Engineering
59 Strategy code abstract class SortStrategy { abstract void sort (List list); class Quick extends SortStrategy { void sort (List list) {... class Merge extends SortStrategy { void sort (List list) {... 38/50 Software Engineering
60 Strategy code class List { private List elements; private SortStrategy ss; public void setsort (SortStrategy s) { this.ss=s; public void sort () { this.ss.sort(this.elements); 39/50 Software Engineering
61 Strategy code class List { private List elements; private SortStrategy ss; public void setsort (SortStrategy s) { this.ss=s; public void sort () { this.ss.sort(this.elements); 39/50 Software Engineering
62 Observer Problem Allow following the state modification of an object 40/50 Software Engineering
63 Observer Problem Allow following the state modification of an object Example Graphic interface depending on the application engine. Model-View-Controller 40/50 Software Engineering
64 Observer Problem Allow following the state modification of an object Example Graphic interface depending on the application engine. Model-View-Controller Solution The observable is linked to all its observers The observable should notify all its observers when its state is changed Each observer requires the necessary information 40/50 Software Engineering
65 Observer: example 41/50 Software Engineering
66 Observer: example 42/50 Software Engineering
67 Observer: structure 43/50 Software Engineering
68 Observer code class Subject { private List<Observer> observers; private int state; public void setstate (int val) { state=val; notifyall(); public void attach (Observer ons) { observers.add(obs); public void notifyall () { for (Observer obs: observers) obs.update(); 44/50 Software Engineering
69 Observer code class Subject { private List<Observer> observers; private int state; public void setstate (int val) { state=val; notifyall(); public void attach (Observer ons) { observers.add(obs); public void notifyall () { for (Observer obs: observers) obs.update(); 44/50 Software Engineering
70 Observer code abstract class Observer { protected Subject subject; public abstract void update(); class ConcreteObserver { public ConcreteObserver(Subject sub) { this.subject=sub; this.subject.attach(this); public void update () { System.out.println("new value: " +subject.getvalue()); 45/50 Software Engineering
71 Observer code abstract class Observer { protected Subject subject; public abstract void update(); class ConcreteObserver { public ConcreteObserver(Subject sub) { this.subject=sub; this.subject.attach(this); public void update () { System.out.println("new value: " +subject.getvalue()); 45/50 Software Engineering
72 MVC Pattern used to implement an user s interface Widely adopted in web applications 46/50 Software Engineering
73 MVC Pattern used to implement an user s interface Widely adopted in web applications Separate the elements of an application into three groups View: output representation of information that allows the interaction with users Model: central component that expresses the application s behaviors, independent of the user interface Controller: accepts input and converts it to commands for the model or view 46/50 Software Engineering
74 MVC Pattern used to implement an user s interface Widely adopted in web applications Separate the elements of an application into three groups View: output representation of information that allows the interaction with users Model: central component that expresses the application s behaviors, independent of the user interface Controller: accepts input and converts it to commands for the model or view Simultaneous development with separate parts Ease of modification Multiple views or controls for a model 46/50 Software Engineering
75 MVC 47/50 Software Engineering
76 MVC in Java Packages are used to represent model/view/controller The elements in each group are represented by classes 48/50 Software Engineering
77 Example Problem An application to draw geometrical forms with the library SWING 49/50 Software Engineering
78 Example Problem An application to draw geometrical forms with the library SWING One possible solution a view package containing one window class one draw surface class one class to manage mouse events 49/50 Software Engineering
79 Example Problem An application to draw geometrical forms with the library SWING One possible solution a view package containing one window class one draw surface class one class to manage mouse events a model package containing a form class with its sub-classes like polygon, circle, etc. an arrangement class (contains an array of forms)... 49/50 Software Engineering
80 Example Problem An application to draw geometrical forms with the library SWING One possible solution a view package containing one window class one draw surface class one class to manage mouse events a model package containing a form class with its sub-classes like polygon, circle, etc. an arrangement class (contains an array of forms)... a controller package containing a controller class 49/50 Software Engineering
81 Simple and elegant solutions to specific problems Useful for designing reusable object-oriented software Several key steps: 1 factor pertinent objects into classes at the right granularity 2 define class interfaces and inheritance hierarchies 3 establish key relationships among them 50/50 Software Engineering
Ingegneria del Software Corso di Laurea in Informatica per il Management. Design Patterns part 1
Ingegneria del Software Corso di Laurea in Informatica per il Management Design Patterns part 1 Davide Rossi Dipartimento di Informatica Università di Bologna Pattern Each pattern describes a problem which
Design Patterns. An introduction
Design Patterns An introduction Introduction Designing object-oriented software is hard, and designing reusable object-oriented software is even harder. Your design should be specific to the problem at
Design Pattern. CMPSC 487 Lecture 10 Topics: Design Patterns: Elements of Reusable Object-Oriented Software (Gamma, et al.)
Design Pattern CMPSC 487 Lecture 10 Topics: Design Patterns: Elements of Reusable Object-Oriented Software (Gamma, et al.) A. Design Pattern Design patterns represent the best practices used by experienced
Slide 1. Design Patterns. Prof. Mirco Tribastone, Ph.D
Slide 1 Design Patterns Prof. Mirco Tribastone, Ph.D. 22.11.2011 Introduction Slide 2 Basic Idea The same (well-established) schema can be reused as a solution to similar problems. Muster Abstraktion Anwendung
Topics in Object-Oriented Design Patterns
Software design Topics in Object-Oriented Design Patterns Material mainly from the book Design Patterns by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides; slides originally by Spiros Mancoridis;
SDC Design patterns GoF
SDC Design patterns GoF Design Patterns The design pattern concept can be viewed as an abstraction of imitating useful parts of other software products. The design pattern is a description of communicating
Object-Oriented Oriented Programming
Object-Oriented Oriented Programming Composite Pattern CSIE Department, NTUT Woei-Kae Chen Catalog of Design patterns Creational patterns Abstract Factory, Builder, Factory Method, Prototype, Singleton
Design Patterns. Gunnar Gotshalks A4-1
Design Patterns A4-1 On Design Patterns A design pattern systematically names, explains and evaluates an important and recurring design problem and its solution Good designers know not to solve every problem
Software Engineering - I An Introduction to Software Construction Techniques for Industrial Strength Software
Software Engineering - I An Introduction to Software Construction Techniques for Industrial Strength Software Chapter 9 Introduction to Design Patterns Copy Rights Virtual University of Pakistan 1 Design
CSCD01 Engineering Large Software Systems. Design Patterns. Joe Bettridge. Winter With thanks to Anya Tafliovich
CSCD01 Engineering Large Software Systems Design Patterns Joe Bettridge Winter 2018 With thanks to Anya Tafliovich Design Patterns Design patterns take the problems consistently found in software, and
EPL 603 TOPICS IN SOFTWARE ENGINEERING. Lab 6: Design Patterns
EPL 603 TOPICS IN SOFTWARE ENGINEERING Lab 6: Design Patterns Links to Design Pattern Material 1 http://www.oodesign.com/ http://www.vincehuston.org/dp/patterns_quiz.html Types of Design Patterns 2 Creational
6.3 Patterns. Definition: Design Patterns
Subject/Topic/Focus: Analysis and Design Patterns Summary: What is a pattern? Why patterns? 6.3 Patterns Creational, structural and behavioral patterns Examples: Abstract Factory, Composite, Chain of Responsibility
SOFTWARE PATTERNS. Joseph Bonello
SOFTWARE PATTERNS Joseph Bonello MOTIVATION Building software using new frameworks is more complex And expensive There are many methodologies and frameworks to help developers build enterprise application
Produced by. Design Patterns. MSc in Communications Software. Eamonn de Leastar
Design Patterns MSc in Communications Software Produced by Eamonn de Leastar (edeleastar@wit.ie) Department of Computing, Maths & Physics Waterford Institute of Technology http://www.wit.ie http://elearning.wit.ie
Using Design Patterns in Java Application Development
Using Design Patterns in Java Application Development ExxonMobil Research & Engineering Co. Clinton, New Jersey Michael P. Redlich (908) 730-3416 michael.p.redlich@exxonmobil.com About Myself Degree B.S.
Introduction and History
Pieter van den Hombergh Fontys Hogeschool voor Techniek en Logistiek September 15, 2016 Content /FHTenL September 15, 2016 2/28 The idea is quite old, although rather young in SE. Keep up a roof. /FHTenL
The Strategy Pattern Design Principle: Design Principle: Design Principle:
Strategy Pattern The Strategy Pattern defines a family of algorithms, encapsulates each one, and makes them interchangeable. Strategy lets the algorithm vary independently from clients that use it. Design
Tuesday, October 4. Announcements
Tuesday, October 4 Announcements www.singularsource.net Donate to my short story contest UCI Delta Sigma Pi Accepts business and ICS students See Facebook page for details Slide 2 1 Design Patterns Design
DESIGN PATTERN - INTERVIEW QUESTIONS
DESIGN PATTERN - INTERVIEW QUESTIONS http://www.tutorialspoint.com/design_pattern/design_pattern_interview_questions.htm Copyright tutorialspoint.com Dear readers, these Design Pattern Interview Questions
Idioms and Design Patterns. Martin Skogevall IDE, Mälardalen University
Idioms and Design Patterns Martin Skogevall IDE, Mälardalen University 2005-04-07 Acronyms Object Oriented Analysis and Design (OOAD) Object Oriented Programming (OOD Software Design Patterns (SDP) Gang
Software Design Patterns. Background 1. Background 2. Jonathan I. Maletic, Ph.D.
Software Design Patterns Jonathan I. Maletic, Ph.D. Department of Computer Science Kent State University J. Maletic 1 Background 1 Search for recurring successful designs emergent designs from practice
Ingegneria del Software Corso di Laurea in Informatica per il Management. Design Patterns part 1
Ingegneria del Software Corso di Laurea in Informatica per il Management Design Patterns part 1 Davide Rossi Dipartimento di Informatica Università di Bologna Pattern Each pattern describes a problem which
Socket attaches to a Ratchet. 2) Bridge Decouple an abstraction from its implementation so that the two can vary independently.
Gang of Four Software Design Patterns with examples STRUCTURAL 1) Adapter Convert the interface of a class into another interface clients expect. It lets the classes work together that couldn't otherwise
2.1 Design Patterns and Architecture (continued)
MBSE - 2.1 Design Patterns and Architecture 1 2.1 Design Patterns and Architecture (continued) 1. Introduction 2. Model Construction 2.1 Design Patterns and Architecture 2.2 State Machines 2.3 Timed Automata
Information systems modelling UML and service description languages
Internet Engineering Tomasz Babczyński, Zofia Kruczkiewicz Tomasz Kubik Information systems modelling UML and service description languages Overview of design patterns for supporting information systems
An Introduction to Patterns
An Introduction to Patterns Robert B. France Colorado State University Robert B. France 1 What is a Pattern? - 1 Work on software development patterns stemmed from work on patterns from building architecture
Goals of Lecture. Lecture 27: OO Design Patterns. Pattern Resources. Design Patterns. Cover OO Design Patterns. Pattern Languages of Programming
Goals of Lecture Lecture 27: OO Design Patterns Cover OO Design Patterns Background Examples Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 6448 - Spring Semester, 2001 April 24, 2001 Kenneth
What is Design Patterns?
Paweł Zajączkowski What is Design Patterns? 1. Design patterns may be said as a set of probable solutions for a particular problem which is tested to work best in certain situations. 2. In other words,
Design Patterns. Definition of a Design Pattern
Design Patterns Barbara Russo Definition of a Design Pattern A Pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem,
2.1 Design Patterns and Architecture (continued)
MBSE - 2.1 Design Patterns and Architecture 1 2.1 Design Patterns and Architecture (continued) 1. Introduction 2. Model Construction 2.1 Design Patterns and Architecture 2.2 State Machines 2.3 Abstract
Object Oriented Methods with UML. Introduction to Design Patterns- Lecture 8
Object Oriented Methods with UML Introduction to Design Patterns- Lecture 8 Topics(03/05/16) Design Patterns Design Pattern In software engineering, a design pattern is a general repeatable solution to
Object-Oriented Design
Object-Oriented Design Lecturer: Raman Ramsin Lecture 20: GoF Design Patterns Creational 1 Software Patterns Software Patterns support reuse of software architecture and design. Patterns capture the static
Software Engineering I (02161)
Software Engineering I (02161) Week 10 Assoc. Prof. Hubert Baumeister DTU Compute Technical University of Denmark Spring 2016 Last Time Project Planning Non-agile Agile Refactoring Contents Basic Principles
Design Patterns. Manuel Mastrofini. Systems Engineering and Web Services. University of Rome Tor Vergata June 2011
Design Patterns Lecture 1 Manuel Mastrofini Systems Engineering and Web Services University of Rome Tor Vergata June 2011 Definition A pattern is a reusable solution to a commonly occurring problem within
Applying the Observer Design Pattern
Applying the Observer Design Pattern Trenton Computer Festival Professional Seminars Michael P. Redlich (908) 730-3416 michael.p.redlich@exxonmobil.com About Myself Degree B.S. in Computer Science Rutgers
Applying Design Patterns to accelerate development of reusable, configurable and portable UVCs. Accellera Systems Initiative 1
Applying Design Patterns to accelerate development of reusable, configurable and portable UVCs. Accellera Systems Initiative 1 About the presenter Paul Kaunds Paul Kaunds is a Verification Consultant at
Trusted Components. Reuse, Contracts and Patterns. Prof. Dr. Bertrand Meyer Dr. Karine Arnout
1 Last update: 2 November 2004 Trusted Components Reuse, Contracts and Patterns Prof. Dr. Bertrand Meyer Dr. Karine Arnout 2 Lecture 5: Design patterns Agenda for today 3 Overview Benefits of patterns
Think of drawing/diagramming editors. ECE450 Software Engineering II. The problem. The Composite pattern
Think of drawing/diagramming editors ECE450 Software Engineering II Drawing/diagramming editors let users build complex diagrams out of simple components The user can group components to form larger components......which
Object-Oriented Design
Object-Oriented Design Lecture 20 GoF Design Patterns Behavioral Department of Computer Engineering Sharif University of Technology 1 GoF Behavioral Patterns Class Class Interpreter: Given a language,
Design Patterns. Observations. Electrical Engineering Patterns. Mechanical Engineering Patterns
Introduction o to Patterns and Design Patterns Dept. of Computer Science Baylor University Some slides adapted from slides by R. France and B. Tekinerdogan Observations Engineering=Problem Solving Many
3 Product Management Anti-Patterns by Thomas Schranz
3 Product Management Anti-Patterns by Thomas Schranz News Read above article, it s good and short! October 30, 2014 2 / 3 News Read above article, it s good and short! Grading: Added explanation about
CHAPTER 6: CREATIONAL DESIGN PATTERNS
CHAPTER 6: CREATIONAL DESIGN PATTERNS SESSION III: BUILDER, PROTOTYPE, SINGLETON Software Engineering Design: Theory and Practice by Carlos E. Otero Slides copyright 2012 by Carlos E. Otero For non-profit
Patterns. Erich Gamma Richard Helm Ralph Johnson John Vlissides
Patterns Patterns Pattern-based engineering: in the field of (building) architecting and other disciplines from 1960 s Some software engineers also started to use the concepts Become widely known in SE
Software Engineering Prof. Rushikesh K.Joshi IIT Bombay Lecture-15 Design Patterns
Software Engineering Prof. Rushikesh K.Joshi IIT Bombay Lecture-15 Design Patterns Today we are going to talk about an important aspect of design that is reusability of design. How much our old design
An Introduction to Patterns
An Introduction to Patterns Robert B. France Colorado State University Robert B. France 1 What is a Pattern? Patterns are intended to capture the best available software development experiences in the
CSCD01 Engineering Large Software Systems. Design Patterns. Joe Bettridge. Winter With thanks to Anya Tafliovich
CSCD01 Engineering Large Software Systems Design Patterns Joe Bettridge Winter 2018 With thanks to Anya Tafliovich Design Patterns Design patterns take the problems consistently found in software, and
Crash course on design patterns
Crash course on design patterns Yann-Gaël Guéhéneuc guehene@emn.fr From Olivier Motelet s course (2001/10/17) École des Mines de Nantes, France Object Technology International, Inc., Canada Design patterns
LECTURE NOTES ON DESIGN PATTERNS MCA III YEAR, V SEMESTER (JNTUA-R09)
LECTURE NOTES ON DESIGN PATTERNS MCA III YEAR, V SEMESTER (JNTUA-R09) Mr. B KRISHNA MURTHI M.TECH, MISTE. Assistant Professor DEPARTMENT OF MASTER OF COMPUTER APPLICATIONS CHADALAWADA RAMANAMMA ENGINEERING
Design Pattern What is a Design Pattern? Design Pattern Elements. Almas Ansari Page 1
What is a Design Pattern? Each pattern Describes a problem which occurs over and over again in our environment,and then describes the core of the problem Novelists, playwrights and other writers rarely
be used for more than one use case (for instance, for use cases Create User and Delete User, one can have one UserController, instead of two separate
UNIT 4 GRASP GRASP: Designing objects with responsibilities Creator Information expert Low Coupling Controller High Cohesion Designing for visibility - Applying GoF design patterns adapter, singleton,
Introduction to Software Engineering: Object Design I Reuse & Patterns
Introduction to Software Engineering: Object Design I Reuse & Patterns John T. Bell Department of Computer Science University of Illinois, Chicago Based on materials from Bruegge & DuToit 3e, Chapter 8,
The GoF Design Patterns Reference
The GoF Design Patterns Reference Version.0 / 0.0.07 / Printed.0.07 Copyright 0-07 wsdesign. All rights reserved. The GoF Design Patterns Reference ii Table of Contents Preface... viii I. Introduction....
Design patterns. OOD Lecture 6
Design patterns OOD Lecture 6 Next lecture Monday, Oct 1, at 1:15 pm, in 1311 Remember that the poster sessions are in two days Thursday, Sep 27 1:15 or 3:15 pm (check which with your TA) Room 2244 + 2245
Outline. Design Patterns. Observer Pattern. Definitions & Classifications
Outline Design Patterns Definitions & Classifications Observer Pattern Intent Motivation Structure Participants Collaborations Consequences Implementation 1 What is a Design Pattern describes a problem
Last Lecture. Lecture 17: Design Patterns (part 2) Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 4448/ Spring Semester, 2005
1 Lecture 17: Design Patterns (part 2) Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 4448/6448 - Spring Semester, 2005 2 Last Lecture Design Patterns Background and Core Concepts Examples
A Reconnaissance on Design Patterns
A Reconnaissance on Design Patterns M.Chaithanya Varma Student of computer science engineering, Sree Vidhyanikethan Engineering college, Tirupati, India ABSTRACT: In past decade, design patterns have been
CS/CE 2336 Computer Science II
CS/CE 2336 Computer Science II UT D Session 20 Design Patterns An Overview 2 History Architect Christopher Alexander coined the term "pattern" circa 1977-1979 Kent Beck and Ward Cunningham, OOPSLA'87 used
Applying the Decorator Design Pattern
Applying the Decorator Design Pattern Trenton Computer Festival Professional Seminars Michael P. Redlich (908) 730-3416 michael.p.redlich@exxonmobil.com About Myself Degree B.S. in Computer Science Rutgers
Design patterns. Jef De Smedt Beta VZW
Design patterns Jef De Smedt Beta VZW Who Beta VZW www.betavzw.org Association founded in 1993 Computer training for the unemployed Computer training for employees (Cevora/Cefora) 9:00-12:30 13:00-16:00
Chapter 12 (revised by JAS)
Chapter 12 (revised by JAS) Pattern-Based Design Slide Set to accompany Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman
Software Design COSC 4353/6353 D R. R A J S I N G H
Software Design COSC 4353/6353 D R. R A J S I N G H Design Patterns What are design patterns? Why design patterns? Example DP Types Toolkit, Framework, and Design Pattern A toolkit is a library of reusable
Design patterns. Valentina Presutti courtesy of Paolo Ciancarini
Design patterns Valentina Presutti courtesy of Paolo Ciancarini Agenda What are design patterns? Catalogues of patterns Languages of patterns Two case studies: design with patterns Software Architectures
Last Lecture. Lecture 26: Design Patterns (part 2) State. Goals of Lecture. Design Patterns
Lecture 26: Design Patterns (part 2) Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 6448 - Spring Semester, 2003 Last Lecture Design Patterns Background and Core Concepts Examples Singleton,
Reuse at Design Level: Design Patterns
Reuse at Design Level: Design Patterns CS 617- Lecture 17 Mon. 17 March 2008 3:30-5:00 pm Rushikesh K. Joshi Department of Computer Sc. & Engg. Indian Institute of Technology, Bombay Mumbai - 400 076 Reuse
CPSC 310 Software Engineering. Lecture 11. Design Patterns
CPSC 310 Software Engineering Lecture 11 Design Patterns Learning Goals Understand what are design patterns, their benefits and their drawbacks For at least the following design patterns: Singleton, Observer,
What is Design Patterns?
Paweł Zajączkowski What is Design Patterns? 1. Design patterns may be said as a set of probable solutions for a particular problem which is tested to work best in certain situations. 2. In other words,
CSCD01 Engineering Large Software Systems. Design Patterns. Joe Bettridge. Winter With thanks to Anya Tafliovich
CSCD01 Engineering Large Software Systems Design Patterns Joe Bettridge Winter 2018 With thanks to Anya Tafliovich Design Patterns Design patterns take the problems consistently found in software, and
Facade and Adapter. Comp-303 : Programming Techniques Lecture 19. Alexandre Denault Computer Science McGill University Winter 2004
Facade and Adapter Comp-303 : Programming Techniques Lecture 19 Alexandre Denault Computer Science McGill University Winter 2004 March 23, 2004 Lecture 19 Comp 303 : Facade and Adapter Page 1 Last lecture...
Produced by. Design Patterns. MSc in Communications Software. Eamonn de Leastar
Design Patterns MSc in Communications Software Produced by Eamonn de Leastar (edeleastar@wit.ie) Department of Computing, Maths & Physics Waterford Institute of Technology http://www.wit.ie http://elearning.wit.ie
Design Patterns. CSC207 Fall 2017
Design Patterns CSC207 Fall 2017 Design Patterns A design pattern is a general description of the solution to a well-established problem using an arrangement of classes and objects. Patterns describe the
Design Patterns. Dr. Rania Khairy. Software Engineering and Development Tool
Design Patterns What are Design Patterns? What are Design Patterns? Why Patterns? Canonical Cataloging Other Design Patterns Books: Freeman, Eric and Elisabeth Freeman with Kathy Sierra and Bert Bates.
Design Pa*erns. + Anima/on Undo/Redo Graphics and Hints
Design Pa*erns + Anima/on Undo/Redo Graphics and Hints Design Pa*erns Design: the planning that lays the basis for the making of every object or system Pa*ern: a type of theme of recurring events or objects
Design Patterns. CSC207 Fall 2017
Design Patterns CSC207 Fall 2017 Design Patterns A design pattern is a general description of the solution to a well-established problem using an arrangement of classes and objects. Patterns describe the
Lecture 13: Design Patterns
1 Lecture 13: Design Patterns Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 6448 - Spring Semester, 2005 2 Pattern Resources Pattern Languages of Programming Technical conference on Patterns
THOMAS LATOZA SWE 621 FALL 2018 DESIGN PATTERNS
THOMAS LATOZA SWE 621 FALL 2018 DESIGN PATTERNS LOGISTICS HW3 due today HW4 due in two weeks 2 IN CLASS EXERCISE What's a software design problem you've solved from an idea you learned from someone else?
An Expert System for Design Patterns Recognition
IJCSNS International Journal of Computer Science and Network Security, VOL.17 No.1, January 2017 93 An Expert System for Design Patterns Recognition Omar AlSheikSalem 1 and Hazem Qattous 2 1 Department
Pattern Resources. Lecture 25: Design Patterns. What are Patterns? Design Patterns. Pattern Languages of Programming. The Portland Pattern Repository
Pattern Resources Lecture 25: Design Patterns Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 6448 - Spring Semester, 2003 Pattern Languages of Programming Technical conference on Patterns
SYLLABUS CHAPTER - 1 [SOFTWARE REUSE SUCCESS FACTORS] Reuse Driven Software Engineering is a Business
![SYLLABUS CHAPTER - 1 [SOFTWARE REUSE SUCCESS FACTORS] Reuse Driven Software Engineering is a Business](/thumbs/91/106502756.jpg "SYLLABUS CHAPTER - 1 [SOFTWARE REUSE SUCCESS FACTORS] Reuse Driven Software Engineering is a Business")
Contents i UNIT - I UNIT - II UNIT - III CHAPTER - 1 [SOFTWARE REUSE SUCCESS FACTORS] Software Reuse Success Factors. CHAPTER - 2 [REUSE-DRIVEN SOFTWARE ENGINEERING IS A BUSINESS] Reuse Driven Software
MVC. Model-View-Controller. Design Patterns. Certain programs reuse the same basic structure or set of ideas
MVC -- Design Patterns Certain programs reuse the same basic structure or set of ideas These regularly occurring structures have been called Design Patterns Design Patterns Design Patterns: Elements of
Software methodology and snake oil
Software methodology and snake oil programming is hard programs are very expensive to create full of errors hard to maintain how can we design and program better? a fruitful area for people selling "methodologies"
Lecture 20: Design Patterns II
Lecture 20: Design Patterns II Software System Design and Implementation ITCS/ITIS 6112/8112 001 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at Charlotte Nov.
Design Patterns. CSC207 Winter 2017
Design Patterns CSC207 Winter 2017 Design Patterns A design pattern is a general description of the solution to a well-established problem using an arrangement of classes and objects. Patterns describe
Software Eningeering. Lecture 9 Design Patterns 2
Software Eningeering Lecture 9 Design Patterns 2 Patterns covered Creational Abstract Factory, Builder, Factory Method, Prototype, Singleton Structural Adapter, Bridge, Composite, Decorator, Facade, Flyweight,
1 Software Architecture
Some buzzwords and acronyms for today Software architecture Design pattern Separation of concerns Single responsibility principle Keep it simple, stupid (KISS) Don t repeat yourself (DRY) Don t talk to
Brief Note on Design Pattern
Brief Note on Design Pattern - By - Channu Kambalyal channuk@yahoo.com This note is based on the well-known book Design Patterns Elements of Reusable Object-Oriented Software by Erich Gamma et., al.,.
Design Patterns Lecture 2
Design Patterns Lecture 2 Josef Hallberg josef.hallberg@ltu.se 1 Patterns covered Creational Abstract Factory, Builder, Factory Method, Prototype, Singleton Structural Adapter, Bridge, Composite, Decorator,
Software Engineering I (02161)
Software Engineering I (02161) Week 11 Assoc. Prof. Hubert Baumeister DTU Compute Technical University of Denmark Spring 2017 Recap I Software Development Processes (cont.) I Project Planning I Design
Object-oriented Software Design Patterns
Object-oriented Software Design Patterns Concepts and Examples Marcelo Vinícius Cysneiros Aragão marcelovca90@inatel.br Topics What are design patterns? Benefits of using design patterns Categories and
CS560. Lecture: Design Patterns II Includes slides by E. Gamma et al., 1995
CS560 Lecture: Design Patterns II Includes slides by E. Gamma et al., 1995 Classification of GoF Design Pattern Creational Structural Behavioural Factory Method Adapter Interpreter Abstract Factory Bridge
Coordination Patterns
Coordination Patterns 1. Coordination Patterns Design Patterns and their relevance for Coordination Oscar Nierstrasz Software Composition Group Institut für Informatik (IAM) Universität Bern oscar@iam.unibe.ch
Design Patterns Reid Holmes
Material and some slide content from: - Head First Design Patterns Book - GoF Design Patterns Book Design Patterns Reid Holmes GoF design patterns $ %!!!! $ "! # & Pattern vocabulary Shared vocabulary
Modellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico
Modellistica Medica Maria Grazia Pia INFN Genova Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003 Lezione 9 OO modeling Design Patterns Structural Patterns Behavioural Patterns
Design Patterns 2. Page 1. Software Requirements and Design CITS 4401 Lecture 10. Proxy Pattern: Motivation. Proxy Pattern.
Proxy : Motivation Design s 2 It is 3pm. I am sitting at my 10Mbps connection and go to browse a fancy web page from the US, This is prime web time all over the US. So I am getting 100kbps What can you
Design Patterns. CSE870: Advanced Software Engineering (Design Patterns): Cheng
Design Patterns Acknowledgements Materials based on a number of sources D. Levine and D. Schmidt. Helm Gamma et al S. Konrad Motivation Developing software is hard Designing reusable software is more challenging
CSCI 253. Overview. The Elements of a Design Pattern. George Blankenship 1. Object Oriented Design: Iterator Pattern George Blankenship
CSCI 253 Object Oriented Design: Iterator Pattern George Blankenship George Blankenship 1 Creational Patterns Singleton Abstract factory Factory Method Prototype Builder Overview Structural Patterns Composite
What is a Pattern? Lecture 40: Design Patterns. Elements of Design Patterns. What are design patterns?
What is a Pattern? Lecture 40: Design Patterns CS 62 Fall 2017 Kim Bruce & Alexandra Papoutsaki "Each pattern describes a problem which occurs over and over again in our environment, and then describes
CSC207H: Software Design Lecture 6
CSC207H: Software Design Lecture 6 Wael Aboelsaadat wael@cs.toronto.edu http://ccnet.utoronto.ca/20075/csc207h1y/ Office: BA 4261 Office hours: R 5-7 Acknowledgement: These slides are based on material
Design Patterns! Acknowledgements!
Design Patterns! Acknowledgements! Materials based on a number of sources! D. Levine and D. Schmidt!. Helm! Gamma et al! S. Konrad! (Cheng) 1 Motivation! Developing software is hard! Designing reusable
What is Design Patterns?
Paweł Zajączkowski What is Design Patterns? 1. Design patterns may be said as a set of probable solutions for a particular problem which is tested to work best in certain situations. 2. In other words,
CS342: Software Design. November 21, 2017
CS342: Software Design November 21, 2017 Runnable interface: create threading object Thread is a flow of control within a program Thread vs. process All execution in Java is associated with a Thread object.