Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product.
Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use.
Define any safety certifications that must be satisfied. Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product.
Define any user identity authentication requirements.
TODO:
Provide safety/security requirements based on your interview with the client - again you may need to be somewhat creative here.
At the least, you should have some security for the mobile connection.
For Example:
NFR5: Data transmitted from and received are always encrypted with AES-128.
NFR6: All approving roles must use a different factor of authentication from the user authentications (on top of 2FA) for approval processes.
Description:
TODO:
For Example:
NFR5: Data transmitted from and received are always encrypted with AES-128. NFR6: All approving roles must use a different factor of authentication from the user authentications (on top of 2FA) for approval processes.