Monday, January 24, 2011

Extreme Programming Ch 4-6 and Design of Future Things Ch 2

Extreme Programming
By: Ron Jeffries; Ann Anderson; Chet Hendrickson
Publisher: Addison-Wesley Professional
Pub. Date: October 16, 2000

Chapter 4 : User Stories
The XP programming methodology advocates the user of "user stories" that are made by the customer to introduce requirements and functionality in a narrative format. These user stories are made in meetings with the programmers and each story will have only a small set of features written down on a note card. Customers are encouraged to rip up their cards to act as kind of an ice breaker where the team isn't afraid to dispose of bad ideas. Programmers are forbidden from writing stories or asking influencing the customer with ideas about the implementation of the stories. A typical project will be composed of many stories; The book gives an estimate of 60 to 120.



Chapter 5 : Acceptance Tests
Since customers have the right to see progress on the project and because progress is measured by tests of the system, XP advocates frequent tests, particularly unit testing with test automation, on each iteration. Frequent acceptance testing reduces bugs and speeds up the project compared to if testing was done right before product release. Furthermore, the customer can evaluate the testing results and provide feedback.

Chapter 6 : Story Estimation
Since project requirements and features take the form of user stories, programmers must learn how to estimate how long it will take them to implement a story. Estimates are made on a point basis (rather than time) where each programmer makes the estimate by comparing similar stories/features, keeping a "perfect engineering week" frame of reference, and by doing "spike solution" for stories that are difficult to make a comparison to. A spike solution is coming up with a general idea or set of steps for solving a new problem. The spike solution isn't thorough but just a rough estimation.

The Design of Future Things

Design of Future Things:
By: Donald Norman
Publisher: New York Basic Book
Pub. Date: November 2007

Chapter 2 : The Psychology of People and Machines

Norman begins the chapter by giving a brief sets of example scenarios of machine to human communication and claimed that machines will soon be communicating autonomously
or semi-autonomously. Norman highlights the differences between machine and human thinking by pointing out that machines, while fast, lack the kind of massively parallel computation and pattern recognition that humans have. Norman also says that he demands of the real world create a need for autonomous agents to tackle problems. Norman reviews a points from his previous book, "Emotional Design" that outline the three levels of human processing:

Visceral - Basic, automatic, subconscious
Behavioral - learned skills, mostly subconscious
Reflective - Self-aware higher level thinking

After reviewing these terms, Norman proposes that machines should be imbued with these levels of thinking and feeling ("emotions") to enhance performance and feedback between human computer interactions. This would create the symbiotic effect that was described in the first chapter.

Norman also points out that machines have problems with goal formulation and deciding how to bridge those goals. Furthermore, machines measure things differently and often can't navigate the world as well.

Finally Norman discusses the issue of "common ground" that informs communication beyond its content. Norman claims that machines need background of protocols with humans to communicate. Even more than that, though, is the need for common perception of the context in order to establish common goals and problem definitions based on observation. Norman describes this as "bridging the super-gulf."

Discussion:

Although using cards to write down story scenarios sounds light and digestible, which is nice, I have my doubts on how complete a system's features and requirements can be elicited especially if the customer is the only one writing the user stories. I do like the idea of unit testing early and often. Looking back at past job experiences I know I could have benefited from that kind of rigorous testing. Errors are much easier to track when caught early because the code is fresh in your mind and there's less interacting factors to take into consideration. The fact that user stories are made in bit-size chunks and that time estimation of the project is done by evaluating these pieces, I'm sure that XP does a wonderful job of time estimation overall.

While Norman's advocacy of emotional machinery is unique and an insightful analysis in terms of its links with communication and synergistic processes, his descriptions fall flat in terms of providing means to implement these kinds of reactions. Ultimately his observations of the limitations of machines are perhaps the easiest to digest and correspond to current areas of research in parallel computing, neural networks, and, in particular, AI. Normans discussion hit on AI's fields of computer vision (and other sensing), robotics (mobility), mapping of percept sequences to action states that reach a goal state and how to form a goal based rational agent. Although Norman's perceptions mirror AI's fields of study, his observations on needing a common ground to communicate and formulate problems with machines is insightful.

Saturday, January 22, 2011

Extreme Programming Ch 1-3 and Design of Future Things Ch 1

Extreme Programming Installed
By: Ron Jeffries; Ann Anderson; Chet Hendrickson
Publisher: Addison-Wesley Professional
Pub. Date: October 16, 2000

Chapter 1 discusses the role of the customer, the programmer, and the manager.

Customer:
Defines the business value, is on site to communicate with the programmers throughout the entire project and is always available (preferably on-site), defines the tests and requirements that are reflected in "user stories."

Programmer:
Programmers write code in pairs to reduce errors and to always have help. Extreme programming also advocates iterative development where code is released in functioning implements with value added at each iteration. To ensure code quality, refactoring and unit testing is encouraged. Programmers are to stay in constant communication with the customer.

Manager:
Removes obstacles that the programmers might encounter, schedules regular meeting and encourages communication. The manager isn't directly involved in the development but makes the day-to-day operation easier by managing the team's disagreements, giving rewards, coordinating, and reporting.

Chapter 1 also lists manager and customer rights and programmer rights:
Manager and Customer Rights

1. You have the right to an overall plan, to know what can be accomplished, when, and at what cost.
2. You have the right to get the most value out of every programming week.
3. You have the right to see progress in a running system, proven to work by passing repeatable tests that you specify.
4. You have the right to change your mind, to substitute functionality, and to change priorities without paying exorbitant costs.
5. You have the right to be informed of schedule changes, in time to choose how to reduce scope to restore the original date. You can cancel at any time and be left with a useful working system reflecting investment to date.

