Use case 21: NoSQL Database Schema Design for User Account

[VictorKwong]

NoSQL Database Schema Design for Data

User Story

As a backend developer, I want to design and implement a NoSQL database schema to store data efficiently so that users can log in to their accounts accurately.

Description

This use case involves designing a NoSQL database schema to store user account and password data registered from a live website. The schema should be optimized to handle large amounts of data efficiently over time and include appropriate indexing to ensure quick and reliable data retrieval.

Acceptance Criteria

• [ ] A NoSQL database schema is created to store sensor data, with fields for user account and password
• [ ] The schema supports efficient storage and retrieval of time-series data.
• [ ] The schema is implemented in a NoSQL database (e.g., MongoDB).
• [ ] Indexes are added to optimize performance for querying real-time and historical data.
• [ ] Sample data is inserted into the database to test the schema's performance and data retrieval.

Testing

Normal Flow of Events

The backend developer designs a database schema using a NoSQL database (e.g., MongoDB). A user account can be registered/stored in the database with timestamps. A user account can log in and retrieve their data from the NoSQL database.

Alternate/Exceptional Flows:

S-1: Schema does not support efficient querying

The schema is inefficient for querying large datasets, leading to slow response times. The developer refines the schema or adds appropriate indexing to improve query performance.

S-2: Data insertion errors

Account data is not correctly inserted into the database due to missing fields or incorrect data types.

[VictorKwong]

User can register and login into their account to view their data. They cannot view any sensitive information (such as sensor data) when they are not authorized.