Chapter08设计工程….pptVIP

Chapter 8 设计工程Design Concepts and Principles 8.1 软件设计 软件设计一般分为两个阶段 总体设计——概要设计，系统设计，体系结构设计 详细设计——模块设计，构件级设计，过程（算法） 设计 设计的依据是需求规格说明书 基于类的元素→数据/类设计，体系结构，接口，模块 基于场景的元素→软件接口 面向流的元素→体系结构，接口，模块 行为元素→接口，模块 Analysis to Design Where Do We Begin? 8.2 设计过程和设计质量 软件设计是一个迭代过程 通过设计，需求被变换成用于构建软件的“蓝图” McGlaughlin评价设计良好演化的三个特征： 设计必须实现所有包含在分析模型中的明确需求，而且必须满足客户期望的所有蕴含需求。 对于编码、测试和维护人员而言，设计必须是可读的、可理解的指南。 设计必须提供软件的全貌，从实现的角度说明数据域、功能域和行为域。 设计质量指导原则（p149） 软件质量属性（p150） 设计决定软件的稳定性 Wasserman’s Five Ways of Design Modular decomposition High-level function depiction→lower-level components organization Data-oriented decomposition General data structure depiction → Data elements Event-oriented decomposition System state depiction → State transformations Outside-in design All possible input depiction → What the system does for producing outputs Object-oriented design Object type → attributes and action → relationship Design Principles(Davis [DAV95])  The design process should not suffer from ‘tunnel vision.’ The design should be traceable to the analysis model. The design should not reinvent the wheel. The design should “minimize the intellectual distance” between the software and the problem as it exists in the real world. The design should exhibit uniformity and integration. The design should be structured to accommodate change. The design should be structured to degrade gently, even when aberrant data, events, or operating conditions are encountered. Design is not coding, coding is not design. The design should be assessed for quality as it is being created, not after the fact. The design should be reviewed to minimize conceptual (semantic) errors. 8.3 设计概念 抽象abstraction—data, procedure, control 逐步求精refinement—elaboration of detail for all abstractions 模块化modularity—compartmentalization of data and function architecture—overall structure of the software Structural properties Extra-structural properties Styles and patterns procedure—the algorithms that achieve function 信息隐蔽hidin