Scribd
Upload
84 views4 pages

Functional Requirements

This document outlines the functional and non-functional requirements for an online social networking system. It describes 5 main functional requirements: 1) Sign up/Sign in, 2) Recharge card and view transaction details, 3) Buying tickets, 4) Reporting a lost card/applying for a new card, and 5) Admin functions. It also describes 7 non-functional requirements: 1) Correctness, 2) Usability, 3) Portability, 4) Availability, 5) Efficiency, 6) Performance, and 7) Reliability.

Uploaded by

HRiSHiKESH MiSHRA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
84 views4 pages

Functional Requirements

This document outlines the functional and non-functional requirements for an online social networking system. It describes 5 main functional requirements: 1) Sign up/Sign in, 2) Recharge card and view transaction details, 3) Buying tickets, 4) Reporting a lost card/applying for a new card, and 5) Admin functions. It also describes 7 non-functional requirements: 1) Correctness, 2) Usability, 3) Portability, 4) Availability, 5) Efficiency, 6) Performance, and 7) Reliability.

Uploaded by

HRiSHiKESH MiSHRA
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1.1.

Functional Requirements
R: Online Social Networking System R1: Sign up/ Sign in

Description— New users who wish to create a new account have to sign up. Existing
users
have to just login.

R1.1: Create new account


Input: Enter name, surname, mobile number, email address, password, date
of birth, gender. Agree to terms and conditions.
Output: Account created prompt is displayed and verification link is sent to mail
and contact number. Error message is displayed if any filled detail is wrong.

R1.3: Log in
Input: Email or phone number and password. Click on log in.
Output: Open home page of user. Send email to user if log in is done from a new
device.
R1.3.1: Forgot password
Input: Click forgot password.
Output: The reset mail is sent to the user’s email id.
R2: recharge card of details of transaction
Description— user can recharge there card and see details of their deduction

R2.1: recharge card

Input: enter details of card and the amount for


recharge Output:payment completed or error message

R2.2: Settings
Description— User can change password or email.
R2.2.1: Change email or password
Input: Enter old email/password and new email/password.
Output: Apply the respective changes and send confirmation mail to user.

R2.3: details of transaction


Input: input the details of the card
Output: shows the all the translation of card
R3: buying ticket
Description— user can buy ticket for the metro
R3.1: search for destination
Input:enter name of destination station
Output:show the list of destination station with similar
name
R3.2: payment for ticket
Input: enter the card details
Output:ticket booked collect for vending machine

R4:Report for lost card/apply for new card Description—


Allows users to rate and/or review a movie.
R4.1: report for lost card
Input: enter the details of lost card
Output:lost card reported

R4.2: apply for new card


Input: give details of new card like name and address etc
Output: request for new card is been sent

R5: Admin functions


Description— Admin can accept request for new card or block cards ,
R5.1: accept the request for new card
Input: select the user to accept the request for new card
Output:new card generated
R5.2:blocks card
Input: give the card details and reason for blocking
Output: card blocked successfully
1.2. Non-Functional Requirements

3.3.1. Correctness Requirement


This software performs accurately as intended and in no other way.
3.3.2. Usability Requirement
The software has a simple but efficient user interface, which can be used by all types
of users, both technically sound as well as people not having so much knowledge
about technology. So, any user can use its functionalities without any sort of
complications.
3.3.3. Portability Requirement
This software provides a web based interface to the user. Any device with latest
stable browser will be able to run this software if they have JavaScript enabled and
Cookies enabled.
3.3.4. Availability Requirement
The software will be available 24/7. Moreover, the software would be available on
internet.
3.3.5. Efficiency Requirement
The software is highly efficient and various tasks in its various modules and sub-
modules can be performed simultaneously.
3.3.6. Performance Requirement
The database can accommodate high number of users and data without any fault. As
the latest technologies have been used, so the system would be very responsive and
the response would be extremely fast.
3.3.7. Reliability Requirement
The system is extremely reliable as there are proper measures to protect the data of
the users. Proper firewall and other security measures have been used to prevent any
kind of breaching. The software stores no personal data from the user.

.
.

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