User management and data persistence

Milestone 8

Summary

In Milestone 8 we developed a Data Base Management System intended for storing and retrieving the users data while having security measures intact. Storage will be ensured through a local file where it will be directly stored independent of other files and easily edited. Furthermore a remote database management system will be in place where remote connection between a database client and a database server will be maintained. Also users will be able to register new account and sign-in with their registered account where the system will check for validity.

Highlights

• Remote database access for users and Mission Control
• Local file based data persistence that is easily edited by users
• Users are able to register new account and sign-in with their registered account
• System will automatically check for duplicate usernames and validity

Description

Database Management Systems will help the user share data more quickly and efficiently across the platform. Making accessing data faster and more accurate. With a higher degree of precision. Features restricted to authorised users where they can add new data to the database while also updating present data and deleting data that have become obsolete. Offering a high level of flexibility for the user.

Having a local file system in place will enable initial set up information to be easily edited by users. It will allow access to single files at a time. Here the data is directly stored in a set of files that have no relation to other files. Also having remote Database Management System is used for exchanging information between client to server. Granting access to authorised personell with a high layer of security intact.

Functional requirements:

• Local file based data persistence so that initial setup information can be easily edited by users
• Remote DBMS system config information is also needs to configured in the local config file
• Users can register new account and sign-in with their registered account
• System needs to check whether duplicate username exists
• Present mission templates and user mission data is stored remotely

Non-functional requirements:

• Settings page will be one of the main defining UI aspects of this milestone
• Remote DBMS contain user data, mission data and certain settings that can be stored remotely
• Users can choose their desired usernames based on generic requirements
• Users can choose to not to enter their email address
• Database import file should be delivered as part of the initial setup packages