1.

Introduction

1.1 Project Profile

Title Description

Project Title Blog Management System

This Website is Used for Creation and Manage
Project Description
the blog
Project Type: Software Development

Type of Application Web-Based Application

Front End Tool HTML,Notepad++,JAVASCRIPT

Back End Tool PYTHON,PHP, MySQL

Language and Platform HTML AND PYTHON

Operating System Windows 10

Duration 4 Months

Miss Mohini U. Patel

Guided By
1. Agrawal Vishal A.[22BCA04]
Developed By
2. Ahir Hetanshi J.[22BCA07]

1|Page
 2. Proposed system

2.1 Introduction

In Traditional time Before Blog Management Systems, Blogging was a

more manual and technically demanding process. Bloggers typically had to
create and manage their blogs using basic web development tools and coding.
 Manual HTML coding

 Lack of User-Friendly Tools

 Content Organization Challenges

 Etc more.

Before Blog Management Systems, Blogging was more challenging,

especially for non-technical individuals, as it required a deeper understanding of
web development and a greater investment of time and effort to manage and
maintain a blog.

The introduction of Blog Management Systems significantly simplified

and democratized the blogging process. In a digital world bursting with ideas and
information, the Blog Management System is your trusted ally for simplifying
the art of blogging. Imagine a toolbox filled with easy-to-use gadgets that help
you write, organize, and share your thoughts effortlessly.

Blogging has become an essential way to express yourself, share

knowledge, or promote your business. But juggling words, pictures, and
comments can be tricky. That's where the Blog Management System steps in.

2|Page
 With this system, you'll have a friendly editor to create and edit blog posts,
smart tools to sort and tag your articles, and a handy comment manager to
engage with your readers. Plus, it offers insights into how well your blog is
doing, helping you refine your content strategy.

Think of it as your blogging sidekick, simplifying the tetchy stuff so you

can focus on what you do best: writing and connecting with your audience.

2.2 Objective
The objective of the Blog Management System is to provide an
easy-to-use platform for bloggers to create, organize, and share their
content effortlessly. It aims to simplify content management, foster
reader engagement, and offer insights into blog performance, all while
allowing for customization and adaptability to evolving blogging needs.
The primary goal is to empower bloggers by handling technical
complexities, so they can focus on crafting quality content and
connecting with their audience.
2.3 Scope

The scope of the Blog Management System encompasses a wide

array of features and functionalities to streamline the entire blogging
process.
It includes user-friendly content creation and editing tools,
categorization and tagging systems for effective content organization,
robust comment management capabilities to enhance reader engagement,
and analytics to provide bloggers with valuable insights into their blog's
performance.
Additionally, the system offers customization options for blog
appearance and branding, ensuring a unique and tailored online presence.

3|Page
 Its scope also extends to accessibility, security, and scalability, enabling
bloggers to reach their audience across devices, protect user data, and
accommodate growing content demands.
The system is designed to anticipate and embrace future
enhancements, making it adaptable to emerging blogging trends and
technologies. Ultimately, its scope is to empower bloggers to excel in the
digital by simplifying technical aspects and promoting content creation
and connection.
2.4 Constraints
2.4.1 Hardware Constraints:
Processing Power:
 The system's performance depends on the processing power of the
server where the blog is hosted.
 High traffic blogs require powerful processors to handle simultaneous
requests efficiently.

Memory (RAM):
 Sufficient RAM is necessary for smooth operation.
 Large blogs with multimedia content need more memory to handle
media uploads and streaming.

Storage Space:
 Blogs with extensive media libraries require significant storage space.
 Regular backups and database storage also demand substantial disk
space.

Network Bandwidth:
 Adequate bandwidth is crucial for fast loading of blog pages,
especially if the blog contains high-resolution images or videos.

4|Page
  Limited bandwidth can result in slow page loading times, leading to
a poor user experience.

Redundancy and Failover:

 Implementing redundancy and failover mechanisms require
additional hardware resources.
 Redundant servers and network devices ensure the blog remains
accessible even if one server fails.

2.4.2 Software Constraints:

Operating System Compatibility:
 The blog software must be compatible with the server's operating
dsystem.
 Some blogging platforms are designed specifically for Linux,
Windows, or other operating systems.

Web Server Compatibility:

 The blog software should be compatible with the web server software.
 Web server configuration impacts the blog's performance and security.

