Functional Requirements

Part of General Document Zone (v0.1.0) last public on August 5, 2023 at 12:00 AM UTC. You may see previous version(s) of the zone.

Below are functional requirements to be implemented to make a Kotovaulo system. The non-functional requirements may depend on the language or framework used.

Prerequisites

Readers are assumed to have the ability to create REST APIs to perform CRUD operations.

Main Requirements

These requirements must be implemented and dictates the overall direction of the project.

  1. The system may receive the following account data from the user:
    • Platform name
    • Account identifier of the user (i.e. email or username)
    • Associated password of the account
    • Other data associated with that account
    • Delegating platform name
    • Delegating identifier
  2. The server must encrypt the sensitive details in main requirement #1 before storing in a database.
  3. Clients should allow users to connect on different servers one at a time.

Notes

Should there be changes in the main requirements, functional specification may be affected.

Optional Requirements

These requirements have low priority compare to main requirements.

  1. The system has the ability to sync with other devices as long as permitted. Transmission should be encrypted.
  2. The system can receive new credentials from other servers.
  3. User should be able to export his/her encrypted credentials upon request and import them to another device.

Origin

Some contents of this document came from the server variant A’s blueprint.

Previous versions

There are no previous versions yet. Check back in the future.