Mediaspace scheduled maintenance: Aug 25, 2026 07:00 - 12:00 AM. During this time, videos will be temporarily unavailable. Check status updates.

Lecture

Design: Abstraction and Modularity

In course

CS-305: Software engineering

This course teaches the basics of modern software development: designing software, working in a team, writing good code, shipping software, and evolving software. It emphasizes building software that meets high standards of quality, reliability, security, ...

Description

This lecture covers the importance of designing software based on actual needs, not possible needs, illustrated by examples such as a 'campus companion' app and a course management system. It also discusses the concepts of estimating complexity, the 'You Aren't Gonna Need It' principle, and design patterns like MVC, MVP, and MVVM.

This video is available exclusively on Mediaspace for a restricted audience. Please log in to MediaSpace to access it if you have the necessary permissions.

Watch on Mediaspace

Instructor

George Candea

Official source

Related concepts (16)

Software design pattern

In software engineering, a software design pattern is a general, reusable solution to a commonly occurring problem within a given context in software design. It is not a finished design that can be transformed directly into source or machine code. Rather, it is a description or template for how to solve a problem that can be used in many different situations. Design patterns are formalized best practices that the programmer can use to solve common problems when designing an application or system.

Design pattern

A design pattern is the re-usable form of a solution to a design problem. The idea was introduced by the architect Christopher Alexander and has been adapted for various other disciplines, particularly software engineering. An organized collection of design patterns that relate to a particular field is called a pattern language. This language gives a common terminology for discussing the situations designers are faced with. The elements of this language are entities called patterns.

Software design

Software design is the process by which an agent creates a specification of a software artifact intended to accomplish goals, using a set of primitive components and subject to constraints. The term is sometimes used broadly to refer to "all the activity involved in conceptualizing, framing, implementing, commissioning, and ultimately modifying" the software, or more specifically "the activity following requirements specification and before programming, as ... [in] a stylized software engineering process.

Behavioral pattern

In software engineering, behavioral design patterns are design patterns that identify common communication patterns among objects. By doing so, these patterns increase flexibility in carrying out communication.

Middleware

Middleware is a type of computer software that provides services to software applications beyond those available from the operating system. It can be described as "software glue". Middleware makes it easier for software developers to implement communication and input/output, so they can focus on the specific purpose of their application. It gained popularity in the 1980s as a solution to the problem of how to link newer applications to older legacy systems, although the term had been in use since 1968.

Related lectures (32)

Software Engineering: Methods and Tools

Explores software engineering complexity, UML, DSL, design patterns, agile development, and introduces the Arcimboldo tool.

Design Reflection Minute

Focuses on the SWISH principle in instructional design and the orchestration graph.

Imperative Event Handling: The Observer Pattern

Introduces the widely used Observer Pattern for views to react to model changes, with examples of Publisher, Subscriber, and a Consolidator.

Design Patterns: Introduction

Covers association relationships, abstract classes, and the Builder pattern in Java.

Design Patterns: Bosses of Object-Oriented Programming Practice