0% found this document useful (0 votes)
13 views7 pages

Features of Pwerpal

SRS doc of My app PowerPal The Electricity Companion

Uploaded by

hbnasir2023
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)
13 views7 pages

Features of Pwerpal

SRS doc of My app PowerPal The Electricity Companion

Uploaded by

hbnasir2023
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/ 7

DESCRIPTION OF THE PROJECT

NED UNIVERSITY OF ENGINEERING AND TECHNOLOGY


DEPARTMENT OF SOFTWARE ENGINEERING
SOFTWARE DESIGN AND ARCHITECTURE
COURSE CODE: SE-308
SRS DOCUMENT

GROUP N0:16

NAME ROLL NO
SYED MUHAMMAD RAYYAN SE-23067
HARIS BIN NASIR SE-23084
AMMAR BIN AMIR SE-23098
SHAZAIB DAR SE-230101
LAIBA MAJEED SE-23302

Page 41
DESCRIPTION OF THE PROJECT

FEATURE 1:USER SIGNUP AND LOGIN


Functional Requirements:

F1.1 The user must select their user type (Residential or Industrial) before proceeding.
F1.2 The user must enter a valid consumer number and account number.
F1.3 The system should verify the consumer and account numbers by connecting to the KE database and checking
their validity.
F1.4 After successful verification, the user must provide a valid email address for account creation.
F1.5 The system should send a verification link to the provided email, which the user must click to confirm their
account.
F1.6 After email verification, the system should prompt the user to create a password following predefined
complexity rules (e.g., minimum of 8 characters, with at least one uppercase letter, one number, and one special
character).
F1.7 The system must generate an authentication token for secure user sessions upon account creation.
F1.8 The user should have the option to enable two-factor authentication (2FA) via SMS or email for added security.
F1.9 Users can log in using their email address and password after account creation.
F1.10 The system must allow users to log out securely from any session.
F1.11 If the user forgets their password, the system must provide a password recovery option by sending a reset link
to their email.

Non-Functional Requirements:

NF1.1 The system must use encrypted communication (e.g., SSL/TLS) for all user data, including consumer numbers,
account numbers, and passwords.
NF1.2 Passwords must be hashed before being stored in the database, using strong algorithms like bcrypt or Argon2.
NF1.3 The system should verify consumer and account numbers with the KE database within 3-5 seconds.
NF1.4 Email verification must occur within 30 seconds of submission.
NF1.5 The system must ensure 99.9% uptime for reliable access to authentication services.
NF1.6 The system should scale to handle large numbers of users signing up or logging in simultaneously.
NF1.7 The user interface for signing up, email verification, and password creation must be intuitive and easy to use.
NF1.8 If the consumer or account number is invalid, a clear error message should be displayed to the user within 1
second.
NF1.9 The system must provide appropriate feedback for failed verifications, incorrect passwords, or invalid tokens
during login.

FEATURE 2: Energy Consumption Tracking

Functional Requirements:
F2.1 The system should be able to track energy consumption in real time.
F2.2 It should store historical energy consumption data for future analysis.
F2. If energy consumption exceeds a predefined threshold, the system should trigger an alert.
F2.5 Users should have a dashboard where they can view their current and historical energy usage in graphical form.
F2.6 The system should be able to calculate the cost of energy consumed based on the given formula.

Non-Functional Requirements:
NF2.1 The system must ensure high accuracy (95% or more) in energy measurement.
NF2.2 Real-time updates should be displayed within 10 mins of consumption change.

Page 42
DESCRIPTION OF THE PROJECT
NF2.3 User data, including energy usage, must be protected through encryption and secure access control.
NF2.4 The system should have a 99.9% uptime to ensure continuous tracking.
NF2.5 The system should work with a wide range of smart appliances and energy meters.

FEATURE 3: Bill Management

Functional Requirements
F.3.1 The app will display current and past electricity bills.
F.3.2 The app will allow users to view detailed breakdowns of their bills, including consumption of electricity, taxes
and extra charges.
F.3.3 The app will allow users to pay their bills using multiple payment methods like credit card, bank transfer,
easypaisa, etc.
F.3.4 The app will notify users of upcoming bill due dates and overdue payments via notifications.
F.3.5 The app will allow users to download their bills in PDF format for record-keeping.

Non-Functional Requirements
NF.3.1 Payment processing should be completed within 5 seconds to provide users with a seamless and efficient
experience.
The app will support secure payment gateways and comply with PCI-DSS standards for handling payment
information.
NF.3.2 The app will have a 99.9% availability uptime to ensure reliable access to bill information and payment
services.
NF.3.3 Notifications for upcoming due dates or overdue bills will be sent within 30 seconds of the event trigger,
ensuring timely alerts for users.
NF.3.4 The app will store billing data in an encrypted format to ensure data privacy and security.

FEATURE 4: Predictive Energy Analysis

Functional Requirements
F.4.1 The app will look at users' past energy use and give personalized tips to help them save energy.
F.4.2 The app will estimate future energy bills based on current usage.
F.4.3 The app will allow users to compare their current energy consumption with previous periods (daily, weekly, or
monthly).

Non-Functional Requirements
NF.4.1 The app will process and display predictive energy analysis results within 2 seconds of user interaction.
NF.4.2 The app will use secure data encryption method to protect user’s past energy-use data to ensure privacy.
NF.4.3 The app will show predictions in a simple, easy-to-read way using charts and graphs.
NF.4.4 The app will run predictive energy analysis quickly and use minimal battery power on devices.
NF.4.5 The app will provide updates to the predictive analysis feature without interrupting the user experience.

FEATURE 5: Power Quality Monitoring

