Create Sequence Diagrams for Use Cases: 16,17,18

[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:23

[GoogleCodeExporter]

Original comment by murataki...@gmail.com on 22 Mar 2015 at 5:56

• Changed state: Done

[GoogleCodeExporter]

for reporting user: 

-User should call UserInterface::showUserProfileInfoToUser
-User should call UserInterface::showUserReportOptionsToUser()
-User should call UserInterface::userReportedUser()
-UserInterface should call System::AddReportToUser()

Original comment by mustafat...@gmail.com on 23 Mar 2015 at 2:12