renate
Uploaded by
4 SLIDES
200 VUES
40LIKES

Avoiding PowerPoint Karaoke: Effective Teaching Strategies by Dr. Stephen Marshall

DESCRIPTION

Dr. Stephen Marshall from the University Teaching Development Centre shares insights on effective teaching methodologies to engage learners and avoid the pitfalls of uninspired presentations. This guide emphasizes the significance of design patterns, emphasizing the use of identifiable objects with unique behaviors and public interfaces. By addressing the fundamental principles of object-oriented design and their application in creating vibrant public spaces, Dr. Marshall provides actionable solutions for educators and urban planners alike.

1 / 4

Download Presentation
Télécharger la présentation

Avoiding PowerPoint Karaoke: Effective Teaching Strategies by Dr. Stephen Marshall

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. Avoiding Powerpoint KaraokeDr Stephen MarshallUniversity Teaching Development Centrestephen.marshall@vuw.ac.nz Design Examples

  2. Object • Behaviour • Each object has some behaviour that it supplies: • A point in a graphics system: get coordinates, add to another point • A bank account: withdraw, deposit, calculate interest, print statement • Every object can also be created and destroyed • What you get: • An obkects methods can access its private state • If you need to reprogram an object’s behaviour, you only need to reprogram that object, not the whole system (maybe…) • If other objects need to make use of a behaviour, they should use that object’s public interface • Identity • Each object can be distinguished from every other object: • Two bank accounts with the same name and balance are not the same account: • Withdrawals and deposits in one don’t affect the other • You can certainly have two accounts with teh same name • Different banks can have accounts with the same number

  3. Problem A town needs public spaces. How big should they be? Context You are designing an Identifiable Neighbourhood Forces The square should be “full of life” People should enjoy just “hanging out” Solution Make squares no more than 15 or 20 metres across Known Uses Cuba Street Manners Mall Related Patterns Pedestrian Density Activity Pockets Positive Outdoor Space Building Fronts Stair Seats Something Roughly in the Middle Example: Small Public Squares

  4. Issues in Composite • Explicit Parent references • Sharing components • Maximising the Component interface • Declaring the child management operations • Should Component implement a list of Components? • Child ordering • Caching to improve performance • Who should delete components? • What’s the best data structure for storing components?

More Related
SlideServe
Audio
Live Player
Audio Wave
Play slide audio to activate visualizer