At the beginning of this project the primary users of this application came from the EU to New York to show and tell us what they needed. Business and IT had already documented requirements extensively and it was clear that they were trying to speak to each other. To my fortune, and hopefully to theirs as well, I had to ask many questions to understand both the business needs and, frankly, the basics of trading, including the many product types and strategies involved in trading around the world.
Thankfully the IT group knew enough, after buildling something similar twice before, they quickly taught this guy (me) about trading, and then how to translate the new business requirements which included user-defined holding rules (worldwide aggregrations) and subsequent user-defined thresholds for triggering alerts, into an interface that allowed the compliance officers to manage those rules and thresholds in addition to user entitlements.
The site map was always a work in progress, serving both as a means of defining scope and of structuring the application, at least conceptually. Items that are struck out were determined to be part and parcel of another component of the system.
The annotations detail the reasoning behind naming Holding Rules Definitions (HRD), their status, the related Threshold Rule (TR) that tripped the alert, among other columnar data.
Upon clicking the name/title of the HRD, an overlay displays details on the alert. In the next wireframe the user is able to act upon the alert by whatever means will keep the institution in compliance with regulations.
Several selectors in Holding Rules Definitions (HRD) feature large sets of menu items that may be classified by category and sub-category. The item lists may also be long enough to warrant a search facility. The wireframe above demonstrates the multiple means by which searching and selecting is possible inside a single drop-down menu.
