Create Sequence Diagrams for Use Cases: 7,8,9

[GoogleCodeExporter]

Create the requested sequence diagrams, and add them 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:21

[GoogleCodeExporter]

Started to review class diagram and related use cases.
Will start to prepare the requested sequence diagrams as soon as possible.

Original comment by hakansah...@gmail.com on 22 Mar 2015 at 10:18

• Changed state: Started

[GoogleCodeExporter]

First drafts for related use cases has been added to the wiki page: 'Sequence 
Diagrams'.

Original comment by hakansah...@gmail.com on 23 Mar 2015 at 12:00

[GoogleCodeExporter]

For following User: 

-User should call UserInterface::ShowUserProfileInfoToUser
-User should call UserInterface::ShowUserFollowingOptionsToUser
-User should call UserInterface::UserFollowedUser
-UserInterface should then call User::FollowUser(of the followed user)

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

[GoogleCodeExporter]

I think User::FollowUser method of the user,who followed the other user, should 
be called. In our case, method of 'User:user1' should be used. Apart from that, 
I have done necessary changes.

Original comment by hakansah...@gmail.com on 23 Mar 2015 at 2:25

• Changed state: Done