save to my nooz
save author to my nooz
Related Articles
Markovian Processes in the Triangle Model - Graphics at Last - 02 - Dave49000 0 comments
Markovian Processes in the Triangle Model - Graphics At Last - 04 - Dave49000 0 comments
Markovian Processes in the Triangle Model - Graphics At Last - 05 - Dave49000 0 comments
Markovian Processes in the Triangle Model - Graphics At Last - 03 - Dave49000 0 comments
Markovian Processes in the Triangle Model - The Graphic At Last - Dave49000 2 comments
Markovian Processes in the Triangle Model - Graphics 01 - Dave49000 3 comments
Markovian Processes in the Triangle Model - Graphics 01 a - Dave49000 5 comments
Using the Boundary and Figure Representation of Information - Dave49000 0 comments
Diverge, Converge, and the Conic Representation - Dave49000 0 comments
All articles by David W. Locke
Applause from 0 readers
This is a graphic related to the post at http://www.noozit.com/article/.ee7e738...
Applause from 0 readers
The following figure illustrates how for a series of divergent innovations interpreted as sustaining and radical in the market
Continuous innovation grows the ontology in a Bayesian space
Inserts successive ontons, ontological sortables, into the ontology, while growing a Markovian process simultaneously
The reaching of commoditization and the shift to a new vector of differentiation, which together crates widely separated and distinct markets that are inaccessible to each other, because of the cultures of the populations involved
Learning barriers that accompany new ontons and new vectors of differentiation
Applause from 0 readers
The figure below shows how
Convergent innovations combine members of two separate cultures into a new culture that is likely to differentiate itself from both of its parent cultures...
Applause from 0 readers
The next graphic shows how the amount of memory involved in a process, here shown as distance or radius, determines whether a process is Bayesian or Markovian...
Applause from 1 reader
See http://www.noozit.com/article/.ee7e876 for the text that explains the graphic posted below...
Applause from 1 reader
In the graphic below, I use ther term invention where the term innovation is usually used...
Applause from 1 reader
In the graphic attached, I use ther term invention where the term innovation is usually used...
Applause from 0 readers
In Nooz 31, Figure 1 translates the grid of a spreadsheet into a collection of boundaries and their figures...
Applause from 0 readers
Taking up from http://www.noozit.com/article/.ee846d6 where I wrapped the triangle model representation into a cone, I thought about how the exploratory and selecting or realization could each have their own cone...
All articles by David W. Locke
UI, UX: Graphical Representation
Beginning Noozer
-
Last week on Twitter, we engaged in a conversation around the number of clicks, et.al.
Afterwords, I went off to the bookstore and took up reading some more of "Whats Next?" by Max Brockman. I tweeted last week about various articles that I found in this science anthology. I had read "The Vital Importance of Imagination" by Dena Skolnick Wiesberg at the end of last week, but decided to revisit it. She discusses how our brains structure our real and imaginary existances to keep them separate while simultaneous.
I was struck by how this fit with Rassmussen's wriing on interactions with systems and how experts use troubleshooting models to loop towards a solution. When users engage with software they have an expected result, an imaginary scenario, and they have a set of tools, provided by the software, that enable and constrain the realization of that scenario. They plan, one of those imaginary existances Wiesberg is talking about.
I've written about the Triangle Model before. Reading Wiesberg. I could see Rassmussen's loops running orthogonally towards realization in the Triangle Model. So here, I start out with the Triangle Model highlighting the use space towards a user realization, an in MS Word used to write a letter.
It's important to realize that any realization effort diverges and then converges to the desired functionality, artifact or performance.
Now, I'll lay the triangle out flat and draw the story of the artifacts creation as they intesect.
In this figure (bottom) the triangle to the left is the application. The thick gray line is the application at its interface. Zero (0) refers to the ground position for the user's efforts towards realizing their work product (Final). The aqua is the application plane. The orange receeds into the background (Back) behind the application plane. The yellow shows where the use pierces the application plane into the forground (Front). I 1-3 indicate successive artifacts. I1 results from divergence. I1 is checked against the imagined Final. I2 results from convergent efforts to bring I1 into the imagined Final state. I3 results from more conergence. And, finally, the state of the realization matches that of the planned or imagined Final.
The notion of convergence and divergence is shown by the relative height of the Iterations. I1 is divergence. L2 and L3 are convergent, as is Final.
The thick blue line abstracts the intesecting of the application plane with the story surface. In iterative programming, successive iterations should be faster and involve less content or bits. This leaves us with a summary curve as shown below.
Each iteration's curve (blue) varies in regards to the number of bits and the amount of time taken. The summary distribution is shown in red. Any interruptions of the efforts towards realization would be stretched out, but it would still be the same distribution.
An application that uses a wizard involves a minimum or maximum number of control interactions, and it consumes a long period of time before the use sees the results from their efforts. Then, they might have to open the wizard again and repeat the effort. Otherwise, they could hunt down individual controls and obtain successive iterations towards the realization faster. These kinds of things build the blue iteration curves. Ajax improved the web experience by eliminating the time required for the reloading the page. Ajax shortened the time to feedback, the blue iteration curves.
The number of bits in an iteration and the final realization would be reflected in the volume of stored content in a source control system. The number of bits would also correlate with the development conceptual model. User conceptual models would be built from the user interface. These bits and the time required to implement the associated features would enable to you graph each iteration curve.
Simple might remain complicated. Users might require complication.
What do you think? Leave a comment. Thanks!
Afterwords, I went off to the bookstore and took up reading some more of "Whats Next?" by Max Brockman. I tweeted last week about various articles that I found in this science anthology. I had read "The Vital Importance of Imagination" by Dena Skolnick Wiesberg at the end of last week, but decided to revisit it. She discusses how our brains structure our real and imaginary existances to keep them separate while simultaneous.
I was struck by how this fit with Rassmussen's wriing on interactions with systems and how experts use troubleshooting models to loop towards a solution. When users engage with software they have an expected result, an imaginary scenario, and they have a set of tools, provided by the software, that enable and constrain the realization of that scenario. They plan, one of those imaginary existances Wiesberg is talking about.
I've written about the Triangle Model before. Reading Wiesberg. I could see Rassmussen's loops running orthogonally towards realization in the Triangle Model. So here, I start out with the Triangle Model highlighting the use space towards a user realization, an in MS Word used to write a letter.
It's important to realize that any realization effort diverges and then converges to the desired functionality, artifact or performance.
Now, I'll lay the triangle out flat and draw the story of the artifacts creation as they intesect.
In this figure (bottom) the triangle to the left is the application. The thick gray line is the application at its interface. Zero (0) refers to the ground position for the user's efforts towards realizing their work product (Final). The aqua is the application plane. The orange receeds into the background (Back) behind the application plane. The yellow shows where the use pierces the application plane into the forground (Front). I 1-3 indicate successive artifacts. I1 results from divergence. I1 is checked against the imagined Final. I2 results from convergent efforts to bring I1 into the imagined Final state. I3 results from more conergence. And, finally, the state of the realization matches that of the planned or imagined Final.
The notion of convergence and divergence is shown by the relative height of the Iterations. I1 is divergence. L2 and L3 are convergent, as is Final.
The thick blue line abstracts the intesecting of the application plane with the story surface. In iterative programming, successive iterations should be faster and involve less content or bits. This leaves us with a summary curve as shown below.
Each iteration's curve (blue) varies in regards to the number of bits and the amount of time taken. The summary distribution is shown in red. Any interruptions of the efforts towards realization would be stretched out, but it would still be the same distribution.
An application that uses a wizard involves a minimum or maximum number of control interactions, and it consumes a long period of time before the use sees the results from their efforts. Then, they might have to open the wizard again and repeat the effort. Otherwise, they could hunt down individual controls and obtain successive iterations towards the realization faster. These kinds of things build the blue iteration curves. Ajax improved the web experience by eliminating the time required for the reloading the page. Ajax shortened the time to feedback, the blue iteration curves.
The number of bits in an iteration and the final realization would be reflected in the volume of stored content in a source control system. The number of bits would also correlate with the development conceptual model. User conceptual models would be built from the user interface. These bits and the time required to implement the associated features would enable to you graph each iteration curve.
Simple might remain complicated. Users might require complication.
What do you think? Leave a comment. Thanks!
Please log in to post a comment.