IS480 Team wiki: 2012T1 6-bit Final Wikipage
by offering a place for exchanging ideas and information on its public domain.
|Home||Technical Overview||Project Deliverables||Project Management||Learning Outcomes|
- 1 Project Progress Summary
- 2 Project Management
- 3 Quality of Product
- 4 Reflection
Project Progress Summary
The development of Chapalang! will lead to a commercialization of the project after the completion of IS480 course. It is neither a proof-of-concept nor prototype, but a commercial project and hence proves that there is real business value in the project. Additionally, the system features and processes ought to be sound and valid in order to qualify as a commercial service, which will good project management and effort. Therefore, Chapalang! will be a unique project in IS480 with special values and qualities.
Real users environment
While the official launch date of Chapalang! as a commercial service will be at the discretion of our client, we will be accepting real sellers, real products, real buyers and real transactions. The fulfilment of the transactions has the logistical support of the client, but our team will be fully responsible for catering to the system processes.
A real user environment offers 2 key challenges. The first challenge is that the system function has to be of the same quality and operational standard as a competing commercial service, as customers will have the same quality expectations. Authoring, staging and production environments and policies have to be clear and strictly adhered to. Secondly, real users in this project belong to a mass market audience and hence have highly diversified preferences on functionalities or user experience. Hence, it is challenging to satisfy most or a value stratified users, and subsequently aligning it to our project objectives. As it is uncommon for most IS480 projects to face these project characteristics, we believe it is a unique X-Factor.
Problem Scenario: Click Here
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 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, having 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!
What unexpected events occurred:
- Accidental deletion of live website database
- Website server down
- Members machine breakdown
Completed Features of Chapalang.com
Prototype of Chapalang's Features: Click Here
|1. User interface
- AJAX UI - Maintenance screen - Error pages - Deletion, mouseover to display delete icon - Bulleting, auto bullets convertion from - Spinner, replacement for loading of activities - Tracking all activities
|2. Facebook login
- Pulling of basic data - Pulling of friends list - Multi -threading on pulling of friends list - Extend access token expiration
|3. Private Message
- CRUD - Read/Unread
|4. Post on Social Media(Facebook wall/Twitter Feeds)|
- Follow - Unfollow
|7. Email notifications
- Welcome email - Auto-follow email - General notifications email
|8. Like & Unlike|
- Posts - Replies - Products - Reviews
|10. Web Parser
- Development - Artificial intelligence
|11. Cronjob setup|
|12. Profile page|
|14. Privacy settings|
|15. Notification settings|
|16. Wish List|
|1. Posts||1. Marketplace product management
- List all products - View product item - Review Product - Rate Product
|2. Replies||2. Product search|
|3. Uploading images
- Scalable photo hosting
|3. Shopping Cart
- Order confirmation page - Payment page - Payment confirmation page
|4. Image processor
- Convertion upon upload - Dynamic thumbnail creation
|4. Gift a friend|
|5. Post links
- Redirection processor
|5. Paypal payment gateway
- Refund api
|6. Post search||6. Validation|
|7. Programming forum||7. Marketplace transaction|
|8. Gift sharing campaign|
|9. Mass Order campaign|
- "Confirm order received" button
- Manage orders - Manage products - Manage sales
Visit http://www.chapalang.com to try these features out yourself! =)
Quality of Product
|Project Management||Minutes||Click Here|
|Metrics||Schedule metrics: Click Here|
|Bug metrics: Click Here|
|Scope Prioritization||Click Here|
|Problem Scenario||As-Is: Click Here|
|To-Be: Click Here|
|Analysis||Use case||Click Here|
|Business Process Diagram||Click Here|
|Screen Shots||Click Here|
|Design||Logical Diagram||Click Here|
|Class Diagram||Click Here|
|Sequence Diagrams||Click Here|
|Data Architecture||Click Here|
|Testing||Test plan||[Click Here]|
User Testing 1
The objective of User Test 1 is on functionality and usability testing of the system. The coverage of the test is focused on forum functions.
The purpose of the test is to allow neutral testers to endorse that the system is functioning according to design, or spot any bugs or anomalies. Click data which collects data about a user’s number of clicks or time taken to achieve a task is also collected to understand the experience, and for comparison purposes for future tests.
There are a total of 20 testers who attended the User Test, of which 60% (12) are male and 40% (8) are female, representing various schools in SMU with SIS students being the majority. There is no stratification in the test users, and testers are selected without any intended bias. It is also observed that most testers are users of Chrome and Firefox web browser.
There is no test grouping employed in this test.
Testers are invited to attend the User Test session and required to bring their own laptops. They are informed on the purpose of the test and given a brief description of the system objective of Chapalang!. Subsequently, they are provided with an instruction sheet for a guided test experience. Testers will be required to perform a series of system tasks based on a test case that will go through all the system features and use-case. Thereafter, testers will answer Yes/No binary questions, and can fill in details in an open-ended textbox appended after each question, should they encounter any bugs or suggestions for improvements. While the primary method of testing is on direct user experience and feedback, we have also employed secondary method which collects results indirectly. The number of clicks that each user made, together with the click coordinates or link URL, as well as timestamp of each click is captured for analytical purposes.
Learning Outcome: Click Here