W.R.O.S.E

A waste management and scenario evaluation application.

THE PROBLEM

Take a very sophisticated, complex idea born of professors' minds and create an easy-to-use application without losing the sophistication.

The functional requirements document has more than 40 pages, outlining each and every functionality requirement. The intention is to commercialize the software, which will enable governments, corporations, organizations, and NPOs to effectively study, measure, and deal with waste management on a large scale, effortlessly.

HIGH LEVEL TIMELINE

More than 6 months.

MAKE OF THE TEAM

UX/UI designer, ASP.NET developer, business strategist, graphics designer, and project manager.

KEY GOAL

Find a way to uncomplicate the processes, design, and build a user-friendly application.

MY ROLE

My role was to translate the functional requirements document into a visual representation to guide the development team.

I first created hand-drawn wireframes on paper and then after discussions with the client, business strategist, and many iterations, I created what I would call medium-fidelity wireframes to facilitate further engagement with stakeholders.

This allowed the client to be able to further refine their idea and closely inspect their functional requirements.

UNDERSTANDING THE USER

The university had been using the W.R.O.S.E model for more than a year, and there was no shortage of data gathered from field tests and exercises performed by students and academics.

The major task was using that data to create test cases to test the prototype, get feedback and make changes as directed by findings.

WIREFRAMES

Since I initiated the wireframing phase with pen and paper wireframes, my next step was to create medium-fi wireframes..

The overall application has more than 52 wireframes in total, including those of the admin dashboard. The project was placed on hold by the university, and we didn't get to the UI design phase, but an exciting project to have worked on, and I am still part of the team.