Portfolio Development – Requirements List

The final part of my portfolio development planning, the projects requirements list:

Portfolio-RequirementsList

These are the key aspects that will create the best user experience and get us to our end goal.

Portfolio Development – Calculated Sub-System Weight

Based on sub-system usage we can calculate where the focus should be while developing the overall system.

PortfolioSubSystemWeight

Portfolio Development – Projected Sub-System Use Over-Time

Per session is good to estimate but doesn’t tell the whole story. I also want to take a look at the sub-system use over time:

PortfolioProjectedSub-SystemUseOverTime

Portfolio Development – Projected Sub-System Visits per Session

To find out priority ranking for my portfolio sub-systems I compare user groups against sub-systems and how many times they would visit that sub-system in a single session.

PortfolioProjectedSub-SystemVisitsPerSession

Portfolio Development – User Break Down

To be able to better understand the priorities of my portfolio system I need to understand who my users are. With understanding who they are we can get to what they’ll want out of the system.

So I’ve divided my users into distinct groups that will have similar needs:

PortfolioUserBreakDown

Portfolio Development – Sub-System List

Image to display what the sub-systems would be for a portfolio:

PortfolioSubSystemListBasically just opening the magic box up a little bit to see how we can sub divide the master system.

Portfolio Development – Context Diagram

An overall ‘Magic Box’ view of how my portfolio system will work:

PortfolioContextDiagram003

This wasn’t really necessary but a fun step. It also doesn’t strictly follow context diagrams standards.

Portfolio Development – Visual Brainstorming

Some visual brainstorming for developing my portfolio site. Just a fun and weird exercise.

PortfolioStorming