Titlebook: Use Case Driven Object Modeling with UMLTheory and Practice; Theory and Practice Doug Rosenberg,Matt Stephens Book 2007Latest edition Don R

magnate

Critical Design Reviewiguate the use case text and discover any missing domain classes, you’ve held a Preliminary Design Review (PDR) to make sure the use cases match up with what the customer really wants, and you’ve carefully crafted a detailed design for the use cases you’re implementing in this release.

bronchiole

follicular-unit

Addressing Requirements differences between requirements, use cases, and behavior (operations). Since we talked about use cases in Chapter 3, allocating behavior in Chapter 8, and a whole series of techniques driven by use cases and operations in the subsequent chapters, it’s easier to talk about requirements in terms of how they contrast with those items.

Default

Preliminary Design ReviewThe Preliminary Design Review (PDR) session helps you to make sure that the robustness diagrams, the domain model, and the use case text all match each other. This review is the “gateway” between the preliminary design and detailed design stages, for each package of use cases.

愛(ài)社交

Technical ArchitectureThe purpose of technical architecture (TA) is to get an overall feel for the system that you’re going to be developing. Will it be a web-based system? Or a rich-client system in VB .NET or Java Swing? Does it need to use a specific application framework (e.g., a company-standard framework)?

駁船

Sequence DiagramsOnce you’ve finished robustness analysis, and you’ve held a preliminary design review, it’s time to begin the detailed design effort. By this time, your use case text should be complete, correct, detailed, and explicit. In short, your use cases should be in a state where you can create a detailed design from them.

calumniate

Code Review and Model UpdateDuring coding, it’s likely that you’ll have made a few changes to the design, so the code will now be slightly out of sync with the design diagrams. A depressingly common reaction at this stage is to deem the design documentation obsolete, throw it away, and continue all subsequent development work without doing any more design work.

小卷發(fā)

Design-Driven TestingIt’s easy to look at a program module and say, “There, that’s finished,” but this sense of completion can be deceptive. How do you know for sure that the code completes all the use case scenarios—not just the basic courses, but the alternate courses, too?

屈尊

有節(jié)制

http://image.papertrans.cn/u/image/944422.jpg