ONLINE NEWSPAPER

SHRI MANILAL KADAKIA COLLEGE OF COMMERCE,

MANAGEMENT,
SCIENCE AND COMPUTER STUDIES ANKLESHWAR

VEER NARMAD SOUTH GUJARAT UNIVERSITY

A PROJECT REPORT
As a Partial Fulfilment For The Post Degree of
Bachelors of Computer Application (B.C.A)
Third Year (5th Semester)
Year(2024-2025)
Project Title: Online Newspaper
Submitted By: Khatri Aman. (Roll no: 09)

1|Page
 INDEX
Sr. no. Subject Page no.
1. Introduction to Project 3
1.1 Program Objectives 3
1.2 Scope of the Project 3
1.3 Project Objectives 3
1.4 Project Goals 3
1.5 Details 4
2 System Requirement Specification
2.1 Scope
2.2 Objectives
2.3 Overall Description
2.3.1 Project Prospective
2.3.2 Product Functions
2.3.3 Assumptions and Dependencies
2.4 Specific Requirements
2.5 Functional And Non-Functional Requirements
3 System Design
3.1 Data Flow Diagram
3.2 E R Diagram

2|Page
1.Introduction to Project
1.1 Program Objectives
Online Newspaper is a website designed to provide readers with the latest news in
categories such as politics, entertainment, sports, technology, etc. It allows journalists
and writers to publish articles, while readers can and interact with content. The purpose
of the conference is to realize the provision of reliable records, assistance in the
management of editorial work, and interest worthy of the individual.

1.2 Scope of the Project

Online Newspaper size also includes front-end functionality. It allows administrators to
manage content, and customers to write, post and exchange information. The project
also includes a subscription service for premium content and a search/filtering system
to improve the user experience. The work will be:

Support user roles such as Admin, Editor, Author, and Reader.

Provide a system that works desktop users. Engage with copy link and share
information on any Social Media. Allow users to subscribe to premium products
through secure payment methods.Include CMS views, configurations, and
modifications.

1.3 Project Objectives

Broad goals of the Online Newspaper project are the following:

To provide a detailed, rich platform allowing users to view various categories of news .

3|Page
Tools to be developed that will make it easy and fast to write, post, edit, and publish for
both writers and editors

Premium subscription service offering additional content exclusively to paying users.

1.4 Project Goals

Design a vibrant, content based website where the audience may be updated on
current issues

Streamline the editorial process to allow for easy authors and editors interaction.

Implement user roles and permissions to allow secure, efficient management of content

Offer high end subscriptions that will grant clients access to premium and exclusive
content.

To avail of SEO optimization and speedy loading speed to enhance search engine's
ability to see and the user's capacity to access.

1.5 Details

Collaboration
The platform will support collaboration between various user roles:

• Admin: Can manage all content, users, and settings.

• Editor: Approves and publishes articles submitted by authors.
• Author: Can write and submit articles for approval.
• Reader: Can read articles, leave comments, and engage with social media
features.

Content Management

• CMS: A comprehensive Content Management System to handle article

creation, media uploads, and category management.
• Scheduling: Authors can schedule articles for publication at specific
times.
• Drafts and Revisions: Users can save drafts and make revisions before
submitting articles.

Responsive Design
The website will be designed to be fully responsive, ensuring a smooth
experience desktop devices. The design will include:

4|Page
 • A clean and modern homepage showcasing the latest news and top
stories.
• Category pages for different sections like Politics, Sports, Entertainment,
etc.
• A search bar and filter options to help users find relevant content quickly.

Subscription Model
The project will implement a subscription model that allows users to:

• Access premium content that is only available to paying subscribers.

• Subscribe via secure payment methods such as PayPal or Stripe.
• Receive newsletters and updates based on their interests.

Security and Access Control

• Role-based access control: Ensures that only authorized users can edit,
publish, or delete articles.
• SSL encryption: For securing user data, especially during payment
transactions.
• Backup and recovery: Ensures data integrity in case of system failures.

Social Media Integration

The platform will integrate social media sharing buttons on each article page,
allowing readers to share content across:

• Facebook
• Twitter
• Instagram
• WhatsApp

Analytics and Insights

Admins will have access to a dashboard showing:

• The number of page views.

• Reader engagement (shares).
• Subscription data.
• Most popular articles.

2. System Requirement Specifications (SRS)

2.1 Scope:

5|Page
The online newspaper project aims for the ultimate delivery of a dynamic digital
platform for users to read and interact with news articles through topics and
places. The users are allowed to register themselves as well as comment upon
published articles; they can view free as well as premium content. Article
submission, user comments, and search functionality where filtering is possible
using category and city names are among the proposed core features of the
application. In addition, premium subscribers will enjoy privileged access to
certain content and services, layering multiple engagement points.

