UML Weekend Crash Course™ - To Parent Directory
Share Embed Flag
Download ePaper

UML Weekend Crash Course™ - To Parent Directory

UML Weekend Crash Course™ - To Parent Directory UML Weekend Crash Course™ - To Parent Directory

crnarupa.singidunum.ac.rs
from crnarupa.singidunum.ac.rs More from this publisher
01.01.2015 Views

Index 357 resources, 50, 51–52 Use Case diagram, 52–58 user associations, defining, 64–65 conversation with Use Case (dialog), 71–72 evaluating, 65–66 features, associating (relationships), 55–58 generalization, evaluating, 67 identifying, 62–63 inventory control system case study requirements, 40–41 Use Case diagram, 53–54 user expectations, defining described, 24–25 elements, 52–53, 319–320 inventory control system case study, 61–67 people, systems, or devices trading information, 53–54, 319 relationships, 55–58 required features, defining (Use Cases), 54–55 rules, capturing, 39 system, 53 Use Case model, 52–58 Web development, 289–290 user expectations, describing assumptions, 70, 75 elements, listed, 69–70 inventory control system case study, writing, 74–78 pre-conditions, 70–71, 75 start point (initiation), 71, 75 states at end (post-conditions), 72–73, 77–78 step-by-step description (dialog), 71–72, 76 termination, 72, 77 user interface, 259–260 user objects, 7 value, default, 96–97 Varveris, Lou, 331 verifiable output, 14 verification, Shlaer-Mellor Method, 16, 318 version control in modeling tools, 310–311 UML (Unified Modeling Language)-supported modeling tools, 309 view benefits of using, 27–28 Class diagram, creating different, 102 defined, 23–24 Dynamic View, 26–27 Functional View, 24–25 Static View, 25–26 visibility attribute, modeling, 96–97 operation, 99 protected, 122 Visual Basic client, Deployment diagram, 300 data, transferring via XML (eXtensible Markup Language), 303 HTTP (HyperText Transfer Protocol), communicating, 299 Visual Basic for Applications (VBA), 312 visual description of process. See Activity diagram WAE (Web Application Extension), 305 WAP protocol, 294–295 weather Web site, 281 Web application Activity diagram, displaying, 327 appointments and contacts, uploading, 299–300 implementation Class diagram, 302–305 Model 2 Architecture, 297–299 querying appointments and contacts, 300–301 UML (Unified Modeling Language) extension, 305 Web development basic architecture and static content, 278–280 Class diagram representing business problem (analysis phase), 290–291 design phase, 291–295 dynamic content, 280–284 Friendly Reminder case study, 287–288, 294–295 Java servlets, 281–282 JSPs (JavaServer Pages), 283–284, 292–293 MVC (Model View Controller) design pattern, 291–292, 294–295 requirements, gatering, 288–291 template pages, 283 Use Case diagram, 289–290 value of UML (Unified Modeling Language), 277–278 Web page component notation, 256 moving among, 300, 301 Web sites, addresses listed methodologies, 21 modeling tools, 16, 313 UML Revision Task Force (RTF), 9 WAE (Web Application Extension), 305 Windows, using back-of-the-book CD-ROM, 329–330

358 Index wireless devices, 289, 294–295 WML (Wireless Markup Language), 294, 295 workflow activities notation, 151 Activity diagram, benefits of using, 83, 318, 327 concurrency, 154–155 decisions, 152–153 end point, 154 Fill Order case study, 85 guard condition, 151–152 inventory control system case study, 157–164 merge point, 153 methods, defining, 150 requirements, 73 RUP (Rational Unified Process), 14–15 sample, 328 start point, 154 transitions notation, 151–152 Use Cases, modeling, 149–150 XML (eXtensible Markup Language) described, 278 Friendly Reminder case study, 303–305 modeling tool, XMI (XML Metadata Interchange), 312–313 Visual Basic, communicating, 299 XP (Extreme Programming), 20–21 zero, 108

358<br />

Index<br />

wireless devices, 289, 294–295<br />

WML (Wireless Markup Language), 294, 295<br />

workflow<br />

activities notation, 151<br />

Activity diagram, benefits of using, 83, 318, 327<br />

concurrency, 154–155<br />

decisions, 152–153<br />

end point, 154<br />

Fill Order case study, 85<br />

guard condition, 151–152<br />

inventory control system case study, 157–164<br />

merge point, 153<br />

methods, defining, 150<br />

requirements, 73<br />

RUP (Rational Unified Process), 14–15<br />

sample, 328<br />

start point, 154<br />

transitions notation, 151–152<br />

Use Cases, modeling, 149–150<br />

<br />

XML (eXtensible Markup Language)<br />

described, 278<br />

Friendly Reminder case study, 303–305<br />

modeling tool, XMI (XML Metadata<br />

Interchange), 312–313<br />

Visual Basic, communicating, 299<br />

XP (Extreme Programming), 20–21<br />

<br />

zero, 108

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!