1 / 10

ITEC 370

ITEC 370. Lecture 11 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?

loren
Télécharger la présentation

ITEC 370

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITEC 370 Lecture 11 Design

  2. 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?

  3. Objectives • Design patterns • Not by shotgun approach

  4. 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?

  5. 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 are formalized best practices that the programmer must implement themselves in the application. wikipedia

  6. 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?

  7. Graphically

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

  9. Code • How did the command pattern was used to help build this system • Available on sourceforge if you want it

  10. Review • Design patterns • Command pattern • Definition • Example

More Related