The project also enables administrative control so that there can be content
moderation, user management, and category-based organization. The
responsive design ensures compatibility across different devices, and there are
social media icons that make sharing easy. The platform will also feature a
subscription model, giving users access to the specialized contents and giving
monetization chances for the website.

2.2 Objectives
This will, therefore, produce a form of online space through which publishing
and management of news articles can take place.
This would allow surfers to browse and search for articles based on category,
city, and keyword.
This will make it possible to provide an administrative interface for tasks related
to managing articles, user accounts, and subscription services.
Provide opportunities to users for communication and discussion as part of
commenting on articles and giving feedback.
Provide service to enable subscription services based on premium content, such
as an article for specific city or category-based news.

2.3 Overall Description

2.3.1

Product Perspective
The online newspaper platform will be a responsive web application. The website will have
three main roles: users, administrators, and guest visitors. Guests will have limited access
to content, while registered users will be able to comment, subscribe, and interact with
articles. Admins will manage content, users, and system settings.

6|Page
2.3.2

Product Functions

User Management:

• User registration module with login functionality.

• Administration of the profile, which includes changing of personal information
and the use of profile images.
• Different types of users, named admin, editor, subscriber, guest.

Article Management:

• Articles that admin and editor can add, edit, or remove.

• Arrange articles under topic and city header.
• Add a cover image and extra images for article's content.

Search and Filtering:

• Users can search for articles based on city, category, or keywords.

• Auto-suggest in the search box for city-based news and categories.

Subscription Service:

• Users can subscribe to access premium content.

• Payment options for different subscription tiers.

Contact Us Page:

• Contact form with an option to add social media icons (Facebook, Twitter, Instagram,
WhatsApp).

2.3.3

Assumptions and Dependencies

• Database Assumption: The system assumes a functional database structure with tables for
users, articles, categories, and subscriptions.
• Browser Compatibility: The system should work seamlessly on all modern web browsers.
• Payment Integration: Subscription services will depend on the integration of third-party
payment gateways like PayPal or Stripe.
• Server and Hosting: Assumes the application will be deployed on a cloud-based server for
scalability.

7|Page
• Content Moderation: Assumes an admin is actively moderating user content, including
articles and comments.

2.4 Specific Requirements

Software Requirements:

• Compatible with browsers newer than Mozilla Firefox 4.0 or Internet Explorer 6.0.
• Requires Adobe Flash Player version 10.0 or higher.

Hardware Requirements:

• Processor: Any model newer than Pentium 4.

• Operating System: Any version of Windows XP or more recent.

2.5 Functional and Non-Functional Requirements:

• Functional Requirements:

The online newspaper project will allow users to register, log in, and manage their
profiles. Administrators and editors can manage articles by submitting, editing, and deleting content,
while users can search for articles by keywords, category, or city. A commenting system will enable
registered users to leave comments on articles, with moderation options available to administrators.
Additionally, the platform will include a subscription system where users can access premium
content through integrated payment gateways such as PayPal or Stripe. An admin panel will provide
administrative control over users, articles, and comments, ensuring proper content and user
management.

• Non-Functional Requirements:

• Performance:

The website should load in under 3 seconds for most users, even with high traffic.

• Scalability:

The system should be able to handle an increasing number of users and articles
without degradation in performance.

• Security:

Secure user data storage with encryption, secure logins, and protection against
common attacks like SQL injection and XSS.

• Usability:

8|Page
 The platform should be easy to navigate with a responsive design for mobile and
desktop users.

• Reliability:

The system should have 99.9% uptime, ensuring continuous access for users.

• Maintainability:

The system should be easy to maintain, with modular code for quick updates and bug
fixes.

System Design

3.1 Data Flow Diagram:

CONTEXT LEVEL DFD

9|Page
1ST LEVEL DFD FOR ADMIN

10 | P a g e
1st Level DFD For User
11 | P a g e
12 | P a g e
3.2 E R Diagram

13 | P a g e
3.3 Data Dictionary
A data dictionary is a centralized repository that defines the structure, relationships, and
attributes of data elements within a system. It serves as a comprehensive reference that helps
stakeholders, including developers, data architects, and analysts, understand how data is
organized, used, and maintained in a project. By documenting each data element's name,
description, format, type, and constraints, a data dictionary ensures that the data used within
the system is standardized and consistent.

Purpose of a Data Dictionary

The primary purpose of a data dictionary is to provide clear definitions of data entities and
attributes to promote data integrity and consistency across the system. It acts as a guide to
understanding the data’s purpose, structure, and usage. A well-constructed data dictionary
also helps streamline communication among team members, ensuring that everyone has a
shared understanding of the data. It plays a crucial role in avoiding data redundancy and
ensuring that every piece of data is well-documented.

Components of a Data Dictionary

