Item Details

Enterprise Java With UML

CT Arrington
Format
Book
Published
New York : J. Wiley, c2001.
Language
English
ISBN
0471386804 (pbk. : alk. paper)
Contents
  • Chapter 1 Introduction to Modeling Java with the UML 1
  • What Is Modeling? 2
  • UML 4
  • Modeling Software Systems with the UML 13
  • Modeling Process 14
  • Chapter 2 Gathering Requirements with UML 17
  • What Are Good Requirements? 18
  • Guidelines for Gathering Requirements 34
  • How to Detect Poor Requirements 37
  • Chapter 3 Gathering Requirements for the Timecard Application 41
  • Listen to the Stakeholders 42
  • Build a Use Case Diagram 44
  • Describe the Details 48
  • Gathering More Requirements 58
  • Revising the Use Case Model 61
  • Chapter 4 A Brief Introduction to Object-Oriented Analysis with the UML 77
  • What Is Object-Oriented Analysis? 80
  • Discover Candidate Objects 81
  • Describe Behavior 90
  • Describe the Classes 95
  • Chapter 5 Analysis Model for the Timecard Application 103
  • Prioritizing the Use Cases 103
  • Discover Candidate Objects 112
  • Describe Object Interactions 118
  • Describe Classes 126
  • Chapter 6 Describing the System for Technology Selection 133
  • Group Analysis Classes 134
  • Describe Each Group 136
  • Technology Requirements for the Timecard Application 144
  • Chapter 7 Evaluating Candidate Technologies for Boundary Classes 153
  • Technology Template 153
  • Swing 154
  • Java Servlets 168
  • XML 175
  • Technology Selections for the Timecard System 180
  • Chapter 8 Evaluating Candidate Technologies for Control and Entity Classes 183
  • RMI 183
  • JDBC 193
  • EJB 1.1 199
  • Sample Technology Selection 208
  • Chapter 9 Software Architecture 211
  • Goals for Software Architecture 213
  • UML and Architecture 214
  • Guidelines for Software Architecture 221
  • Creating a Software Architecture 222
  • Sample Architecture for the Timecard System 225
  • Chapter 10 Introduction to Design 239
  • What Is Design? 239
  • Need for Design 240
  • Design Patterns 241
  • Planning for Design 243
  • Designing Packages or Subsystems 246
  • Design Efforts for the Timecard Application 247
  • Chapter 11 Design for the TimecardDomain and TimecardWorkflow 249
  • Establish Goals for the Effort 250
  • Review Prior Steps 251
  • Apply Design for Each Use Case 262
  • Evaluate the Design 273
  • Implementation 277
  • Chapter 12 Design for HTML Production 323
  • Design Goals 324
  • Design to Goals 327
  • Filling in the Details 339
  • Implementation 346
  • Chapter 13 Design for the TimecardUI Package 373
  • Establish Design Goals 373
  • Review Prior Steps 374
  • Design to Goals 379
  • Design for Each Use Case 381
  • Implementation 387
  • Chapter 14 Design for BillingSystemInterface 401
  • Identify Goals 401
  • Review of Analysis Model 402
  • Review of Architecture 402
  • Design 403
  • Implementation 407.
