LOSE4GOOD.org (By Team 08) Promote healthy living
Independent Verification and Validation ALI ALOTAIBI
Overall Project Evaluation • Exceptional work and relentless effort from team members to make this project succeed. • It is not a course project anymore! • C.R.A.C.K stakeholder. • Interesting and ambitious project.
Operational Concept Description AnkitKalwar
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.
Desired Capabilities and Goals Organizational Goals
Prototype Manas Jog
Changes from last iteration • Weight validation prototype removed • Facebook login prototype implemented • Mockups covering most win-win conditions added.
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
Mockups • Main website • Sponsor Donation • Monitor Payment
Architecture Arul Samuel Rajkumar
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
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
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. • has a REST API and hence provides a easy way to integrate with our system. Facebook API • Allows users to directly login using their Facebook account. • Allows access to their personal information • REST API and provides a easy way to integrate with our system. • Architected Agile
Life Cycle Plan OmkarYerunkar
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
Re-baseline Foundation (Jan 13- Feb 10) • Rebaseline the project(Jan 13- Jan 24) • Prepare for development phase • Plan for testing • Prepare for Rebaselined development Commitment Iteration • Work Products Preparation RDCR(Jan 24- Feb 07)
Construction Iteration 1( Feb 10- Mar 26) • Modules:- • Profile Management – 80% • Donation Management – 70% • Goal Creation and Tracking – 70% • Capabilities:- • Achieve Goal • Create Goal • Respond to the sponsorship request • Invite sponsor • Add charity organization • Update weight • Login • Register
Construction Iteration 2(Mar 27- Apr 14) • Modules:- • Profile Management – 100% • Donation Management – 100% • Goal Creation and Tracking – 100% • Capabilities:- • Login using Facebook • Delete Goal • Track Goal • Monitor Payment
Feasibility Analysis ShaliniSrinivas
Feasibility Analysis • Business Case Analysis - Program model presented in FCR ARB - Personnel cost has been presented in FCR ARB and revised. - Hardware and software cost presented in FCR ARB - Benefit Analysis has been revised after FCR ARB • ROI Analysis has been revised after FCR ARB • Risk Assesment - Updated the risks – some risks’ magnitude has been reduced, new risks are added for the development phase
Acceptance Test Plan and Cases • Test Strategy : Requirements-test traceability • The test cases have been designed to insure that the implemented functionalities fulfill project requirements as captured in the Win-Win conditions.