Unformatted text preview: ping an actor to initiate a process). If I were some of you, I wouldn't show it in usecase diagram. However, I found the B‐Line document stresses the role of phone. As an analyst, if I found that my customer insists on a technology, I will show that in use‐case. That's because he/she has the money ;‐) and I need that money; not that it's the right thing to do. I didn't deduct mark for this. But, having "web server" as an actor, it's obvious that in analysis we don't include it as an actor. Use cases must be related to information processing. "pick up items from supplier" or "loading truck" is a physical action. State Diagram The chosen object must be important for the information system (here in B‐Line saving the states of an employee is not important (we're not interested in having them in the database; it could be important for a Human Resource division) but the state of an "order" or inventory levels of "a product" is very important. all states in a state diagram must be related to one and only one object. In state diagram, the focus is on a thing (entity) not a process. When you focus on a process, then it's an activity diagram, not a state diagram. Sequence diagram An Incoming arrow to an object's timeline is labeled with a work done by that object, not a work done by the sending object. Objects in the header part include actors; although we use ORDER and INVENTORY object in design, we don't use them in analysis as they won't do anything at organizational level. Instead of them, use the name of the role who records them....
View Full Document
This homework help was uploaded on 04/04/2014 for the course COMM 436 taught by Professor Carsonwoo during the Fall '12 term at UBC.
- Fall '12