10
ITEC 370 Lecture 11 Design

ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Embed Size (px)

Citation preview

Page 1: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

ITEC 370

Lecture 11Design

Page 2: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Design

Review

• Questions?• Today!

– Rough draft of your SRS document– Introduction, Features (Functional / Non-functional),

Interfaces– Prepare for presenting the next week

• UML– UML by shotgun approach– What are the reasons for using UML?– What are some dangers of using UML?– How do you think UML will be used in your project?

Page 3: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Design

Objectives

• Design patterns– Not by shotgun approach

Page 4: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Design

Design patterns

• What is a design pattern in your own words?

• What are they used for?• Have you ever used one before?– How useful was it?

Page 5: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Design

Definition

In software engineering, a design pattern is a general reusable solution to a commonly occurring problem within a given context in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Patterns areformalized best practices that the programmer must implement themselves in the application.

wikipedia

Page 6: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Design

Example pattern

• Command– Used to call methods on classes

• Parts– Client– Invoker– Receiver

• Goal– Middleman that handles details between

client and functionality– What are some of the uses of this?

Page 7: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Design

Graphically

Page 8: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Design

Example

• mQuiz–Mobile quiz app– Quick, functional system– Used for a couple of semesters in ITEC 120

Page 9: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Design

Code

• How did the command pattern was used to help build this system

• Available on sourceforge if you want it

Page 10: ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces

Design

Review

• Design patterns• Command pattern– Definition– Example