> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "IKE Project Forum" group.
> To post to this group, send email to ikepr...@googlegroups.com
> To unsubscribe from this group, send email to ikeproject-
> unsub...@googlegroups.com
> For more options, visit this group at http://groups.google.com/
> group/ikeproject?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
Efficiency, simplicity and flexibility are quality attributes. How we
rank them will determine our emphasis on general purpose or special
purpose tools. It seems unlikely, though, that we will dismiss one of
these quality attributes altogether.
Hmmmm.... thinking of different skill levels.... Isn't it true that
different people will rate these quality attributes differently? Some
people may have very limited interaction with other members of the
community. They may just read the latest College news on the Web or
in their e-mail. Others may have complex, dynamic and innovative
interactions, and be willing to develop skill with general purpose
tools, trading some simplicity and efficiency for flexibility.
Does this obviate or inform the Quality Attribute Workshop process?
For instance, the overall software architecture of a Web system might be
designed to be highly available but an element within the architecture might be
designed to be high performance (e.g., load balancer) as a way of supporting the
overall goal of being highly available.
The main reason I bring this up is to be clear that quality attributes are
applied and prioritized at all levels of abstraction (at least the levels worthy
to be documented).
-S2
--
Steve Moitozo II
Software Architect and Manager of Internet Software Services
Bates College
"Opportunity is missed by most because it is dressed in overalls and looks like
work." --Thomas Edison
Are you an Outlook user having problems replying to my messages? Read this:
<http://www.geekwisdom.com/dyn/outlookusers>
-Jay
> begin:vcard
> fn:Steve Moitozo II
> n:Moitozo II;Steve
> org:Bates College;Information and Library Services
> adr;dom:;;;Lewiston;ME;04240
> email;internet:smoi...@bates.edu
> title:Software Architect & Manager of Internet Software Services
> tel;work:207-786-6266
> note:"Opportunity is missed by most because it is dressed in
> overalls and looks like work." --Thomas Edison
> x-mozilla-html:FALSE
> url:http://www.bates.edu/ils/offices/web/
> version:2.1
> end:vcard
>
http://abacus.bates.edu/~jhart/4dimensions.pdf
Let's keep stretching our minds and assumptions.
Jim H.
p.s. Given the new devices coming along, using "Browser" as the 4th
dimension may not be a good idea. So, let's not get hung up on that.
The first 3 dimensions are more important.
Jay Collier wrote:
> By grid, I assume you mean <http://tinyurl.com/63k6wv>.
>
>
I meant this one:
http://abacus.bates.edu/~jhart/4dimensions.pdf
> By "content" I'm thinking of any digital asset, including text and all
> media, not just static content.
>
> I am thinking that any "content" objects (even a Tweet or chat or
> discussion item) can be interacted with, in real time or
> asynchronously. Consuming content is a subset of interaction. If the
> interaction is immediate, that's real time. If delayed, it's
> asynchronous.
>
Yes, it can be that generalized, can't it?
So what are the variables in an IKE experience?
- Synchronous versus asynchronous is too discrete. The time between
beginning to interact, as Jay defined interaction, and receiving the
interaction is really a continuum. What should it be called? "Delivery
time?" "Interactivity response time?" ???
- Push versus pull?
- Any others?
> In other words, I agree with your last line. All digital media
> interaction methods are moving toward integration. By way of example,
> take a look at the demo at <http://www.voicethread.com>.
>
>
Great tool. I hope they come out with some group pricing. A class of 30
plus a professor with Pro accounts would cost $1860. Some of the limits
on free accounts, e.g. 30 mins. of Webcam time, 25MB maximum file size,
and the presence of advertising, might be unacceptable in some college
courses.
The next functionality step would be the ability to apply all those
commenting tools to any content, anywhere, without changing it.
> I think this is a great conversation. Let's keep it going!
>> jhart.vcf
>> < 1KViewDownload
>>
>
>
As to the grid you posted at <http://abacus.bates.edu/~jhart/4dimensions.pdf
>, I'd suggest that we have two sets of "dimensions" we're
discussing: those of the user experience, and those of the technology
architecture.
I have collected the attributes of the user experience, which appear
in general, and in more detail, in these places:
<http://sites.google.com/site/ikeproject/home/discovery/principles>
<http://tinyurl.com/3gbpjz>
It is my preference that the technology should be invisible, so I
encourage you, Steve, and our other Bates technology colleagues to
develop your architectural dimensions as you need in order to be as
effective as you can for technology development.
Does that help?
-JFC