HINDUSTAN COLLEGE OF SCIENCE ANTECHNOLOGY,

FARAH, MATHURA

Session:- 2024-25

DEPARTMENT OF COMPUTER SCIENC ENGINEERING

Software Engineering Lab Report
(Subject Code: BCS 651)

Submitted By-
SUMIT KUSHWAHA
Roll no.: 2200641540020
B.Tech - CSE IIIrd Year
Section : C2
 INDEX
Sr Particular Date Signature
no.
 Software Requirement Specification
(SRS) of SOCIAL MEDIA ANALYTIC DASHBOARD
1. Introduction:
1.1 Purpose: Use the insights gathered from your analytics dashboard to drive
implement data-driven strategies to enhance your content, optimize posting
time, and engage with your audience more effectively, ensuring sustained
success.

1.2 Scope: With the growing use of social media, businesses, organizations,
and individuals rely on social media analytics to gauge their performance,
identify trends, and optimize their online presence.

1.3 Definition: Social media analytics is the process of collecting, analyzing,

and interpreting data from social media platforms to inform decision-making,
improve marketing strategies, and better understand audience behavior.

1.4 References
 Facebook Graph API Documentation

 Twitter API Documentation

 Instagram Graph API Documentation
 LinkedIn API Documentation
 https://www.w3schools.com/

1.5 Overview: A Social Media Analytics Dashboard is an invaluable tool for

businesses, marketers, and content creators looking to optimize their social
media strategies. By consolidating data from multiple platforms into a single,
easy-to-navigate interface, it allows users to monitor key performance
indicators (KPIs) such as engagement, audience insights, content
performance, and campaign
effectiveness.

2. Overall Description:
2.1 Product perspective: The Social Media Analytics Dashboard will integrate
with APIs from various social media platforms to collect data and display it
in a user-friendly manner. The dashboard will provide charts, graphs, tables,
and other visualizations to help users make data-driven decisions.

2.2 Product Functions:

The system will provide the following functions:
 Integration with multiple social media APIs (e.g., Facebook, Instagram,
Twitter, LinkedIn).
 Authentication and user management.
 Display of key metrics such as likes, shares, comments, reach, impressions,
etc.

. Audience demographics (age, gender, location, etc.).

 Content performance tracking (top posts, engagement by content type).

 Comparative analysis of different platforms.

 Customizable reports and dashboards.
 Alerts and notifications for significant changes in metrics.
 Data export to CSV/PDF.
2.3 User Characteristics:
 End Users: Marketing professionals, content creators, social media
managers who will be the primary users. They should have basic
technical proficiency in handling analytics tools.
 Admin: Administrators who manage user access and system settings.
 Developers: The technical team responsible for integrating APIs and
ensuring smooth data processing.

2.4 Compulsions:
 Data latency due to API rate limits and third-party data availability.

 User data security and privacy considerations.

 Browser compatibility issues across devices.
 Regular updates and maintenance required for platform integration as
APIs may change.

2.5 Assumptions and Dependencies:

 The system assumes that the social media platforms' APIs will provide
the necessary data.
 The platform depends on stable internet connectivity for real-time data
fetching.
 The system assumes that the end users will have authorized access to
the social media accounts they wish to track.

3. specific requirements
Hardware requirements:
Processor: Intel Core 2 Duo
Memory: 512 MB RAM Graphics: DirectX 9.0c compatible video card 512MB.
DirectX: Version 9.0
Software platforms:
Power BI

Excel

3.1 Appendices
 Engagement: Interactions such as likes, shares, comments, and
reactions.
 Reach: The number of unique users who have seen a post.
 Impressions: The total number of times a post has been displayed.
1. Introduction
1.1 Purpose

The purpose of the Notes Management System is to provide users with a convenient,
secure, and efficient platform for creating, organizing, and managing their notes. This system
aims to eliminate the hassle of traditional note-taking methods by offering a digital solution
that ensures accessibility, organization, and data security.
1.2 Scope

The Notes Management System is a web-based application designed to help users

efficiently create, store, organize, and manage their notes in a structured manner. This
system provides a user-friendly and secure environment for individuals and organizations
to store important information, ideas, and reminders digitally.

1.3 Definitions

Notes Management System (NMS) – A digital application designed to help users create,
store, organize, and manage their notes efficiently.

User – An individual who interacts with the system to create, edit, store, or retrieve notes.

Authentication – The process of verifying a user’s identity before granting access to the
system.

Authorization – The process of granting specific permissions and access levels to

authenticated users.

Cloud Storage – A remote database where users' notes and related data are stored
securely for accessibility from multiple devices.

1.4 Reference Documents

IEEE 830-1998 – Software Requirements Specification (SRS) Standard

• Provides guidelines for structuring and writing an effective SRS document.