Description
xxii, 451 p. : ill. ; 24 cm. + 1 computer optical disc (4 3/4 in.)
Systems requirements: at least 300 Mhz Pentium ;128MB RAM, 120MB hard drive space ;Windows NT or 2000.
Notes
Includes bibliographical references (p. 435-438) and index.
Technical Details
  • Access in Virgo Classic

  • LEADER 03946pam a22003374a 4500
    001 u3701650
    003 SIRSI
    005 20010227142914.0
    008 001221s2001 nyua b 001 0 eng
    010
      
      
    a| 00054566
    020
      
      
    a| 0471386804 (pbk. : alk. paper)
    035
      
      
    a| (Sirsi) i0471386804
    035
      
      
    a| (OCoLC)45700825
    040
      
      
    a| DLC c| DLC d| NhCcYBP d| MvI
    042
      
      
    a| pcc
    050
    0
    0
    a| QA76.73.J38 b| A78 2001
    082
    0
    0
    a| 005.13/3 2| 21
    090
      
      
    a| SCIENG/QA76.73.J38 b| A78 2001
    100
    1
      
    a| Arrington, C. T.
    245
    0
    0
    a| Enterprise Java with UML / c| CT Arrington.
    260
      
      
    a| New York : b| J. Wiley, c| c2001.
    300
      
      
    a| xxii, 451 p. : b| ill. ; c| 24 cm. + e| 1 computer optical disc (4 3/4 in.)
    504
      
      
    a| Includes bibliographical references (p. 435-438) and index.
    505
    0
    0
    g| Chapter 1 t| Introduction to Modeling Java with the UML g| 1 -- t| What Is Modeling? g| 2 -- t| UML g| 4 -- t| Modeling Software Systems with the UML g| 13 -- t| Modeling Process g| 14 -- g| Chapter 2 t| Gathering Requirements with UML g| 17 -- t| What Are Good Requirements? g| 18 -- t| Guidelines for Gathering Requirements g| 34 -- t| How to Detect Poor Requirements g| 37 -- g| Chapter 3 t| Gathering Requirements for the Timecard Application g| 41 -- t| Listen to the Stakeholders g| 42 -- t| Build a Use Case Diagram g| 44 -- t| Describe the Details g| 48 -- t| Gathering More Requirements g| 58 -- t| Revising the Use Case Model g| 61 -- g| Chapter 4 t| A Brief Introduction to Object-Oriented Analysis with the UML g| 77 -- t| What Is Object-Oriented Analysis? g| 80 -- t| Discover Candidate Objects g| 81 -- t| Describe Behavior g| 90 -- t| Describe the Classes g| 95 -- g| Chapter 5 t| Analysis Model for the Timecard Application g| 103 -- t| Prioritizing the Use Cases g| 103 -- t| Discover Candidate Objects g| 112 -- t| Describe Object Interactions g| 118 -- t| Describe Classes g| 126 -- g| Chapter 6 t| Describing the System for Technology Selection g| 133 -- t| Group Analysis Classes g| 134 -- t| Describe Each Group g| 136 -- t| Technology Requirements for the Timecard Application g| 144 -- g| Chapter 7 t| Evaluating Candidate Technologies for Boundary Classes g| 153 -- t| Technology Template g| 153 -- t| Swing g| 154 -- t| Java Servlets g| 168 -- t| XML g| 175 -- t| Technology Selections for the Timecard System g| 180 -- g| Chapter 8 t| Evaluating Candidate Technologies for Control and Entity Classes g| 183 -- t| RMI g| 183 -- t| JDBC g| 193 -- t| EJB 1.1 g| 199 -- t| Sample Technology Selection g| 208 -- g| Chapter 9 t| Software Architecture g| 211 -- t| Goals for Software Architecture g| 213 -- t| UML and Architecture g| 214 -- t| Guidelines for Software Architecture g| 221 -- t| Creating a Software Architecture g| 222 -- t| Sample Architecture for the Timecard System g| 225 -- g| Chapter 10 t| Introduction to Design g| 239 -- t| What Is Design? g| 239 -- t| Need for Design g| 240 -- t| Design Patterns g| 241 -- t| Planning for Design g| 243 -- t| Designing Packages or Subsystems g| 246 -- t| Design Efforts for the Timecard Application g| 247 -- g| Chapter 11 t| Design for the TimecardDomain and TimecardWorkflow g| 249 -- t| Establish Goals for the Effort g| 250 -- t| Review Prior Steps g| 251 -- t| Apply Design for Each Use Case g| 262 -- t| Evaluate the Design g| 273 -- t| Implementation g| 277 -- g| Chapter 12 t| Design for HTML Production g| 323 -- t| Design Goals g| 324 -- t| Design to Goals g| 327 -- t| Filling in the Details g| 339 -- t| Implementation g| 346 -- g| Chapter 13 t| Design for the TimecardUI Package g| 373 -- t| Establish Design Goals g| 373 -- t| Review Prior Steps g| 374 -- t| Design to Goals g| 379 -- t| Design for Each Use Case g| 381 -- t| Implementation g| 387 -- g| Chapter 14 t| Design for BillingSystemInterface g| 401 -- t| Identify Goals g| 401 -- t| Review of Analysis Model g| 402 -- t| Review of Architecture g| 402 -- t| Design g| 403 -- t| Implementation g| 407.
    538
      
      
    a| Systems requirements: at least 300 Mhz Pentium ;128MB RAM, 120MB hard drive space ;Windows NT or 2000.
    596
      
      
    a| 5
    650
      
    0
    a| Java (Computer program language)
    650
      
    0
    a| UML (Computer science)
    999
      
      
    a| QA76.73 .J38 A78 2001 w| LC i| X004474761 l| STACKS m| SCI-ENG t| BOOK

Availability

Google Preview

Library Location Map Availability Call Number
Brown Science and Engineering Stacks N/A Available