Database Management System (DBMS):

 Compatibility with specific DBMS (e.g., MySQL, PostgreSQL) is
essential.
 Database constraints include maximum connections, table size limits, and
query execution time.

Browser Compatibility:
 The blog's frontend (user interface) must be compatible with popular web
browsers (e.g., Chrome, Firefox, Safari).
 Different browsers interpret HTML, CSS, and JavaScript code differently,
leading to potential display issues.

5|Page
 Security Software:
 Security plugins, firewalls, and anti-malware software add an extra layer
of protection but may consume server resources.
 Software-based security solutions should be optimized to avoid excessive
resource usage.

2.4 Advantages:

1. User-Friendly Content Creation:

Bloggers can create and publish content easily using intuitive,

WYSIWYG (What You See Is What You Get) editors, reducing the
need for technical expertise in web development.

2. Efficient Organization:
Built-in categorization and tagging tools make it simple to organize
and structure blog posts, enhancing content discoverability and
navigation for readers.

3. Engagement and Interaction:

Robust comment management features facilitate reader

engagement, allowing bloggers to moderate comments, respond to
readers, and build a community around their content.
4. Customization:

Bloggers can personalize the appearance of their blogs with

themes, layouts, and branding options, creating a unique online
identity.
6|Page
 5. Accessibility:

Responsive design ensures that blogs are accessible across

various devices and screen sizes, improving the user experience for
readers on smart phones, tablets, and desktops.

6. Security:

Many Blog Management Systems offer built-in security

features and updates to protect against common threats, reducing
the risk of hacks and data breaches.

7|Page
 3. Environment Specification

3.1 Hardware and Software Requirement

Hardware Requirement
The efficient hardware and software configuration requires to run the
system is as suggest below. The configuration suggested is for better
performance. Same functionality or higher configuration will always better.

Admin Tools
Software
Operating system Windows
Database MySQL
Memory 4 GB
Hard Disk 50 GB

User Tools
Software
Operating system Any Operating System with Internet
Database MySQL

Software Requirement
Mozila Firefox
Google Chrome
Notepad++

8|Page
 3.2 Development Description

Front-end: HTML, Notepad++ , Javascript

Back-end: MYSQL,PHP,Python

 Notepad++
Notepad++ is a popular open-source text editor and source code editor
for Windows. It has a wide range of features that make it a preferred choice
for developers and programmers. Here are some key aspects and features of
Notepad++:

Features:
Syntax Highlighting: Notepad++ supports syntax highlighting for various
programming languages, making it easier to read and understand code.

Auto-Completion: It provides auto-completion for words and functions,

which saves time and reduces typing errors.

Multiple Tabs: You can work on multiple files simultaneously using tabs,
allowing easy switching between different documents.

Multi-Language Support: Notepad++ supports multiple languages and

allows you to switch the interface language.

Search and Replace: Advanced search and replace functionality with regular
expression support.

Customizability: Users can customize the editor's appearance, including

themes, fonts, and language settings.

File Comparison: It has a file comparison feature that allows you to compare
two different versions of a file and highlights the differences.

Macro Recording: Notepad++ allows you to record and play macros,

automating repetitive tasks.

9|Page
 Lightweight: Notepad++ is lightweight and fast, making it ideal for quick
editing tasks and programming.

 PHP:

PHP, originally known as Personal Home Page, now stands for

Hypertext Preprocessor. It is a versatile, server-side scripting language
primarily used for web development. PHP is embedded within HTML code
and executed on the web server, generating dynamic web content. This means
that PHP scripts run before the HTML is loaded, allowing developers to
create interactive, data-driven websites.
PHP was created in 1994 by Rasmus Lerdorf as a set of Common
Gateway Interface (CGI) binaries written in the C programming language. Over
the years, it evolved into a powerful scripting language with a vast ecosystem of
tools and frameworks. The PHP Group, an open-source community, manages its
development, ensuring continuous updates and improvements.

Features:
Performance:

 PHP script is executed much faster than those scripts which are written in
other languages such as JSP and ASP. PHP uses its own memory, so the
server workload and loading time is automatically reduced, which results
in faster processing speed and better performance.

Open Source:

 PHP source code and software are freely available on the web. You can
develop all the versions of PHP according to your requirement without
paying any cost. All its components are free to download and use.

