Software Engineering - Session 8 - Sub-Topic 1 - Design Patterns, Architectural Patterns

Sep 22, 2026

Session 8, Sub-Topic 1 focuses on design patterns and architectural patterns in software engineering. It explains how patterns capture proven experience and address recurring design or implementation problems, then contrasts learning fundamentals with repeatedly studying expert examples. The material defines software architecture, components, subsystems, and key pattern categories including architectural patterns, design patterns, idioms, and frameworks. A first example introduces a dice game, outlining activities and a layered architecture approach.

LanguageEnglish

CategoryTechnology

FormatPDF

Pages127

Reading Time5 h 20 min

AccessFree to download

Design Patterns, Architectural Patterns

Patterns

Becoming a Chess Master

Becoming a Software Designer Master

Software Architecture

Components and Subsystems

Architectural Patterns and Design Patterns

Idioms and Frameworks

First Example: A Dice Game

Design Stage and Layered Architecture

Layer

Software Engineering G22.2440-001 Session 8 – Sub-Topic 1 Design Patterns, Architectural Patterns Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Design Patterns, Architectural Patterns Bibliography… 􀂄 « A System of Pattern » Bushmann et All 􀂄 « Design Patterns » Gamma et All 􀂄 « Concurrent Programming in Java » D. Lea. 􀂄 « Distributed Objects » Orfali et All 􀂄 « Applying UML and Patterns » Larman 3 Patterns… 􀂃 « Patterns help you build on the collective experience of skilled software engineers. » 􀂃 « They capture existing, well-proven experience in software development and help to promote good design practice » 􀂃 « Every pattern deals with a specific, recurring problem in the design or implementation of a software system » 􀂃 « Patterns can be used to construct software architectures with specific properties…» 4 Becoming a Chess Master 􀂄 First learn rules and physical requirements – e.g. , names of pieces, legal movements, chess board geometry and orientation, etc. 􀂄 Then learn principles – e.g. , relative value of certain pieces, strategic value of center squares, power of a threat, etc. 􀂄 However, to become a master of chess, one must study the games of other masters – These games contain patterns that must be understood, memorized, and applied repeatedly 􀂄 There are hundreds of these patterns 5 Becoming a Software Designer Master 􀂄 First learn the rules – e.g. , the algorithms, data structures and languages of software 􀂄 Then learn the principles – e.g. , structured programming, modular programming, object oriented programming, generic programming, etc. 􀂄 However, to truly master software design, one must study the designs of other masters – These designs contain patterns must be understood, memorized, and applied repeatedly 􀂄 There are hundreds of these patterns 6 Software Architecture 􀂄 A software architecture is a description of the subsystems and components of a software system and the relationships between them. 􀂄 Subsystems and components are typically specified in different views to show the relevant functional and non-functional properties of a software system. 􀂄 The software system is an artifact. It is the result of the software design activity. 7 Component 􀂄 A component is an encapsulated part of a software system. A component has an interface. 􀂄 Components serve as the building blocks for the structure of a system. 􀂄 At a programming-language level, components may be represented as modules, classes, objects or as a set of related functions. 8 Subsystems 􀂄 A subsystem is a set of collaborating components performing a given task. A subsystem is considered a separate entity within a software architecture. 􀂄 It performs its designated task by interacting with other subsystems and components… 9 Architectural Patterns 􀂄 An architectural Pattern expresses a fundamental structural organization schema for software systems. It provides a set of predefined subsystems, their responsibilities, and includes rules and guidelines for organizing the relationships between them. 10 Design patterns 􀂄 A design pattern provides a scheme for refining the subsystems or components of a software system, or the relation ships between them. It describes a commonlyrecurring structure of communicating components that solves a general design problem within a particular context. 11 Idioms 􀂄 An Idiom is a low-level pattern specific to a programming language. An idiom describeshow to implement particular aspects of components or the relationships between them using the features of the given language. 12 Framework 􀂄 A framework is a partially complete software (sub-) system that is intended to be instantiated. It defines the architecture for a family of (sub-) systems and provides the basic building blocks to create them. It also defines the places w

FAQs

What are patterns and why are they useful in software design?

Patterns help build on collective experience of skilled engineers, capture well-proven practice, and solve specific recurring problems. They can also be used to construct software architectures with desired properties.

How does an architectural pattern differ from a design pattern?

An architectural pattern describes a fundamental structural organization schema, including predefined subsystems, responsibilities, and rules for relationships. A design pattern refines subsystems or components, describing a recurring structure of communicating components that solves a general design problem in a context.

What role do idioms and frameworks play?

An idiom is a low-level pattern specific to a programming language, showing how to implement aspects of components or relationships using that language’s features. A framework is a partially complete software (sub-)system meant to be instantiated, defining an architecture family and providing building blocks and adaptation points.

Sep 22, 2026

Upload by Jordan Avery