Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour EXAMPLES.

Slides:



Advertisements
Similar presentations
Chapter 3 Requirements Analysis, Negotiation and Modeling Part 3 Dr. Eman Al-Maghary Requirements Engineering.
Advertisements

1 CIS224 Software Projects: Software Engineering and Research Methods Lecture 6 State Machine and Activity Diagrams (Based on Stevens and Pooley (2006,
Overview UML Extensions for Agents UML UML Agent UML (AUML) Agent UML (AUML) Agent Interaction Protocols Agent Interaction Protocols Richer Role Specification.
Customer calls into Call Centre OR walks into Retail Store OR s regarding a debit order that was not honoured Agent verifies customer.
Use Case - Example University library system requirements
Assignment I, part 1. Groups of three students. Specify one as group leader. group names to TA and me. Create an object-oriented conceptualization.
Letters of Recommendations For admission to Graduate School By: Jocelyn VanNederynen.
7M822 UML Sequence Diagrams 2 December 2010.
Lecture 11: Chapter 22 Topics –Object Oriented Modeling –UML –Use case.
Chapter 8: Modelling Interactions and Behaviour
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Review 2.
UML Notations Activity diagrams State diagrams Class diagrams Use-case diagrams.
Process-oriented System Analysis Qualitative Process Analysis.
Presented by Michelle Scharf, Transfer Center Director.
Heli Pihlajamaa June 2015Director Patent Law Update on electronic tools of the EPO – notification, filing and fee payment.
GS On line Application Form November-2008 Click to continue.
Use Case Analysis From soft systems methodology to understanding the system functionality.
Interaction Modeling. Sequence Models  There are two kinds of sequence models: scenarios and sequence diagrams  A scenario is a sequence of events that.
College of Central Florida Devona Sewell.  Application.
Use Cases 2 ENGR ♯10 Peter Andreae
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
Additional Structure Exercise 2 ANSWERS NB. As not whole case study was given some of these answers may not be within the text.
©The McGraw-Hill Companies, Inc. Permission required for reproduction or display. 4 th Ed Chapter Chapter 1: Introduction to Object-Oriented Programming.
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
Understand Application Lifecycle Management
Pfleeger and Atlee, Software Engineering: Theory and PracticePage 4.1 © 2006 Pearson/Prentice Hall Sidebar 4.1 Why Are Requirements Important? Top factors.
January, 2008Douglas Dombrosky Graduate Admissions Workflow.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
Interaction Modeling Interaction model describes how objects interact to produce useful results. Interactions can be modeled at different levels of abstraction:
Chapter 10 Information Systems Analysis and Design
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
Other UML Diagramming Techniques CS 124. UML Diagramming Techniques Class Diagrams Use Case Diagrams Interaction Diagrams Sequence diagrams Collaboration.
Visamäki Campus Library Building D Introduction to HAMK Library and information services.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
Do Now What do you notice about the sums of these sequences?
UHD::3320::CH121 DESIGN PHASE Chapter 12. UHD::3320::CH122 Design Phase Two Aspects –Actions which operate on data –Data on which actions operate Two.
Business Process Analysis
Requirements Engineering Methods for Requirements Engineering Lecture-30.
1 Object-Oriented Modeling Using UML CS 3331 Section 2.4 Modeling Requirements with Use Cases.
Sequence Models.
Sequence Diagrams Sequence; Interaction Diagrams Behavioral Diagrams
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour UML Sequence Diagram.
Software Production ( ) First Semester 2011/2012 Dr. Samer Odeh Hanna (PhD)
Applying for your credential College of Education Office of Student Services September 21, 2012.
West Virginia University Slide 1 Copyright © K.Goseva 2010 CS 736 Software Performance Engineering Comments on Homework #1  Please revise the solution.
Common Application Workshop Online application-allows for online document submission Utilized by nearly 600 colleges and universities.  Preview the Common.
Student Orientation Seminar Student Services. College Catalog The Jefferson College Catalog is printed annually and is your official source of information.
Data Flow Diagrams Often a good way of summarising sources and destinations of data and the processing that takes place Shows how data is transformed into.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
TK2023 Object-Oriented Software Engineering CHAPTER 9 INTRODUCTION TO OBJECT DESIGN.
To book Bus Ticket. Click on the option Bus Booking.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
SEG2105 FINAL REVIEW December 2015
Systems Analysis & Design
WELCOME BACK SENIORS!! AUGUST 27,
 The sooner the better › SAT is changing Spring don’t know as much about it at this time  SAT-June 2 nd test (deadline to register is May 8 th.
ONLINE IMPORTS & EXPORTS PRESENTED BY T.NALINI( ) R.KIRANMAI( )
1 M206 Chapter 31: An Overview of Software Development 1.Defining the problem 2.Analyzing the requirement – constructing initial structural model 3.Analyzing.
Why apply to graduate programs? Better job choices Ability to have more control over your career Enriching research that can have long lasting affects.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
Object-Orientated Analysis, Design and Programming
CompSci 280 S Introduction to Software Development
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
Use Cases & Use Case Diagrams
Scheme for Growth Pilot
Nomination and Application Guidelines for partners - Instructions for online nominations - Information about application documents.
Exercise Develop a context Diagram for a small bank for “Loan Granting” process Identify EXTERNAL entities Develop a Context diagram.
Information system analysis and design
Presentation transcript:

Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour EXAMPLES

State Machine Diagram (1) You shall model the lifecycle of an application to a university graduate program. Potential students who apply to graduate programs need to provide their personal information as well as recommendation letters from former employers or professors. The lifecycle must reflect that: 1.Once created, an application needs to be verified for completeness. 2.An incomplete application may require additional information from the student (a university transcript, the results of an English/French test, or the payment of the application fees!) or from recommenders (the famous letters!). 3.Once evaluated, a complete application (where the information and the letters have been provided) is usually accepted or rejected. 4.The evaluation of an application may however also be postponed if the decision would be too close to the beginning of the next semester © Lethbridge/Laganière 2012 Chapter 8: Modelling Interactions and Behaviour2

State Machine Diagram (cont’d) In the following, the variables are: allStudentInfo (a Boolean): true iff all the required student info (transcript, language test, fees) have been received. allRecLetters (a Boolean): true iff all the required letters from recommenders have been received. tooClose (a Boolean): true iff the current date is such that the decision would be too close to the beginning of the next semester. acceptable (a Boolean): true iff the student is found admissible. © Lethbridge/Laganière 2012 Chapter 8: Modelling Interactions and Behaviour3

Activity Diagram – for the processing of a stock trade The online stock broker first verifies the order against the customer’s account, then executes it with the stock exchange. If the order executes succesfully, the system does three things concurrently: 1. s trade confirmation to the customer 2.Updates the online portfolio to reflect the results of the trade 3.And settles the trade with the other party by debiting the account When all three tasks are completed, the system closes the order. If the order execution fails, then the system sends a failure notice to the customer and closes the order. © Lethbridge/Laganière 2012 Chapter 8: Modelling Interactions and Behaviour4

Sequence Diagrams Draw sequence diagrams representing the following interaction: (a) A client searches for a book in a library. He or she then asks to borrow the book. If a copy of this book is available, a loan object is created. © Lethbridge/Laganière 2012 Chapter 8: Modelling Interactions and Behaviour5