1 / 86

Thrdplace Social Networking

Thrdplace Social Networking. Remote Team Member. Test Plan and Cases. Gaurav Doon. Testing Overview. Type of testing : system level acceptance test of the Thrdplace Social Networking project. Purpose of testing: verify the requirements captured in Winbook .

tawny
Download Presentation

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. Remote Team Member

  3. Test Plan andCases GauravDoon

  4. TestingOverview • Type of testing:system level acceptance test of the Thrdplace Social Networking project. • Purpose of testing:verify therequirements captured in Winbook. • Scope of testing: include all capabilities and level of service requirements. • Focus of testing: testing will focus on use cases corresponding withwin conditions captured in Winbook. 4

  5. Acceptance Test PlanandCases 5

  6. ATest CaseExample

  7. 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.

  8. 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.

  9. Overall Project Evaluation • Atpresent,allthewinconditionshavebeendesignedandprototyped. • Initially,slowprogressandinconsistency betweenprototypeandwinconditions. • Adjustquicklyandcooperatewithclientscloselytocompleteaseriesofdifficultytasks,includingdatabasedesignandpopulation,influencemoduleimplementation,searchengineimplementation,recommendationsystemimplantation.

  10. Operational Concept Description YixiangLiu

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

  12. System Purpose 12

  13. Changesin current system

  14. Proposed new system 14

  15. System BoundaryandEnvironment

  16. CapabilityGoals

  17. LevelofServices

  18. RefinedElement Diagram 18

  19. Refined Workflow 19

  20. Prototype FengWen

  21. 21

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

  23. RecommendationSystem 23

  24. 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) 24

  25. Demo 25

  26. Requirements GauravDoon

  27. RequirementsPriority

  28. System Architecture RonghuiZhang

  29. 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

  30. System Context Diagram

  31. Actor Summary

  32. Process Diagram

  33. Hardware Component

  34. Software Component

  35. Deployment Diagram

  36. Artifact & Information

  37. Interface Classes

  38. Search Classes

  39. Process Realization

  40. COTS/ReuseSelection

  41. Lifecycle planning KanQi

  42. Development phase - Construction Iteration Duration: 2/10/14 – 4/17/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/18/14 – 5/05/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

  43. Deliverables in Development Phase

  44. Responsibilities by phase

  45. SkillsandResponsibilitiesfornewteammembers 46

  46. Major milestones in 577b 47

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

  48. Major Activities in Development Phase-Transition Iteration 49

  49. Iteration PlanCapabilities to be implemented 50

More Related