Programmer Rights

1. You have the right to know what is needed, with clear declarations of priority.
2. You have the right to produce quality work at all times.
3. You have the right to ask for and receive help from peers, superiors, and customers.
4. You have the right to make and update your own estimates.
5. You have the right to accept your responsibilities instead of having them assigned to you.

Chapter 2:
Included a diagram showing customer and programmer communication. It illustrated how extreme programming emphasizes customer/programmer communication and allowed the customer to evaluate the amount of value added in certain features as well as allow the programmer to make good estimates of the time needed to implement those features.

Chapter 3:
This chapter expounds on the benefits of having an on-site customer; namely, that communication will be clearer and more concise than it would be if communication only occurred through e-mail or other slower less expressive forms of communication. This clarity keeps programmers from guessing on potentially important details or switching to work on less important parts of the program. Overall, on-site communication results in a product that the customer will be happier with.

Design of Future Things:
By: Donald Norman
Publisher: New York Basic Book
Pub. Date: November 2007

Chapter 1: Cautious Cars and Cantankerous Kitchens
In this Chapter, Norman expresses his reservations and observations about intelligent or "smart" systems in a number of settings. Norman complains that smart systems don't actually communicate or listen to the user, but rather claims that they condescendingly tell the user through "recommendations" that tend to quite poor. Norman also notes that the machines aren't actually intelligent but that the intelligence is "in the heads of the designers. So when the unexpected happens, the designer isn't there to help out, so the machine usually fails."

Norman cites that what humans can do easily, machines struggle with. For example, machines don't understand their surroundings or the context of their environment. Machines don't communicate, have social knowledge, or empathize with others. (He gives an example of a self driving car that pulls in front of other drivers and slams on the brakes.) On the other hand, machines are able to "think" much faster than their human counterparts. Norman says that human-machine interaction should complement each other and be "synergistic."


Discussion:
The chapters in extreme programming were very terse and extremely cut-and-dry. I've heard of and even used extreme programming principles in my programming studio class and I like the recommendations it makes for programmers. Particularly, I'm a fan of pair programming since tiny bugs are caught and logic errors are found before they become too embedded in the structure of the code. Having the customer on site is a difficult proposition for most real life scenarios, so I think XP's credibility is damaged by their zealous advocacy of it.




The first chapter of "The Design of Future Things" is an interesting introduction that focuses the reader on how intelligent systems can go wrong and raises fears and suspicions about the direction of modern technological development. Primarily, the idea of having haughty and downright annoying applications constantly buzzing recommendations, helpful or otherwise, sounds undesirable. Perhaps Norman's observations will inspire future designers to keep smart systems behind the scenes will still being useful agents. I think that kind of concealing of actions would go a long ways toward the "symbiotic" relationship J.C.R Licklider advocated. Imbuing machines with emotional clues or reactions may be a huge step forward in CHI, but the implementation would require contextual awareness that I think is beyond current technology. (Although that shouldn't stop us from trying.)

Wednesday, January 19, 2011

Capstone Intro Post

1) What is your name?

Ross Cameron Peterson

2) What will you be doing after graduation?

I'm going to go to graduate school at Texas A&M University for a master's in computer science! (Whoop!)
I hope to specialize in CHI, AI, and graphics to strengthen my chances of getting into the video game industry.

3) List your computing interests (HCI, information retrieval, databases, etc.).

Specifically, I'm interesting in haptic sensing, wearable computing, and interactive projection areas combined with context aware intelligent systems.

4) List your computing strengths (a language, focus area, etc.).

Languages: C++, C, Java, Haskell and to some extent, HTML, XML, javascript, CSS, php

It's hard for me to identify a particular strength, but I've had a lot of experience in C and Windows programming, particularly when it comes to using sockets, threads, and GUI elements.

My greatest strength is my work ethic, though, so I can tackle anything you throw at me.

5) What was your favorite computer science project that you worked on and why?

Doing the Huffman Compression Algorithm in data structures in algorithms was particularly interesting to me. I was still very much a novice programmer at the time and creating an program to compress data (I used some Shakespeare works and Moby Dick) and analyze it was kind of cool.

Also most the programming studio assignments were pretty fun.

6) What was your least favorite and why?
hmmmmm
Probably the heap allocation program we had to make for Betatti's 313 class.
I had no idea what was going on and it was waaaay above my head, even if the idea of it was interesting.

7) What do you see as the top tech. development of the last 5 years and why?
...........
Man, that's a pretty broad question.
Microsoft's Bonfire system. It's a contextually aware laptop made possible by cameras, projectors, and internal logic. It makes the laptop much more intelligent and interactive. I have a blog entry for it in my computer human interaction blog.

8) Provide some insight into your management/coding styles. This could include your preferred coding method, how you use line breaks, what time of day you work best, or any other relevant programming-related facts.

Management:
I tend to be a "let's get things done as early as possible" kind of guy and I
usually want everyone in the same place communicating in person when we're working on a project, even if they technically aren't doing anything there. I imagine I can be pretty annoying to teammates because I'm constantly trying to manage schedules and riding everyone's tail to get things done.

Coding: I'm kind of a pack-rat with my code. I comment a lot of stuff out that I might not need anymore because I don't want to throw an idea away. Other than that I try to adhere to good coding style/conventions.

9) Make sure to include a picture of yourself.



Here's another: