[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fDsuotxapHxFV8zqYSkHxd8UBhMkw7tQptMOUjXNbX34":3},{"answer":4,"createTime":5,"id":6,"options":7,"origin":12,"question":19,"related":20,"source":24,"type":25},[],"2025-05-14 15:56:15",187890891,[8,9,10,11],"开闭原则","依赖倒置原则","迪米特法则","里氏替换原则",{"count":13,"courseId":14,"courseImg":15,"courseName":16,"workId":17,"workName":18},12,"f6f7360442fd63bf14ce398a91c95e99","https:\u002F\u002Ftihai-oss-cloud.itihey.com\u002Fimg\u002F25b30343053994e8940089572d36015b.jpg","软件设计模式","work_42798098","作业六","关于面向对象设计原则:&quot;高层模块不应该依赖于低层模块,两者都应该依赖其抽象;抽象不应该依赖细节,细节应该依赖抽象.&quot;是对( )的描述",[21,26,35,44,53,61,70,80,87,96],{"answer":22,"createTime":5,"id":6,"options":23,"question":19,"source":24,"type":25},[],[8,9,10,11],"v1",0,{"answer":27,"createTime":5,"id":28,"options":29,"question":34,"source":24,"type":25},[],187890892,[30,31,32,33],"工厂方法模式","观察者模式","适配器模式","命令模式","定义对象间的一种一对多依赖关系,使每当一个对象状态发生改变时,其相关依赖对象皆得到通知并被自动更新",{"answer":36,"createTime":5,"id":37,"options":38,"question":43,"source":24,"type":25},[],187890893,[39,40,41,42],"时序图","类图","对象图","状态机图","关于UML图形:( )描述一组类之间的关系,用于对应用域中的概念及与系统实现有关的内部概念建模",{"answer":45,"createTime":5,"id":46,"options":47,"question":52,"source":24,"type":25},[],187890895,[48,49,50,51],"将一个类的接口转换成客户希望的另外一个接口,本模式使原本由于接口不兼容而不能一起工作的那些类可以一起工作","将一个请求封装为一个对象,从而使用户可用不同的请求对客户进行参数化,对请求排队或记录请求日志,以及支持可撤销的操作","定义一个用于创建对象的接口,让子类决定实例化哪一个类","表示一个作用于某对象结构中的各元素的操作,它使用户可以在不改变各元素的类的前提下定义作用于这些元素的新操作","下列表达中,( )描述了适配器(Adapter)模式的意图",{"answer":54,"createTime":5,"id":55,"options":56,"question":60,"source":24,"type":25},[],187890897,[57,30,58,59],"单例模式","简单工厂模式","抽象工厂模式","下图所示的类图描述的设计模式为( ). \u003Cimg src=\"https:\u002F\u002Ftihai-oss-cloud.itihey.com\u002Fimg\u002F5b548e86267a1ce3556cca9b609da316.png\">",{"answer":62,"createTime":5,"id":63,"options":64,"question":69,"source":24,"type":25},[],187890899,[65,66,67,68],"策略(Strategy)模式","观察者(Observer)模式","工厂方法(Factory Method)模式","外观(Facade)模式","以下不属于行为对象模式的是( )",{"answer":71,"createTime":72,"id":73,"options":74,"question":79,"source":24,"type":25},[],"2025-05-14 15:56:16",187890901,[75,76,77,78],"汽车和座位","汽车和车窗","汽车和音乐系统","汽车和发动机","使用UML绘制汽车系统的类图时,以下( )之间不属于组合关系",{"answer":81,"createTime":72,"id":82,"options":83,"question":86,"source":24,"type":25},[],187890903,[84,85,30,31],"类适配器模式","解释器模式","下列设计模式不属于类设计模式的是( )",{"answer":88,"createTime":72,"id":89,"options":90,"question":95,"source":24,"type":25},[],187890905,[91,92,93,94],"观察者(Observer)","单例(Singleton)","迭代器(Iterator)","外观(Facade)","模式定义了一个更高层的接口来简化子系统的使用,为子系统提供一个统一的入口",{"answer":97,"createTime":72,"id":98,"options":99,"question":104,"source":24,"type":25},[],187890907,[100,101,102,103],"算法使用客户不应该知道的数据.可使用该模式以避免暴露复杂的、与算法相关的数据结构","许多相关的类仅仅是行为有异.该模式提供了一种用多个行为中的一个行为来配置一个类的方法","需要使用一个算法的不同变体.例如,用户可能会定义一些反映不同的空间\u002F时间权衡的算法.当这些变体实现为一个算法的类层次时,可以使用该模式","当一个对象必须通知其他对象,而它又不能假定其他对象是谁.换言之,用户不希望这些对象是紧密耦合的","关于模式适用性,以下( )不适合使用策略(Strategy)模式"]