10 | P a g e
Familiarity with syntax:

 PHP has easily understandable syntax. Programmers are comfortable

coding with it.

Embedded:

 PHP code can be easily embedded within HTML tags and script.

Platform Independent:

 PHP is available for WINDOWS, MAC, LINUX & UNIX operating

system. A PHP application developed in one OS can be easily executed in
other OS also.

Database Support:

 PHP supports all the leading databases such as MySQL, SQLite, ODBC,
etc.

Error Reporting -

 PHP has predefined error reporting constants to generate an error notice or

warning at runtime. E.g., E_ERROR, E_WARNING, E_STRICT,
E_PARSE.

Loosely Typed Language:

PHP allows us to use a variable without declaring its datatype. It will be taken
automatically at the time of execution based on the type of data it contains on its
value. Web servers Support:

 PHP is compatible with almost all local servers used today like Apache,
Netscape, Microsoft IIS, etc.

11 | P a g e
Control:

 Different programming languages require long script or code, whereas

PHP can do the same work in a few lines of code. It has maximum
control over the websites like you can make changes easily whenever
you want.
 MySQL:

MySQL is an open-source relational database

management system (RDBMS). Its name is a combination of "My", the name of
co-founder Michael Widenius' daughter, and "SQL", the abbreviation for
Structured Query Language. The MySQL development project has made its
source code available under the terms of the GNU General Public License, as
well as under a variety of proprietary agreements. MySQL was owned and
sponsored by a single for-profit firm, the Swedish company MySQL AB, now
owned by Oracle Corporation. For proprietary use, several paid editions are
available, and offer additional functionality.

MYSQL architecture with pluggable storage engines.

MYSQL is a database server
MYSQL is ideal for both small and large application.
MYSQL compiles on a number of platforms
MYSQL is free to download and use

12 | P a g e
 4. System Planning

4.1 Feasibility Study

The main purpose of feasibility analysis is to check the economic
capability of the proposed system. The result of Feasibility study will indicate
whether to proceed to the feasibility study are positive, then we can proceed to
developed a system otherwise project should be purchased. The Feasibility study
include three option.

Technical Feasibility:

 Institute has hardware and software to fulfill the requirement of the

project and they have no obstacle whether economic or otherwise
toward spending on hardware or software. Capacity of hardware is
sufficient system is full proof and user friendly. On-line help,
message, error handling is own. The system is flexible.

Economic Feasibility

 The proposed system requires less cost of hardware and software

Time and cost involved in repeated auditing and verification of
records in manual system can be avoided if the system is
computerized, so this is also feasible economically.

Operational Feasibility:

 The new system can be beneficial only if it satisfies the

organization requirements; in such a way that resource utilization
and optimum outcome is justified. A new system should not only be
robust but should also be able to work simultaneously with other
systems. Operational feasibility means that new system should not
13 | P a g e
 affect any existing system during the development phase or even in
the implementation phase.

The proposed system made best efforts in achieving necessary

function and performance, as required by the user and keeping in mind
some infrastructure constraints.

4.2 Software Engineering Model

Software engineering is the discipline whose aim is:

 Production of quality software

 Software that is delivered on time
 Cost within the budget
 Satisfies all requirements

A software life cycle is the series of identifiable stages that a software

product undergoes during its lifetime. A software lifecycle model is a
descriptive and diagrammatic representation of the software life cycle.
A life cycle model represents all the activities required to make a
software product transit through its lifecycle phases. I t also captures the
order in which these activities are to be taken. There are various life
cycle models to improve the software processes.

 Waterfall model
 Prototype model
 Spiral model

14 | P a g e
Prototype Model

 Since in this methodology a working model of the system is provided, the

users get a better understanding of the system being developed.
 Errors can be detected much earlier.
 Quicker user feedback is available leading to better solutions.
Missing functionality can be identified easily.

4.3 Risk Analysis

Risk analysis in a Blog Management System involves identifying
potential risks, evaluating their impact, and devising strategies to mitigate
or manage these risks effectively.
1. Security Risks:
Risk: Unauthorized access, data breaches, SQL injections, cross-site
scripting attacks.
Mitigation: Implement secure coding practices, use parameterized queries
to prevent SQL injections, employ HTTPS for data transmission, conduct
regular security audits, and employ firewalls and intrusion detection
systems.
2. Data Loss:
Risk: Accidental deletion of posts or user data, database corruption.
Mitigation: Implement regular automated backups, store backups in
secure off-site locations, and test the backup and restore procedures
periodically.
3. Performance Issues:
Risk: Slow loading times, server crashes under heavy traffic.
Mitigation: Optimize database queries, use caching mechanisms, employ
Content Delivery Networks (CDNs), and choose a reliable hosting
provider capable of handling the expected traffic.

