0% found this document useful (0 votes)
472 views8 pages

Srs Blogging System

ji

Uploaded by

Sukriti Mugdha
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
0% found this document useful (0 votes)
472 views8 pages

Srs Blogging System

ji

Uploaded by

Sukriti Mugdha
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
You are on page 1/ 8

Software Requirements

Specification
for

Online Blogging System

Version 1.0 approved

Prepared by Dhiraj Govindvira

Dharmsinh Desai University, Nadiad

10 December 2020

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ............................................................................................................................ ii
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions.................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 1
1.5 References ........................................................................................................................................ 1
2. Overall Description ..................................................................................................................1
2.1 Product Perspective.......................................................................................................................... 1
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 2
2.4 Operating Environment.................................................................................................................... 2
2.5 Design and Implementation Constraints .......................................................................................... 2
2.6 User Documentation ........................................................................................................................ 2
2.7 Assumptions and Dependencies ...................................................................................................... 2
3. External Interface Requirements ...........................................................................................3
3.1 User Interfaces ................................................................................................................................. 3
3.2 Hardware Interfaces ......................................................................................................................... 3
3.3 Software Interfaces .......................................................................................................................... 3
3.4 Communications Interfaces ............................................................................................................. 3
4. System Features .......................................................................................................................3
4.1 Functional requirements................................................................................................................... 3
5. Other Nonfunctional Requirements .......................................................................................5
5.1 Performance Requirements .............................................................................................................. 5
5.2 Safety Requirements ........................................................................................................................ 5
5.3 Security Requirements ..................................................................................................................... 5
5.4 Software Quality Attributes ............................................................................................................. 6
5.5 Business Rules ................................................................................................................................. 6
6. Other Requirements ................................................................................................................6
Appendix A: Glossary....................................................................................................................6

Revision History
Name Date Reason for Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose
An Online Blogging System is basically a website which is used for chronological listing of blog
posts. A blog has the most recent content shown first followed by the previously updated content.
An Online Blogging System website is a site dedicated to the blogging. One such good example of
this service is https://www.blogger.com/about/

1.2 Document Conventions


This document is formed using IEEE SRS format, headings are in bold capital letters and wherever
a necessary diagram is provided.

This document uses the following conventions.


- DB database

1.3 Intended Audience and Reading Suggestions


This project is a prototype for the blogging system and it is restricted within the college premises.
This has been implemented under the guidance of college professors.

1.4 Product Scope


The purpose of the online blogging system is to ease blog management and to create a convenient
and easy-to-use application for bloggers.

1.5 References
- IEEE SRS Document
- https://www.google.com
- https://www.perforce.com/blog/alm/how-write-software-requirements-specification-srs-
document

2. Overall Description

2.1 Product Perspective


A blogging system database system stores the following information.

1. Blog description:
It includes blog content, date and time for blog, author of blog etc.
Software Requirements Specification for <Project> Page 2

2. User details:
It includes user name, password, email-id, blogs etc.

2.2 Product Functions


This product can be useful in the replacing the newspaper articles to save the nature.

- Login module
- Registration module
- Show Blogs list
- Create / edit / update / delete blogs
- Search blogs based on title, author or dates
- Markdown syntax for blog content

2.3 User Classes and Characteristics


- Users:
o Users can access the blogs.
o Users can sign up for new account.
o Users can create, delete, update posts(blogs).

2.4 Operating Environment


This website will work on any platform which have integrated browser and internet support.
It works on major browsers like chrome, Firefox, safari, edge etc. Works with many operating
systems like windows, Linux and macOS.

2.5 Design and Implementation Constraints


Blogging System is a Web application, so user needs to use any kind of browsers and also need
internet. When users or merchants use legacy browser then the UI of website sometime does not
work. Software maintenance will be available from our side without any charges.

2.6 User Documentation


User manual and product tutorial video link is provided with SRS. Screenshot of the whole product
is also available to user for future reference.

2.7 Assumptions and Dependencies


While developing this product we assumed following factors.
• User will have any kind of smart device like laptop, pc or smartphone.
• All these devices are capable to run modern browsers.
• User will have internet connection. The project could be affected if any of these assumptions are
incorrect.
Software Requirements Specification for <Project> Page 3

3. External Interface Requirements

3.1 User Interfaces