• URL: IEEE SRS Standard (If applicable, provide the actual link)

1.5 Overview

The Notes Management System (NMS) is a web-based application designed to help users
create, manage, and organize their notes efficiently. This system eliminates the need for
physical note-taking by providing a digital platform where users can store important
information securely and access it anytime, anywhere
2. Overall Description
2.1 Product Perspective

The Notes Management System (NMS) is a standalone web-based application designed to

provide users with a convenient and efficient way to create, organize, and manage their
notes. It serves as a digital alternative to traditional note-taking methods, offering enhanced
accessibility and security. The system operates independently but can integrate with cloud
storage services for data backup, authentication services for secure login, and notification
systems for reminders. It features a user- friendly web interface that allows users to create,
edit, delete, and categorize notes effortlessly. Additionally, search and filtering
functionalities enable quick retrieval of information. The system relies on a secure database
to store user data and notes while ensuring encryption for privacy. Designed to be accessible
across multiple devices, the NMS supports real-time synchronization, making it ideal for
students, professionals, and organizations. However, the system requires an internet
connection for cloud-based access and is optimized for modern web browsers. Its scalable
architecture ensures smooth performance.

2.2 Product Functions

- User Authentication & Authorization

• Secure login and registration with username, email, and password.

• Integration with third-party authentication (e.g., Google OAuth).

• Password recovery and reset options.

Notes Creation & Management

• Users can create, edit, and delete notes easily.

• Rich text editing support, including text formatting, images, and file attachments.

• Auto-save feature to prevent data loss.

Organization & Categorization

• Users can categorize notes into folders or notebooks.

• Tagging system to label and group notes for quick access.

2.3 User Characteristics

- General Users (Students, Professionals, and Individuals)

• Users with basic computer literacy who need a simple and intuitive interface for
managing notes.

• They primarily use the system for personal note-taking, task management, and
organizing study or work-related information.

2.4 Constraints

- Platform Compatibility: The application is web-based and must be compatible with

all major browsers, including Google Chrome, Mozilla Firefox, Safari, and Microsoft Edge. It
should also be optimized for use on both desktop and mobile devices.

- Performance: The web application should load within 3-5 seconds and be responsive
to different screen sizes for optimal usability on desktops, tablets, and mobile phones.

- Accessibility: The platform should comply with accessibility standards to ensure that
it is usable by people with disabilities.

2.5 Assumptions and Dependencies

- User Engagement: It is assumed that users will be motivated to take the eco-
assessment test and engage with the application regularly to track their progress and
implement recommended improvements.

- Government Policies Data: The effectiveness of the Eco-Mind Games is dependent

on the availability and accuracy of up-to-date environmental policy data from government
sources or NGOs.

- Internet Access: The application depends on users having consistent internet access
to load the web app, take the eco-assessment, receive real-time updates, and interact with
the Eco-Mind games.

3. Specific Requirements
3.1 Functional Requirements
User Authentication & Authorization

• The system shall allow users to register using an email, username, and password.

• The system shall provide login functionality with email and password authentication.

• The system shall support third-party authentication (e.g., Google OAuth).

• The system shall provide a password recovery option via email.

2. Notes Creation & Management

• The system shall allow users to create, edit, and delete notes.

• The system shall support a rich text editor for text formatting, adding images, and file
attachments.

• The system shall provide an auto-save feature to prevent data loss.

3. Organization & Categorization

• The system shall allow users to create folders or categories to organize notes.

• The system shall allow users to tag notes for easier classification.

4. Search & Filtering

• The system shall allow users to search for notes using keywords.

• The system shall provide filtering options based on date, category, and tags.

5. Cloud Storage & Synchronization

• The system shall store notes in a cloud database for multi-device access.

• The system shall provide real-time synchronization of notes.

3.2 Non-Functional Requirements

1. Performance

- Pages should load within 3-5 seconds.

2. Security

- User data, especially passwords, must be encrypted and comply with data protection
regulations (e.g., GDPR, CCPA).
3. Scalability

- The system must handle increased user traffic without performance issues.

4. Accessibility

- Compliant with WCAG 2.1 accessibility standards.

5. Compatibility

- Compatible with modern browsers (Chrome, Firefox, Safari, Edge) and mobile devices.

4. Appendices
4.1 Glossary

- Notes Management System (NMS) – A web-based application that allows users to

create, store, organize, and manage digital notes efficiently.

User – An individual who interacts with the system to create, edit, store, or retrieve notes.

Authentication – The process of verifying a user's identity before granting access to

the system.

Authorization – The process of granting specific permissions and access levels to

authenticated users.

Cloud Storage – A remote server where users' notes and related data are securely stored
for accessibility from multiple devices.

4.2 References

- IEEE 830-1998: IEEE Recommended Practice for Software Requirements Specifications.

