Scribd
Upload
12 views14 pages

Social Networking Site Design Overview

This design document outlines the structure and specifications for a social networking site called Vibez, detailing its purpose, scope, and system architecture. It includes modular designs for user registration, profile management, and administrative functions, as well as data flow, use case, and sequence diagrams to illustrate system interactions. Additionally, it provides an overview of the database architecture and entity relationship diagrams to support the project's implementation.

Uploaded by

sumanth7021
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
12 views14 pages

Social Networking Site Design Overview

This design document outlines the structure and specifications for a social networking site called Vibez, detailing its purpose, scope, and system architecture. It includes modular designs for user registration, profile management, and administrative functions, as well as data flow, use case, and sequence diagrams to illustrate system interactions. Additionally, it provides an overview of the database architecture and entity relationship diagrams to support the project's implementation.

Uploaded by

sumanth7021
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

DESIGN DOCUMENTATION

for

SOCIAL NETWORKING
SITE

Version 1.0

Prepared by :
1. Ria (190001051)
[Link] Kumar (190001038)
[Link] Patel (190001034)
[Link] Sruthi (190001047)

Submitted to : Anup Kumar Gupta

May 7, 2021

1
Contents
1 Introduction 3
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Design Specifications 4
2.1 Modular design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 System Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.1 Data Flow Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2.2 Use Case Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2.3 Sequence Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2.4 Data Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.5 Entity Relationship Diagram . . . . . . . . . . . . . . . . . . . . . 13

2
1 Introduction
1.1 Purpose
This design document is intended to give the overview of implementation of the project
(Vibez) at a high level. It also identifies the framework and technologies used for the
development and tries to define the system architecture. This document will also be
used for identifying contradictions, if any, prior to coding phase. The main goal of this
document is to make design level information easily understandable

1.2 Scope
This design document is meant to provide an overview of the structure of the system.
This document also includes the database architecture of Aloha along with database
diagram for reference. This document also serves as a mandate for the design standards,
data structures and design patterns to be implemented. UML diagrams are included to
show how they different components interact with each other.

1.3 Overview
The remaining document has 2 more sections. The second section gives overall view
design view of the project. It includes data flow diagram, use case diagram, sequence
diagrams, data base explanation and entity relationship diagram. They give a deep
understanding of the overall project design.

3
2 Design Specifications
2.1 Modular design
The application comprises the following major modules

Register to be a member Module


This module provides functionalities for those people who wants to open an account.
Applicants can post their views with personal and professional details. They can also
update the profile as frequently as required. The member can also browse through the
friends profile available. Members can also get message alerts when their friends message
them.

Profile Module
This module provides functionalities related to members profile. Logged users can see
their details and if they wish to change any of their information they can edit it.

Admin Module
This module provides administrator related functionalities. Administrator manages en-
tire application and maintains the profiles of all the registered users and their activities.

2.2 System Design


2.2.1 Data Flow Diagrams
Data flow diagrams model the flow of data into, through, and out of an information
system:
• Show the processes that change or transform data
• Show the movement of data between processes
• Represent a system as a network of processes which transform data flowing between
them
The user screen flow shows what a user of the community will see. After successfully
logging on, the user will be given various links (such as search users, see posts, view
messages, etc.), and be able to select options from there, or go back to their home.

4
Figure 2.1: Data Flow Diagram

2.2.2 Use Case Diagrams


A use case diagram is a graphic depiction of the interactions among the elements of a
system. A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. In this context, the term ”system” refers to something
being developed or operated, such as a mail-order product sales and service Web site. Use
case diagrams are employed in UML (Unified Modeling Language), a standard notation
for the modeling of real-world objects and systems.
A use case diagram contains four components. The boundary, which defines the system
of interest in relation to the world around it.

• The actors, usually individuals involved with the system defined according to their
roles.

• The use cases, which are the specific roles played by the actors within and around
the system.

• The relationships between and among the actors and the use cases.

The main actors of the social networking site in the below use case diagram are : users
and admin. They perform various use cases like login, registration, manage account,
post, chat etc

5
Figure 2.2: Use Case Diagram

6
2.2.3 Sequence Diagrams
Registration
Figure 2.3

Figure 2.3: Sequence Diagram for user signup

Login
Figure 2.4

7
Figure 2.4: Sequence Diagram for user login

Manage account
Figure 2.5

