CS619 phases
- CS619 Sample srs
- CS619 Samle design Doc
- CS619 Sample Final Delivery
- cs619 Viva
- Project Viva
- Favorite Subject Viva
What is SRS
SRS Contain
- Title Of The Project
- Version
- Logo
- Your id
- Supervisor
- Version History
- Category of Project
- Introduction/Scope
- Functional requirement
- Non Functional Requirement
- Use Case Diagrams
- Purpose or Use Case Of Project
- Software and Tool
- Environment
- Advantage
Books Bazar- Online
Software
Requirements Specification
Version 1.0
Group Id:
Supervisor Name:
Nowadays, E-commerce has become an
essential tool in our life. People have no time to visit the market and do
shopping. That is why the trend of buying and selling online has increased. All
businesses are also providing their services online. E-Wallet based books bazar online is a web-based application that will
facilitate the user to buy the books online by using this website.
Revision History
Revision History
|
Date (dd/mm/yyyy) |
Version |
Description |
Author |
|
15/01/2023 |
1.0 | Books Bazar-Online that will provide books of different categories to its users in soft form. A user will be able to purchase / make order against available books using e-wallet system of this website. The website will provide interactive/responsive interfaces and rich search facility for finding the different types of books through different filters. |
Your Id |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional and non-Functional Requirements:
1) User Registration, Sign Up/ Sign In
· Visitor (Unregistered User)
· Registered user as Client
· Registered user as Seller
· Registered user as Administrator
Proper
interfaces for user registration and Sign In will be available for all users.
Roles
of the users will be as follow:
· Visitors will be able to visit the website to search
books of his / her interest on the website without login. Such user will be
able to only read the books of free category online.
· A registered user as a client will be able to
perform all tasks of a visitor and additionally will be able to download any
free book and to place order for paid book(s) on the website.
· A user registered as Seller will be able to put the
details of the books on the website for sale and will be able to see the
related reports.
· A user registered as the Administrator (Admin) will
have all the rights/privileges of all the information management i.e. Books,
all types of registered Users, Stock, Wallet and different types of reports. In
addition, the Admin will add /approve/reject the seller registration requests.
2) Email Notification and Verification
An unregistered user will register him/her on the
website. On submitting the registration information, an email notification will
be sent with a confirmation link to the user’s given email ID for the
verification of the email ID.
3) Admin Panel
- The admin panel will allow the Admin to perform category management, Wallet Management as well as user management (accepting /rejecting the seller registration requests).
- Admin will also be able to perform all tasks of a registered user Client, Seller and unregistered user (Visitor).
4) Dashboard for Registered Users
1. Registered User- Client
There will be a proper Dashboard comprising of
interactive interfaces for the registered users. The dashboard will include
some common links and interfaces such as user profile, E-Wallet, favorite
books, view order status, list of books read or downloaded by the user, etc. and
any other required links and interfaces.
2. Registered User- Seller
In addition to the above functionalities, interfaces
of the list of orders and manage orders, uploading the books detail for sale,
A list of sold-out books etc. will be provided to the registered user as a
Seller. There will be a proper Dashboard comprising interactive interfaces
through which the seller will be able to add/ delete and update all information
about books such as Book Title, ISBN, Publisher, short description, price,
stock availability etc.
5)
Display of Information on the Website
The website will display the information of available books category wise
such as Free, Paid and subcategories like Religious, Academic, Science,
Health, The Books of Travels, Biographic, Novels, Poetry, Fairy Tales, Wars and
Fiction etc. (A student may add further sub-categories). Book Title, Author, Publisher,
Publishing Year, ISBN (if applicable), Book Category, Price (In case of Paid
category), In Stock etc., and user’s reviews/ratings will be displayed in
proper format.
6) Display of Prefac
The website will allow any type of user to read the preface of any book of Paid Category. There will be a proper link and display interface for this purpose
Placing Order on the Website
The website will allow the registered user(s) to make an order against their
selected books. There will be proper interfaces on the website in this regard.
The user will first have to select the item to put into the shopping cart and
then will have to pay from the E-Wallet System of this website.
8) Confirmation email on transaction (Order Placing)
A confirmation email on the successful transaction will
be sent to the user’s provided email.
9) Search Facility
Search
information on the website using different filters and keywords such as:
1. Book Type /Category
2. Book Title / Name
3. Author
4. Publisher
5. ISBN
6. Price
7. New Arrivals
8. Publishing Year
9. Best Sellers
10)E-Wallet System
There will be a proper E-Wallet System on the website which will allocate a specific amount to the registered users on the assumption that an offline submission of money has been paid to the Admin via any means at the time of registration. A registered user will be able to place an order for paid books by using this wallet. On each successful transaction (order placing), an automatic deduction will be made in the amount in the account of the user. The Admin will manage the E-Wallet account against each registered user.
11)Feedback/Suggestion
The
registered users will be able to submit their feedback and suggestions about
the website’s services to Admin or about the books to the seller.
12) Reviews and Rating
The
registered users will be able to submit their reviews using a star rating
system against the book(s) read, downloaded or purchased by them.
Non-Functional Requirements:
A non-functional requirement is a specification that
describes the system’s operational capabilities and constraints that enhance its
functionality. These may be speed, security, reliability, etc.
Usability
The term “usability” in the
context of creating software represents an approach that puts the user, rather
than the system, at the center of the process. This philosophy, called
user-centered design, incorporates user concerns and advocacy from the
beginning of the design process and dictates that the needs of the user should
be foremost in any design decisions. In designing of this course Management, it
is taken care that it can be easy to use no more complex abilities.
Security
· The system use SSL (secured socket layer) in all transactions that include any confidential customer information.
· The system must automatically log out all customers after a period of inactivity.
· The system should not leave any cookies on the customer’s computer containing the user’s password.
· The system’s back-end servers shall only be accessible to authenticated
administrators.
· Sensitive
data will be encrypted before being sent over insecure connections like the
Internet.
Availability
The system should be available at all times,
meaning the user can access it using a web browser, only restricted by the down
time of the server on which the system runs. In case of a hardware failure or database
corruption, a replacement page will be shown. Also in case of a hardware
failure or database corruption, backups of the database should be retrieved
from the server and saved by the administrator. Then the service will be
restarted. It means 24 X 7 availability.
Performance
The software
shall be based on the web and has to be run from a web server. The software shall
take an initial load time depending on internet connection strength which also
depends on the media from which the product is run. The performance shall
depend upon the hardware components of the client/customer.
Maintainability
A commercial database is used for maintaining the
database and the application server takes care of the site. In case of a
failure, a re-initialization of the program will be done. Also the software
design is being done with modularity in mind so that maintainability can be
done efficiently.
Performance
and Scalability
Scalability
accesses the highest workload under which the system will still meet the
performance requirements.
Reliability
The system provides storage of all databases on redundant computers with automatic switchover. The reliability of the overall program depends on the reliability of the separate components. The main pillar of reliability of the system is the backup of the database which is continuously maintained and updated to reflect the most recent changes. Thus the overall stability of the system depends on the stability of the container and its underlying operating system.
Portability
The application is HTML and scripting language based. So The
end-user part is fully portable and any system using any web browser should be
able to use the features of the system, including any hardware platform that is
available or will be available in the future. An end-user is using this system on
any OS; either it is Windows or Linux.
Usage Scenarios:
|
Use
Case Title |
Approve
Seller |
|
|
Use
Case Id |
UC-01 |
|
|
Description: Admin can view all the register seller into the system.
Admin can approve the registration request of the seller. |
||
|
Pre-Conditions: 1. Seller must
have registered into the system 2.
Admin login into the system |
||
|
Task
Sequence |
Exceptions |
|
|
1.Click on seller button |
System may show authorization
exception |
|
|
2.System will show seller record |
|
|
|
3.Click on approve/ reject button |
|
|
|
Post Conditions: - Sellerapproved
successfully. - Seller will be
able to login into the system |
||
|
Author:Your Id |
||
0 Comments