TechLauncher
Our project comprises two inseparable parts: database and website. For the database branch, it is essential to implement the following functions:
- Protect customer privacy from leaking out
- Integrate the whole data related to the ordering procedures into the database for management and analysis Store client order specifications, metrology, and operational information Track costs and usages of materials and services Support documentation for future modifications
Details
- [Requirement] Must be secure against data breach and information theft.
- [User Story] The database contains sensitive info about the customers who take privacy seriously.
- [Importance]
- [Notes] Offline database for highest level of security
- [Requirement] Need a convenient way (identifier) to match customer company to the ones already in the database without confusions
- [User Story] John is a customer from Reflection Optics Inc. who orders a standard coating. On the webpage, when asked to type his company name, he might enter Reflection Optics Inc or Reflection Optics or ROI for short. The database needs to record this correctly in order to avoid mismatches and confusions.
- [Importance]
- [Notes] Using email domains; ABN or link to other validation system
- [Requirement] Must be able to minimize human errors when updating the databases
- [User Story] Deon wants to update the database with a new design. During the process, if Deon was asked to type the file name or other info by hand, there is always a possibility of misspelling because everyone makes mistakes. So the interactions and operations of the database software must minimize manual typing and checking.
- [Importance]
- [Notes] Automatically generate metadata of files and load info into database
- [Requirement] Must be flexible enough for staff to supplement new info later or add new designs or modifications
- [User Story] Johannes wants to experiment on new material for the customer, but not sure of the specifications right now. He can create a record in the database, and update and add more info later on to complete the design.
- [Importance]
- [Notes] Links to new design files; Tags/hashtags added manually when updating; Versions no. for different designs
- [Requirement] Must be searchable for easy lookup
- [User Story] Steve wants to check the percentage of a certain wavelength of all orders to optimize coating procedures. By searching for a wavelength keyword or type in a certain range, the database should show him the corresponded records.
- [Importance]
- [Notes] Using tags to manage records
- [Requirement] Need to figure out a way to sync between different nodes of computers across several labs, while preventing conflicts when multiple staff try to update record at the same period of time
- [User Story] Both Deon and Johannes are in charge of a new design, so they need to test the coatings in different labs and write in the database their own parameters. When Deon is updating the file, Johannes should not be able to change the same field to avoid conflicts.
- [Importance]
- [Notes] Perhaps utilising the Physics network; Using USB on local computer to copy data
- [Requirement] Must be able to prompt a warning banner to staff when his operations are incomplete or false
- [User Story] Deon just finishes updating the specifications of a new design but forgets to add the version number. The software needs to remind him of the lack of version field to complete the accurate update.
- [Importance]
- [Notes] Set up required fields that match primary keys in the database
- [Requirement] Key data in the database should only be accessed by staff in charge
- [User Story] Steve recruits a new intern to help him with the design, but the intern should not be able to change the key fields of the database right away until Steve thinks it is time and grants him a higher level account
- [Importance]
- [Notes] Different levels of authorizations to access database
- [Requirement] The data in the database needs to have regular back-up copies
- [User Story] Since many data will be stored in the local computer.What if the computer system crashes? Then all the data will be lost even if there is no data breach.
- [Importance]
- [Notes] Have a local back-up copy
- [Requirement] The interface needs to be user friendly
- [User Story] The development of the database must be based on the the users requirements and our clients wish it can be easy to use.
- [Importance]
- [Notes] Set up drafts of the interface during the design part and can be modified
- [Requirement] It will be better if the back-end doesn’t need the programmer maintence.
- [User Story] Steve wishes we can build the database that can be long term use without the techinical maintenance
- [Importance]
- [Notes] Do not put so many contributes in the main table to avoid the redundancy; The data base has to be flexible for future needs.
- [Requirement] Need to have a way to update the website database (once a day) to update client tracking data.
- [User Story] The staff Jack needs to be able to either schedule an automatic update or manually update the order status so that clients can track their orders from time to time.
- [Importance]
- [Notes]
- [Requirement] Must be easy to update the website database automatically when there’s new record in the main local database
- [User Story] When Deon types in a new order specifications and updates the main database, the website file should be able to update accordingly for the customers to track order status. For now, a daily sync is enough.
- [Importance]
- [Notes]
- [Requirement] Need to notify the administrator for the new update in the main database
- [User Story] Johannes/Steve/Deon needs supervise the design sometimes to ensure that the database is well maintained.
- [Importance]
- [Notes] A push notification may suffice