Create Sequence Diagram for Use Case: 22

[GoogleCodeExporter]

Create the requested sequence diagram, and add it to the wiki page: Sequence 
Diagrams. 

- Examine the class diagram we have created carefully. 
- Read the use cases thoroughly.
- Using -only- the classes and methods defined in the class diagram, draw the 
sequence diagram which clearly defines the process in terms of communication 
(method calls) between the involved classes. 

important: If you detect any missing required methods, classes, relationships, 
or if you think any of the method parameters or return types are incorrect, 
request an update on the class diagram immediately, by creating a new issue. 

Original issue reported on code.google.com by mustafat...@gmail.com on 20 Mar 2015 at 10:27

[GoogleCodeExporter]

I has just started to work on preparing sequence diagram for the use case 
defined above. 

estimated time: 3 hours

Original comment by buket.yi...@gmail.com on 21 Mar 2015 at 10:09

• Changed state: Started

[GoogleCodeExporter]

I completed the task. Please review it, and let me know your feedbacks. 

Original comment by buket.yi...@gmail.com on 22 Mar 2015 at 10:41

[GoogleCodeExporter]

Here, the login is unnecessary. Because we assume he is allready logged in, in 
the preconditions. 

User should first call the showCase and showRelationInsertionFormForCase 
methods of UserInterface. Then the user should call the userAddedRelation 
method of the UserInterface, passing self as a parameter. 

Then UserInterface should call the addRelation method of the Case class. 

Original comment by mustafat...@gmail.com on 23 Mar 2015 at 1:19

[GoogleCodeExporter]

Sequence diagram 22 was updated.

Original comment by buket.yi...@gmail.com on 28 Mar 2015 at 10:39

• Changed state: Done