Page 1 of 28

Blog Portal

Project Submitted in Partial Fulfillment of the

Requirement for the Award of the Degree of
Master of Computer Applications

Semester IV
Jan - May, 2024

Under the guidance of Submitted By

Dr. Praveen Gupta Mohammad Ramzan (222010010)

Centre For Distance and Online Education

Devi Ahilya Vishwavidyalaya, Indore, M.P.
2024
 Page 2 of 28

Centre For Distance and Online Education

Devi Ahilya Vishwavidyalaya, Indore, M.P.

DECLARATION

I hereby declare that the project titled “Blog Portal” submitted by me for the partial
fulfillment of the requirement for the award of Master of Computer Applications (ODL) to
Centre For Distance and Online Education, Devi Ahilya Vishwavidyalaya, Indore, comprises
my own work and due acknowledgment has been made in the text to all other material used.

Signature of Student:

Date:

Place:
 Page 3 of 28

Centre For Distance and Online Education

Devi Ahilya Vishwavidyalaya, Indore, M.P.

CERTIFICATE FROM GUIDE

It is to certify that dissertation on “Blog Portal”, submitted by Mr. Mohammad Ramzan to the
Centre For Distance and Online Education, DAVV, Indore has been completed under my
supervision and the work is carried out and presented in a manner required for its acceptance
in partial fulfillment for the award of the degree of Master of Computer Applications (ODL).

Project Guide
Signature:

Name:

Date:
 Page 4 of 28

Centre For Distance and Online Education

Devi Ahilya Vishwavidyalaya, Indore, M.P.

CERTIFICATE

It is to certify that we have examined the dissertation on “Blog Portal”, submitted by Mr.
Mohammad Ramzan to the Centre For Distance and Online Education, DAVV, Indore and
hereby accord our approval of it as a study carried out and presented in a manner required for
its acceptance in partial fulfillment for the award of the degree of Master of Computer
Applications (ODL).

Internal Examiner External Examiner

Signature: Signature:

Name : Name :

Date : Date :
 Page 5 of 28

Centre For Distance and Online Education

Devi Ahilya Vishwavidyalaya, Indore, (M.P.)

ACKNOWLEDGEMENT

I acknowledge our sincere thanks to those who have contributed significantly to this project. It is a
pleasure to extend deep gratitude to our internal guided Dr. Praveen Gupta, DAVV, for his valuable
guidance and support and to continuously prompt us for the progress of the project. We thank him for
his valuable suggestion towards my project, which helped us in making this project more efficient and
user-friendly. A special mention needs to be made for Dr. Pratosh Bansal, Head of CDOE, DAVV,
and all the faculty members of CDOE, DAVV who helped very willingly as often as I wanted and
cooperated with interest.We thank and acknowledge each and everyone's efforts that helped us in some
or the other way for small and significant things

Mohammad Ramzan (222010010)

 Page 6 of 28

Centre For Distance and Online Education

Devi Ahilya Vishwavidyalaya, Indore, (M.P.)

ABSTRACT

• The Blog Portal is a web-based application intended for bloggers. The main objective
of this application is to make it interactive and its easy of use. A blog, short for weblog,
is a frequently updated web page used for personal commentary or business content.
Blogs are often interactive and include sections at the bottom of individual blog posts
where readers can leave comments. Blog Portal is a portal to share knowledge with
other User. There is two types of user roles User and Admin. User can create,edit, and
view their own blog posts, along with checking the status of each post. Additionally,
they have access to a dashboard displaying approved blog posts.Admin play a crucial
role by reviewing and approving or rejecting blog posts submitted by employees,
managing reported posts,deciding whether to ignore or delete posts if he found
inappropriate content.The main emphasis lies in providing a user-friendly search
engine for effectively showing the desired results.
 Page 7 of 28

Table of Contents
1. ACKNOWLEDGEMENT ............................................................................................... 5

2. ABSTRACT ....................................................................................................................... 6

3. INTRODUCTION..............................................................................................................9
3.1. Aim .......................................................................................................................... 9
3.2. Objectives ................................................................................................................ 9
3.3. Scope ....................................................................................................................... 9
3.4. Problem Statement .................................................................................................. 9
3.5. Purpose.................................................................................................................. 10
3.6. Methodology ......................................................................................................... 10

4. PROJECT ANALYSIS................................................................................................... 12
4.1. Existing System ..................................................................................................... 12
4.2. Proposed System ................................................................................................... 12
4.3. Data Flow Diagram ............................................................................................... 12

5. PROJECT PLANNING..................................................................................................15

6. SYSTEM DESIGN .......................................................................................................... 18

7. SOFTWARE DEVELOPMENT METHODOLOGY ................................................. 19

8. SYSTEM IMPLEMENTATION ................................................................................... 21

