1 / 65

Thrdplace Social Networking

Thrdplace Social Networking. Strong Points. We are good at sharing our vision. We agree on a decision only after consulting everyone in the team and when everyone is satisfied with it. Familiarity with technologies like MySql and HTML 5 which are used in the project will make things easier.

lavi
Télécharger la présentation

Thrdplace Social Networking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Thrdplace Social Networking

  2. Strong Points • We are good at sharing our vision. • We agree on a decision only after consulting everyone in the team and when everyone is satisfied with it. • Familiarity with technologies like MySql and HTML 5 which are used in the project will make things easier. • Client has provided us access to his technical staff, which have been very helpful.

  3. Weak Points • Due to clash of schedules, sometimes it becomes difficult to organize a team meeting. • Some technologies like PHP, thrdplace database are not known to the team members, but they will be implemented in the project. • Two of our team members left the team in 577 b. We have a new team member who needed to get acquainted with the project quickly.

  4. Overall Project Evaluation • Atpresent,allthewinconditionshavebeendesignedandprototyped. • Initially,slowprogressandinconsistency betweenprototypeandwinconditions. • But, we adjusted quickly to build a prototype which has so far been to the liking of the client. • Now, we have setup our prototype on client’s server. But there are some inconsistencies with the client’s database. So, we are working with his database architect to remove them to continue the progress.

  5. TPC Ronghui Zhang

  6. Test Strategy • Agile test-first: in each iteration, IIV&V will test the new capabilities and improvements when they’re completed. • Boundary and exit/entry criteria between unit testing and integration testing: each new feature will first be tested to make sure it is fully functional and then will be tested ensure it integrates well with the existing system • Requirements-test traceability: the traceability matrix will be used to ensure that the capabilities will keep consistent with win conditions.

  7. Test Preparation • Hardware: PC, MacBook, ThrdPlace server • Software: IE/Chrome/Firefox, Safari, Solr

  8. Requirements Traceability

  9. Acceptance Test PlanandCases

  10. Test Identification

  11. Schedule

  12. Operational Concept Description YixiangLiu

  13. System Purpose • Thrdplace.comis a venue for fund-raising, resource sharing and commerce. • OursystemisasubsystemofThrdplace.com. • Oursystemisdesignedtoprovidesearch,rankingandrecommendationfunctionstoprojectcreatorsandcontributorsonThrdplace.com.

  14. System Purpose 14

  15. Changesin current system

  16. Proposed new system 16

  17. Prototype YixiangLiu

  18. 18

  19. SearchEngine • WeuseApache Solrfull-textsearchenginetosearchfor projectsor contributors fromthrdPlace.comdatabase.Searchresultswillbedisplayedinalistview. 19

  20. RecommendationSystem 20

  21. RankingSystem Rankby influence(formulasagreedbyclient) • INFLUENCE (Contributors) • (Weight 1 * Number of Project Contributed) + (Weight 2 * Promotions) • INFLUENCE (Projects) • (Weight 1 * Project Success) + (Weight 2 * Promotions) • PROMOTIONS = (weight 1 * Facebook Likes) + (weight 2 * Twitter Shares) + (Weight 3 * Number of Comments) • PROJECTSUCCESS=RaisedCapital/ExpectedCapital • CAPITAL=(weight1 * Integer value of Funds) + (weight2 * Supply Items) + (weight3* Volunteer hours) 21

  22. Progress of work

  23. Progress of work

  24. Progress of work

  25. Demo 25

  26. System Architecture RonghuiZhang

  27. Outlines • Overall Architecture • System Context Diagram • Process Diagram • Hardware Component Diagram • Software Component Diagram • Deployment Diagram • Detailed Architecture • Artifacts & Information Diagram • Interface Classes • Process Realization • COTS/ReuseSelections

  28. System Context Diagram

  29. System Context Diagram

  30. Actor Summary

  31. Process Diagram

  32. Process Diagram

  33. Hardware Component

  34. Hardware Component

  35. Software Component 35

  36. Deployment Diagram

  37. Deployment Diagram

  38. Artifact & Information

  39. Interface Classes

  40. Search Classes

  41. Process Realization

  42. Process Realization

  43. COTS/ReuseSelection

  44. Lifecycle planning KanQi

  45. Development phase - Construction Iteration Duration: 2/12/14 – 4/16/14 Concept: In this phase, the development team should keeps detailing project plan and recording project progress and emphasize on implementing the system and performing testes. Deliverable: Transition Readiness Review Package, Draft Transition Readiness Review Package Milestone: Transition Readiness Review, Core Capability Drivethrough Strategy: Development and testing Development phase - Transition Iteration Duration: 4/17/14 – 4/30/14 Concept: In this stage, the development team should perform system transition by providing maintenance information, tutorial session, technical support, as well as user menu which covers different user roles. Deliverable: Operational Commitment Review Package, Transition manual, Source code Milestone: Operation Commitment Review Strategy: Deployment, Training, and Transition

  46. Responsibilities by phase

  47. New member of our team 48

  48. Major Activities in RDCR, Development Phase-Construction Iteration 49

  49. Major Activities in Development Phase-Transition Iteration 50

More Related