A data dictionary typically includes the following elements:

• Data Element Name: The name or label used to identify the data element.
• Description: A brief explanation of the purpose or meaning of the data element.
• Data Type: Specifies the type of data (e.g., integer, string, date) that the element holds.
• Format: Indicates how the data should be formatted (e.g., date format YYYY-MM-DD).
• Length: The maximum number of characters or digits allowed.
• Required/Optional: Specifies whether the data element is mandatory or optional.
• Constraints/Rules: Any rules or constraints on the data, such as validation requirements.

Benefits of a Data Dictionary

1. Improved Data Quality: By defining data formats and validation rules, a data dictionary
helps in maintaining high-quality data. It prevents incorrect data entry and ensures that data
values adhere to predefined standards.
2. Facilitates Communication: A data dictionary serves as a common reference point for all
stakeholders involved in a project. Whether it’s developers, database administrators, or
business analysts, everyone can refer to the same definitions, reducing confusion and
misinterpretation.
3. Streamlined Development: Developers can refer to the data dictionary to understand how
to structure databases, create queries, or design forms without ambiguity. This speeds up
the development process and ensures that all team members are aligned with the same
data standards.
4. Support for Data Integrity: By defining clear relationships between data elements and the
rules for how data should be managed, the data dictionary helps ensure that the system
maintains consistent and accurate information.

14 | P a g e
Importance in System Development

In any project, especially those involving complex databases or systems with numerous data
interactions, a data dictionary is essential. It provides a roadmap for data usage, ensuring that
developers and users alike understand the purpose of each data element and how it fits into
the larger system. During system maintenance or updates, the data dictionary serves as a
reference to ensure that new data structures or modifications do not conflict with the existing
data model. It also aids in documentation and future scaling of the system.

Types of Data Dictionaries

1. Active Data Dictionary: This is an integrated dictionary maintained within the system,
automatically updated as changes are made to the database. It provides real-time
information about the data.
2. Passive Data Dictionary: A static reference document that is maintained manually and must
be updated whenever the system changes. It’s useful for smaller projects where real-time
integration isn’t necessary.

Database Information
➢ Database Name : e_newspaper
➢ Number of Tables :5
➢ Number of primary key :4
➢ Number of Unique Key :4

Table Name: admins

Objective: This table is used to give admins details.
Primary key: id
Unique key: username
Field Name Data type Size Constraints Description
id Int N/A PRIMARY KEY Unique identifier for each admin
user
username Varchar 50 Unique key Admin's username for login
password1 varchar 255 NOT NULL Admin's password for
authentication
created_at timestamp N/A NULL, DEFAULT Timestamp when the admin was
CURRENT_TIMESTAMP created

15 | P a g e
 Table Name: articles
Objective: This table is used to give all articles.
Primary Key: id
Field Name Data type Size Constraints Description
id int 255 PRIMARY KEY, Unique identifier for each
AUTO_INCREMENT article
title varchar N/A NOT NULL Title of the article
content Text N/A NOT NULL Main content of the article
author_id int N/A NOT NULL ID of the author (references
user)
created_at timestamp N/A NULL, DEFAULT Timestamp when the article
CURRENT_TIMESTAMP was created
updated_at timestamp N/A NULL, DEFAULT Timestamp when the article
CURRENT_TIMESTAMP was last updated
ON UPDATE
media text N/A NULL Additional media content for
the article
cover_image varchar 255 NULL Cover image for the article
category varchar 255 NOT NULL Category of the article
city varchar 255 NULL City associated with the article
(optional)

Table Name: users

Objective: This table is used to give all users.
Primary Key:
Field Name Data Type Size Constraints Description
id int N/A PRIMARY KEY, Unique identifier for each user.
AUTO_INCREMENT
first_name varchar 100 NOT NULL First name of the user
last_name varchar 100 NOT NULL Last name of the user
email varchar 100 NOT NULL User's email address
password varchar 255 NOT NULL User's password
profile_image varchar 255 NULL Profile image URL or path
(optional)
created_at timestamp N/A NULL, DEFAULT Timestamp when the user was
CURRENT_TIMESTAMP created

Table Name: Settings

Objectives: This Table Is used to handle Project settings.
Primary Key: id
Field Name Data Type Size Constraints Description
id int N/A PRIMARY KEY, Unique identifier for each
AUTO_INCREMENT setting
setting_key varchar 50 NOT NULL, INDEX Key name of the setting
setting_value varchar 255 NOT NULL Value associated with the
setting key

16 | P a g e
 created_at timestamp N/A NULL, DEFAULT Timestamp when the setting
CURRENT_TIMESTAMP was created
updated_at timestamp N/A NULL, DEFAULT Timestamp when the setting
CURRENT_TIMESTAMP was last updated
ON UPDATE