9. SYSTEM TESTING ....................................................................................................... 22

8.1. Unit Testing..........................................................................................................
8.2. Integration Testing..............................................................................................
8.3. Validation Testing...............................................................................................

10. OUTPUT FORMS & REPORT ..................................................................................... 24

11. CONCLUSION ................................................................................................................ 28

 Page 8 of 28

12. BIBLIOGRAPHY & REFERENCE ............................................................................ 28

 Page 9 of 28

Chapter 1
INTRODUCTION

1.1. Aim
• The prime aim of a blog is to grab attention by making the visitors more engaged.
Hence, the blog page does need that type of presentation which should be dynamic
by nature. Blogs are not static like websites are; they should be dynamic.

1.2.Objective
• Blog Portal is a portal to share knowledge with other Users.

• There are two types of user roles User and Admin.

• User can create, edit, and view their own blog posts, along with checking the
status of each post. Additionally, they have access to a dashboard displaying
approved blog posts.

• Admin plays a crucial role by reviewing and approving or rejecting blog posts
submitted by employees, managing reported posts, and deciding whether to ignore
or delete posts if he found inappropriate content.

1.3.Scope
• Our blog portal currently offers a robust platform for sharing and managing blog
content. However, we envision several enhancements to further enrich user
experience and functionality:
• User Account Creation and Management: We will extend the system to allow
users to create and manage their own accounts. This feature will enable users to
have personalized profiles, manage their blog posts more efficiently, and
customize their experience on the platform.
• Post Alerts and Notifications: Users will have the option to subscribe to
notifications for updates on specific blog topics or authors. This feature will
notify users when new content is published or when their favorite authors post
new blogs, ensuring they never miss out on relevant updates.
• Admin Tools and Controls: Admins will benefit from enhanced tools for
managing and moderating content. This includes advanced options for
reviewing, approving, or rejecting posts, and handling user reports with greater
efficiency.
 Page 10 of 28

1.4.Purpose
Diverse Content Categories: Users will have the ability to explore a wide array of
topics and categories, ensuring that there is something of interest for everyone.
Whether users are looking for insights on technology, lifestyle, or any other field, they
can find and engage with content that matches their interests.

Enhanced Interaction and Engagement: The platform will support an interactive

user experience with real-time updates and advanced features. This will enable users
to create, edit, and share blog posts seamlessly, as well as interact with other users
through comments, likes, and shares.

User-Friendly Interfaces: We are committed to providing intuitive and user-friendly

interfaces that make it easy for users to navigate the platform, manage their content,
and engage with the community.

1.5.Methodology
Design Principles: We employ a set of design principles to guide the creation of the
blog website. This includes user-centered design to ensure a seamless and intuitive
experience, as well as best practices for responsive design to ensure the site functions
well across various devices.

Planning Process: The planning phase involves defining project requirements, setting
objectives, and outlining the scope of the project. We use systematic procedures to
create a detailed project plan, including timelines, resource allocation, and risk
management strategies.

Implementation Strategy: Our implementation strategy involves translating the

design and plan into a functional website. This includes selecting appropriate
technologies, developing features, and conducting iterative testing to ensure the site
meets all requirements and performs optimally.

Systematic Procedures: Our methodology follows systematic procedures for

managing activities throughout the project lifecycle. This includes establishing clear
workflows, conducting regular reviews, and applying best practices to maintain high
standards of quality and efficiency.

I used JAVA server-side framework Spring Boot it is used to create dynamic webcontent. It is
 Page 11 of 28

a Web-based technology that helps us to create dynamic and platform-independent web pages.
In which, Spring Boot framework and JAVA Application Programming Interfaces (APIs) is
intergrated with ReactJS library. We also used for Database MongoDB NoSQL database.
 Page 12 of 28

Chapter 2
PROJECT ANALYSIS

2.1. Existing System:

• User Management: Users can create, edit, and view their blog posts, and check their status.
The system offers easy access to all post-related information.
Admin Features: Administrators have centralized access to manage all blog posts and user data,
review content, and handle reported issues.
• Backend: Developed in Java for robust server-side functionality.
• Frontend: ReactJS for dynamic user interfaces, with Bootstrap for responsive design.
• Database: MySQL for efficient data storage and management.
• Cloud Integration: Supports cloud storage for remote data access.
Development: Built using an Integrated Development Environment (IDE) to ensure streamlined
development and deployment.

2.2. Proposed System:

User Accounts: Users can create and log in to their accounts.

Blog Management: Logged-in users can write, edit, and manage their blog posts.
Admin Access: Administrators will log in to review and manage blog submissions.
Content Approval: Admins can approve or reject posts; approved blogs will appear on the homepage.
Interactive Interface: The system will offer an intuitive interface for easy navigation.