Since Blogging system is a web application, it comes with user friendly and easy to use user
interface. It comes with easy navigation without any learning curve.

- Front-end software: Angular, Html, CSS, JavaScript


- Back-end software: Mongo DB, Node js

3.2 Hardware Interfaces


- A browser which supports HTML & JavaScript.
- As a hardware we need smart devices which can easily run any modern web browsers. To
communicate with data in the system user need good internet connection

3.3 Software Interfaces

Following are the software used for the blogging system.


Operating system - Linux, windows or macOS.
Database - To save the blogs content, passengers records we have chosen Mongo database.
For the communication of the data user must require internet connection.

3.4 Communications Interfaces


This project supports all types of web browsers. We are using simple forms for the login, signup
etc.

4. System Features
Blogging Site provides services to add, remove and updating of the post with access control. The
site saves the time of author by giving the lots of feature on hand.

4.1 Functional Requirement

4.1.1 Show Blogs list


Input: button click
output: List of posts with the link to respective post page.
description: To list down all the post on the home page of the site.
precondition: There is no need to log in to as blogs must be available to all users.

4.1.2 Search blogs


Software Requirements Specification for <Project> Page 4

input: search query as a string.


output: Success or Failure.
process: search based on user query and show matching blogs.
precondition: There is no need to log in to as blogs must be available to all users.

4.1.3 Login
input: Username and Password.
output: Success or Failure.
description: User can use this page to login to the system by entering personal
credentials (username and password) and will be redirected to a home page based
on role to use the features of the website.
process: Check the username and matching password in the database. If found in
the database then redirect the user to his/her home page.
precondition: User must be registered on the website.
postcondition: User is logged in to the website and a new session is associated
with the client connection.

4.1.4 Registration
input: User needs to fill up the registration form.
output: Success or Failure based on availability.
process: If data are valid, make changes to database otherwise handle
appropriately.
postcondition: User is logged in to the website and a new session is associated
with the client connection.

4.1.5 Add Blog

input: User needs to fill up the from containing info like title, description, content etc.
output: Success or Failure.
description: This feature is used to add new blog.
precondition: User must be login on the website.
process: If validation is successful, make changes to database otherwise handle
appropriately.
postcondition: An alert is displayed based on success or failure. If success, post
will be added.

4.1.6 Update Blog

input: User needs to fill up the from containing info like title, description, content etc.
output: Success or Failure.
description: This feature is used to add new post by the user.
Software Requirements Specification for <Project> Page 5

precondition: User must be login on the website


process: If validation is successful, make changes to database otherwise handle
appropriately.
postcondition: An alert is displayed based on success or failure. If success, post
will be updated.

4.1.7 Delete Blog

input: User click.


output: Success or Failure.
precondition: User must be login on the website.
process: If validation is successful, make changes to database otherwise handle
appropriately.
postcondition: An alert is displayed based on success or failure. If success, post
will be removed.

4.1.8 Logout

input: button click.


output: Success or Failure.
process: Session is destroyed and user is redirected to home page.
precondition: User must be logged in the website

5. Other Nonfunctional Requirements

5.1 Performance Requirements


Performance should not be an issue because of all the data queries involves small pieces of data.
Changing screen will require very little computation and thus will occur very quickly. Server
updates could only take few seconds as long as device can maintain steady signal. website will
also up for 24x7 except the maintenance.

5.2 Safety Requirements


Make this application lightweight, so that it put low load on device.
Only the project admin will be having access to the database at the back-end. So, the admin will
have rights for modifications as well as direct updates to the database.

5.3 Security Requirements


System should provide secure login/registration system. And don’t allow unauthorized user to
access the application.
Security systems need database storage just like many other applications.
Software Requirements Specification for <Project> Page 6

5.4 Software Quality Attributes


System should be
- Consistent in performance
- Safe and Secure
- Robust
- Scalable
- Flexible
- User friendly
- Efficient
-
Availability: The website should be stable and available at any time.
Correctness: The blog’s details and content should be displayed correctly.
Usability: The blogging system should satisfy a maximum number of customer’s needs.

5.5 Business Rules


Blog owner can only manage the blogs of his/her own. He/she cannot interfere in other’s blog post.

6. Other Requirements
Database: NoSQL (Mongo dB)
Web based application

Appendix A: Glossary
Developer means A person or group of people who are going to make your application.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy