复旦大学:《面向对象分析和设计》课程资料_课程注册系统_9-11 UC Design、Subsystem Design、Class Design

9 UC Design
1 9 UC Design

IBM Software Group Mastering object-Oriented Analysis and Design With UML Module 9: Use-Case Design Rational software
2

Class Design in Context [Early Elaboration [Inception Iteration Iteraton(Optional) Define a Candidate Perform Architecture Architectural Analyze Behavor Refine the (Optional) Arch tecture 大 Class Desian Define Design the Databas H
3

E bonn arabo 架构分析 ⑧ E Defne a candidate Partum Arcteetra 用例分析 Anay 识别设计元素 Anaya BehaVor 运行时架构 Rore ne Archtecture 描述分布 Degn物e 数据库设计 用例设计 子系统设计 类设计 M 且
4

Project Use Case Mo del Supplementary Guidelines Caps ule Specification D esign Caps ule Des igner Use case Modg Realizations Capsule Proto col esian ase Class Des ign Desi Interface Review Designe the d es ign Te chic al Reviewe Tes tability Subsystem ments Des ign Design Subsyst Pro ject Revew Test Interface Specific Guidelines pecif icat io Test Interface Testability Design specification Class Package Interface Define Testa bili Design Elements Test Model Desig Use Case
5

Use-Case Design Steps Describe interaction among design objects Simplify sequence diagrams using subsystems Describe persistence-related 0 behavior Refine the flow of events description ◆ Unify classes and subsystems← H
6

Use-Case Design Steps ★◆ Describe interaction among design objects Simplify sequence diagrams using subsystems Describe persistence-related behavior Refine the flow of events description Unify classes and subsystems H
7

Representing Subsystems on a Sequence Diagram ◆| interfaces Represent any model element that realizes the interface No message should be drawn from the interface ◆ Subsystem Component Represents a specific subsystem Messages can be drawn from the subsystem Obiect A Interface Object B ObjectA Subsystem Object B Component 1: Message 1 Message 1 2:Me、sa,e2 2: Message 2 Invalid message Valid message E写喜
8 Representing Subsystems on a Sequence Diagram Interfaces Represent any model element that realizes the interface No message should be drawn from the interface Subsystem Component Represents a specific subsystem Messages can be drawn from the subsystem Object A Interface Object B 1: Message 1 2: Message 2 Object A Subsystem Component Object B 1: Message 1 2: Message 2 X Invalid message Valid message

EXample: Incorporating Subsystem Interfaces Analysis Classes Design Elements > > Billing System Billing System /submit billo I System submit Bill(for Tuition: Double, for Student: Student) > Course Catalog System > Course Catalog system get course offerings lCourse Catalog System get CourseOfferings(for Semester: Semester, for Student: Student): Course OfferingList All other analysis classes are mapped directly to design classes
9 All other analysis classes are mapped directly to design classes. Analysis Classes Design Elements Example: Incorporating Subsystem Interfaces BillingSystem //submit bill() > Billing System > IBillingSystem submitBill(forTuition : Double, forStudent : Student) CourseCatalogSystem //get course offerings() > ICourseCatalogSystem getCourseOfferings(forSemester : Semester, forStudent : Student) : CourseOfferingList initialize() Course Catalog System >

EXample: Incorporating Subsystems Before Analysis class to be replaced RegisterForCoursesForm: Registration Controller: Course Catalog System: Schedule Student Student 1.∥ create schedule 1.1.get course offerings() Student wishes to create a new 1.1.1.get course offerings(forSemester) schedule 1. 2. / display course offerings() A list of the available course offerings for this semester are displayed a blank schedule 1.3. /I display blank schedule() is displayed for the students to select oFFerings Select Offerings Submit Schedule
10 Example: Incorporating Subsystems (Before) Analysis class to be replaced : Student : RegisterForCoursesForm : RegistrationController : CourseCatalogSystem : Schedule : Student Student wishes to create a new schedule 1. // create schedule( ) 1.2. // display course offerings( ) 1.1. // get course offerings( ) 1.1.1. // get course offerings(forSemester) 1.3. // display blank schedule( ) A blank schedule is displayed for the students to select offerings A list of the available course offerings for this semester are displayed Select Offerings Submit Schedule ref ref
按次数下载不扣除下载券;
注册用户24小时内重复下载只扣除一次;
顺序:VIP每日次数-->可用次数-->下载券;
- 复旦大学:《面向对象分析和设计》课程资料_课程注册系统_6-8 Identify Design Elements、RunTime Architecture、Describe Distribution.pdf
- 复旦大学:《面向对象分析和设计》课程资料_课程注册系统_1-5 最佳实践、需求、分析设计、架构分析、用例分析.pdf
- 复旦大学:《面向对象分析和设计》课程资料_Exception handling refactorings.pdf
- 复旦大学:《面向对象分析和设计》课程资料_Error Handling.pdf
- 复旦大学:《面向对象分析和设计》课程资料_AntiPattern_2.Servlet.pdf
- 复旦大学:《面向对象分析和设计》课程资料_AntiPattern_1.JSP J2EE Refactoring Patterns/AntiPatterns.pdf
- 复旦大学:《面向对象分析和设计》课程资料_分析模式_责任模式 Accountability.pdf
- 复旦大学:《面向对象分析和设计》课程资料_分析模式_观察和测量模式.pptx
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_UMLProfile.pdf
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_5.5 Iteration 3 持久化框架 DESIGNING A PERSISTENCE FRAMEWORK WITH PATTERNS.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_5.4 Iteration 3 状态图 MODELING BEHAVIOR IN STATECHART DIAGRAMS.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_5.3 Iteration 3 SSD和合约 ADDING NEW SSDs AND CONTRACTS.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_5.2 Iteration 3 领域模型 MODELING GENERALIZATION & REFINING THE DOMAIN MODEL.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_5.1 Iteration 3 用例加关系.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_4.2 Iteration 2 用GoF设计用例实现 DESIGNING USE-CASE REALIZATIONS WITH GoF DESIGN PATTERNS.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_4.1 Iteration 2 GRASP:MORE PATTERNS.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_3.5 Iteration 1 实现模型.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_3.4 Iteration 1 设计模型 GRASP——设计带职责的对象.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_3.4 Head 2 On to Object Design.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML&GRASP_3.4 Head 1 Logical Architecture and UML Package Diagrams.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 1 - 面向对象分析和设计.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 2 - 迭代、进化和敏捷.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_OOP:Object-Oriented Programming.pptx
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 3 - 案例分析 THE NEXTGEN POS SYSTEM.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 4 Chapter 5 - 初始阶段的需求.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 6 - 用例.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 7 - 其他需求.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 8 - 细化阶段的迭代——基础.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 9 - 领域模型.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 10 - 系统顺序图.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 11 - 操作契约.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 13 - 逻辑架构和UML包图.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 14 - 迈向对象设计.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 15 - UML交互图.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 16 - UML类图.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 17 - GRASP基于职责设计对象.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 18 - 使用GRASP的对象设计示例.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 19 Chapter 20 Chapter 22.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_Chapter 21 测试驱动的开发与重构.ppt
- 复旦大学:《面向对象分析和设计》课程资料_UML和模式_复习:OOAD部分.ppt