2.3.Data Flow Diagram

Context Level Diagram

0.0
Users
Blog Admin
Portal

First Level DFD

1.0
Registrati
Users
on
 Page 13 of 28

2.0

login
 Page 14 of 28

Second Level DFD

View my Blogs
2.1
Users
Post Blog

2.2

View
Dashboard
Blogs

2.3

Edit Blogs

2.4 2.5 2.6 2.7

Like / Report Comments Filters

Dislike Blogs Blogs
Blogs

Admin 3.1 3.2 3.3

Review Approved Rejected

Blogs
 Page 15 of 28

Chapter 3
PROJECT PLANNING

Project can’t be started without proper planning. After a good research, I started our
project planning. The Planning is divided into many subcategories described below.

I have used the Gantt chart for simplifying the project schedule A Gantt chart is a type of
bar chart that illustrates a project schedule, named after its inventor, Henry Gantt, who
designed such a chart around the years 1910–1915. Modern Gantt charts also show the
dependency relationships between activities and current schedule status.

3.1. Team Structure: Team structure refers to the composition of an individual team or of
a multi team system. Team structure is an integral part of the teamwork process. A
properly structured patient care team is an enabler for and the result of effective
communication, leadership, situation monitoring and mutual support.
3.2. Specific Requirement: Since the Administrator and the user are the main target group
of our software, we will only concern about some important functions for the admin and
the user.
3.3. Administrator: -
➢ It tracks the status of purchased products.
➢ Manage the information of every product of different categories.
➢ It deals with monitoring the information of various products and order placed.
➢ Editing, deleting and updating of Records is improved which results in proper
resource management of shopping products.
3.4. Users: -
➢ Provides the searching facilities based on various factors. Such as product name,
category, company, brand etc.
➢ Shows the information and specification of each product as per user’s demand.
➢ Shows the information and specification of each product as per user’s demand
 Page 16 of 28

Gantt chart
Task Name January February March April May
Requirement analysis
Research
Database design
Programming
Implementation

3.5. Software configuration:

The Software used for the development of ‘Blog Portal’ is,
➢ Operating System - Windows 7 / 8 / or Updated
➢ Environment - XAMPP
➢ Back-end Language - JAVA version 1.8
➢ Back-end Framework - Spring Boot-4
➢ Tool for Back-end - Spring tool suite 4 (STS)
➢ Front-end Framework - ReactJS
➢ Front-end tool - vs code
➢ Database Management System - MongoDB
➢ Database tool - mongoDBCompass
➢ Web Server - Apache Tomee
➢ Web Browser - Google Chrome, Microsoft Edge etc.
3.6. Software Requirement: The system services and goals are established by consultation
with system user. They are then defined in details and serve as a system specification.
System requirement are those on which the system runs. The “Blog Portal” will be
suitable for the devices having above configuration.
3.7. Hardware Requirement:
Operating System - 64- bit Operating System
RAM - 4 GB RAM or more
Processor - Quad-Core Processor (CPU) with 2 Gigahertz (GHz)
Frequency or above

Tool logo
 Page 17 of 28

3.8. Performance Requirements:

➢ System should be able handle multiple users
➢ Database updating should follow transaction processing to avoid data inconsistency.
 Page 18 of 28

Chapter 4

SYSTEM DESIGN

4.1. ER Diagram
An entity relationship model, also called an entity - relationship (ER) diagram, is a
graphical representation of entities and their relationships to each other, typically used
in computing in regard to the organization of data within databases or information
state. An entity is a piece of data - an object or concept about which data is stored.
 Page 19 of 28

Chapter 6
SOFTWARE DEVELOPMENT METHODOLOGY

System Development Life Cycle is a conceptual model used in software development

projects. In this method, there is a possibility of combining two or more project
management methodologies for the best outcome. Therefore we have used waterfall Model
along with SDLC. SDLC also heavily emphasizes on the use of documentation and has
strict guidelines on it.

Waterfall Model: This is the legacy model for software development projects. This
methodology has been in practice for decades before the new methodologies were
introduced. In this model, development life cycle has fixed phases and linear timelines. The
Waterfall Model is a sequential software development process, on which progress is seen
as steadily downwards (like waterfall) through phases of requirement, design,
implementation, verification and maintenance.

Requirements
Specification

Design

Development

Testing

Maintenance

4.2.Feasibility Study
The Blog Portal is a web-based application. It can handle data about products of
various categories. This includes details of registered users, retailers and various
products of different categories etc. In case of manual system, they need a lot of time,
manpower etc. Here almost all work is computerized. So, the accuracy and security is
maintained.
 Page 20 of 28

4.2.1. Economical Feasibility: The project is economically feasible as the only

