{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}


ISOM221+Lecture+16+-+Interaction+Diagrams+I - Agenda...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
ISOM221 Information Systems Analysis and Design Lecture 16: Interaction Diagrams I (Sequence Diagram) 1 Agenda Understand the relationship between the behavioral models and the structural and functional models Understand the rules and style guidelines for sequence diagram Understand the processes used to create sequence diagram 2 STUDENT -STU_StudentID -STU_LastName -STU_FirstName -STU_Username -STU_Password -STU_Address -STU_Phone -STU_Email + Register() Some Updates on Last Class SHORTLISTING_RECORD -SR_ShortlistingID -SR_ShortlistingDate -SR_Status + Add () + Delete() + Update_Status() has 1 0..10 is included in 0..* Access to contact + Login() OWNER -OWN_OwnerID -OWN_LastName -OWN_FirstName -OWN_Username -OWN_Password -OWN_Address -OWN_Phone -OWN_Email + Insert() + Read_Contact() APARTMENT -APT_ApartmentID -APT_Address -APT_Size -APT_Bedroom -APT_Rent -APT_PostingDate + Insert() + Delete() + Match_Search_Criteria() + Show_Matched_Results() has 1 0..* 1 3 information in the OWNER class must be allowed in order to generate the search results by “Show_Matched_Results()” in the APARTMENT class Structural vs. Behavioral Models Systems have static & dynamic characteristics Structural models describe the static aspects of the system (Class diagram in Lecture 15) Behavioral models describe the dynamics and interactions of the system and its components Behavioral models describe The internal dynamic aspects of an information system that supports business processes in an organization The interaction between the classes (objects) in the structural models to support the use cases in a time- ordered manner 4
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Why Do We Care About Class Behaviors? Class diagram is static It tells you “what” should happen, not “how” it occurs Need to get a more dynamic view of the classes in order to be able to code the system
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}