Thursday, October 16, 2008

#3 - Developing

This past week I have been working solidly on my project. I have finally come up with a name for it: “Cityplanner”. I created most of the screens and have started writing the Actionscript code that will control the Flash application’s response to user input. I started developing the application by creating the main activity first.
The main activity consists of an interface where the user can input investment values for modes of transportation (bicycles, cars, buses, trains, and pedestrians) which control social and environmental indicators such as: pollution, taxes, travel time, and local development. I thought it would be a good approach to be able to work from a top-down perspective and then work my way to the details and additional content.
I think my project is going well. Products are coming out as planned and though there is still a lot more ahead of me I feel like I am making progress. Once I finish the main activity, I will migrate to the subsequent (or supporting) activities and then focus on the introductory animation, which will provide contextual information for the user.
I have shown the initial screen from my project to a few friends and family members. They all seem to like it. It was a good experience to have other people look at my work and see their reaction to it. By showing them my ideas and exposing how I was going to build my project, I was also clearing out some of my own doubts. It has helped me immensely to walk through my project with other people that were not involved with it. Papert (1996) discussed, that problem solving situations require more than just to apply rules. “It is not using the rule that solves the problem; it is thinking about the problem that fosters learning. So does talking about the problems or showing them to someone.”(p.12) Papert suggests that we spend time “playing with problems”(p.12) in order to come to better ideas to problem-solving scenarios.
In his older article Situating Constructionism, Papert (1991) again presented very interesting ideas that in many ways have related to my reflections and to my experience in showing my project to other individuals. Beyond clarifying the difference between constructivism and constructionism, Papert discussed the differences in the way we think, learn and create: “One ("bricolage") takes its starting point in strategies for the organization of work: The painter-programmer is guided by the work as it proceeds rather than staying with a pre-established plan. The other takes off from a more subtle idea which we call "closeness to objects"--that is, some people prefer ways of thinking that keep them close to physical things, while others use abstract and formal means to distance themselves from concrete material. Both of these aspects of style are very relevant to the idea of constructionism.”

----------------
References:
Papert, S. (1991). Situating constructionism. In I. Harel & S. Papert (Eds.), Constructionism, (pp. 1-11). Norwood, NJ: Ablex. Available online: http://www.papert.org/articles/SituatingConstructionism.html
Papert, S., (1996). A word for learning. In Y. Kafai & M. Resnick (Eds.), Constructionism in practice: Designing, thinking, and learning in a digital world (pp. 9-24). Mahwah, NJ: Lawrence Erlbaum Associates. [PDF]

Saturday, October 11, 2008

#2 - Meeting with 6210 teams

Yesterday, October 10th, I attended my second 6210 meeting. This time it was a casual meeting. The team members were relaxed after having presented a brief overview of their project to the class. They also seemed to be satisfied with the organization and progress of their work.

The previous meeting, the team members were a little overwhelmed with all the work they had in front of them. At that time, I felt lost in what they were doing since I did not know what their project was about. Also, I did not know in which stage they were in the designing process of their instructional project. As such, the second meeting made a lot more sense to me once I had more information on their team and had just seen their first presentation.

This meeting was also shorter. After the meeting was over; they stayed for a while and talked casually about the project. They showed me the screens they made for the Flash application they are developing and they looked very good. Rather than just listen, this time I got to ask them questions about the development of their work. I feel this meeting was more productive for me even though it was less formal.

Thursday, October 9, 2008

#2 - Service Hours

Characters for Fantastic Stories

I have been working on the characters and scenarios for Histórias Fantásticas (Fantastic Stories). We are now thinking about the initial animation, how the characters are going to move, and where they are going to be positioned in the interface.

#2 - Creative Process

The creative process for my project has started and this past week I have been: 1) trying to decide on a name for it; 2) defining due dates for project components; 3) thinking about the scope of work for the flash application to be built.

1-I have had some interesting ideas for my project name; however, I decided to wait another week until I have more of the project materials done. Once I can see the direction where the project is going I will probably be able to choose a name that will suit it.

2-I took a look at the calendar and started to account the time available for this project and the hours I will have per week to work on it. The initial phase of my designing process has been going slow, though I do not think this is a bad thing. This is the time to make ideas clear and choose a path to follow, so I guess I can afford to spend a little more time now then to have serious issues with the development stage later on. Time is also a very important aspect to my next point, the scope of work.

3-I created an outline of the scope of work and the content of the flash application. I thought about the screens, how the content and instructions would be presented, and decided on a character who is going to be the “spokesperson” for the activities.

Shahaf Gal (1996) interestingly depicted the configurations of the design process. In his article “Footholds for Design”, learning is not conceived in unproblematic situations. Likewise, the design process occurs from the relationships among materials, experiments, project participants, and challenging situations. He sees the activity of designing materials as the extreme sport of rock climbing. The designer, much like the rock climber, has to make decisions based on the previously chosen trajectories and on his or her personal strategies to get safely to the next stage.

Designing an application, like the one I am developing, Gal’s ideas can be very helpful. Being the designer requires the ability to develop strategies that will lead to the accomplishment of target objectives. Selecting strategies and supportive technology is a task that must be performed seriously and especially, intentionally.

Agenda for upcoming weeks:
1)Keep thinking about a name for the project.
2)Start developing the screens and the flash application.

-------------------------------
References:
Gal, S. (1996). Footholds for design. In Winograd, T. (Ed.), Bringing Design to Software (pp. 215-227). New York: Addison-Wesley.