15 | P a g e
 4. Content Quality and Moderation:
Risk: Inappropriate or offensive content, spam comments.
Mitigation: Implement content moderation features, use algorithms and
keyword filters to detect and filter inappropriate content, and allow users
to report suspicious activities.

4.4 Project Schedule

4.4.1 Task Dependency
4.4.2 Time-line Chart
4.4.3 Project Table

4.4.2 Time Line Chart

Task Month1 Month2 Month3 Month4

1) Requirement analysis
Collected requirement from our
Analyze gathered information
Determine scope of the system
Milestone: req. Analysis
2) Planning and risk analysis
Analyze data for possible risks
Identify technical risks
Determine different modules
Milestone: Planning completed
3) Designing
Design basic interface of the site
Design database tables
Design web form for modules
Milestone: designing completed
4) Coding and integrating
Implement logic for different
Implement database connectivity
Integrate different modules
Implement Report
Milestone: coding completed
5) testing
Validate input control and check
Milestone: testing in progress
6) Documentation
Milestone: testing completed

16 | P a g e
 5. System Analysis
5.1 Detailed SRS

This system content some components which make r\the current system
able to provide the better facility than the existing one .
3.1 User Registration and Authentication
Specify the requirements for user registration, login, and authentication,
including password policies and security measures.
3.2 User Roles and Permissions
Define the different user roles (e.g., admin, blogger, reader) and their associated
permissions and access levels.
3.3 Blog Post Management
Detail the functionality for creating, editing, and deleting blog posts, including
formatting options and media upload capabilities.
3.4 Category Management
Describe how categories for blog posts can be created, edited, and organized,
and explain how posts are associated with categories.
3.5 Comment System
Specify how comments can be posted, moderated, and managed by both users
and administrators.
3.6 User Profile Management
Outline the features related to managing user profiles, including user avatars,
bios, and account settings.
3.7 Search and Filtering
Describe the search and filtering options available to users for discovering blog
posts based on keywords, categories, and dates.

17 | P a g e
5.2 UML Diagram

5.2.1 Use Case Diagram

Symbol Symbol Name Symbol Description

Actor An actor is a person, group, or system

that interacts with the use case.

The actor symbol represents a textual

Admin
explanation of the actor that is created in
a document independently from a
diagram.

Association A relationship between two elements in

the diagram.

Associations between actors and use

cases and represented by a solid line.

System Boundary The system boundary separates a system

System from actors and other systems.

To add elements to a system, create them

outside the boundary, and then drag them
into the boundary.

18 | P a g e
  Use case for Admin

 Use case for USER

19 | P a g e
5.2.2 Activity Diagram
 Activity diagram is basically a flow chart to represent the flow form one
activity to another activity. The activity can be described as an operation
of the system.
 Purpose:
o Activity diagram use for to represent flow of function.

Symbol Symbol Name Symbol Description

Black circle A black circle is the standard notation

for an initial state before an activity
takes place.

It can either stand alone or you can

use a note to further elucidate the
starting point.

Activity The activity symbols are the basic

building blocks of an activity diagram
and usually have a short description
of the activity they represent.
State 1

20 | P a g e
 Join A join combines two concurrent
activities back into a flow where only
one activity is happening at a time.

Arrows Arrows represent the direction flow

of the flow chart.

The arrow points in the direction of

progressing activities.

Fork splits A fork splits one activity flow into

two concurrent activities.

Diamond A marker shaped like a diamond is

the standard symbol for a decision.

There are always at least two paths

coming out of a decision and the
condition text lets you know which
options are mutually exclusive.

21 | P a g e
 Black circle The black circle that looks like a
selected radio button is the UML
symbol for the end state of an a
activity.

As shown in two examples above,

notes can also be used to explain an
end state.

 Activity Diagram for Admin

22 | P a g e
  Activity diagram for Login

23 | P a g e
  Activity
vity Diagram for Blog Management System

24 | P a g e
 5.3 E-R Diagram

25 | P a g e
 6. System Design