Functional Requirements:
F5.1 Voltage Monitoring: The system should monitor the voltage levels to detect under-voltage or over-voltage
conditions.
F5.2 Frequency Monitoring: It must track the electrical power frequency to ensure it stays within specified limits
(e.g., 50/60 Hz).
F5.3 Harmonic Distortion Detection: The system should be able to detect harmonic distortions that may affect power
quality.
F5.4 Event Logging: It should log events such as power sags, surges, and interruptions for diagnostic purposes.
F5.5 Alert System: If power quality metrics exceed predefined safety or efficiency limits, users should be alerted.
Page 43
DESCRIPTION OF THE PROJECT
F5.6 Report Generation: Generate periodic reports (e.g., daily, weekly) on power quality metrics and anomalies
detected.

Non-Functional Requirements:
NF5.1 Accuracy: The system must detect and report power quality issues with at least 98% accuracy.
NF5.2 Latency: Power quality data should be updated in real-time with minimal latency (less than 1 second).
NF5.3 Scalability: It should support many devices and locations for power quality monitoring.
NF5.4 Reliability: The system must operate 24/7 with minimal downtime (99.99% uptime).

FEATURE 6: CUSTOMER SERVICE


Functional Requirements:
F.6.1The app will verify user authentication before providing services like maintenance, repair, and new connections.
F.6.2 The app allows users to schedule service appointments by selecting the service type, date and time.
Additionally, it provides users with the history of previous appointments with key details like service type, date, time
and status.
F.6.3 The app will send confirmation message to user on successful appointment scheduling via SMS, EMAIL or the
APP.
F.6.4 The app must provide the client with a tracking service for keeping track of each request (acknowledged, in
progress, or completed).
F.6.5 The app offers a live chat feature that connects users with supportive representatives, ensuring a complete
understanding of their problems and providing real-time, personalized assistance.
F.6.6 The app maintains high integrity to manage requests from multiple clients and ensure timely scheduling for
each request.
F.6.7 The app provides users with a contact option for emergency repairs.

Non-Functional Requirements:
NF.6.1 The user authentication must be secure with support for 2 factor authentications.
NF.6.2 The app must respond to service requests promptly (within 1-2 seconds).
NF.6.3 Ensure high scalability to handle many users and requests simultaneously.
NF.6.4 The user interface should be intuitive and easy to navigate to avoid service delays.
NF.6.5 Service request data should be encrypted both when it is stored and while it is being transmitted.

Page 44
DESCRIPTION OF THE PROJECT
Domain Requirements
Formula for Bill Calculation:
The application will utilize the following formula to calculate the total electricity bill for users:
Total Bill = (On-Peak Units × On-Peak Rate) + (Off-Peak Units × Off-Peak Rate) + FCA + Quarterly Adjustment +
Additional Surcharge + MUCT(KMC) + TV Fee + Income Tax + Sales Tax

RESIDENTIAL USER:

Component Description/Rate

On-Peak Rate Based on consumption slabs:

- 0 to 100 units: 36.92 PKR/unit

- 101 to 210 units: 40.23 PKR/unit

- 211 to 400 units: 49.88 PKR/unit

- 401 to 600 units: 52.58 PKR/unit

- 601 to 800 units: 56.49 PKR/unit

- 801 and above: 59.37 PKR/unit

Off-Peak Rate Based on consumption slabs:

- 0 to 100 units: 36.92 PKR/unit

- 101 to 210 units: 36.92 PKR/unit

- 211 to 400 units: 38.27 PKR/unit

- 401 to 600 units: 40.37 PKR/unit

- 601 to 800 units: 42.57 PKR/unit

- 801 and above: 44.31 PKR/unit

FCA (Fuel Adjustment Charge) Varies monthly based on fuel costs.

Quarterly Adjustment Adjustments made quarterly based on actual consumption.

Additional Surcharge Applicable based on conditions set by the utility provider.

MUCT (KMC) 1000 PKR (fixed).

TV Fee 500 PKR (fixed).

Income Tax Based on total bill:

Page 45
DESCRIPTION OF THE PROJECT
- 4% for totals below 50,000 PKR.

- 6% for totals between 50,001 and 100,000 PKR.

- 8% for totals between 100,001 and 200,000 PKR.

- 10% for totals between 200,001 and 400,000 PKR.

- 15% for totals above 400,000 PKR.

Sales Tax 17% of the total bill.

INDUSTRIAL USER:

Component Description/Rate

On-Peak Rate Based on consumption slabs:

- 0 to 100 units: 24.61 PKR/unit

- 101 to 210 units: 26.82 PKR/unit

- 211 to 400 units: 33.25 PKR/unit

- 401 to 600 units: 35.05 PKR/unit

- 601 to 800 units: 37.66 PKR/unit

- 801 and above: 39.58 PKR/unit

Off-Peak Rate Based on consumption slabs:

- 0 to 100 units: 24.61 PKR/unit

- 101 to 210 units: 24.61 PKR/unit

- 211 to 400 units: 25.51 PKR/unit

- 401 to 600 units: 26.91 PKR/unit

- 601 to 800 units: 28.38 PKR/unit

- 801 and above: 29.54 PKR/unit

FCA (Fuel Adjustment Charge) Varies monthly based on fuel costs.

Quarterly Adjustment Adjustments made quarterly based on actual consumption.

Additional Surcharge Applicable based on conditions set by the utility provider.

MUCT (KMC) 100 PKR (fixed).


Page 46
DESCRIPTION OF THE PROJECT
TV Fee 35 PKR (fixed).

Income Tax Based on total bill:

- 0% for totals below 25,000 PKR.

- 7.45% for totals between 25,001 and 50,000 PKR.

- 15% for totals above 50,000 PKR.

Sales Tax 17% of the total bill.

Page 47

You might also like