Study Guide - Design

Tactics for Creating Software

This Design Study Guide pulls together, in one place, the resources we use in CSE687 - Object Oriented Design to discuss design issues.
Design Presentations Design Concepts and Notes
Definition: Object Oriented Design

Structuring design of an application with classes and class relationships.

Core Presentations

  1. Class Relationships, Example Relationships, Example code
    Illustrates complete set of class relationships: inheritance, composition, aggregation, using.
  2. Software Design Goals, pptx
    Describes design goals and attributes for large software projects.
  3. Design Principles
    Discusses Liskov Substitution, Open and Closed, Dependency Inversion, and Interface Segregation principles.
  4. Design Strategies, pptx
    Discusses general design and more specific OOD strategies.
  5. Design Notes, pptx
    Discusses interface design and some cautions for team development.
  6. Design Guidelines, pptx
    A bag of design ideas, suggestions, and advice.
  7. Abstract Data Types, pptx, Code Example: Str Class
    Complete discussion of building a reusable package, using a string class as an example.
  8. Hiding and Other Evils, docx, Code Demo
    Demonstrates one of the dark corners of the C++ programming language.
  9. Packages, Code Example: Str Pkg
    A package is a physical packaging of code in (two) files.
  10. UML Notation
    Diagram notation used to describe software designs.
Design Concepts:
  1. Encapsulate classes and packages
  2. Principle of Least Knowledge
  3. Prime Directives: No Surprises, Maximize Cohesion, Minimize Coupling, Keep it Small and Simple
  4. Distinguish between application-side and solution-side
  5. Use Namespaces to define a Project Taxonomy
  6. Top-Down design
  7. Bottom-up design
  8. Incremental Development
  9. Partitioning: classes, packages, processes, and machines
  10. Distinguish between Interface, Abstract Class, and Concrete Class
  11. Component: Interface, Object Factory, Concrete Implementation, DLL package
  12. Delegation and Events
Design Notes:
  1. Software size matters
  2. Package structure is important
  3. Favor local consequences
  4. Extract function instead of cut and paste
  5. Display information, not data
  6. Distinguish between test types
  7. Robustness: validate user input and directory specifications
Language Notes:
  1. Distinguish between Value and Reference Types
  2. Resource Acquizition is Initialization (RAII)
  3. Implementing Initialization
  4. Virtual Function Pointer Tables

CST strip