HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T1 6-bit Final Wikipage"

From IS480
Jump to navigation Jump to search
Line 181: Line 181:
  
 
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Reflection</font></div>=
 
=<div style="background: #FF0080; background: -webkit-gradient(linear, left top, left bottom, from(#FF0080), to(#F660AB)); padding: 12px; font-weight: bold; text-align: center "><font color="white" size="6" >Reflection</font></div>=
 +
Houston: It is never easy to understand user's expectations when we try to push out new concepts to the saturated market. Many times I observed how users use our system. For example, where did users' mouse travel, what buttons s/he clicked and finding out why or what makes user did certain actions. I learned that these are important cues that I need to capture so as to understand user's expectations.
 +
<br>
 +
Designing and developing a e-commerce system and providing decent user-experience from scratch have been the biggest challenge for me when doing IS 480. I could resonate fully the programming concepts that are taught in the first 2 years of SIS education. I realized modularity is very important when building a modern application. I need to have modular design and programming practices. In this modern world, change in user's expectations happens very often. In order to response to these ever changing expectations of our application using the shortest time, our modular design of our application allows us to "plug and play" our code blocks wherever we need them. Of course, integration of these modular code blocks is another challenge that we have to overcome before we could "plug and play". We have to agree on a set of coding standards before we start the development phase. Coding standard are crucial when we are developing as a team. These standards allow us to focus on more coding and less discussions on what-to-expect-of-your-codes. We set standards like the inputs and the output format of methods, the array structure of a particular entity and as well as naming conventions of classes and methods.
 +
<br>
 +
Lastly, I learned team communications must effective and efficient. Everyone on the team should be on the same page and it is everyone's responsibility to be on the page. That's what our team learned and did eventually. Only when everyone on the team is in sync, then the team can be efficient in our tasks and help out each other whenever possible. IS480 has been a gruelling but fruitful journey with anger, sadness, joy and most importantly laughter. The team and I have grown when doing this project, technically and mentally.

Revision as of 03:28, 28 November 2012

6-bit logo.png
6-bit's Chapalang! is a social utility that connects people with friends and new friends
by offering a place for exchanging ideas and information on its public domain.
http://www.chapalang.com

Final Wikipage
Home Technical Overview Project Deliverables Project Management Learning Outcomes

Project Progress Summary

Final Presentation Slides *Coming Soon by 5th December!*
Our website: http://www.chapalang.com

Team 6-bit is formed during the month of May in 2012. We have battled through 16 iterations of planning, designing, constructing and deploying our project, Chapalang and have successfully completed the project maintaining to our planned scope. Throughout the 16 iterations, we have our ups and downs. We faced several unexpected technical challenges which brought down the morale of the team. People with different methods of solving problems created communication problems. However, we had a common goal in mind, we endure and frantically looking for workarounds and alternatives to overcome these challenges. We, too, faced some project management challenges where some tasks are not complete on time and caused disturbance to our schedule. These project challenges allow us to iron out our differences and streamlined a better working process. After overcoming these challenges, we had improved ourselves as individuals as well as improved as a team!


6-bit poster.jpg


Click here to view our 1min Video Pitch!

6-bit videopitch.gif













Project Highlights

What unexpected events occurred:

  • Accidental deletion of live website database
  • Website server down
  • Members machine breakdown

HOW ARE THEY HANDLED???












Project Challenges

Describe areas of the project that were particularly difficult and how they were dealt with, whether successfully or not. Again, a few sentences are enough. If there are no challenges, remove this section.

Project Achievements

Methods, technologies, processes, teamwork, etc. which were particularly successful – highlight things which worked very well towards completing the project. A bulleted list of one to two sentences each will do. If there are no achievement, remove this section.

Project Management

Completed Features of Chapalang.com

Prototype of important features: ‎Click Here

Quality of Product

Reflection

Houston: It is never easy to understand user's expectations when we try to push out new concepts to the saturated market. Many times I observed how users use our system. For example, where did users' mouse travel, what buttons s/he clicked and finding out why or what makes user did certain actions. I learned that these are important cues that I need to capture so as to understand user's expectations.
Designing and developing a e-commerce system and providing decent user-experience from scratch have been the biggest challenge for me when doing IS 480. I could resonate fully the programming concepts that are taught in the first 2 years of SIS education. I realized modularity is very important when building a modern application. I need to have modular design and programming practices. In this modern world, change in user's expectations happens very often. In order to response to these ever changing expectations of our application using the shortest time, our modular design of our application allows us to "plug and play" our code blocks wherever we need them. Of course, integration of these modular code blocks is another challenge that we have to overcome before we could "plug and play". We have to agree on a set of coding standards before we start the development phase. Coding standard are crucial when we are developing as a team. These standards allow us to focus on more coding and less discussions on what-to-expect-of-your-codes. We set standards like the inputs and the output format of methods, the array structure of a particular entity and as well as naming conventions of classes and methods.
Lastly, I learned team communications must effective and efficient. Everyone on the team should be on the same page and it is everyone's responsibility to be on the page. That's what our team learned and did eventually. Only when everyone on the team is in sync, then the team can be efficient in our tasks and help out each other whenever possible. IS480 has been a gruelling but fruitful journey with anger, sadness, joy and most importantly laughter. The team and I have grown when doing this project, technically and mentally.