Functional Boundaries Redux

http://docandersen.podbean.com

https://docandersen.wordpress.com

http://scottoandersen.wordpress.com

My Amazon author page!!!!

http://lukeoandersen.wordpress.com

http://chuckandersen.wordpress.com/

http://NickOandersen.wordpress.com

A classic (blast from the past).

The concept of Functional Boundaries

A functional boundary is the edge of both how something is used but also the requirements for that use. It has two aspects that must be considered Human and Machine. The human functional boundary can be “physical” such as physical limitations that make usage harder. The Machine boundaries can be as complex as overall maximum processor capacity or as simple as the screen simply can’t display the content.

Functional boundaries don’t impact you or your solution until they actually impact you and your solution. From having to hold your phone at arm’s length to read information or having to wear glasses because the print is so small you can’t read it there are human boundaries to solutions. The machines continue to get smaller, faster and more capable. But the screen size is a significant impact. Watching a movie on your cellular phone is one thing, working your way through a complex spreadsheet or presentation with lots of builds is quite another thing.

Machine boundaries

The machine boundary can be broken into capabilities and capacity. Simply put some devices has a set of capabilities that support the “Syncverse” effectively. Other devices do not have those capabilities and will limit the effectiveness of the solution overall.

Capabilities

· HD screen or capacity to render video or images in HD

· Local storage capacity for cache

· Processor capable of rendering requirements

Capacity

· Network bandwidth (right now)

· Network bandwidth (overall monthly)

· Software interaction that allows for soft keyboard and other functional “interactions” such as camera (video conferencing) and voice.

Human boundaries

Human boundaries are harder to discuss because all of us have them. It is the willingness to try new things, the ability to understand and use technology and a willingness to try new ways of doing things.

Ability

· Can you use an on-screen keyboard?

· Can you see what is on the screen clearly?

· What do you want your device to do?

Access

· Is the environment you are in conducive to the task you are trying to complete (is it loud? To bright? Etc…)

·

From ability as is often the case we open the door. If you have the ability to do something that is frequently the first step. There is a factor that is limiting your ability and that is simply what do you want the device to do. I bought my first Swiss army knife when I was 11 years old. I used that knife to open wine, carve balsa wood and as a screw driver and all around quick to use device. Would I however use a Swiss army knife to cut down a tree? Only if it was the only device I had for that purpose other than my hands, yes. Otherwise I would never use a Swiss army knife to cut down a tree.

Machine boundaries are often more clearly defined and less variable. They do appear frequently as you move to the edges of what you are trying to accomplish. You see people all the time who struggle with the performance of their device as they attempt to complete a task. This represents the functional boundary of that device for them. It could be as simple as lack of bandwidth or as complex as trying to work on a spreadsheet on a phone screen.

.doc