【文章內(nèi)容簡介】 ses ? Inventory/stock management systems ? Clientserver ? Web browser/Web server ? Peertopeer ? Distributed databases ? Communication satellites 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 Choosing the Right Style ? Ask questions on whether a certain style makes sense ? The Inter as a blackboard ? Does that scale? ? Stock exchange as a layers ? How to deal with the continuous change? ? Math as hierarchy ? How to properly call different modules for different functions? ? Draw a picture of the major entities ? Look for the natural paradigm ? Look for what “feels right” 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 Mixing Styles Is Often Necessary Blackboard + ClientServer Provided Interface Blackboard Provided Interface One “Part” Required Interface Provided Interface My “Bit” Required Interface Provided Interface Her “Piece” Required Interface Provided Interface A “Part” Required Interface Provided Interface Another “Piece” Required Interface Provided Interface His “Bit” Required Interface 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 Provided Interface Blackboard Provided Interface One “Part” Required Interface Provided Interface My “Bit” Required Interface Provided Interface Her “Piece” Required Interface Provided Interface A “Part” Required Interface Provided Interface Another “Piece” Required Interface Provided Interface His “Bit” Required Interface Original Blackboard 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 Mixing Styles is often Necessary Blackboard + Implicit Invocation Provided Interface Blackboard Provided Interface One “Part” Required Interface Provided Interface A “Piece” Required Interface Provided Interface Some “Bit” Required Interface Provided Interface Bus Required Interface 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 Mixing Styles Is Often Necessary PipeandFilter + ClientServer + Hierarchy Pipe FCalls Provided Interface Audio Encoder Required Interface Provided Interface Tuner Required Interface Provided Interface Audio Player Required Interface 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 Your Tasks 1. Read and study slides of this lecture 2. Read and study Chapters 10 and 11 of Sommerville 3. Memorize the architectural styles ? Chalk lecture next Thursday Lecture 31 169。 2021, Univ ersity of C alifornia, Irv ine ICS 52 Introduction to Software Engineering Lecture Notes for Winter Quarter, 2021 Andr233。 van der Hoek Lecture 32 Copyright 169。 2021, Andr233。 van der Hoek Duplication of course material for any mercial purpose without the written permission of the lecturer is prohibited. 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 Today’s Lecture ? Architectural design revisited ? Modules ? Official ICS 52 design notation ? Interfaces 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 A Good Design… ? …is half the implementation effort! ? Rigor ensures all requirements are addressed ? Separation of concerns ? Modularity allows work in isolation because ponents are independent of each other ? Abstraction allows work in isolation because interfaces guarantee that ponents will work together ? Anticipation of change allows changes to be absorbed seamlessly ? Generality allows ponents to be reused throughout the system ? Incrementality allows the software to be developed with intermediate working results 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 A Bad Design… ? …will never be implemented! ? Lack of rigor leads to missing functionality ? Separation of concerns ? Lack of modularity leads to conflicts among developers ? Lack of abstraction leads to massive integration problems (and headaches) ? Lack of anticipation of change leads to redesigns and reimplementations ? Lack of generality leads to “code bloat” ? Lack of incrementality leads to a bigbang approach that is likely to “bomb” 169。 2021, Univ ersity of C alifornia, Irv ine Lecture 31 Design ? Architectural design ? Highlevel partitioning of a software sys