Srs Book Bank

187
srs
srs (software requirments specifications)

SRS Book Bank

The Book Bank will be an android application that assists users in reading, buying, and selling books. The purpose of this app is to make reading books convenient. It provides free access to some books for reading. You can sign up for access to the books you want. This app allows users to sell their books. You can search for specific books based on your preferences. Users can also earn money by selling their books. Users are able to carry all their books in one app. It is suitable for all types of users. Users can get rid of the burden of carrying books. With this app, you can read and buy all kinds of books.


 

Scope of Project Book Bank:

Project scope is the part of project planning that involves determining and documenting a list of specific project  goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target

Functional and Non Functional Requirements of Book Bank:

Functional Requirements :

A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs

Functional Requirements of Book Bank:

1. The login system for each user (Admin, Buyer, Seller, and Visiting User) shows its
dashboard correctly with appropriate functionality. Buyers and Sellers can register through
signup.
2. Seller can add details of a book with price tags and descriptions.
3. Buyer can add books to their shopping cart for buying.
4. Buyers and sellers can use the search to find books.
5. A limited number of pages are available for the reading session of all books.
6. Admin can check the details of the books as well as demand and supply.
7. Payment methods such as (Credit/Debit Card, Cash on delivery) are available for purchasing.

 

NON-FUNCTIONAL REQUIREMENTS Book Bank:

  • Application is user friendly.
  • Application Perform fast manipulation and calculations.
  • Application is adaptable.
  • Application will be able to work on all types of operating systems.
  • Application will be capable to handle multi user activities simultaneously.
  • There will be back up system to face any problem in system
  • All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
  • Response Time is very awesome.
Some others are:
  • Accessibility
  • Maintainability
  •  Fault Tolerance.
  • Security
  • Robustnes



 

Use Case Diagram of Diagnosis of Book Bank

a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve



 

 

Usage Scenarios Diagnosis of Book Bank:

A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.

 

ADOPTED METHODOLOGY for Book Bank:

The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.



 

Work Plan of Diagnosis of Book Bank:

Work plan



for complete srs contact us

watsapp: 03469806607