1 / 50

LOSE4GOOD ( By Team 08 )

LOSE4GOOD.org ( By Team 08 ). Promote healthy living. TEAM MEMBERS. What have changed?. More than h alf of the team members have left. More implementation. Detailed responsibilities. Minor business logic changes . Team Strong Points. Team Weak Points. Operational Concept Description.

tirza
Download Presentation

LOSE4GOOD ( By Team 08 )

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. LOSE4GOOD.org (By Team 08) Promote healthy living

  2. TEAM MEMBERS

  3. What have changed? • More than half of the team members have left. • More implementation. • Detailed responsibilities. • Minor business logic changes.

  4. Team Strong Points

  5. Team Weak Points

  6. Operational Concept Description

  7. System Purpose • Online application that potential weight-losers can use to stay motivated in their pursuit to lose weight. • Motivation provided by sponsor who pledges donation to charity against weight-loser’s goal.

  8. System Boundary Diagram Gmail

  9. Business Workflow Diagram

  10. Desired Capabilities and Goals Organizational Goals

  11. Level Of Service

  12. Prototype Arul

  13. POSITIVE POINTS • Minor changes in requirements • Focus more time on development of system • Focus more time on Integration of the Facebook & Paypal API’s Changes from last iteration • Mockups minor modifications • System navigation modified

  14. INITIAL Navigation Flow Financial Officer Page Lose4Good home page Pending Transaction Page Profile Page Create Goal Page Invite Sponsor Page Your Account Page Sponsor Donation Page Pledge money page Transaction Result Page

  15. CURRENT SYSTEM Navigation Flow Financial Officer Page Lose4Good home page Refund Page Pending Transaction Page Facebook Profile Page Track Goal Achieve Goal Create Goal Page Invite Sponsor Page Personal Details Page Pledge Money Page Transaction Result Page Email Paypal

  16. MOCKUPS • Goal Creation • Sponsor Donation • Monitor Payment

  17. SUMMARY Completed Tasks • Facebook Login Prototype • PAYPAL Prototype • Modification of the Mockups Upcoming Tasks • Facebook Prototype Integration with Django • Prototype Track Goal in Django

  18. Architecture SheryasDevaraj

  19. System Context Diagram

  20. Use Case Diagram

  21. Architectural Style Client Side Server Side • Django’s MVT Style - Separation of Concerns - Future Modification Database Lose4Good.org - Django’s version of the popular MVC style

  22. Class Diagram

  23. Sequence Diagram – Sponsorship invitation response

  24. Entity Relationship Diagram

  25. Deployment Diagram

  26. Design Patterns & Frameworks • Python’s Django framework - Model class handles the ORM - Callback handling - OAuth Implementation • Design Patterns - Wrapper Façade Pattern - provides implied interface for several operations

  27. NCS PAYPAL • provides cheap transaction fees (2.2% per transaction). • provides packages for non-profit organization. • provides extensive documentation for performing automatic refund. • supports wide range of countries and has wide popularity and trust. Facebook API • Allows users to directly login using their Facebook account. • Allows access to their personal information • Architected Agile

  28. Life Cycle Plan OmkarYerunkar

  29. 577 a,b Team Members

  30. Estimation • Available members: • 6 members on-campus • Duration: • 10 weeks – 577b • Efforts: • 15 hours per week • COCOMO Estimated Effort: • 10.45 person-month most likely • Staff = 10.45/1.67 = 6.25

  31. Re-baseline Foundation (Jan 13- Feb 10) • Rebaseline the project(Jan 13- Jan 24) • Prepare for development phase • Prepare for Rebaselined development Commitment Iteration • Work Products Preparation RDCR(Jan 24- Feb 07)

  32. Re-baseline Foundation (Jan 13- Feb 10) • Modules:- • Profile Management • Donation Management • Goal Creation and Tracking • Capabilities Implemented:- • Login • Register • Create Goal • Invite sponsor • Select charity organization

  33. Construction Iteration 1( Feb 10- Mar 26) • Modules:- • Profile Management • Donation Management • Goal Creation and Tracking • Capabilities:- • Achieve Goal • Respond to the sponsorship request • Update weight • Login (via Facebook) • Monitor Payment • Track Goal – Graph • Delete Goal

  34. Detailed Plan

  35. Construction Iteration 2(Mar 27- Apr 14) • Modules:- • Donation Management • Goal Creation and Tracking • Capabilities:- • Posting on Facebook • Report Generation

  36. Detailed Plan

  37. Transition Iteration Detailed Plan

  38. Quality Management Abdulkareem & Hasan

  39. Risk Analysis

  40. Metrics • Progress Indicator Metric • Cumulative Completed Tasks • Plan vs. Actual • Test Case Metric • Cumulative Completed Test Cases • Plan vs. Actual • Passed vs. Failed

  41. Traceability Matrix

  42. Code Quality. • Commenting. • Readable variable names. • Indentation. • Code versioning using Github.

  43. Test Cases • TC-01-01 Verify successful Login • TC-01-02 Verify successful Login using Facebook credentials • TC-01-03 Verify unsuccessful Login • TC-01-04 Verify successful registration • TC-02-01 Verify successful goal creation • TC-03-01 Verify goal tracking • TC-04-01 Verify weight updating • TC-05-01 Verify achieve Goal • TC-05-02 Verify delete Goal • TC-06-01 Verify sponsor's invitation • TC-06-02: Verify successful sponsor donation • TC-07-01 Monitor payment for a valid transaction • TC-07-02 Verify invalid transaction

  44. Test Cases

  45. Test Cases

  46. Test schedule

  47. Definition of done (DoD) • All modules implemented • Code review completed • All test cases passed • Source code checked into Git repository • Website deployed on production server • Documentation artifacts consistent • All architecture documentations up to date • All Bugzilla issues closed or deferred to later release • Risks are resolved or mitigated • Requirements are traceable

  48. Demo

  49. Thank you Team 08

More Related