Difference between revisions of "IS480 Team wiki: 2012T1 6-bit Final Wikipage"
|Line 36:||Line 36:|
<b> Completed Features of Chapalang.com
<b> Completed Features of Chapalang.com
Revision as of 02:15, 28 November 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
- 1.1 Project Highlights
- 1.2 Project Management
- 1.3 Quality of product
- 1.4 Reflection
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!
Completed Features of Chapalang.com
- 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
|Posts||Marketplace product management
- List all products - View product item
- Pulling of basic data - Pulling of friends list - Multi -threading on pulling of friends list - Extend access token expiration
- CRUD - Read/Unread
- Scalable photo hosting
- Order confirmation page - Payment page - Payment confirmation page
|Post on Social Media(Facebook wall/Twitter Feeds)||Image processor
- Convertion upon upload - Dynamic thumbnail creation
|Paypal payment gateway
- Refund api
- Redirection processor
- Follow - Unfollow
|Post search||Product review|
- Welcome email - Auto-follow email - General notifications email
|Programming forum||Product rating|
|Like & Unlike||Marketplace transaction|
- Posts - Replies - Products - Reviews
|Gifts sharing campaign|
- Development - Artificial intelligence
|Mass Order campaign|
- "confirm order received" button
|Profile page||Gift a friend|
- Manage orders - Manage products - Manage sales
- 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
- Facebook login
- Pulling of basic data
- Pulling of friends list
- Multi**threading on pulling of friends list
- Extend access token expiration
- Private Message
- Post on Social Media(Facebook wall/Twitter Feeds)
- Email notifications
- Welcome email
- Auto-follow email
- General notifications email
- Like & Unlike
- Web Parser
- Artificial intelligence
- Cronjob setup
- Profile page
- Privacy settings
- Notification settings
- Wish List
What unexpected events occurred:
- Accidental deletion of live website database
- Members machine breakdown
Provide more details about the status, schedule and the scope of the project. Describe the complexity of the project.
Project Schedule (Plan Vs Actual):
Compare the project plan during midterm with the actual work done at this point. Briefly describe a summary here. Everything went as plan, everything has changed and the team is working on a new project with new sponsors or the supervisor is missing. A good source for this section comes from the project weekly report.
Provide a comparison of the plan and actual schedule. Has the project scope expanded or reduced? You can use the table below or your own gantt charts.
|1||Customer CRUD||1 Sept 2010||25 Aug 2010||Fiona took the Sales CRUD as well.|
|Trend Analytic||1 Sept 2010||15 Sept 2010||Ben is too busy and pushed iteration 1 back|
|2||User tutorial||1 Oct 2010||Removed proposed by Ben|
|Psycho analysis||1 Oct 2010||New module proposed by sponsor|
Summary of analysis for the metrics collected. You may refer to another page for the details about the metrics and how it is collected.
Describe and list the technical complexity of your project in order of highest complexity first. For example, deploying on iPhone using Objective-C, customizing Drupal with own database, quick search for shortest flight path, database structure, etc.
Quality of product
Provide more details about the quality of your work. For example, you designed a flexible configurable system using XML.config files, uses Strategy Design Pattern to allow plugging in different strategy, implement a regular expression parser to map a flexible formula editor, etc.
List the artifacts produced for this project. The entire deliverable can be submitted in a separate thumb drive, web repository or place in the IS480 team wiki.
|Project Management||Minutes||Sponsor weeks -10 -5 3 7 Supervisor weeks -2 3 5 7|
|Requirements||Story cards||CRUD Customer, Trend Analytic|
|System Sequence Diagram||client, server|
|Business Process Diagram|
|Screen Shots||CRUD Customer, Trend Analysis|
|Design||ER Diagram||1, 2, 3|
|Class Diagram||1, 2, 3|
|Handover||Manuals||User tutorial, Developer manual, Setup manual|
Not all parts of the deliverables are necessary but the evidence should be convincing of the scope.
Explain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.
In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.
Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.
Compile common lessons and reflection for the team and for each team member. Be brief.
Key lessons learned – indicating where the team improved, or would do things differently next time. You may refer to the learning outcome summary in your proposal. A very short checklist style will suffice. It would be very convincing if the knowledge is share at the wiki knowledge base and linked here.
Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.