Add in appendix effort and make some changes

docs/DeveloperGuide.md

@@ -602,20 +602,17 @@ testers are expected to do more *exploratory* testing.
 
 1. Saving window preferences
 
-   1. Resize the window to an optimum size. Move the window to a different location. Close the window.
+   1. Window size is automatically scaled strictly to a 16:9 ratio and **saved** upon start up. It will not be resizable.
 
-   1. Re-launch the app by double-clicking the jar file.<br>
-       Expected: The most recent window size and location is retained.
-
-1. _{ more test cases …​ }_
+   1. If you are using a screen of a different size, delete the `preferences.json` file and run BayMeds again.
 
 ### Deleting a medication
 
 1. Deleting a medication while all medications are being shown
 
    1. Prerequisites: List all medications using the `list` command. Multiple medications in the list.
 
-   1. Test case: `delete 1"`<br>
+   1. Test case: `delete 1`<br>
       Expected: Aspirin is deleted from the list. Details of the deleted medication shown in the Result Display.
 
    1. Test case: `delete 9`<br>
@@ -624,15 +621,14 @@ testers are expected to do more *exploratory* testing.
    1. Other incorrect delete commands to try: `delete`, `delete x`, `...`<br>
       Expected: Similar to previous.
 
-1. _{ more test cases …​ }_
-
 ### Saving data
 
 1. Dealing with missing/corrupted data files
 
-   1. _{explain how to simulate a missing/corrupted file, and the expected behavior}_
+   1. To simimulate a corrupted file, feel free to edit the data inside `data/prescriptionList.json` and `data/CompletedPrescriptionList.json`. You may change the format entirely, or input an invalid value for one of the fields.
+
+   1. By design, if there are issues with the stored data files, BayMeds will begin with an empty prescription list.
 
-1. _{ more test cases …​ }_
 
 --------------------------------------------------------------------------------------------------------------------
 
@@ -647,3 +643,14 @@ Given below are known issues and planned enhancements in the future.
 1. **When adding prescriptions**, if you name your prescriptions with numbers "1", "234" or "4 5 6", BayMeds will add this prescription as per normal. As these names do not properly identify the exact prescription stored in BayMeds, we will implement a fix for this in the future.
 1. **When taking prescriptions**, we will implement a feature that automatically reminds you when it is time to eat your medication.
    <br></br>
+
+--------------------------------------------------------------------------------------------------------------------
+
+## **Appendix: Effort **
+
+Given below documents the tremendous efforts put in by each and every member of the BayMeds team.
+
+We implemented a combined total of 14 command features in BayMeds, to ensure that users have a comprehensive way to interact with their prescription lists. Apart from the basic functionalities of adding, deleting, editing and listing prescriptions, we have also expanded the product with several features. Users can find prescriptions easily either by keyword, or those that they have to consume today. Users are also able to view a list of completed prescriptions. We have also implemented the underlying logic infrastructure to faciliate the tracking of conflicting drugs. We have also added filtering functionalities that filter prescriptions that are running low in stock or about to expire.
+
+Apart from command related features, we have also implemented implicit features, such as the automatic resetting of the consumption count.
+