04.06.2015 Views

Database Modeling and Design

Database Modeling and Design

Database Modeling and Design

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3.2 Activity Diagrams 49<br />

Customer<br />

Request quote<br />

Manufacturer<br />

Generate quote<br />

Review quote<br />

[unacceptable]<br />

[acceptable]<br />

Place order<br />

Enter order<br />

Produce order<br />

Ship order<br />

Receive order<br />

Receive invoice<br />

Generate invoice<br />

Pay<br />

Record payment<br />

Figure 3.12<br />

UML activity diagram, manufacturing example.<br />

In parallel to the Customer receiving the order, the Manufacturer generates<br />

an invoice (Generate invoice), <strong>and</strong> then the Customer receives the<br />

invoice (Receive invoice). Order of activities between threads is not constrained.<br />

Thus, the Customer may receive the order before or after the<br />

manufacturer generates the invoice, or even after the Customer receives<br />

the invoice.<br />

At a join, multiple threads merge into a single thread. The notation<br />

is a solid bar with multiple incoming arrows <strong>and</strong> one outgoing arrow. In

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

Saved successfully!

Ooh no, something went wrong!