Design Specifications for a Social Networking System: 8th Dimension, Essays (university) of Abnormal Psychology

Download Design Specifications for a Social Networking System: 8th Dimension and more Essays (university) Abnormal Psychology in PDF only on Docsity!

Design Specifications for Social Networking

System

8th Dimension

May 11, 2004

Marcos Boyington, Po Chen, Grace Kum, Van Le-Pham, Eric Morales, Jake Warmerdam, Cheuk (Anna) Yu, Jingren Zhou

Contents

• 1 Project Summary
• 2 Sample User Interfaces
  • 2.1 Community Generation Sample Interface
  • 2.2 User Information Sample Interface
  • 2.3 View Message Boards Sample Interface
  • 2.4 View Messages Sample Interface
• 3 Screen flow
• 4 Project Class Diagram
• 5 Packages
• 6 Deployment
• 7 Communication Diagrams
  • 1 Community Generation Sample Interface List of Figures
  • 2 User Information Sample Interface
  • 3 View Message Boards Sample Interface
  • 4 View Messages Sample Interface
  • 5 Client Screen Flow
  • 6 User Screen Flow
  • 7 Project Class Diagram
  • 8 Project Package Diagram
  • 9 Project Deployment Diagram
  • 10 Use Case 1 communication diagram
  • 11 Use Case 3 communication diagram
  • 12 Use Case 4 communication diagram
  • 13 Use Case 5 communication diagram
  • 14 Use Case 6 communication diagram
  • 15 Use Case 7 communication diagram
  • 16 Use Case 8 communication diagram
  • 17 Use Case 9 communication diagram
  • 18 Use Case 10 communication diagram
  • 19 Use Case 11 communication diagram
  • 20 Use Case 12 communication diagram
  • 21 Use Case 13 communication diagram
  • 22 Use Case 14 communication diagram
  • 23 Use Case 15 communication diagram
  • 24 Use Case 16 communication diagram

Figure 1: Community Generation Sample Interface

2.2 User Information Sample Interface

Once a community is generated, users will be able to access it much the same as other social networks. Below we have a sample image of what a user infor- mation page may look like. Only public attributes (which were chosen by the administrator) will be viewable by other users.

Figure 2: User Information Sample Interface

2.3 View Message Boards Sample Interface

A user can join existing message boards, or create their own. Here they are given a list of all available message boards, which will likely be produced from some sort of search. The user can then go to that message board and ask the owner permission to join.

Figure 4: View Messages Sample Interface

3 Screen flow

The client screen flow shows an overview of the pages a client wanting to update their existing community or create a new one will see. After successfully setting up the community options, the client is given the option to either download the community or ”test” it. The user screen flow shows what a user of the community will see. After suc- cessfully logging on, the user will be given various links (such as search users, search boards, view mail, etc.), and be able to select options from there, or go back to their home.

Figure 5: Client Screen Flow

4 Project Class Diagram

Figure 7: Project Class Diagram

The class diagram consists of four primary objects: The social network gen- erator, the social network system, the user, and the message board. The person and client objects are also important, but they are actors, and will not actually be implemented in the system. The social network generator is the interface that the client will use to generate their social network, or community. The social network system, or community, is what users will register and log on to to communicate and socialize with other users and use the many features of the social network system. The user object is the actual user information stored on the database. It is responsible for all abstract action requested by the person using the social net- work system. It includes all information submitted when the user registered, along with various functions to load this information and interact with the rest of the system. This object will also include the user’s mailboxes, which will in turn include the user’s messages. The message board object is the object responsible for all message board func- tionality. This includes all the messages belonging to the board, along with functionality to create new ones, view existing ones, join the board, create a new board, etc.

Figure 9: Project Deployment Diagram

7 Communication Diagrams

Some communication diagrams for relevant use cases are given.

1. Site options - Administrator can select the options about the site that he/she wants to generate, and select where the database is going to be store. So, the database will only store the options that the administrator selected. Some of the options are default that the website will automat- ically include such as firstname, lastname, password and email etc. So basically, the design of the website will be generate by the ”option site” which controls by the administrator.

Figure 10: Use Case 1 communication diagram

2. Site Generation - After the administrator selected all the options, the sys- tem must generate a website base on the options that he/she selected. The system will make the website available for the administrator to download. Then a website will be generated for the administrator to use.
3. Download generated site - Administrator must download the generated site to their local machine after all the configuration is done in order to get the site running. We will provide instructions of how to run the website for the administrator, most likely an instruction page.

Figure 11: Use Case 3 communication diagram

7. Login - The system will ask the user for his username and password. It will then check if the entered info is correct. If it’s so, the system will let the user log on into the system. Otherwise, it keeps asking the user either to enter the info again until it’s correct or go to ”Forgot Password” page (use

case 23) to achieve the password.

Figure 15: Use Case 7 communication diagram

8. View Personal Page - After the user logs on, he will go to his personal page. He also can view portion of message board (messages posted on current day) and portion of his profile. The system will also let him modify his profile if he wants to.

Figure 16: Use Case 8 communication diagram

9. Search Users - System allows a user to search for another user. System will ask the user for first name, last name, and/or other fields (Specified by the admin) of the person that he wants to search for. If matches are found, system will display a list of matching users.

Figure 17: Use Case 9 communication diagram

10. List All Users - If a user wants to see the list of all users, the system will ask him for options to display the list of users.

Figure 18: Use Case 10 communication diagram

11. View Other User’s Page - The User can see the info of other users. the user can only view what is allowed depending on what the permission is set to. Also, if it is allowed the user is also able the see the persons picture.

Figure 21: Use Case 13 communication diagram

14. View Mailbox - The user can view their on mailbox. They can read messages, delete messages, reply to a message, and forward a message. They can see the info of the message, i.e. who sent it.

Figure 22: Use Case 14 communication diagram

15. Read User Message - User can read a message from the mailbox.

Figure 23: Use Case 15 communication diagram

16. List Message Boards - User can list message board by selecting type and order to list.

Figure 24: Use Case 16 communication diagram

17. Create Message Board - User can post a message board with certain mes- sage that can be viewed only by the group which has the permission from the user.