/src/site/portfolio/revamping-course-registration.md

https://github.com/andrewpucci/andrewpucci.com · Markdown · 41 lines · 35 code · 6 blank · 0 comment · 0 complexity · cff8e033bed770d64427a9b70c771268 MD5 · raw file 

    

  1. ---
    2. 

  2. layout: artifact
    3. 

  3. title: Revamping Course Registration  - Andrew Pucci
    4. 

  4. description: Portfolio piece showing the process used to revamp academic course registration.
    5. 

  5. name: revamping-course-registration
    6. 

  6. hero: /assets/img/card-img/course-selection.png
    7. 

  7. heroTitle: Revamping Course Registration
    8. 

  8. team:
    9. 

  9.   - name: Andrew Pucci (me!)
    10. 

  10.   - name: Brian Buirge
    11. 

  11.     link: https://www.linkedin.com/in/brian-buirge-4255368/
    12. 

  12.   - name: Nisha Somnath
    13. 

  13.     link: https://www.linkedin.com/in/nisom/
    14. 

  14. responsibilities:
    15. 

  15.   - Persona Development
    16. 

  16.   - User Flows
    17. 

  17.   - Interactive Prototype
    18. 

  18. tools:
    19. 

  19.   - LovelyCharts
    20. 

  20.   - OpenOffice Draw & Impress
    21. 

  21.   - Axure RP
    22. 

  22. ---
    23. 

  23. 

  24. ## Challenge
    25. 

  25. Registering for academic courses can be difficult. A small team and I endeavored to create a more usable design that would allow for simpler registration, especially for students who have never registered before. This group of students was a special focus for us since they usually require the assistance of their academic advisor to use the system when they register for their first classes.
    26. 

  26. 

  27. ## Approach
    28. 

  28. As a team, we decided to start our research by completing a competitive analysis of a handful of existing course registration software systems, discovering and developing user personas, and mapping existing interaction and process flows.
    29. 

  29. 

  30. Once we had a good understanding of the user environment, we started sketching out workflows, interaction flows, and wireframes. The wireframes were then turned into interactive prototypes using Axure RP. These prototypes were iteratively tested and improved with undergraduate study participants.
    31. 

  31. 

  32. ## Outcome
    33. 

  33. When we were comfortable with our experience design direction, we created high-fidelity wireframes which were used to present our design decisions.
    34. 

  34. I also [presented](http://www.slideshare.net/andrewrpucci/ixda-cleveland-ux-show-tell-oct-2011) the project process and outcomes at an IxDA Cleveland meeting.
    35. 

  35. 

  36. <div class="embed-responsive embed-responsive-4by3 mb-3">
    37. 

  37.   <iframe class="embed-responsive-item" src="https://docs.google.com/presentation/d/1pysSKJNCSWJojZDcBSQOe25DPdZuNfill93RR9w96zA/embed?start=true&loop=true&delayms=3000" frameborder="0" width="1058" height="823" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true" title="Slides for presentation of course registration redesign at IxDA Cleveland"></iframe>
    38. 

  38. </div>
    39. 

  39. 

  40. ## Lessons Learned
    41. 

  41. This project gave me a great deal of experience creating an interactive prototype using Axure RP, especially with using dynamic panels to mimic rich interactions.
    42.