For each of the above four types of nonfunctional requirements, please post one

Question

For each of the above four types of nonfunctional requirements, please post one or more example statements of what you believe CWU should require for MyCWU. Here are some examples to get you thinking:

Usability: The browser-based version of MyCWU shall use an internally consistent user interface style throughout, which is additionally consistent with the user interfaces students utilize with the most popular browser-based applications. [Also give reasoning here.]

Reliability: If and only if a transaction appears to the user to have completed, that transaction shall indeed have been completed in the database. [Also give reasoning here.]

Performance: The turnaround of a transaction between arrival at the server and response from the server even under high-peak processing loads shall only exceed 5 seconds 1% of the time. [Also give reasoning here.]

Security: The user's browser shall not cache private or hack-enabling information in the user's non-volatile storage, and shall assure any such information does not remain in the user's volatile memory after MyCWU is closed -- without reliance on the user to close the browser. [Also give reasoning here.]

Make sure your reasoning explains both why this requirement is needed and why you believe it will be cost effective. (E.g., 100% uptime as a reliability requirement is very expensive.) You do not need to quantify the benefit or cost, just explain your belief that meeting your requirement will save considerably more in dollars and/or user suffering than implementing it will cost.

Explanation / Answer

Reasoning out why the requirement is needed and why it is believed to be cost effective:

1) Usability: The browser-based version of MyCWU shall use an internally consistent user interface style throughout, which is additionally consistent with the user interfaces students utilize with the most popular browser-based applications. [Also give reasoning here.]

Users are the key for any application as they are the ones who ultimately browse and navigate. Having an internally consistent user interface style would mainly help in eliminating too much learning and confusion among the users. Thus, it would enable smooth experience, which plays a main role in achieving the intended purpose of the application. Having a non-consistent UI style would lead to non-friendly application, thus reducing the number of users.

2) Reliability: If and only if a transaction appears to the user to have completed, that transaction shall indeed have been completed in the database. [Also give reasoning here.]

Reason:

Reliability refers to the extent to which the application is consistent.

When an user performs a transaction, he/she expects the application to move from one consistent state to another. The transactions should be performed in a way that the user expects and the application is designated to. If not, it would be faulty and recovering the application back to the original state could be very tedious and may involve huge cost along with difficulty involved.

3) Performance: The turnaround of a transaction between arrival at the server and response from the server even under high-peak processing loads shall only exceed 5 seconds 1% of the time. [Also give reasoning here.]

TurnAround Time(TAT):

TAT refers to the time between the arrival at the server and response from the server. In other words, it is the time taken to fulfil a request. It depends on memory needed, execution time, resources needed, etc.

Reason:

TAT is one of the metrics for determining the efficiency of an application. Less TAT indicates that the application is able to handle more number of requests, which is a sign of high efficiency. Also, if the TAT is high, it may lead to dissatisfaction from the users and would reduce the number of customers. In the dynamic world, nobody wants to wait for the results. Hence, it is a much needed requirement which would help in achieving the objectives and reducing the cost.

4)  Security: The user's browser shall not cache private or hack-enabling information in the user's non-volatile storage, and shall assure any such information does not remain in the user's volatile memory after MyCWU is closed -- without reliance on the user to close the browser. [Also give reasoning here.]

How browser cache works?

Browser stores the contents of the downloaded files in a temporary storage called cache. When a website is visited, the browser compares the contents with the cache and downloads the file only if the content is not present already or if it got updated.

What is non-volatile memory?

Non-volatile memory represents the secondary storage, which means the contents of the memory are preserved even after the computer is shut down.

Reason:

Hence, if the browser caches the private or hack-enabling information and if the information remains in the user's non-volatile storage, it would lead to security threats if the user revisits the corresponding website again, since the contents are loaded from cache. Based on the information, such security threats could be highly risky and the cost to repair/restore could be based on the impact of the security threats.

Related Questions

Navigate

• Browse (All)
• Browse F
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.