SWEN 745 Lecture Notes - Lecture 14: Architectural Pattern, Component-Based Software Engineering, Weak Solution
21 Oct 2016
School
Department
Course
Professor
Document Summary
A package of design decisions which have known properties and resue. All syste(cid:373)s ha(cid:448)e a(cid:374) ar(cid:272)hite(cid:272)ture, (cid:271)ut they (cid:373)ay (cid:374)ot (cid:271)e e(cid:374)gi(cid:374)eered. This is k(cid:374)o(cid:449)(cid:374) as (cid:862)big ball of mud(cid:863). A pattern is an optimized and generalized solution to a common problem in a given context. Context this is the situation in which the problem occurs. Problem a common problem that arises in a context. Solution a successful architecture that solves the problem. Architecture patterns are more high level (abstract) than design patterns. A system can be composed of many types of architecture patterns (e. g. a web app can be composed of: layer, Relationships between the subsystems/components (e. g. client is attached/connected to server) Rules, guidelines and constrains for the relationship (e. g. multiple clients can connect to a server) Module patterns shows modules (e. g. layer) Component and connector pattern shows the components and connectors (e. g. client-server) Allocation pattern shows modules, components & connectors and non-software elements (e. g. multi-tier)
