Difference between revisions of "IS480 Team wiki: 2012T1 6-bit Final Wikipage"
|Line 60:||Line 60:|
of and , not .
, a are .
there are challenges
<!-- ==Project Achievements==
<!-- ==Project Achievements==
Revision as of 20:25, 3 December 2012
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
Click Here to View our X-Factors!
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
There are several challenges that the team has faced throughout the IS480 journey. The bulk of Chapalang! is a highly functional and complete solution to a business opportunity of our sponsor, and hence it is not on the basis of a single sophisticated function.
However, it is a cumulatively complex system as it is formed by several functions, and the team has been challenged in different levels on integration issues, and micro-components of the project. One example of the micro-component is Paypal integration where Paypal documentations have been brief and changes are frequent, resulting in integration difficulties but eventually resolved. Another example is on our image cropping tool, where significant amount of time is spent on getting it right especially when none of us in the team has ever ventured into image manipulation.
Nonetheless, there are two other independent challenges which introduce much learning lessons for the team.
Scalability and Load Testing
As part of our User Test 4, we attempted to have a better understanding of scalability and load handling of our system by conducting a test.
To reiterate, performance measures the speed with which a single request can be executed, while scalability measures the ability of a request to maintain its performance under increasing load. In order to conduct the test, the following steps are required.
- Performance Testing
- Identify a system process with a series of activities
- Measure the elapse time of each activity
- Identify the bottleneck which is the single important activity which has highest elapse time
- Scalability Testing
- Increase the number of concurrent connections for the identified activity and measure of elapse time of each connection
- Count the number of concurrent connections possible, within the same approximate amount of elapse time of each connection
- Load Testing
- Measure the elapse time of each connection over a range of concurrent connections, including 1, 25, 50, 75, 100 as markers
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]|
Key Performance Indicators(KPI)
For the purpose of benchmarking ourselves with specific goals, we have derived on a set of indicators to understand our progress.
The following figures are accurate as of 21st November 2012.
505 real members
106 real transactions
189 real physical items sold
$2536.50 real revenue
9 registered and active sellers
62 real products
49 days of operations
There are a total of 4 User Tests conducted, each with a different coverage and test methodology.
Click Here to view the details of User Test 1
Click Here to view the details of User Test 2
Click Here to view the details of User Test 3
Click Here to view the details of User Test 4
Learning Outcome: Click Here