6.1 Database Design

1. Login

Name Login

Alias Name login_master

Where and How to This System is used for Stored Username, Password
Use and Type for different kind of Users of the System.
Description Id, username, password, type

Column Type Null Primary Key Foreign

Key
Id int(15) No Yes

Username varchar(20) No

Password varchar(20) No

Type varchar(20) No

2. USER

Name User
Alias Name User_mstr
Where and How This table is used to store details of Staff
to use or Faculty.

User_id,User_fname,User_lname,email_id,photo,passw
Description ord,forget_password,user_type,recovery_email,mobile_
no.

26 | P a g e
Column Type Null Primary Key Foreign Key

User_id int(3) No Yes

User_fname Varchar(50) No

User_lname Varchar(50) No

User_email Varchar(100) No

User_type Varchar(100) No

Photo Varchar(500) No

Recovery_email Varchar(500) No

Password Varchar(255) No

userType Varchar(255) No

3. Blog Manage

Name Blog_manage

Alias Name Tblblog

This table is used to store blog which is writtern by
Where and How to use
user.
Description User_id,name,password

Column Type Null Primary Key Foreign Key

user_Id int(3) No Yes

user_Name Varchar(50) No

Password Varchar(50) No

27 | P a g e
 7. Testing
Software Testing:

Testing means (the aim of the testing process is) to identify all defects in
the existing in a developed software. This software can be tested in many ways,

Testing a Blog Management System is crucial to ensure its functionality,

security, and user experience meet the desired standards. Here’s how you can
approach testing the system effectively:

1. Unit Testing
1. User Authentication:
a. Test user registration process.
b. Test user login and logout functionality.
c. Verify password encryption and storage.
2. Post Management:
a. Test creating a new post with valid and invalid data.
b. Test editing and deleting posts.
c. Ensure proper categorization of posts.
3. Comment System:
a. Test adding comments to posts.
b. Test comment moderation features (approve, edit, delete).

2. Integration Testing
1. User Roles and Permissions:
a. Test that different user roles (admin, editor, visitor) have
appropriate access levels.
b. Ensure admins can moderate posts and comments
effectively.
2. Post-Comment Interaction:
a. Test that comments are correctly associated with the
respective posts.
b. Ensure deleted posts do not display comments.

28 | P a g e
 3. Functional Testing

1. User Interface:
a. Test the user interface for responsiveness and compatibility
with various devices and browsers.
b. Verify all buttons, links, and forms work as intended.
2. Search Functionality:
a. Test the search feature with different keywords and phrases.
b. Verify search results are accurate and relevant.
3. Security:
a. Test for vulnerabilities such as SQL injection, cross-site
scripting (XSS), and CSRF attacks.
b. Verify data privacy and ensure sensitive user information is
properly encrypted.

4. Performance Testing
1. Load Testing:
a. Simulate a high number of concurrent users accessing the
system.
b. Monitor server response time and system behavior under heavy
load.
2. Scalability Testing:
a. Test the system's ability to handle a growing amount of data,
posts, and users.

6. Security Testing
1. Authentication and Authorization:
a. Test login/logout functionality thoroughly.
b. Verify that unauthorized users cannot access restricted
features.
2. Data Security:
a. Ensure user data is stored securely and is not accessible without
proper authentication.
b. Test for data leakage vulnerabilities.

29 | P a g e
 8. Future Enhancement

In the future, Blog Management Systems are likely to undergo

significant enhancements. These advancements may include the integration of
sophisticated AI algorithms, enabling features like real-time collaborative
editing, personalized content recommendations, and automated content
moderation. Additionally, there could be a focus on community building, with
interactive elements such as discussion forums, blogging challenges, and user
profiles, fostering a sense of belonging among bloggers and readers.
Monetization options might expand through seamless ad integration and
subscription models. Enhanced security measures, like two-factor
authentication and AI-powered moderation, will bolster user safety.
Furthermore, the user experience will be enriched with mobile applications,
custom themes, and intuitive rich text editors. These enhancements
collectively aim to create a vibrant, secure, and user-friendly environment,
catering to the evolving needs of bloggers and readers alike.

9. References

o https://in.pinterest.com/pin/blog-database-er-diagram--
297870962864404617/
o https://online.visual-paradigm.com/diagrams/templates/entity-relationship-
diagram/
o Old documentation paper

30 | P a g e