Non-Functional Requirements
3.4.1 Usability Requirements
- Our user interface should be interactive simple and easy to understand . The system should prompt for the user and administrator to login to the application for proper input criteria.
- Weather Application shall handle expected and non expected errors in ways that prevent loss in information and long downtime period.
3.4.2 Security Requirements
- System should be using secure web forecasting API.
- Normal users can just read information about the weather but they cannot edit or modify anything except their personal and some other information if required.
- System will have different types of users and every user has access constraints.
- Proper user authentication should be provided.
- Personal details like location should not be stored for security purpose.
3.4.3 Availability Requirements
Availability requirements for a weather application using APIs are crucial to ensure that the service is consistently accessible and operational.
Here are key availability requirements:
- Uptime Percentage: Maintain a high level of service availability, such as 99.9% uptime. Users rely on the weather application for real-time information, so a high uptime percentage ensures that the service is consistently accessible.
- Load Balancing: Use load balancing to distribute incoming traffic across multiple servers or instances. Load balancing helps distribute the load evenly, preventing individual servers from becoming overwhelmed and improving overall system performance and availability.
- Monitoring and Alerting: Implement continuous monitoring of key metrics and set up alerting systems to notify administrators of any issues or anomalies. Proactive monitoring allows for the rapid identification and resolution of potential problems, minimizing downtime.
- Scalability: Design the system to be scalable, allowing for the seamless addition of resources during periods of increased demand. Scalability ensures that the application can handle varying levels of traffic and user activity without degradation in performance.
- Backup and Recovery: Regularly back up critical data and implement robust recovery procedures. In the event of data loss or system failures, a well-defined backup and recovery strategy ensures that the application can be restored quickly and efficiently.
3.4.4 Performance Requirements:
- The system shall accommodate high number of users simultaneously and users can check the weather of any location any number of times.
- Responses to view information shall take no longer than 5 seconds to appear on the screen.
4.5.4 Error Requirements:
Weather app shall handle expected and non-expected errors in ways that prevent loss in information and long downtime period.
An alert should be shown if the API is not working properly which will improve the uptime of the service.
Weather Forecast Project
Weather Forecasting Application is one of the most common mini project in Software Development . In this article, we are going to make a Weather Forecasting Application from scratch which will tell us the weather of any location using its name . We will be covering all the steps you have to do while developing this mini project. The title of our project will be Todays Weather App.
Weather Forecasting Project
Before Diving into the Implementation of the Project Let us look into the End Result of our project. Its Features and Functionalities: