Optimizing C/C++ applications on complex multicore software requires a complete understanding of the software architecture and its behavior on the hardware.

Developers are challenged with the task of optimising sequential and parallel code that comprises a variety of compute engines. SLX  programming tools accelerate the journey from software to application-specific hardware systems, democratizing accelerated computing. WEBSITE LINK

My task is to redesign the software interface from scratch for the Desktop version and Could (web-based platform) to improve the usability and visualization for different use cases.

SLX is built upon Eclipse and Codenvy.io. Two widely used deep programming knowledge-required IDE tools. Designers barely are dedicated to redesigning specialized programming software with deep program knowledge-based and highly complex functions and hardcore technology. Consequently, there are plenty of constraints on GUI development but barely case studies when it comes to redesigning them.

After closely collaborating with the engineering team to get a general understanding of Eclipse IDE and Codenvy.io., I worked with the project manager as well as the software architect to map out the workflow between different user personas and the function sitemaps.

With all pieces of key leads in hand, a concept was created which shows SLX.Desktop and SLX.Cloud in modern flat design with platform-specific accents to it. I also integrated the configuration interface and visual analysis graphs into theprototypes.

SLX Sitemap - Information Architecture

On the basis of Eclipse IDE, software engineers kept adding features while developing SLX.Desktop. Because of the high dependency on Eclipse and Codenvy.io., SLX.Desktop interface is full of complex configurations and irrelevant elements.

As such, the first step is to map out all the features with the functions and clean up the interface by getting rid of the irrelevant visuals.

User Persona and User Journey

After cleaning up the interface, the next step is, together with the PMs, software architects, and FAEs, to draft the different Personas according to all the inputs. The persona models took a key function as an approach to carve out the user needs from different user types and use cases and how they going to cope with each other in one project.

In this step, I took on the role of UX designer by visualizing the brainstorming footprint, sorting and analyzing all the information and ideation, I also took the responsibility as a coach to help the team judge questions and actions from a user perspective.

SLX.Cloud

USER persona: Information Architect / Project Manager

USER needs - 3 tops

1. Quick access to the simulation configuration
2. Quick access to comparing the simulation results of different version of the compiled software
3. Easy coordination with the developers across the teams

SLX.Desktop - Data visualization

USER persona: Software Developers ( both individual  and cooperative work)

USER needs - 3 tops

1. Data visualization
2. Version control of the code
3. Easy coordination with other developers and information architects in the workgroup