01.01.2015 Views

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

350<br />

Index<br />

HTML (HyperText Markup Language) (continued)<br />

modeling tools, 309<br />

in MVC (Model View Controller), 292, 294<br />

static Web page, 279<br />

tag structure, 327<br />

template pages, 283<br />

HTTP (HyperText Transfer Protocol)<br />

described, 279<br />

Java servlet, generating response, 282<br />

Sequence diagram, 280<br />

Visual Basic, communicating, 299<br />

WAP, translating, 295<br />

<br />

IDE (Integrated Development Environment), 310<br />

identifier, 111–112<br />

identifying<br />

requirements for inventory control system<br />

case study, 40–42<br />

use case, 63–64<br />

users, 62–63<br />

implementation<br />

Class diagram for Web application, 302–305<br />

constraints, 38<br />

defined, 31–32<br />

hiding in encapsulation, 33<br />

replicating existing, 43<br />

stereotype, 248, 252, 326<br />

dependency, 56–57, 66<br />

incremental, 14, 318<br />

index cards. See CRC<br />

information<br />

encapsulating (association class), 110–111<br />

object-oriented information, 29<br />

inheritance, 58, 94, 121<br />

initial state, 227<br />

inner class construct, 120<br />

instance, 81<br />

Integrated Development Environment.<br />

See IDE interaction<br />

on Dynamic View, 26–27<br />

mapping to objects in Sequence diagram, 168–169<br />

interface<br />

Activity diagram, 150<br />

defined, 30–31<br />

finding and validating, 185<br />

modeling tools, 328<br />

notation, component diagram, 257, 326<br />

prototypes, 82–83<br />

publishing pre-conditions, 70–71<br />

querying appointments and contacts, 294<br />

internal events and activities, 210<br />

Internet address<br />

dynamic Web content, 281<br />

HTTP (HyperText Transfer Protocol),<br />

Sequence diagram, 280<br />

inventory control system case study<br />

Activity diagram, 157–164<br />

Class Diagram, 129–137<br />

Collaboration diagram, 193–201<br />

Component diagram, 258–260<br />

Deployment diagram, 266–271<br />

functionality, 42<br />

notation, package, 250–253<br />

pitfalls, avoiding, 43–43<br />

problem statement, 35–36<br />

requirements, identifying, 36–42<br />

Sequence diagram, 179–185<br />

Statechart diagram, 217–224, 237–243<br />

Use Case diagram, building, 61–67<br />

Use Case scenarios, finding, 84–90<br />

“is a” relationship. See generalization<br />

iterative approach, 14–15, 318, 324<br />

<br />

Jacobson, Ivar, 6, 49, 317<br />

Java<br />

dependency, confusion over, 120<br />

inner class construct, 120<br />

JavaScript versus, 283<br />

Java servlets<br />

Class diagram, 302<br />

JSPs (Java Server Pages), 284<br />

Web development, 281–282<br />

Java Web development, 297–299<br />

JavaBeans, 293, 297<br />

JavaScript<br />

Class diagram, 302<br />

Java versus, 283<br />

Jones, Capers, 82<br />

JSPs (Java Server Pages)<br />

Class diagram, 302<br />

JavaBeans, moving content, 292–293<br />

Model 2 Architecture, 297–298<br />

MVC (Model View Controller) design pattern, 294<br />

template, 283–284<br />

<br />

kind of. See generalization

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!