Thursday, October 2, 2008

#1 - Meeting with 6210 teams

I attended my first 6210 meeting with the Global Solutions team on September 25th. It was interesting to see how the meeting was held and how team members interacted. I knew very little about their project then, fortunately, the project manager, Trudian Trail, noticed during the meeting that very little of us attending their meeting knew what was going on, so she handed us a hard-copy of their instructional design process for the Russian Summer Camp Experience.
The meeting seemed to have gone well, the team members were communicating their ideas as they would go through their goals and objectives to make sure that everything was connected and coherent to the project’s purpose. I got the impression that they were a little worried about the time constraints and, therefore, trying to have good ideas that would not require an absurd amount of time to implement.
Like in most meetings (at least from my experience), I think they did not get much done as far as developing the components for their activities. I guess they took the time to review the process, brainstrom ideas and make sure that every group member was in the same page (what is fundamental when project goals must be met in tight schedules).
Attending this meeting made me realize that there is more to a project than a good idea. Although having a good idea helps to create innovative products, I need to keep in mind that being organized is also very important. There are still a lot of things that I need to work on for my project and I need to keep linked to my goals. I am still not sure if I will be able to develop all I want with the time I have, but I will try to do my best to accomplish the goals I stated for this project.

#1 - Service Hours

Turning Page animation - Fantastic Stories Turning page animation for Fantastic Stories Interface
I’m currently a contributor of my hometown university Learning Object Design Group – PROATIVA. I will be designing interfaces and the visual components for a learning object called Histórias Fantásticas (Fantastic Stories). I will probably work more than 10 hours on this project, but I will try to keep track of my hours and post what I have done so far. You can also see the stages of the development process of this learning object by visiting PROATIVA’s website: http://www.proativa.vdl.ufc.br/oa/

#1 - Project Description

Once I had “the idea” for my project, I began to have other concerns, I would even say multiple and much deeper concerns. Some of my worries were: How will I communicate the content? How will I integrate the technology to be supportive of the project’s goals? How will I describe desired scenarios clearly?

I must be focusing on the behavioral aspect of my project’s design as Norman (2004) would describe it. I am currently reviewing its functionality, its purpose and structure.

I understand the process of designing is a real conundrum, like playing soduko. There are many aspects that need to be taken into account and planned for. It is also important to be able to let ideas “simmer” for some time until they have been thoroughly analyzed and are ready to be developed on. Working independently though, seems to be a lot harder. I have Learning Object design experience on a team. There may be some difficulties in working as a group, though, Kapor (1996) described communicational issues that may occur among self-titled designers and programmers, I have to say form my experience that the design process flows a lot smoother when you have more people working on it.

I tried to used elements of ADDIE process to help me organize my ideas. Please see a summary of my project below:


Project context:

Access to petroleum has once again become an issue, as such, communities, local governments and individuals try to migrate from motor vehicles to less petroleum dependant means of transportation. In addition, there has been a rise in awareness of the impact of motor vehicle emissions to communities’ air quality.

Although there is a clear movement for greener transportation systems, governments seem to stumble on the processes of developing and implementing low environmental impact strategies. The main reason for this is that transportation systems have major ties to industry, commerce, and people’s lives. Though motor vehicles carry negative consequences to the environment and impose dependency on the suppliers of petroleum, they have grown with the needs of our society and have brought through the years consequences and implications that cannot be underestimated.

The Purpose:

The reason for this project is to provide a Flash application that helps the learner audience specified below to identify, interpret, and associate costs and benefits related to transportation modes.

Learner Audience:

- Students in transportation planning and engineering.
- Metropolitan Planning Organizations (MPO’s) decision-makers/staff.
- Urbanized city and counties transportation decision-makers/staff.

Instructional Goals:

- The reason for this project is to provide an application that helps users to:
- Interpret the consequences related to investments on specific transportation systems.
- Identify the effects and costs of transportation policies.
- Associate the following factors: Pollution, Oil Consumption, Local Development, and Travel Time to specific transportation systems choices.

The benefits of the project:

- Engage learners in the task of developing cleaner and effective transportation strategies.
- Encourage local governments, cities, and counties to consider the benefits of alternative means of transportation.
- Promote reflection among learners for the creation of transportation strategies that would benefit the global population.

Project Agenda:

1)Create the scope of work and a name for the project.
2)Content selection.
3)Create a storyboard for the events in the application.
4)Design the visual components of the application.
5)Build interface.
6)Generate a prototype.
7)Review all products.
8)Present products.

Resources:

1)Equipment specification for project development:

Laptop Computer
Processor speed: 2.66 GHz
Memory: 4GB
Operating System: Windows XP Professional
Hard Drive: 80GB
Display size: 17" diagonal WXGA
Wireless: Wireless 1350 WLAN (802.11 b/g, 54 Mbps)

2)Software for project development:

- Adobe Design Premium Suite CS3 (which includes Adobe’s: Acrobat, Dreamweaver, Flash, Illustrator, and Photoshop).
- Microsoft Office Suite 2007 (which includes Microsoft’s: Word, PowerPoint, and Excel).

3)Human Resources:

Natasha Barreto - Project Developer.
Robert Sills – Subject Matter Expert.

-------------------------------
References:
Kapor, M. (1996). A software design manifesto. In Winograd, T. (Ed.), Bringing Design to Software (pp. 1-9). New York: Addison-Wesley.

Norman, D. (2004). Emotional Design: Why We Love (Or Hate) Everyday Things. New York: Basic Books.