Bài Giảng Phân tích thiết kế hướng đối tượng (phần 5)

Tham khảo tài liệu bài giảng phân tích thiết kế hướng đối tượng (phần 5), công nghệ thông tin, kỹ thuật lập trình phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả
Nội dung trích xuất từ tài liệu:
Bài Giảng Phân tích thiết kế hướng đối tượng (phần 5)Use case realization Lecture 5Hoa Sen University 1 Agenda Notations Dependency Interaction and Class diagrams Hoa Sen University 2 Interaction diagrams Generalization of two more specialized UML diagram types – Sequence diagrams – Communication diagrams Illustrate how objects collaborate via messages and methods Hoa Sen University 3 Sequence vs. Communication diagram Sequence diagrams :A myB : B illustrate interactions in a kind of fence format doOne doTwo – Easier to see the call doThree sequence – Large set of detailed notation options Communication diagrams doOne :A illustrate interactions in a graph or network format 1: doTwo – More space-efficient 2: doThree myB : B Hoa Sen University 4 Common notation: participants – lifeline box lifeline box representing the class lifeline box representing a Font, or more precisely, that Font is lifeline box representing an named instance an instance of class Class – an unnamed instance of class Sale instance of a metaclass «metaclass» :Sale s1 : Sale Font List is an interface lifeline box representing an lifeline box representing instance of an ArrayList class, one instance of class Sale, in UML 1.x we could not use an parameterized (templatized) to selected from the sales interface here, but in UML 2, this (or hold Sale objects ArrayList collection an abstract class) is legal sales: x : List sales[ i ] : SaleArrayList related example Hoa Sen University 5 Sequence diagram notation Lifeline boxes : R egister : Sale and lifelines Messages doX doA – Synchronous doB message a found m essage w hose sender w ill not – Found message be specified doC Focus of control doD and execution execution specification specification bars bar indicates focus of control typical sychronous m essage show n w ith a filled-arrow line Hoa Sen University 6 Sequence diagram notation Illustrating reply or returns : Register : Sale – Using the message syntax returnVar = message(parameter). doX – Using a reply message line d1 = getDate Message to “self” or “this”public class Register{ getDate public void doX(){ aDate … clear(); … : Register } doX public void clear(){ clear }} ...