Table Name: comments

Objectives: This table give comments
Primary Key: id
Field Name Data Type Size Constraints Description
id int N/A PRIMARY KEY, Unique identifier for each
AUTO_INCREMENT comment
article_id int N/A NOT NULL ID of the associated article
user_id N/A NOT NULL ID of the user who made the
comment
comment text N/A NOT NULL The actual comment content
created_at timestamp N/A NULL, DEFAULT Timestamp when the comment
CURRENT_TIMESTAMP was created

4.1 TEST CASE

1. Unit Testing
Unit testing is the primary test level in software development. Unit
testing is mainly done to test the functionality of any given single unit or
units of code. Any unit could be a function, method, or even a class, but
still, it gets tested in isolation to ensure it works as anticipated. For
instance, such as the online newspaper system, unit test is so that the
registration of users' function correctly handles valid and invalid inputs.
The primary purpose of unit testing is to catch bugs or bugs at the
earliest stages of development, thereby making it easier to correct with
cheaper overheads.

2. Module Testing
Unit testing comes up with module testing. This means a specific module
or set of related modules are tested to ensure whether modules work
correctly alone or with other modules. Module testing inside the context
of the system of an online newspaper will consist of checking how the
17 | P a g e
 process of submitting articles operates, ensuring that users have no
problem in submitting articles, and also guaranteeing that the articles
are correctly saved into the database. Module testing aims to verify the
behaviour of a group of units and ensure proper interaction between
them.

3. Testing of Sub-System
So what we consider under sub-system testing is actually testing of
interfaces of two or more modules or components in the software.
Therefore, checks the aptness of all those modules to work as a whole
system. For example, if we talk about an online news system, here, sub-
system testing would include checking whether the newly registered
user through the user registration module will be able to post articles
without any issues using the article submission module. The objective of
sub-system testing is to verify whether the combined components are
correct or not, and in case there are integration problems, it should be
able to identify and rectify them.

4. System Testing
System testing is a thorough assessment of the complete software
system. It checks out the full application to see if the program works in
all the expected scenarios and fulfills the specified requirements. This is
the basic testing at all the levels, including functional testing,
performance testing, security testing, and so on. System testing for the
online newspaper system may include user registration, posting articles,
and comments to confirm that the developed features work well
integrated with each other. System testing aims at validating all the
software's overall performance and functionality before the release of
the software to be used by users.

5. Acceptance Testing
Acceptance testing is the final level of testing, wherein the product is
tested before its installation to ensure that the product reaches the
expected business requirements and that it is acceptable to end-users. It
could be done by the quality assurance team or even by the users
themselves. For instance, acceptance tests of the online newspaper
system may include determining whether users can register to open an
18 | P a g e
 account, upload articles, and obtain access to premium content.
Generally, acceptance testing is aimed at confirming whether the
software is released-ready and fulfills the requirements of the user.

5.1 Website Related Snapshots:

Registration User Form:

Login User Form:

19 | P a g e
Home Page from User Side:

About Us Page:

20 | P a g e
Contact US Page:

21 | P a g e
Subscribe Page:

User Profile Page:

22 | P a g e
Admin Side
Admin side Login:

Admin Side Home(Dashboard):

Article From Admin:

23 | P a g e
User From Admin:

24 | P a g e
 6.CONCLUSION AND DISCUSSION

6.1 Self-Analysis of project Availibilities

Looking back, this project displays several strengths. Firstly, its design is
user-friendly-very easy to navigate through articles and categories. The system for
content management is dynamic allowing one the ability to submit and manage
articles in real time maintaining a constant flow of new information at all times. Its
scalable structure holds the possibility to improve upon these things by adding
multimedia and new categories, while its comment section supplies a gateway to
community interaction. This would enrich the user experience and engagement in its
totality.

6.2 Problem Encountered and Possible Solutions

• Hardware Limitations
The only limitation posed is when the disk space is exhausted And it can be
solved by extending the disk space.

• Internet speed
Internet connection speed should be minimum 128 kbps.

6.3 Summary of Project work

The project, therefore, encompasses a myriad of requirements including the
functional features- those related to the features of the functionalities such as sign-up
for users, posting articles, as well as content management and commenting. Some of the
requirements are quite non-functional including performance-related, security, and
usability. Detailed planning, therefore, encompasses the main research, design,
implementation, testing stages over the timeline of the project while, at the same time,
spelling out the resources and team members needed. The coding phases were,
therefore carried out in an Agile methodology using suitable programming languages,
frameworks, and libraries. Full test strategy addresses unit, integration, system and user
acceptance testing with proper test cases for major functionalities. Finally, the budget
itemizes cost with resource costs and tool costs and hosting, which ultimately leads up
to the final estimate with an allowance for something unforeseen.

25 | P a g e