5. Index
1.Introduction

1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 Reference Documents
1.5 Overview
2. Overall Description

2.1 Product Perspective

2.2 Product Functions
2.3 User Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 Assumptions and Dependencies

3. Specific Requirements

3.1 Functional Requirements

3.2 Non-Functional Requirements
3.3 External Interface Requirements
3.4 System Features

4. External Interface Requirements

4.1 User Interfaces

4.2 Hardware Interfaces
4.3 Software Interfaces
4.4 Communication Interfaces

5. Other Requirements

5.1 Performance Requirements

5.2 Security Requirements
5.3 Availability and Reliability Requirements
5.4 Maintainability and Supportability
5.5 Legal and Regulatory Requirements

6. Appendices

6.1 Glossary
PRACTICAL – 2 USE CASE DAIGRAM
A use case diagram is a visual representation used in Unified Modeling Language (UML) to
describe the functional requirements of a system from the user's perspective. It shows
actors (users or other systems) and their interactions with the system in terms of use cases
(functions or services). Use case diagrams help identify:
What the system should do
Who will interact with it
The relationships between users and Functionalities.

This use case diagram represents a social media platform and illustrates how three types of
actors interact with the system:
1. User: Can perform general actions such as:
Like, Report Content, Search, Create Account
Login, Logout, View Profile, Edit Profile
Post Content, Comment

Represents a typical end-user engaging with the platform.

2. Admin: Has access to higher-level functions:

Delete Content
Manage User Accounts

3. Moderator:
Moderating Content
PRACTICAL – 3 : DATA FLOW DIAGRAM (DFD)
A DFD (Data Flow Diagram) is a visual representation of how data moves through a system.

1. Data Sources (Social Media Platforms)

Icons of platforms like Facebook, Twitter, etc., indicate where raw data originates (posts,
likes, comments, followers).
These data streams enter the system at multiple input points.

2. Users and Engagement Tracking

Users interacting with posts and campaigns generate engagement metrics.
User avatars and heart icons represent likes, shares, and reactions.

3. Data Aggregation & Storage

Data is likely stored in two formats: raw (unprocessed) and cleaned/aggregated.

4. Processing Engine / Central Analytics Core

The central circular node with a graph is the analytics core.
It performs key functions like trend analysis, KPI calculations, and insights generation.

5. Visualization Dashboards
Multiple graphs and dashboard elements (bar charts, pie charts) show output for metrics
such as:

Engagement rate
Post performance
Follower growth
Sentiment analysis
This data is presented to the end-user (e.g., social media managers) via a dashboard UI.
PRACTICAL – 3:- E-R DIAGRAM:
This E-R diagram models a social media system by representing its entities, their attributes
(implicitly), and the relationships among them. Here's a breakdown of its components:

Main Entities and Relationships:

1. User
A user can publish many items.
This indicates that users are the primary creators of content on the platform.

2. Item
Central entity in the model.
Items can be commented on (one-to-many relationship with Comment).
Items are contained in either a Web Page or a Media Item.
Items are retrieved by Queries.
Items can be associated with a Collection.

3. Web Page and Media Item

These are types of content containers.
Each can contain multiple Items (many-to-many relationship).
Items are the actual content pieces users interact with.

4. Comment
Represents feedback or interaction with Items.
One Item can have many Comments.

5. Collection
A way to group related Items.
Has a many-to-many association with Items.
Also contains Queries.

6. Queries
Represent search or retrieval mechanisms for Items.
Each Query can retrieve multiple Items and vice versa.
Specialized into:
Location Query
Account Query
Keywords Query
 PRACTICAL 4:- Flow Chart:

PRACTICAL 5:- Straight Chart:

1.Flow Chart:
This is a process-oriented chart that illustrates the sequential steps a user follows while
using the software:

Start: The user opens the software.

Decision Point: The user either registers (if new) or logs in (if existing).
Log In: Once logged in, the user enters the Home Page.

From the Home Page, users can:

Access Personal Home Page:
Create a New Post
Check Post
Comment Post

View Fresh News:

Check News
Comment News

Manage Friends:
View Good Friends
Use Friends Management
Find and Add New Friends

End: The user returns to the personal home page.

Purpose: It shows the user flow and functionalities in a clear, step-by-step manner — ideal
for understanding logic and UI interaction order.

2. Straight Chart :
This is more of a component interaction or module dependency diagram. It shows how
different modules of the social media platform are interconnected.
Starts with User Interface.
Users can either Login or Signup.
Once inside, they are directed to the Dashboard or Onboarding.
From there, the user can:
Create Post → Publish Post
View Posts → View Post Details
Connect Accounts

Purpose: It is used to represent system architecture or software module relationships, and

it helps developers understand how different parts of the application interact.