Project Title: Credit card fraud detection

Start Date: 09/08/2019 End Date:N/A

Project Manager: Khyati
Project Sponsor: None
Customer: Major Project
Users: N/A
Stakeholders and Expectations:
Team: Have ready access to individuals with the authority to access the credit card usage
data of the given bank according to the specifications. Be given specific and
detailed feedback on product increments.

Purpose (Problem or opportunity addressed by the project):

People who face issues with the their private information being compromised need that
the bank authorities deal with a solution to cope with the fraud users.
Goals and Objectives: The overall goal is to give users an alternative way to find nearby
hospitals with user required specifications. The research is expected to:
● Provide a solution in finding a fraud user.
Schedule Information (Major milestones and deliverables):
08/09/2019 - Gather requirements
08/14/2019 - Project Charter Complete
08/16/2019 - Scenarios of Use Complete
08/21/2019 - Project Release Plan Complete
08/23/2019 - Requirements Complete
08/28/2019- Project Plan Complete
10/05/2019 - Iteration #1 Plan Complete
10/07/2019 - Technical Prototype Complete
10/14/2019 - Project manager Approved UI Prototype Complete
10/21/2019 - Architecture Document Complete
10/28/2019 - Iteration #1 Complete
11/11/2019 - Test Report Complete
11/18/2019 - Iteration #2 Complete
12/02/2019 - User Guide and System Administration Manual Complete
12/07/2019 - Product Released
Financial Information (Cost estimate and budget information):

Project Priorities and degrees of freedom: Dates are not flexible without prior notice
from the department. This is at the discretion of the team based on approaching deadlines.
Roles are changeable based on workloads of individual team members. Roles are
expected to shift throughout the project as needs arise.
Approach: Iterative and incremental is planned. Feedback will be used from one
iteration to the next. The first iteration will focus on basic functionality of the app.
Subsequent iterations will build upon that and incorporate more features as time allows.
Constraints: Approval is required from our mentor to make this an official app. We are
proceeding with the project while pursuing this consent with the understanding we may
not get it. If consent is denied, the team will create an unofficial App for future use.
Assumptions: We would be needing the details of different hospitals which will be
updated by the hospitals on the web portal about their details and databases if they agree
with our product.
Success Criteria: The project will be considered a success if (1) the team delivers an
operational prototype at the end of the semester with the features mentioned in the goal
section above, and (2) 80% or more of the team members would be willing to work
together on another software project in the future.
Scope: At the minimum, the software will (1) allow users to check their Roo Bucks
balance, and (2) see a list of Roo Bucks locations. Time permitting, the scope could be
extended to include features available to Roo Bucks users online, including adding funds
to their accounts and tracking recent purchases.
Risks and obstacles to success: A risk the team faces is a lack of experience in
developing mobile apps. This lack of experience generates a lot of unknowns. We have
only a best guess for the level of work required for the features we have committed to.
We do not yet have a clear picture of how the code will be implemented.
Signatures

__________________________________
Project Manager

__________________________________
Project Sponsor

__________________________________
Customer

__________________________________
Technical Lead