Back to problems

Track Repeated Approval Alerts and Safely Update Alert Levels

Object-Oriented Programming · Ziphq · Hard

You are asked to extend an existing work-order approval system with a cached mechanism that observes repeated alert events and rejects the order once a count-based condition is met. The extension must also allow an alert's level to be modified after it has been recorded. Before proposing a concrete design, you must identify and pin down the unspecified business rules: what the cache key is, what threshold triggers rejection, what time window or expiry applies, how alert…

Checking your access…