nontrivial非平凡的.pptVIP

Software Engineering: A Practitioner’s Approach, 6/eChapter 11Component-Level Design Objectives To introduce component design and to explain its importance To introduce different views of component To introduce cohesion and coupling and to explain its importance To describe a number of different representation techniques for procedural design and when they may be used 1.Architecture design to component design 2. What is a Component? 3.Designing class-based component (Cohesion and Coupling) 4.Designing conventional component Analysis Model - Design Model Componeng -level design defines the data structures ,algorithms ,interface characteristics ,and communications mechanisms allocated to each software component. 1.Architecture design to component design 2. What is a Component? 3.Designing class-based component (Cohesion and Coupling) 4.Designing conventional component What is a Component? OMG Unified Modeling Language Specification [OMG01] defines a component as “… a modular, deployable, and replaceable part of a system that encapsulates implementation and exposes a set of interfaces.” OO view: a component contains a set of collaborating classes Conventional view: logic, the internal data structures that are required to implement the processing logic, and an interface that enables the component to be invoked and data to be passed to it. OO Component OO Component Conventional view A Conventional component also called module ,resides within the software architecture and serves one of three important roles: 1)control component 2)domain component 3)infrastructure coponent Conventional Component 1.Architecture design to component design 2. What is a Component? 3.Designing class-based component (Cohesion and Coupling) 4.Designing conventional component Cohesion（内聚） Conventional view: the “single-mindedness（专诚性）” of a module OO view Levels of cohesion Functional（功能内聚） Layer（分层内聚） Communicational（通信内聚） Sequential（顺序内聚）