|
|
 |
| Авторизация |
|
|
|
| Поиск по указателям |
|
|
|
|
|
|
|
 |
|
|
|
| Rosenberg D., Stephens M. — Use Case Driven Object Modeling with UML: Theory and Practice |
|
|
|
| Предметный указатель |
Internet Bookstore, reviewing the Write Customer Review use case 309
Internet Bookstore, root cause of the “swarms of tiny classes” problem 311
Internet Bookstore, running test cases for data-retrieval controllers 356
Internet Bookstore, running the BookstoreTestSuite from the command line 350
Internet Bookstore, save() 286
Internet Bookstore, Search for Books use case 131
Internet Bookstore, setBookDao() 243 359
Internet Bookstore, setUp() 354
Internet Bookstore, Show Book Details sequence diagram 347
Internet Bookstore, Show Book Details use case 268 292 344 414—415
Internet Bookstore, Show Book Details use case, CDR example 238
Internet Bookstore, Show Book Details use case, robustness diagram 115 126
Internet Bookstore, Show Book Details use case, updated sequence diagram 252
Internet Bookstore, ShowBookTestHelper 368
Internet Bookstore, showing HttpSession on the sequence diagram 206
Internet Bookstore, showValidationErrors() 213
Internet Bookstore, Spring Framework 165
Internet Bookstore, Spring Web MVC 165 167
Internet Bookstore, testability 179
Internet Bookstore, testBookDetailsFound() 362
Internet Bookstore, testBookIdFound() 353
Internet Bookstore, testBookIdNotFound() 353
Internet Bookstore, testDisplayHomePage() 346
Internet Bookstore, testing HomeController 347—348
Internet Bookstore, testing that a book was not found 356
Internet Bookstore, testing the Display Book Details controller 357
Internet Bookstore, testing the Display Book Not Found page controller 363
Internet Bookstore, testing the Display Home Page controller 345
Internet Bookstore, testing the Retrieve Book Details controller 352
Internet Bookstore, testing to retrieve a book using its ID 354
Internet Bookstore, testPageDisplayed() 359—360 362
Internet Bookstore, tracing individual requirements to use cases 96
Internet Bookstore, tracking the source of the book’s ID 305
Internet Bookstore, turning controllers into methods on sequence diagrams 317
Internet Bookstore, UML model for 324
Internet Bookstore, updated static model 126 210—211
Internet Bookstore, user authentication/authorization 179
Internet Bookstore, using a Code Review and Model Update checklist 304
Internet Bookstore, using Java for 165
Internet Bookstore, using Java’s reflection API 314
Internet Bookstore, validate() 289 313
Internet Bookstore, validation controllers 133
Internet Bookstore, view (presentation) layer 173 175
Internet Bookstore, view page (bookdetails.jsp) 274 277
Internet Bookstore, web security 179
Internet Bookstore, WEB-INF folder 418 421
Internet Bookstore, web.xml 418—419
Internet Bookstore, when the use case text and robustness diagram don’t match 246
Internet Bookstore, why bother with designing unit tests 366
Internet Bookstore, Write Customer Review use case 278 344 416—417
Internet Bookstore, Write Customer Review use case, CDR example 245
Internet Bookstore, Write Customer Review use case, reviewing the controllers 309
Internet Bookstore, Write Customer Review use case, robustness diagram 117
Internet Bookstore, Write Customer Review use case, updated sequence diagram 252
Internet Bookstore, Write Reader Review use case 70—71
Internet Bookstore, WriteCustomerReviewCommand 247 255
Internet Bookstore, WriteCustomerReviewController class 279 284 290 310
Internet Bookstore, writecustomerreviewjsp 290
Internet Bookstore, WriteReviewScreen class 213
Internet Bookstore, writing tests from the calling object’s point of view 338 347 358
Internet Bookstore, writing unit tests prior to coding 344
Inversion of Control (IoC), Dependency Injection (DI) 409 412
Inversion of Control (IoC), design pattern 166 283
Inversion of Control (IoC), Java bean example with one property 409
Inversion of Control (IoC), wiring beans together 411
isLoggedIn() 288
J2EE Servlet API 412
Java Data Objects (JDO) 166
Java Standard Tag Library (JSTL) 412 422
Java Swing 166
Java, classes 410
Java, dot notation 423
Java, naming conventions 410
Java, object naming conventions 275
Java, packages and subpackages, naming conventions 410
Java, property 410
Java, reverse URL convention 410 423
Java, variables 410
JavaBeans 165
JavaServer Pages (JSP) 165—166 412
JavaServer Pages (JSP), testing 179
JDBC 166 258
JdbcBookDao class 275
JDO 260
JGenerator 260
JSP Tag Library (JSTL) 165
Jumpstart training workshops 88
JUnit 18 331 334
JUnit, adding individual tests to the test suite 351
JUnit, AddToShoppingCartTest test case 340
JUnit, assert methods 339
JUnit, assertEquals(), arguments used 340
JUnit, introduction to 339
JUnit, limiting each test method to a single assert statement 339
JUnit, mapping test cases directly to Java test classes 339
JUnit, naming convention followed 339
JUnit, new features in version 4.0 341
JUnit, operation of 339
JUnit, running tests from a test suite 350
JUnit, setUp() 340—341
JUnit, suite() 350
JUnit, tearDown() 341
JUnit, test skeleton 346
JUnit, testDisplayHomePage() 346
JUnit, TestRunner 350
JUnit, unit test class, code example 339
JUnit, website of 339
Link class 86
Linking use cases to objects 11
load() 240 243
Login use case 105 110 122
Manager classes 108
MDG Integration 195 262
Messages, differentiating among programming languages 189
Messages, labeling on sequence diagrams 188 194
messages, passing 187
Method Injection 412
Microsoft Visual Studio 2005 262
Miscommunication in IT projects 23
Mock objects, testing with 354
Mock objects, using sparingly 343 354 369
MockBookDao class 354
Model-View-Controller (MVC) architecture 165 167
ModelAndView object 168 178 412 415
Modeling aggregation and generalization relationships 28
Moderate Customer Reviews use case 122
Moderate Pending Reviews use case 324
Multiplicity, using 214
Naming the logical software functions (controllers) 3
Nonfunctional requirements testing 333
NotFoundException 309
NullPointerException 354
NUnit 334 339
Object discovery 106
object instances 59
Object lifelines 187
Object model, use cases and 25
Object-oriented design (OOD), sequence diagrams and 185
Object-relational mapping (ORM) 166
Objects, classification of 101
Objects, definition of 25
Operation, UML definition of 189
Organizing use cases into packages 9 85—86
Package/component model 161 173
Packages 410 422
Packages, definition of 61
performance testing 334
Performing a Code Review and Model Update 4
Persona, definition of 19
plain old Java objects (POJOs) 165
| pointcuts 74
Prefactoring designs 14
Preliminary design 51
Preliminary Design Review (PDR) 3 12
Preliminary design steps 9
Preliminary design, robustness analysis and 102
Preventing entropy (code rot) 18
problem domain 26 249
Problem space classes 201
Problem space, describing 29
Project glossary 24 26
Project requirements, ongoing changeability of 28
Properties dialog, Enterprise Architect (EA) 383
Property (in Java) 410
Rational Rose 57 196
Rational XDE 260
Real-time systems, using elements on state diagrams to build test cases 330
realization relationship 386
Refactoring 351
Regression testing 334
Relationship Matrix 388
Release testing 333
Requirements gathering, allocation and traceability as a life cycle concern 378
Requirements gathering, avoiding dysfunctional (intermangled) requirements 374—375
Requirements gathering, avoiding the “big monolithic document” syndrome 374 377
Requirements gathering, creating estimates from use cases or controllers list 374 377
Requirements gathering, data analysis and reduction, definition of 378
Requirements gathering, data capture and data reporting, definitions of 378
Requirements gathering, different corporate strategies for handling 373
Requirements gathering, distinguishing between types of requirement specs 374 376
Requirements gathering, drag-and-drop linking of elements back to requirements 374
Requirements gathering, driving requirements from business needs, not design patterns 374 377
Requirements gathering, giving each requirement a short, catchy name 374 376
Requirements gathering, guidelines 6 374
Requirements gathering, intermangling of requirements and scenario text 375—376
Requirements gathering, practice questions in 389
Requirements gathering, removing dysfunctionality from requirements 376
Requirements gathering, separating active-voice use cases from passive-voice requirements 375
Requirements gathering, traceability of requirements 378
Requirements gathering, using examples when writing functional requirements 374 377
Requirements gathering, using modeling tools supporting linkage and traceability 374
Requirements gathering, why requirements tracking is vital 377
Requirements gathering, writing at least one test case for each requirement 374 376
Requirements Review 3 8
Requirements Review as a collaborative review among project stakeholders 83
Requirements Review, accounting for alternate courses of action 93
Requirements Review, achieving basic agreement among all stakeholders 88
Requirements Review, actively describing user interactions and system responses 95
Requirements Review, allocating functional requirements to use cases 89
Requirements Review, avoiding overly abstract use case text 93
Requirements Review, avoiding passive-voice functional requirements in use cases 85—86
Requirements Review, benefits of a facilitator/moderator 88
Requirements Review, changing statements from passive to active voice 95
Requirements Review, creating clear illustrations of user and system behavior 87
Requirements Review, decomposing a system along usage scenario boundaries 93
Requirements Review, describing basic and alternate courses in active voice 86
Requirements Review, eight steps to a better use case 88—89
Requirements Review, guidelines 8 85
Requirements Review, keeping use case terminology concise and consistent 92
Requirements Review, linking the GUI model to the narrative behavior descriptions 87
Requirements Review, making the sign-off process collaborative 84
Requirements Review, naming mock-up screens 87
Requirements Review, naming participating domain objects 92
Requirements Review, organizing use cases into packages 85—86
Requirements Review, performing collaboratively with the right people 88
Requirements Review, placing use cases in the user interface context 87
Requirements Review, rationale for 84
Requirements Review, referring use case text to the appropriate domain objects 87
Requirements Review, removing out-of-scope information 90
Requirements Review, tracing individual requirements to use cases 96
Requirements Review, use case diagram, purpose of 87
Requirements Review, using storyboards and GUI prototypes 87
Requirements Review, writing coherent, specific, and unambiguous use case text 95
Requirements Review, writing use cases in the context of the object model 87
Requirements tree, creating 385
Resin 166
Responsibility-Driven Design (RDD) 194 204 247
Reverse URL convention 410 423
Robustness analysis as preliminary design 102
Robustness analysis as the middle ground between analysis and design 102
Robustness analysis, adding a Customer actor to the robustness diagram 117
Robustness analysis, boundary objects 103
Robustness analysis, bridging the gap from analysis to design 101
Robustness analysis, controllers 103
Robustness analysis, creating a new, blank robustness diagram 117
Robustness analysis, enforcing a noun-verb-noun pattern in use case text 104
Robustness analysis, entity objects 103
Robustness analysis, exercises and solutions for fixing modeling errors 128 131—133 136—137 139
Robustness analysis, guidelines 11 104—105
Robustness analysis, linking use cases to objects 101
Robustness analysis, modeling the alternate courses 122
Robustness analysis, performing for a use case 114
Robustness analysis, practice questions in modeling 140—141
Robustness analysis, rules for noun-verb interaction 103
Robustness analysis, technical architecture (TA) 102 160
Robustness analysis, using to disambiguate use case text 102
Robustness analysis, walking through the Write Customer Review use case 117
Robustness diagrams as a preliminary conceptual design of a use case 105 109
Robustness diagrams as an object picture of a use case 101 105 109
Robustness diagrams, adding a Customer actor 117
Robustness diagrams, adding missing entity classes to the domain model 104 106
Robustness diagrams, arrows as communication associations on 108
Robustness diagrams, avoiding drawing individual UI elements 118 136
Robustness diagrams, boundary objects 103
Robustness diagrams, CASE tools 105
Robustness diagrams, catching rule violations 112—114
Robustness diagrams, controllers 103—104 108
Robustness diagrams, creating a new, blank diagram 117
Robustness diagrams, definition of 101—102
Robustness diagrams, disambiguated nomenclature of boundary objects 108
Robustness diagrams, discovering hidden functionality and missing domain classes 137
Robustness diagrams, doing a preliminary sketch on paper 102
Robustness diagrams, enforcing a noun-verb-noun pattern in use case text 104
Robustness diagrams, entity objects 103
Robustness diagrams, expecting to rewrite (disambiguate) the use case 104 107
Robustness diagrams, generating skeleton tests from 238
Robustness diagrams, GUI 107
Robustness diagrams, learning to draw the use case text 117
Robustness diagrams, main purposes of 108
Robustness diagrams, making a boundary object for each screen 104 108
Robustness diagrams, manager classes 108
Robustness diagrams, modeling alternate courses 122
Robustness diagrams, morphing of objects into the detailed design 105 109
Robustness diagrams, naming screens unambiguously 104
Robustness diagrams, not allocating operations to classes 133
Robustness diagrams, not confusing with a collaboration diagram 107—108
Robustness diagrams, not including sections of use case text 136
Robustness diagrams, not redrawing endlessly 208
Robustness diagrams, not specifying validation checks in detail 139
Robustness diagrams, not worrying about arrow directions 104 108
Robustness diagrams, object discovery 106
Robustness diagrams, object messages as verbs 104
Robustness diagrams, objects as nouns 104
Robustness diagrams, page names as nouns 116
Robustness diagrams, pasting the use case text onto 104—105
Robustness diagrams, performing the highlighter test 122 136
Robustness diagrams, problems arising from ambiguous use case text 136
Robustness diagrams, reading like an activity diagram or a flowchart 103
Robustness diagrams, representing the flow of action between two objects 103
Robustness diagrams, requirement for matching use case text precisely 101
Robustness diagrams, rules for noun-verb interaction 103
Robustness diagrams, Show Book Details use case 115 126
Robustness diagrams, showing invoked use cases 104 109
Robustness diagrams, showing valid and invalid relationships 113
Robustness diagrams, software functions 107
Robustness diagrams, taking entity classes from the domain model 104 106
Robustness diagrams, technical architecture (TA) and 160
Robustness diagrams, three class stereotypes 103
Robustness diagrams, time requirements of 102
Robustness diagrams, using controller classes sparingly 108
|
|
|
| Реклама |
|
|
|
|
|
О проекте