cost involved is having a computer with the minimum requirements
mentioned earlier. For the users to access the application, the only cost
involved will be in getting access to the Internet.
2.12. Technical Feasibility: To deploy the application, the only technical aspects
needed are mentioned below:
Operating Environment: Windows 7 / 8 or updated versions
Database: MySQL
Server: Apache-Tomcat-Windows
➢ Reliability: As database tables are used to store data so reliability is maintained
as exact data is extracted.
➢ Portability: The project is compatible with any computer system with minimal
software and hardware requirements.
➢ Extensibility: The project is easily extensible by further adding more functions.
4.2.2. Behavioural Feasibility: The application requires no special technical
guidance and all the views available in the application are self
explanatory. The users are well guided with warning and failure messages
for all the actions taken.
 Page 21 of 28

Chapter 7
SYSTEM IMPLEMENTATION

Implementation is the stage in the project where the theoretical design is turned into a
working system and is giving confidence on the new system for the users that it will work
efficiently and effectively. It involves careful planning, investigation of the current system
and it's constraints on implementation, design of methods to achieve the changeover, an
evaluation, of changeover methods. Apart from planning major task of preparing the
implementation are education and training of users. The more complex system being
implemented, the more involved will be the system analysis and the design effort required
just for implementation.

An implementation co-ordination committee based on policies of individual organization

has been appointed. The implementation process begins with preparing a plan for the
implementation of the system.

According to this plan, the activities are to be carried out, discussions are made regarding
the equipment and resources and the additional equipment has to be acquired to implement
the new system.

Implementation is the final and important phase .This is the most critical stage in achieving
a successful new system and in giving the users confidence that the new system will work
is effective. The system can be implemented only after thorough testing. This method also
offers the greatest security since the old system can takeover if the errors are found or
inability to handle certain type of transactions while using the new system.
 Page 22 of 28

Chapter 8
SYSTEM TESTING

4.2.3. Unit Testing: System testing is the stage of implementation, which is

aimed at ensuring that the system works accurately and efficiently before
live operation commences. Testing is vital to the success of the system.
Testing is the process of executing a program with the explicit intention
of finding errors that is making the program fail. The tester may analysts,
programmer or a specialist trained for software testing, is actually trying
to make the program fail. Analysts know that an effective testing program
does not guarantee system reliability. Therefore reliability must be
designed into the system.

Testing brings all the pieces together into a special testing environment, then checks
for errors, bugs and interoperability.

4.2.4. Integration Testing: Data can be lost across any interface, one module
can have an adverse effect on another, sub functions when combined, may
not produce the desired major functions .Integration testing is a systematic
testing for conducting tests to uncover errors associated within the
interface .The objective is to take unit tested modules and build a program
structure. All the modules are combined and tested as a whole. Here
correction is difficult because the vast expenses of the entire program
complicate the isolation of causes. Thus in the integration testing step, all
the errors are corrected for the next testing steps. In online test
management tool, each module is integrated and tested .This testing
provides the assurance that the application is well integrated functional
unit with smooth transition of data.

4.2.5. Validation Testing: At the culmination of integration testing, software is

completely assembled as a package; interfacing errors have been
recovered and corrected and a final series of a software tests - validation
tests begin. Validation testing can be defined in many ways but a simple
 Page 23 of 28

definition is that validation succeeds when the software functions in a

manner that can be reasonably expected by the customer.

Invalidation testing if user wants to enter the numeric value he can only enter the
numeric value not the text value. For e.g. :in phone number field user can only enter
numeric value to it .The system is user friendly with user guide and messages to
explain further procedures .An attempt has been made to perfect the process by
incorporating validation at each level
 Page 24 of 28

Chapter 9
OUTPUT FORMS & REPORTS
Page 25 of 28
Page 26 of 28
 Page 27 of 28

.
 Page 28 of 28

Chapter 10
CONCLUSION

The ‘Blog Portal’ is designed to provide a web-based application that would that features
regularly updated content, often written in a personal or conversational style. Blogs can
be maintained by an individual or a group of people and can cover a wide range
of topics, such as Programming Languages, Database Management Systems, Networking,
Frameworks, Computer Sciences, and more.. A blog typically includes text, images, and
links to other websites, and allows readers to leave comments and engage in discussions.
Blogs are typically created and maintained using a content management system (CMS) or
blogging platform, such as WordPress, Blogger, or Medium. These platforms provide the
tools and functionality needed to create, publish, and manage blog posts and other
content. Blogs can be hosted on a website or on a blog hosting service and can be
accessed by anyone with an internet connection.

BIBLIOGRAPHY & REFERENCE

www.youtube.com
www.javatpoint.com.
www.tutorialspoint.com.
www.mysqltutorial.org.
www.mysql.org.
www.stackoverflow.com
https://docs.oracle.com
https://getbootstrap.com
http://tomcat.apache.org/