8
Figure 2.5: Sequence Diagram for account updating

9
Search Friend and list
Figure 2.6

Figure 2.6: Sequence Diagram for searching and adding friends

Post
Figure 2.7

10
Figure 2.7: Sequence Diagram for post

Comment
Figure 2.10

Figure 2.8: Sequence Diagram for comment

Chat
Figure 2.9

11
Figure 2.9: Sequence Diagram for chatting

2.2.4 Data Base


Database Data base is used to store the relevant information of the individuals. A
database is a collection of rows and columns in which rows indicates the tuple and
column indicates the domain of table. Database design is the process of producing a
detailed data model of a database. The data base for this project contains following
tables with the given attributes:

Users table
user id email password profile id timestamp

Profile table
user id name gender about dob place phoneNo. interests

Posts table
post id user id caption pic id video id

12
Likes table
like id post id user id

comments table
comment id post id user id comment reply id

comments replies table


comment id prevcomment id post id user id comment reply id

friends table
user1 id user2 id timestamp

Requests table
user1 id user2 id status timestamp

2.2.5 Entity Relationship Diagram


ENTITY RELATIONSHIP DIAGRAM The entity relationship model is a high level
data model. It is based on a perception of a real world that consists of a collection of
basic objects, called entities, and of relationship among these objects. It was developed
to facilitate database design by allowing specification of an enterprise schema, which
represent the overall logical structure of a database.

13
Figure 2.10: ER Diagram

14

Common questions

Powered by AI

The design documentation ensures that all developers have a unified understanding of the site's architecture by clearly defining the purpose, scope, and structure of the system . It includes comprehensive diagrams like data flow, use case, and ER diagrams that visually map out system processes and components, facilitating clear communication and alignment among the development team . This reduces ambiguity and enhances coordination in the development process.

Data flow diagrams and use case diagrams are crucial for understanding the design of the social networking site. Data flow diagrams map the flow of data into, through, and out of the system, showing processes and data movements . Use case diagrams depict interactions among system elements, clarifying the roles of actors and their relationships with the system . Together, they provide a comprehensive view of system processes and user interactions.

Sequence diagrams in the development process illustrate how objects interact in a particular sequence, detailing the order of operations over time for use cases such as user signup, login, and posting . They differ from data flow diagrams, which focus on the movement of data within the system and between processes, highlighting data transformations rather than the temporal sequence of interactions .

In the Admin Module of the social networking site, the administrator has functionalities related to managing the entire application and maintaining the profiles of all registered users and their activities . This role differs from regular users, who primarily engage in user-centric activities like registering, updating profiles, adding friends, posting, and messaging .

Design standards and design patterns play a pivotal role in developing the social networking site by ensuring a consistent approach to design and implementation, aiding in code reuse, and improving system robustness and maintainability . They provide a structured framework that guides the development process, allowing for efficient problem-solving and communication across the development team.

The system's architecture as outlined in the design document addresses scalability and future expansion through its modular design, which allows for individual modules such as user registration and profile management to be independently updated or expanded . The separation of concerns in database architecture also supports scalability, as it allows for optimized data handling and integration of additional functionalities without compromising system performance.

Including an Entity Relationship Diagram (ERD) in the design documentation is important as it visually represents the database's logical structure. ERDs help in identifying entities, their attributes, and the relationships between them, facilitating better database design and ensuring that all data relationships are properly mapped and understood . This aids in maintaining data integrity and streamlining database management and query optimization.

A well-defined database architecture is crucial for the functionality of the social networking site as it ensures efficient data storage, retrieval, and management. The database contains tables like Users, Profile, Posts, Likes, Comments, and Friends, each with specific attributes essential for user engagement and data integrity . This architecture supports complex queries and interactions, enabling smooth user experience and optimized performance.

The Use Case Diagram illustrates the functionality of the social networking site by depicting the main actors, which include users and admins, and their interactions with use cases like login, registration, post, and chat . It organizes system requirements into relevant roles played by actors and their relationships, clarifying how different elements of the system function together to fulfill user and administrative objectives.

The modular design of the social networking site includes modules like Register to be a member, Profile, and Admin Module . Modularity is significant because it allows for separation of concerns, making the system easier to manage and understand. Each module focuses on specific functionalities, such as user interaction or administration, which aids in maintainability and scalability.

You might also like