LOSE4GOOD ( By Team 08 )

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

7. Operational Concept Description

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

9. System Boundary Diagram Gmail

10. Business Workflow Diagram

11. Desired Capabilities and Goals Organizational Goals

12. Level Of Service

13. Prototype Arul

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

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

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

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

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

19. Architecture SheryasDevaraj

20. System Context Diagram

21. Use Case Diagram

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

23. Class Diagram

24. Sequence Diagram – Sponsorship invitation response

25. Entity Relationship Diagram

26. Deployment Diagram

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

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

29. Life Cycle Plan OmkarYerunkar

30. 577 a,b Team Members

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

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

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

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

35. Detailed Plan

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

37. Detailed Plan

38. Transition Iteration Detailed Plan

39. Quality Management Abdulkareem & Hasan

40. Risk Analysis

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

42. Traceability Matrix

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

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

45. Test Cases

46. Test Cases

47. Test schedule

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

49. Demo

50. Thank you Team 08