Com S 362 --- Object-Oriented Analysis and Design EXERCISE 9: DRAWING SYSTEM SEQUENCE DIAGRAMS (File $Date: 2004/09/03 13:44:50 $) The purpose of this exercise is for you to try drawing a system sequence diagram. As with all exercises, this is to be done individually, not in teams. And it is due the day this topic is planned to be discussed in class, unless specified otherwise (see the syllabus at: http://www.cs.iastate.edu/~cs362/syllabus.shtml). As with all exercises, you have two choices for doing the work. You can either: - complete it as specified or - write down questions or problems that you had in trying to complete it. If you write down questions or problems you have, these should be detailed enough so that we can tell that you have read the materials and thought about them. (Don't just write: "I couldn't get it to work; say what you tried and what you didn't understand.) During the class where this exercise is discussed, you should try to get help with these by explaining what you did and what your problems or confusions are. Don't be shy; there will be other people with the same problem, and everyone can learn by discussing these issues. 1. [SSD: Buying Books Back from Customer] Read chapter 9 of Craig Larman's book Applying UML and Patterns (second edition, Prentice Hall PTR, Upper Saddle River, NJ, 2002). Also, for more examples look at the web page for the StickSync project: http://www.cs.iastate.edu/~cs362/sticksync/ssd.shtml Consider a point of sale system for a university book store. Draw a system sequence diagram for the main success scenario of the use case of "Buying a Book Back from Customer", which would involve the store "book buyer" pricing and buying back used books from a "student". Assume that the store has a database of prices of books, which includes prices for all books the store cares about in various conditions, which should be consulted. WHAT TO HAND IN You should have at the beginning of class, written answers to the above questions (or written out questions and problems you encountered for each part). Make sure your name is on these. Attach the printouts, if any, requested above. ADDITIONAL READINGS If you have time, read chapter 5 of Martin Fowler with Kendall Scott's book UML Distilled (Addison-Wesley Longman, Inc., Reading, MA, 2000), as well as Larman's book, chapter 8.