Assess A Claim
Object Interaction Diagrams
Object sequence Diagrams Use case
• Sequence of events that occur during one
particular execution of a system
• This sequence can effect one or more
objects
• The object sequence diagram shows the
flow of messages between object classes
• Object classes include entity, control and
boundary classes
Sequence diagrams
• An object is shown at the top of a dashed
vertical line - the object’s lifeline.
• The lifeline may start half way down the
diagram, at creation.
• The lifeline may end during the diagram, at
deletion. This can be done by placing an X at the
end of the life of the object.
• Each message is represented by an arrow
between the lifelines of two objects.
• The messages are listed from top to bottom in
order of occurrence.
Components of Sequence
diagrams
• Objects in use
– Sometimes the object is replaced by an
anonymous object from the class.
– This shows that any instance of this class can
realise the operation.
• Events or operations
– These represent messages between the
objects.
– The event is normally where one object
invokes a method on the other object.
Example Sequence Diagram
: Employee
: ViewClaim
: ViewAClaim
: Claim
1. load( )
2. EnterClaimNo( )
2.1. ValidateFormat( )
1.1.1. getDetails( )
3. ConfirmFinished(1.1.
) requestclaim( )
Note: NOT including
buttons to view further
details
Interaction diagrams in UML
• They are models that describe how groups of
objects collaborate in some behaviour.
• An interaction diagram captures the behaviour of
a single use case. It shows a number of
example objects and the messages that are
passed between these objects within the use
case.
• There are two kinds of interaction diagrams:
sequence diagrams and collaboration diagrams.
Elaborated Use Case…
• Continue on from ‘First cut elaboration’
• Convert the methods into inter-object
signals where appropriate.
• Represent inter-object signals as
interactions in an Object Sequence
Diagram.
• See the screens used on the following
slides.
Screens used
Boundary class representation
Control classes
• 1 for implementing Assess A claim
• Possibly one for View a claim
– Details not given here, for the sake of
simplicity.
Data Services or Entity classes
+theClaim
Accident
0...
1
Claim
0..1
1...
1
Claimant
1
0...
Expert Report
Payment
Assessor
0...
Expert
Used classes
• Boundary
– ClaimsForAssessment containing
ClaimsForAssessmentSB
– ViewClaim
– AssessClaimScreen
• Control
– AssessAClaim
• Entity
– Claim
– Assessor
: Assessor
: ClaimsForAssessmentSB
ClaimsForAssessment
AssessClaimScreen
Diagram
: ViewClaim
: AssessAClaim
: Claim
1. load( )
1.1. load( )
1.2. Instantiate( )
1.2.1. getDetails( )
1.2.2.
1.3. AddToSB( )
1.3.1. enableScroll( )
1.3.2. enablepick( )
1.3.3.
1.4.
2. Pick( )
3. close( )
2.1. AssessThisClaim( )
Sequence Diagram: View
Claim / ViewClaim
3.1.
4. pickSettle( )
2.1.1. load( )
4.1. enableValuation( )
4.2.
: Assessor
5. EnterValuationandPIN( )
5.1. ValuationEntered( )
5.1.1. Authorise Assessor( )
5.1.2. UpdateStatusandValuation( )
5.1.3.1.
5.1.3.