ASAP

Data aggregation and restructuring is a very important part of ASAP. Along with filtering and sorting user data, I have identified these as the most important places to focus during development.

For the design of the functions, graphs and user interface, I based the design on user requirements, methodological procedures and standardizations. The main user expectations were as follows:

• in the application you can create a tailor-made solution,
• the application can aggregate data from different sources in different structures and pass it on,
• the application will enable process automation.

The diversity of data and the interconnectedness of functions gave me many opportunities to automate the application, save users time and simplify their access to the information they need:

• monitoring of selected identifiers and their values,
• data categorization,
• analysis of opportunities and threats.

Along with this, risk areas became apparent that could invalidate the presented results:

• poorly chosen visual presentation of data,
• their inappropriate combination and low informative value,
• overwhelming the user with non-priority information.

ASAP is a turnkey solution, which required a thorough definition of the characteristics of all components and modules and their impact on the final data processing. To better understand how the data will be presented and how the user will work with it, I have prepared views for presenting different combinations of data.

Findings:

• users prefer chart formats they are familiar with,
• users want a graphical overview of qualitative data,
• users welcome automation options and intelligent filters.

Solutions:

• where possible, basic chart formats were used,
• I expanded the range of graphs to include types suitable for presentating qualitative data,
• I set up a concept of post-production for data for processing.

Taking all the requirements into account could easily overload the user interface, making it impossible to work with the tool effectively. To include all the features, I had to proceed carefully and test everything repeatedly to keep the application intuitive and easy to understand. The main benefits of testing include the following additional modifications:

• I standardized the basic properties of all components and modules,
• I changed the concept of data visualization to compare the dependencies between qualitative and quantitative data.

Thanks to additional testing, I obtained enough data to be able to describe the influence of individual components on working with the application as a whole. This allowed me to unify the form of user interaction across modules and components.