Architectural Models-II

Lecture 25 continues the study of architectural styles with Layered architectures and Pipe-and-Filter pipelines. In a Layered (abstract machine) architecture, system functionality is organized into hierarchical layers where each layer provides services only to the layer immediately above it and consumes services only from the layer directly below it. Students evaluate layered architecture benefits: modular maintainability, clean abstraction, and standardized layer replacement (e.g., swapping database engines), contrasted with performance overhead from multi-layer call traversal. The lecture explores the Pipe-and-Filter architectural style (exemplified by UNIX shells and image processing pipelines), where discrete processing filters transform streaming data sequentially. Control models, including centralized call-return and event-driven broadcast architectures, are analyzed. Object-oriented analysis using the Coad and Yourdon methodology illustrates identifying classes, responsibilities, attributes, and services. Structural relationships, including Generalization-Specialization inheritance hierarchies and Whole-Part aggregation assemblies, are modeled with precision. Dynamic interaction modeling demonstrates sequence diagrams, object lifelines, activation bars, and synchronous versus asynchronous message exchanges. Software architecture frameworks explore Kruchten's 4+1 view model, connecting logical, process, development, and physical architectural perspectives. Architectural styles, including layered hierarchies, repository patterns, client-server structures, and pipe-and-filter pipelines, are contrasted. Design pattern principles demonstrate how Gang of Four solutions, such as the Observer pattern, decouple subjects from observers to handle state changes. Professional coding style standards detail clear identifier naming, consistent indentation, layout structure, and self-documenting code conventions. Defensive programming practices illustrate safe file handling, resource leak prevention, and robust input validation in C++ and Java environments. Exception handling mechanisms demonstrate try-catch-finally blocks, structured error propagation, and eliminating silent runtime failures. Software portability guidelines detail isolating hardware-dependent logic, handling endianness, and standardizing primitive data type representations. Verification and validation activities contrast static software inspections and walkthroughs with dynamic code execution testing techniques. Testing paradigms emphasize finding defects systematically, contrasting developer testing mindsets with destructive verification approaches. Black-box testing strategies evaluate equivalence class partitioning and boundary value analysis to design high-coverage test case suites. White-box testing methodologies analyze control flow graphs, cyclomatic complexity calculations, and branch and statement coverage criteria.