(1) Student class is an example of -

		A boundary class
		An entity class
		A use case
		A control class

(2) Seminar class is an example of -

		A use case
		A boundary class
		An entity class
		A control class

(3) Check figure 11.7. The actor is interacting with the student page object. The student page object is a -

		Entity object
		Use case
		Boundary object
		Control object

(4) Sequence diagrams are typically used to -

		"Model usage scenarios; That is, they depict how an actor could use a system for a particular use case."
		Model attributes and methods for classes
		Model an alternative way of showing a class diagram
		Model an alternative way of showing an entire use case diagram.

(5) Check figure 11.7. GetSeminars is a message from TranscriptBuilder object to the Seminar object. This message becomes

		An attribute in the Seminar class
		A method in the TranscriptBuilder class
		Not related to methods or attributes in classes.
		A method in the Seminars class

Tab Corilerils. the chapter 1 Leading Edge scftware oewelopment Chapter 2 understanding the Basis-cbert tyde Ubiett-Ul Pter 4 Agi Made Drvi Chapter 5 U ge Modeling D: velopment Chapter 6 U Chapter 7 Supplementary Ra Modeling pter B Conceptual Dot Moceing Chapter 10 fgile Architect chapter 11 pyrami: object M 11.3 UML Stat: Machne Diagrama UMI that You Hav Chapter chapter 13 obje -oriented Programming Pter tt Agile Student studentPage Transcript Builder student Student Seminar > Printer each seminarl Marko calculate Mark00 print studentPage) FIGURE 11.7 Modeling how transcripts are output