Embedded Files
8.3. Social impact: identify any potential hazards in the proposed design, e.g., disposal after the useful life has ended
If any data has been collected, a potential hazard could be mishandling or improperly securing data, resulting in private information being leaked after the useful life of the application. This can be usernames, passwords, user preferences, etc.
Since the design is digitally based, software packages may need to be replaced or new ones can be added. This can result in a lot of software bloating within the application if the older or deprecated softwares are not handled frequently.
If the API used by the current service requires money/call, we should try to limit the amount of calls made to this API because if it keeps fetching every time, a very large bill can be generated.
9.3. Social impact: provide solutions to eliminate hazards identified in Assignment 8.3, e.g., disposal after the useful life has ended
Clearing out our cache and deleting user information once our useful life has ended may prevent data leakage as we will no longer have to worry about security upkeep of the data
Consistently updating software packages as new ones are introduced, deleting older and deprecated softwares to prevent bloating.
Calls should only be made once the user confirms a set of actions, so as not to generate a large bill through the use of several calls.
Page updated
Report abuse