Skip to content

Project SRS

Jump to bottom
Salekur Rahaman edited this page Mar 8, 2020 · 5 revisions

View Project SRS

Download Project SRS

Chapter 1: Introduction

Nowadays, Bachelor are facing a lot of problems in their everyday life. Bachelor app helps them to solve their problems and makes their life easier.

1.1 Purpose:

So our aim is to create Bachelor app that can manage bachelor’s Meal System, their Daily Task, Communication with grouped people and Online Shopping service.

1.2 Intended Audience

  • Developers
  • Bachelors

1.3 Intended Users

Developers:

  • Developers who can improve the app
  • Add more features
  • Remove some features
  • Review project capabilities and so on.

Bachelors:

  • Can give everyday meal input when he/she want their meal
  • Can send money to others bachelor within their group
  • Can check their account balance in meal group
  • Can check the details of every transaction in real-time

1.4 Product Scope

We are going to help bachelors through this app. And have some business goals too. We are going to build this app in som unique way. We will keep some dynamic features that will grab the bachelors to use our app. Bachelor can get some unique and efficient features that make their life easier. It has so many advantages such as,

  1. Bachelor Meal: This will be the main function of our app. It can calculate the amount of Meal, Meal Rate, Total Meal Cost of a single person, update about every Meal and Transactions.

  2. Daily Task Schedule: This function will help bachelors to notify their tasks like class time, exam time, mealtime, etc.

  3. Communication: Bachelor can send friend requests and make friends. Also, they can chat with their friends.

  4. Shopping: Bachelors can sell and buy their useful things by using this app.

1.5 Risk Definition

The following will be the risk involved in this project: People are already using some similar app and websites. So what be the real cause that would motivate bachelors to use our app.

  • If there any transaction error occurs then the user can review.
  • They can able to know instant transaction notification.
  • It will show their schedule and also notify.
  • It will keep their personal data private.

Chapter 2: Overall Description

2.1 User Classes and Characteristics

In our system, the ultimate control will be a hand of three users and they are,

  1. Product Owner
  2. Developer
  3. Users (Bachelors)

2.2 User Needs

Bachelors: Bachelors have so many calculations on their daily meals and life, after all, they have to wait for the end of the month to get an actual calculation, so they need to do it in real-time and every day. They need the details of every transaction on their daily expenses to maintain their bachelor's life. They need to communicate with their friends and family. They need to remind their daily task to get time to work in proper time like assignments, classes, exams, etc. They need to find jobs or works. They need online shopping where they can easily get their products.

2.3 Operating Environment

Our product is basically an android app so that only android users can use our product. For our database system, we will use firebase hosting to host our app.

2.4 Constraints

  • Technical constraints:
  1. Users must be Android user, our app does not support other operating systems.
  • Business constraints:
  1. Budget and time restrictions.
  2. Resource limitations.

2.5 Assumptions

  • Users know English.
  • Users have internet service.
  • User’s device supports internet service.

Chapter 3: Requirements

3.1 Functional Requirements

As a user:

  • I want to manage my meal system. So that, I can calculate the amount of my meal, meal rate, total cost, updated information about meal and transaction.
  • I want to give my opinion on food selection.
  • I want to change meal input on emergency cases.
  • I want to see meal menu.

Acceptance:

  • User has to put about meal as a input.
  • User has to keep a minimum balance to get the meal.
  • User has to submit their meal input on time.

As a user:

  • I want to communicate with other bachelors. So that I can share all my opinions among other bachelors.

Acceptance:

  • The user has to send a friend request through this app to make a group.

As a user:

  • I want to get notifications about my important task.

Acceptance:

  • User need to connect google account to access tasks from google calendar.
  • User has to put the date and the exact time as an input.

As a user:

  • I want to sell and buy some products. So that other users can be benefited from my product and vice versa.

Acceptance:

  • The user who wants to sell the product he/she has to upload a picture of his/her product.
  • User has to mention the price

3.2 Non Functional Requirements

Users Safety:

  • Session log out on changing device
  • Backup data so damage or crush data can be recovered
  • Encrypted password and secure payment

Customer Support:

  • Documentation
  • Complain / Feedback
  • Live Chat

In-App Service:

  • Forget Password / Password Reset
  • Email Verification

Chapter 4: Appendices

Chapter 5: Glossary

  • SRS: A software requirements specification (SRS) is a comprehensive description of the intended purpose and environment for software under development.
  • B. Meal: Bachelor Meal.
  • B. Chat: Bachelor Chat.
  • B. Shop: Bachelor Shop.
  • B. Task: Bachelor Task.

©2020, All right reserved by Bachelor.

Clone this wiki locally