Tuesday, February 10, 2009

Assignment #3: CS 5150 iPhone Project

I am currently in a group for a CS class developing an iPhone application, which can easily be considered a cognitive system. The task in this group is not necessarily to produce a good product, but to produce a happy client. We represent this task through the collaborative writing of several reports on our plans to attack this task. Our first report was a feasibility study that determined whether or not we are capable of completing this project. Then we wrote a report on the functional requirements of our project, followed by a technical requirements document. Each of these reports represents information about our task in a specific realm, and different ideas were taken into account to create each one. However, group members must then process the information in each report and transform the ideas into a cohesive plan that takes into a account business considerations, technical problems and design aesthetic. This intermediary information (after the requirements documents but before the final product) is represented in business letters, computer code and documentation, and graphics applications like Photoshop. While we developed the requirements documents collaboratively, chipping away at our task is done in independent clusters. Nonetheless, these are tightly coupled relationships because we all have unique skills and depend on the others to make up for our lack of skills. For instance, I am terrible at Power Point and putting together presentations, but our group has a member who exceeds in this area. We also require a Mac for our software development, but I am the only group member who personally owns a Mac, so that requires everyone to be tightly coupled to me. As we continue this project hopefully we will succeed as a cognitive system.

3 comments:

  1. This sounds like an interesting project. Was the client able to sell the application or have it downloaded by other iphone users. I agree with the notion of the application being a cognitive system itself rather than simply the group. Tightly coupled seems to be the relationship groups have when they need to create a project as a whole.

    ReplyDelete
  2. It is pretty interesting that the one of the reasons that the group was tightly coupled was because many of the group members don't actually have the tool needed (the mac). Of course, because this project required a lot of time, coordination and team members input(since everyone becomes attach to the project through shared goal and "end state" to create a project). It does sound like an interesting project, though.

    ReplyDelete
  3. Interesting assignment. Will the application be launched and used? I also find it surprising that you're the only group member with a mac- I feel like most people have converted from a pc to mac.

    ReplyDelete