Boxes and Arrows: Comments by Parth Upadhye

Parth Upadhye — Fri, 28 Sep 2007 19:14:05 GMT

Your tile-based thinking has many parallels in the component-driven software architecture world. I am a strong proponent of that and enjoyed reading your articles/thoughts. Also your terminology very close echoes those in content aggregators – Yahoo/IBM Pipes and connectors – and authoring IDEs – Container in Flex. Have you applied your model(s) to any real life examples yet?
Here are a couple of inks that do fair justice in explaining OOP for those not familiar with this software engineering approach: http://www.toa.com/pub/oobasics/oobasics.htm and http://homepages.north.londonmet.ac.uk/~chalkp/proj/ootut…

Reminds me of the story of the blind men and the elephant; each man touches a part of the elephant and declares what the object must be. Here the elephant is Portal and the participants are UX professionals, IA, SA (software architects).

Parth Upadhye — Thu, 04 Oct 2007 14:13:45 GMT

Post-sale, most web projects begin with a meeting of the team. That’s an excellent forum to conduct a quick “game” or workshop – 30 minutes max as you’ve indicated – led by the team not client to clarify the user persona.

Parth Upadhye — Thu, 11 Oct 2007 15:25:57 GMT

I think it’s a very good idea. I was just thinking about the same but using Flex versus Flash. The custom components built for the above can be easily skinned/populated and would serve as functioning prototypes. Also, given that Flex is XML, it can be easily parsed to develop documentation.

Parth Upadhye — Tue, 30 Oct 2007 18:58:01 GMT

I would like to turn this idea into a multi-part story. Here’s my suggested outline. Hopefully no one’s writing it already.

Global, Multi-market, N-tier Architecture >> Laying the groundwork [1]
Brief introduction to what global, multi-lingual and multi-market mean. Also a brief intro to the concepts behind N-tier Architecture. Example of an online property by due to popular demand now wants to expand into uncharted territories.
Why Business Strategy and Goals are important. The impact of the keywords on a company/business’ operations.
Illustration/Example/Checklist

Global, Multi-market, N-tier Architecture >> UX Strategy, Scope, Skeleton, and Surface [2-5]
The following parts will follow JJG’s model for UX, assuming that the final deliverable is a user experience of some sort. Each part will explore deliverables, building blocks and tools necessary to build a solid UX layer. Stakeholders and participants in this UX Design, Development and Implementation process will include: business, program, technical, content, and experiential leads among others. Each part will have many references, examples, checklists etc.

Global, Multi-market, N-tier Architecture >> Deployment [6]
This concluding part will explore the challenges of deploying the site/user experience and what follows or could follow after.

Parth Upadhye — Wed, 19 Dec 2007 16:47:21 GMT

This article and the toolkit is very useful. I can’t wait to use it for my current software project. I am using the Persona approach to flesh out Stakeholder and User profiles. Thanks, this is the best document for my purposes.