Project Report on Expense Tracker

Chapter I
Introduction

Background:
Expense tracking is the process of recording and categorizing all business-related
expenses. This can include fixed expenses like rent and utilities, as well as fluctuating costs like
labor, product orders, and advertising.
Expense tracking can be done daily, over a specific period, or for a particular project. It
helps businesses stay on budget, make necessary adjustments, and improve financial health. By
keeping a daily record of expenses, businesses can avoid digging through receipts and better
manage their budget throughout the year.
Expense tracker software is a type of application designed to help individuals and
businesses keep track of their expenses. The software allows users to record and categorize their
expenses, providing a clear overview of their spending habits and financial situation. Expense
tracker software can help individuals and businesses improve their financial management and
identify areas for cost savings. By consistently tracking expenses, users can gain a better
understanding of their financial situation and make informed decisions about their spending.
By tracking expenses, small business owners can gain a better understanding of their
cash flow, identify areas of excessive or inefficient spending, and prepare for tax season.

Problem Statement:
- Manual Expense Tracking:
 Individuals have been recording their expenses manually on paper or using
spreadsheet applications, leading to inefficiencies and a higher likelihood of
errors.
- Limited Accessibility:
 Users have struggled with limited access to their expense data, especially
when using manual methods or desktop-based tools that are not readily
available on-the-go.
- Lack of Real-Time Information:
 Manual methods or outdated tools does not provide real-time updates on
expenses, making it difficult for users to have an up-to-date understanding of
their financial situation.
- Difficulty in Budgeting:
 Without dedicated budgeting tools, individuals have found it challenging to
set and stick to budgets for different expense categories.
- Security Concerns:
  Users have been concerned about the security of their financial data,
especially when using tools that did not implement robust security measures.
- Limited Analytical Insights:
 Users have lacked tools to analyze their spending patterns, identify trends, or
visualize data through charts and graphs.
- Inefficient Reminder Systems:
 Users have struggled to remember and manage recurring expenses without an
efficient reminder system.
- Currency Limitations:
 Individuals dealing with multiple currencies have found it challenging to
manage and track expenses accurately, especially if their tools lacked
currency conversion features.
- Inconsistency in Data Management:
 Users managing expenses across multiple devices have faced difficulties in
maintaining consistent and synchronized data.
- Cumbersome Data Backup:
 Users have lacked easy and automated options for backing up their expense
data, risking potential data loss in case of device issues.

Objective
The Expense Tracker software provides users with a range of benefits, offering a
comprehensive solution to address common challenges associated with personal finance and
expense management. Here are the key benefits that users can derive from using the software:
 Efficient Expense Tracking:
Users can effortlessly record and categorize their expenses in real-
time, reducing the manual effort associated with traditional methods.
 Real-Time Financial Awareness:
The software provides users with an up-to-date overview of their
financial situation, helping them stay informed about their spending
patterns and available budget.
 User-Friendly Interface:
The intuitive and user-friendly interface simplifies navigation and
ensures a seamless user experience, making it easy for individuals to
manage their expenses.
 Automated Budget Management:
Users can set budgets for different expense categories and receive real-
time updates, alerts, and insights to help them stay within their
financial limits.
  Secure Data Management:
The software implements security measures such as user
authentication, local data encryption, and secure data transmission,
ensuring the confidentiality and integrity of user financial data.
 Visual Analytics and Insights:
Users gain valuable insights into their spending patterns through visual
representations, charts, and graphs, enabling them to make informed
financial decisions.
 Expense Reminders:
The software allows users to set reminders for recurring expenses,
helping them stay organized and avoid missing payments or deadlines.
 Data Backup and Restore:
Users can easily backup and restore their expense data, providing a
safety net against data loss in case of device issues or transitions to
new devices.
 Customizable Expense Categories:
The software often allows users to customize expense categories,
ensuring that the application adapts to their individual financial needs
and preferences.
 Regular Updates and Improvements:
Regular software updates ensure that users receive new features,
performance improvements, and security enhancements, contributing
to an evolving and reliable user experience.

Scope
The Expense Tracker software encompasses a variety of functionalities designed to
streamline expense management and enhance financial awareness. Here are the key software
functionalities:
 Expense Tracking:
Users can effortlessly record individual expenses, including details such as
amount, category, and description.
 Expense Categories:
Provides predefined and customizable categories for organizing and
categorizing expenses.
 Dashboard:
Displays a summary of the current month's expenses, budget status, and
visual representations of spending patterns.
  Date and Time Stamp:
Automatically records the date and time of each expense entry.
 Security Measures:
Implements secure login with username and password.
Utilizes local data encryption to enhance the security of stored
information.
 Customization Options:
Allows users to customize expense categories to align with individual
preferences and needs.

Report Organization
This report on an Android expense tracker is organized into five chapters: Chapter I
introduces the topic and outlines the purpose, scope, and definitions. Chapter II details the
functional and non-functional requirements of the system. Chapter III describes the overall
system design and architecture. Chapter IV explains the testing approaches and validation
methods used. Finally, Chapter V summarizes the project outcomes and reflects on the success of
the Android expense tracker.

Process Model
The development methodology for the Android Expense Tracker software follows an
iterative and incremental approach, combining principles from agile methodologies, particularly
Scrum framework.
 Agile Principles:
 Emphasis on customer collaboration and responding to change over
rigid planning.
 Frequent iterations and releases to gather feedback early and
continuously improve the software.
The Android Expense Tracker software follows an agile development process, which is
characterized by its iterative and incremental nature. Within the broader agile umbrella, the
specific process model used is a blend of Scrum practices.
Scrum is a widely adopted agile framework that provides a structured yet flexible
approach to software development. The Scrum framework is an agile process model widely used
for software development projects. It emphasizes iterative development, collaboration, and
adaptability to changing requirements. Scrum involves organizing work into fixed-length
iterations called sprints, with regular sprint reviews and retrospectives to facilitate continuous
improvement.
So, in the context of the Android Expense Tracker software, the Scrum framework, which
is part of the broader agile methodology, is likely the chosen process model for development.
This choice allows for flexibility, frequent releases of incremental features, and close
collaboration between development teams and stakeholders.
Here are the key elements from Scrum that are likely integrated into the development process:
 Sprints:
 Development is organized into fixed-duration iterations called sprints,
typically lasting 2-4 weeks.
 Each sprint has a predefined goal and results in a potentially shippable
product increment.
 Scrum Team:
 The development team is cross-functional, consisting of members with
diverse skills such as developers, designers, and testers.
 The team collaborates closely to deliver high-quality software.
 Product Backlog:
 The product backlog is a prioritized list of features, user stories, and
tasks that need to be addressed in the project.
 Items in the backlog are continuously refined and reprioritized based
on changing requirements and feedback.
 Sprint Planning:
 At the beginning of each sprint, the team conducts sprint planning
sessions to select items from the product backlog for implementation
during the sprint.
 Goals and tasks for the sprint are defined during this planning session.
 Daily Stand-up Meetings:
 The team holds daily stand-up meetings to provide updates on
progress, discuss any challenges, and plan for the day's work.
 Sprint Review:
 At the end of each sprint, a sprint review is conducted to showcase the
completed work to stakeholders and gather feedback.

 Sprint Retrospective:
 A sprint retrospective is held after each sprint to reflect on the team's
performance, identify areas for improvement, and adjust processes
accordingly.
 Continuous Integration and Testing:
 Continuous integration practices ensure that code changes are
integrated regularly, and automated testing is employed to maintain
software quality.
  Adaptability to Change:
 The Agile and Scrum framework embraces change, allowing the team
to adapt to evolving requirements and customer feedback throughout
the development process.
 User Involvement:
 Regular collaboration with stakeholders, including end-users, ensures
that the delivered software aligns with user needs and expectations.

The selection of the Scrum framework, a key component of the agile methodology, for
the development of the Android Expense Tracker software is rooted in its distinct advantages and
alignment with project requirements.
The iterative and incremental nature of agile methodologies, particularly Scrum, allows
for the continuous delivery of functional software increments, facilitating quick adaptation to
evolving project requirements.
This approach offers flexibility and adaptability, enabling the development team to
respond promptly to changing needs and deliver valuable features at regular intervals. Scrum's
emphasis on collaboration, frequent communication, and regular ceremonies such as sprint
planning, daily stand-ups, and retrospectives fosters a clear understanding among team members
and stakeholders.
Moreover, the continuous feedback loop in Scrum ensures that client expectations are
closely aligned with the delivered product, enhancing client satisfaction. The framework's risk
mitigation strategies, empowerment of development teams, and predictable delivery schedule
further contribute to its suitability for the Android Expense Tracker project.
Ultimately, the Agile and Scrum methodologies provide a dynamic and responsive
framework for developing software that meets user needs and adapts to the evolving landscape of
the project.
 Chapter II
Software Specifications

Requirements Specification is a detailed document that describes the purpose, functionality,

behavior, and constraints of a software system or application. It serves as a blueprint for software
development by documenting the needs and expectations of stakeholders, including clients,
users, and developers.
Functional Requirements: Describes the specific functions, features, and capabilities of the
software system. It includes detailed descriptions of user interactions, system behaviors,
input/output requirements, and expected outcomes.
Non-Functional Requirements: Specifies the quality attributes and constraints that the software
must adhere to, such as performance, reliability, security, usability, scalability, and
maintainability. Non-functional requirements often include measurable criteria for evaluation.

The requirements for the Expense Tracker software is shown below:-

 Functional Requirements:

 Expense Tracking:

The system should allow users to add, edit, and delete expenses. Each
expense should have a date, category, description, and amount.

 User Authentication:
The system should support user authentication to ensure secure access to
personal financial data.
 Expense Entry:
Users should be able to enter individual expenses, including amount, date,
category, and description.
 Expense Categorization:
The system should allow users to categorize expenses into predefined or
customizable categories.
 Visual Analytics:
 The system should provide visual representations of spending patterns
through charts and graphs.
 Reminders:
Users should have the ability to set reminders for recurring expenses or
important financial dates.
The system should provide timely notifications and alerts for approaching
budget limits or important financial events.
 Data Backup and Restore:
Users should have the ability to backup and restore their expense data.
 Non-Functional Requirements:
 Performance:
The system should be responsive, with minimal latency in loading data
and generating visualizations.
 Reliability:
The system should be reliable, ensuring accurate tracking and storage of
financial data.
 Compatibility:
The software should be compatible with various Android devices and
screen sizes.
 Security:
The system should have robust security measures to protect user data from
unauthorized access or breaches.
 Usability:
The app should be easy to use, with a clean and intuitive user interface.
 Scalability:
The app should be able to handle a large number of users and a large
amount of data.
User stories for above requirements are listed below:

User Story 1: Add Income

As a user, I want to be able to add my income to the app so that I can keep track of my
earnings.
Acceptance Criteria:
1. User can add a new income entry with a category, description, and amount.
2. The current date should be selected by default for the income entry.
3. User should be able to select a different date for the income entry.
4. User should be able to select a category from a dropdown list or add a new
category.
5. User should be able to add a description of the income entry with a maximum of
140 characters.
6. User should be able to enter the amount of the income in euros.

User Story 2: Add Expense

As a user, I want to be able to add my expenses to the app so that I can keep track of my
spending.
Acceptance Criteria:
1. User can add a new expense entry with a category, description, and amount.
2. The current date should be selected by default for the expense entry.
3. User should be able to select a different date for the expense entry.
4. User should be able to select a category from a dropdown list or add a new
category.
5. User should be able to add a description of the expense entry with a maximum of
140 characters.
6. User should be able to enter the amount of the expense in euros.

User Story 3: Manage Categories

As a user, I want to be able to create and manage categories for my expenses and income.
Acceptance Criteria:
1. User should be able to add, edit, and delete categories.
2. User should be able to assign a category to an expense or income.
User Story 4: View Transactions
As a user, I want to be able to view all my transactions in the app so that I can see my
income and expenses in one place.
Acceptance Criteria:
1. User can view a list of all income and expense entries.
2. User can filter the list by date, category, or income/expense.
3. User can see the date, category, description, and amount for each transaction.
4. User can see the total amount spent and earned for the current month.

User Story 5: View Reports

As a user, I want to be able to view reports of my expenses and income so that I can see my
spending patterns.
Acceptance Criteria:
1. User can view reports of expenses and income for the current month.
2. User can view reports of expenses and income for the current year.
3. User can view reports of expenses and income for a custom date range.
4. User can view reports of expenses and income by category.
5. User can view reports of expenses and income by payment method.
6. User can view reports of expenses and income as a pie chart or a bar chart.

User Story 6: Set Budget

As a user, I want to be able to set a budget for each category so that I can keep track of my
spending.
Acceptance Criteria:
1. User can set a budget for each category.
2. User can see the amount spent and the remaining budget for each category.
3. User can see the total amount spent and the total budget for all categories.
User Story 7: Set Reminders
As a user, I want to be able to set reminders for my bills so that I don't forget to pay them.
Acceptance Criteria:
1. User can set a reminder for a bill.
2. User can set the date and time for the reminder.
3. User can set a recurring reminder for a bill.
4. User can see the list of reminders.
5. User can mark a reminder as completed.

User Story 8: Backup and Restore

As a user, I want to be able to backup and restore my data so that I don't lose my data if I lose
my phone.
Acceptance Criteria:
1. User can backup their data to the cloud.
2. User can restore their data from the cloud.
3. User can backup their data to a local file.
4. User can restore their data from a local file.

User Story 9: Sync Data

As a user, I want to be able to sync my data across multiple devices so that I can see my
transactions on all my devices.
Acceptance Criteria:
1. User can sync their data to the cloud.
2. User can see their transactions on all their devices.
3. User can add a new transaction on one device and see it on all their devices.

User Story 10: Ensure Compatibility

As a user, I want the app to be compatible with a wide range of Android devices and
versions.
Acceptance Criteria:
1. The app should be compatible with Android 5.0 and later.
2. The app should be compatible with a wide range of screen sizes and resolutions.
 Chapter III
Architecture and Design

In software engineering, architecture and design refer to the process of planning and
structuring a software system. While the terms are often used interchangeably, they refer to
different stages of this process.
Software architecture is the high-level structure of a software system, including the
components that make up the system and how they interact with each other. It provides a
blueprint for the system and helps to ensure that it meets the necessary technical and operational
requirements. Architectural decisions include the selection of structural elements and their
interfaces, behavior as specified in collaborations among those elements, and composition of
these structural and behavioral elements into large subsystems.
On the other hand, software design is the process of creating a detailed plan for the
software system. It includes defining the elements of the system, how they fit together, and how
they will be implemented. The design plan acts as a blueprint during the development process
and guides the implementation tasks, including detailed design, coding, integration, and testing.
Both software architecture and design are critical to the success of a software project. A
well-designed architecture can reduce business risks, expose the structure of the system, handle
functional and quality requirements, and improve external confidence in the system. Meanwhile,
a good design can help to negotiate system requirements, act as a blueprint during development,
and guide the implementation tasks.
It's worth noting that software architecture and design are still emerging disciplines
within software engineering, and there is a lack of standardized ways to represent architecture
and analyze methods to predict whether architecture will result in an implementation that meets
the requirements. However, there are best practices and guidelines that can help to ensure that
the architecture and design of a software system are of high quality.
Architectural design of android expense tracker:

 Level-0 DFD
DFD is the graphical representation of a system’s data and how the process
transform the data. Unlike flowcharts, DFD’s do not give detailed information of
modules but graphically describe a system’s data and how the data interact with the
system.
A Level-0 Data Flow Diagram (DFD) is the highest level of abstraction in a DFD,
which provides a broad overview of the entire system. It is the most basic type of DFD
that provides a high-level overview of the entire system, showing the main processes,
data flows, and data stores in the system, without going into the details of each process.
A Level-0 DFD typically includes external entities that interact with the system,
as well as the main data inputs and outputs. It is also known as a context-level DFD, as it
provides the context of the system in relation to its external entities. The Level-0 DFD
helps to identify the scope and boundaries of the system and provides a high-level
understanding of how the system works.
 Class Diagram
A class diagram in software engineering is a type of UML (Unified Modeling
Language) diagram that visually represents the structure and relationships of classes within a
system. Class diagrams are used in the design and documentation phases of software
development and are an integral part of object-oriented design.
In class diagrams, classes are depicted as boxes, each containing three
compartments: one for the class name, one for attributes (data members), and one for
methods (functions or procedures). Lines connecting classes illustrate associations, showing
relationships such as one-to-one or one-to-many.
Class diagrams provide a high-level overview of a system’s design, helping to
communicate and document the structure of the software. They are a fundamental tool in
object-oriented design and play a crucial role in the software development lifecycle.
There are various types of relationships in class diagrams, including association,
aggregation, composition, inheritance, realization, and dependency. Each type of relationship
serves a specific purpose and helps to represent the connections and interactions between
classes in a system.
 Sequence Diagram
A sequence diagram in software engineering is a type of interaction diagram that
details how operations are carried out, focusing on the time aspect of the interaction. It
shows the order of messages sent between objects involved in an operation, with time
progressing as you go down the page. Objects are listed from left to right according to
when they participate in the message sequence.
Sequence diagrams capture various elements, including lifelines, activations, call
messages, return messages, self-messages, recursive messages, create messages, destroy
messages, duration messages, and notes. They can be somewhat close to the code level,
describing the communication between any two lifelines as a time-ordered sequence of
events.
In a sequence diagram, an individual participant is represented by a lifeline,
positioned at the top of the diagram. An actor, which is out of the scope of the system,
represents a role played by an entity that interacts with the subject. Actors can represent
human users, external hardware, or other subjects, and may or may not represent physical
entities.
 Chapter IV
Implementation and Testing

Implementation and testing are crucial stages in software engineering. Implementation

refers to the process of organizing and prioritizing tests and creating test data, test harnesses, and
automated test scripts. During this stage, the Test Analyst or Test Manager ensures that all
prerequisites are handled and implements the test designs as test cases, test procedures, and test
data.
Testing, on the other hand, verifies the functionality of the software by executing the
implemented test designs. It is essential to choose the right tests and execute them in the correct
order, especially when using risk-based strategies. The Test Manager must define the priority
and execution order of manual and automated tests and acquire the necessary tools for testing,
such as automation testing tools and test data generation tools.
Early test implementation is a good practice as it helps detect bugs early, saving time and
resources while improving overall quality. Implementation involves several steps, such as
planning tests, designing test data, creating test cases, prioritizing tests based on risks, finalizing
the timeline for testing, and test execution schedules.
In summary, implementation and testing are integral parts of software engineering,
ensuring that the software functions as intended and meets the specified requirements. Proper
implementation and testing strategies can significantly improve the quality of the software and
reduce the risk of defects and issues.
SCREEN UI
 Test Cases for Android Expense Tracker Write in tabular form

Creating test cases for an Android expense tracker involves examining various functionalities
and scenarios to ensure the app works as expected. Here's a list of test cases covering different
aspects of an expense tracker app:

 Verify the User Login

Test Feature Test Case Test Steps Result Actual Result Status
Case Description (Pass/Fail)
ID

TC01 User Verify user 1. Open the app User is logged User is logged Pass
authenticatio can log in 2. Enter valid in and directed in and
n with valid username and to the home directed to the
credentials password screen home screen
3. Tap “Log In”

TC02 User Verify user 1. Open the app An error An error Pass
authenticatio cannot log in 2. Enter invalid message is message is
n with invalid username and displayed and displayed and
credentials password user is not user is not
3. Tap “Log In” logged in. logged in.
  Expense Entry:

Test Test Test Test Steps Test Data Expected Actual Result Status
Case Scenario Case Result (Pass/
ID Fail)
TC- Verify Add Test for 1. Tap on “Add Expense Expense The expense is Pass
EE-01 Expense adding an Expense” details such should be added
Functionality expense 2. Enter expense as amount, added successfully and
details category and successfully displayed
3. Tap on “Save” date and displayed

TC- Verify Edit Test for 1. Click on the Edited The expense The expense is Pass
EE-02 Expense editing an expense that expense should be edited
Functionality expense needs to be edited details such edited successfully
2. Edit the as amount, successfully
expense details category, and the
3. Click on the and date updated details
‘Save’ button. should be
4. Verify that the displayed
expense has been
edited
successfully

TC- Verify Delete Test for 1. Click on the The expense The expense is Pass
EE-03 Expense Deleting expense that should be deleted
Functionality an needs to be deleted successfully and
Expense deleted. successfully not displayed in
2. Click on the N/A and not the list of
‘Delete’ button displayed in expenses
3. Verify that the the list of
expense has been expenses
deleted
successfully
  Expense Categories:

Test Test Test Case Test Steps Test Expected Actual Result Status
Case Scenario Data Result (Pass/
ID Fail)
TC- Verify Verify that 1. Navigate to the All predefined All predefined Pass
EC- Predefined all expense categories page expense expense
01 Expense predefined 2. Verify that all categories are categories are
Categories expense predefined expense N/A displayed displayed
categories categories are displayed correctly correctly
are correctly
displayed
correctly
TC- Verify Verify that 1. Navigate to the Custom Custom Custom Pass
EC- Custom users can expense categories page Category Category Category
02 Expense add custom 2. Click on the "Add Name Name is Name is
Categories categories Category" button displayed in displayed in
3. Enter the name of the the list of the list of
custom category. expense expense
4. Click on the "Save" categories categories
button
5. Verify that the custom
category is displayed in
the list of expense
categories
TC-EC- Verify Verify that 1. Navigate to the Custom Custom Custom Pass
03 Deleting users can expense categories page Category Category Category
Custom delete 2. Click on the "Delete" Name Name is Name is
Expense custom button next to the custom removed from removed from
Categories categories category the list of the list of
3. Verify that the expense expense
custom category is categories categories
removed from the list of
expense categories
TC-EC- Verify Verify that 1. Navigate to the Expense The expense The expense Pass
04 Expense expenses are expense page is correctly is correctly
Categorizati correctly 2. Verify that the categorized categorized
on categorized expense is correctly
categorized
  Budget Management:

Test Test Test Case Test Steps Test Expected Actual Status
Case Scenario Data Result Result (Pass/
ID Fail)
TC- Verify Verify that 1. Tap on the "Budget Budget A new The new Pass
BM- Monthly users can set Management" button amount monthly monthly
01 Budget a monthly 2. Tap on the "Create : $500 budget with budget is
Creation budget Budget" button the specified displayed in
3. Select "Monthly" as the amount is the list of
budget period created budgets
4. Enter the budget amount
5. Tap on the "Save"
button
TC- Verify Verify that 1. Tap on the "Budget Budget A new weekly The new Pass
BM- Weekly users can set Management" button amount budget with weekly
02 Budget a weekly 2. Tap on the "Create : $100 the specified budget is
Creation budget Budget" button amount is displayed in
3. Select "Weekly" as the created the list of
budget period budgets
4. Enter the budget amount
5. Tap on the "Save"
button
TC- Verify Verify that 1. Tap on the "Expense A notification The Pass
BM- Budget users Tracker" button is displayed notification
03 Notification receive 2. Add expenses until the indicating that is displayed
notifications budget is exceeded the budget has
when they 3. Wait for the notification N/A been
exceed their exceeded
budgets

TC- Verify Verify that 1. Tap on the "Budget Budget The budget The updated Pass
BM- Budget users can Management" button. amount amount is budget is
04 Editing edit existing 2. Tap on the budget that : $600 updated to the displayed in
budgets needs to be edited. new value the list of
3. Edit the budget amount. budgets.
4. Tap on the "Save"
button.
TC- Verify Verify that 1. Tap on the "Budget The budget is Pass
BM- Budget users can Management" button deleted and no
05 Deletion delete 2. Tap on the budget that N/A longer
existing needs to be deleted displayed in
budgets 3. Tap on the "Delete" the list of
button budgets
  Reports and Analytics:

Test Test Test Case Test Steps Test Expected Actual Status
Case Scenario Data Result Result (Pass/
ID Fail)
TC- Verify Verify that 1. Tap on the "Reports User can view Reports and Pass
RA- Reports and users can and Analytics" tab. reports and analytics are
01 Analytics view reports 2. View the displayed analytics for displayed.
Feature and analytics reports and analytics. N/A their expenses. User can
for their Reports and view and
expenses analytics are interact with
displayed in the the reports
form of pie
charts, bar
graphs, etc.
TC- Verify Verify that 1. Tap on the "Reports Time Reports and Reports and Pass
RA- Reports Data reports and Analytics" tab. period: analytics are analytics are
02 Accuracy accurately 2. Select a specific Last 7 displayed based displayed.
reflect time period or days on the selected Data is
expense data category. criteria. accurate and
based on 3. Verify that the Category: Data is accurate up-to-date
selected displayed reports and Food and up-to-date
criteria analytics match the
selected criteria.
  Security:

Test Test Test Case Test Steps Test Expected Actual Status
Case Scenario Data Result Result (Pass/
ID Fail)
TC- Verify Data Test for 1. Check the database The user data The user data Pass
01 Encryption checking if for the presence of should be is encrypted
user data is encrypted data. encrypted and and securely
encrypted 2. Verify that the data N/A securely stored in the
is encrypted and stored in the database.
securely stored. database.
TC- Verify No Test for 1. Check the database The The Pass
02 Plain Text checking if for the presence of passwords passwords
Passwords sensitive plain text passwords. should not be are not stored
information 2. Verify that the N/A stored in plain in plain text
is not stored passwords are not text in the in the
in plain text stored in plain text. database. database.
TC- Verify Test for 1. Enter data with SQL Data with The app The app is Pass
03 Protection checking if injection code. SQL should not be not
Against the app is 2. Verify that the app is injection vulnerable to vulnerable to
SQL protected not vulnerable to SQL code SQL SQL
Injection against SQL injection. injection. injection.
injection

TC- Verify Test for 1. Enter data with Data with The app The app is Pass
04 Protection checking if cross-site scripting cross-site should not be not
Against the app is code. scripting vulnerable to vulnerable to
Cross-Site protected 2. Verify that the app is code cross-site cross-site
Scripting against not vulnerable to cross- scripting. scripting.
cross-site site scripting.
scripting
 Chapter V
Project Management and Risk Management

Project Management
Project management is the process of planning, organizing, and
controlling resources to bring about the successful completion of specific project goals and
objectives. It involves the following key processes:
 Initiating: Identifying the project's goals and objectives, and getting approval to move
forward.
 Planning: Developing a detailed plan for the project, including timelines, resources, and
budgets.
 Executing: Carrying out the plan and managing the project's day-to-day activities.
 Monitoring and Controlling: Tracking the project's progress and making adjustments as
needed to stay on track.
 Closing: Wrapping up the project and documenting lessons learned for future projects.

Risk Management
Risk management is the process of identifying, assessing, and
prioritizing risks, and then coordinating and implementing risk management strategies to reduce
the probability or impact of adverse events. It involves the following key processes:
 Risk Identification: Identifying potential risks that could impact the project.
 Risk Analysis: Assessing the likelihood and impact of each risk.
 Risk Evaluation: Prioritizing risks based on their likelihood and impact.
 Risk Treatment: Developing and implementing strategies to reduce the probability or
impact of high-priority risks.
 Risk Monitoring and Review: Continuously monitoring risks and reviewing the
effectiveness of risk management strategies.
Schedule Table:

Tasks Start Date End Date Depends On

Requirement Gathering 2024-04-29 2024-05-05 None
Design 2024-05-06 2024-05-15 Requirement Gathering
Development 2024-05-16 2024-06-30 Design
Testing 2024-07-01 2024-07-15 Development
Deployment 2024-07-16 2024-07-17 Testing
User Acceptance Testing 2024-07-18 2024-07-22 Deployment
Release 2024-07-23 2024-07-24 User Acceptance Testing

Gantt chart:
To create a Gantt chart, tools like TeamGantt, Microsoft Project, or Google Sheets are used.
 Requirement Gathering: This task will span from April 29, 2024, to May 5, 2024. It
will be the first task in the Gantt chart.
 Design: This task will start on May 6, 2024, and end on May 15, 2024, following the
Requirement Gathering task.
 Development: This task will start on May 16, 2024, and end on June 30, 2024. It will be
the longest task in the chart.
 Testing: This task will span from July 1, 2024, to July 15, 2024, following the
Development task.
 Deployment: This task will occur from July 16, 2024, to July 17, 2024, and will be the
second shortest task.
 User Acceptance Testing: This task will span from July 18, 2024, to July 22, 2024,
following the Deployment task.
 Release: This task will occur from July 23, 2024, to July 24, 2024, and will be the
shortest task in the chart.
The Gantt chart will visually represent the tasks, start and end dates, and the duration of each
task in a bar chart format. Tasks will be listed on the left side, and the timeline will be displayed
on the top. Bars will correspond to tasks and will span horizontally from the start to end date.
To create a visual Gantt chart for the Android expense tracker schedule table, following steps are
followed:

 Set up the timeline: Start by setting up the timeline, which will span horizontally across
the top of the chart. You can configure the timeline to measure time in days, weeks, or
months, depending on the project's needs.

 Add tasks: Create horizontal bars for each task, spanning across the timeline and down
the page. Label each bar with the corresponding task name, such as "Requirement
Gathering," "Design," "Development," "Testing," "Deployment," "User Acceptance
Testing," and "Release."

 Define dependencies: Use lines to connect tasks that depend on each other. For example,
the "Design" task depends on the "Requirement Gathering" task, and the "Development"
task depends on the "Design" task.

 Track progress: Add a progress feature to show whether you're on track for milestones
and deadlines or falling behind. In this case, the red vertical line represents progress.

 Assign tasks: Assign team members to tasks by tagging them directly in their required
tasks.

Here's a description of the Gantt chart: (in table form)

 Timeline: The project's timeframe spans from April 29, 2024, to July 24, 2024.
 Tasks:
o Requirement Gathering (April 29, 2024 - May 5, 2024)
o Design (May 6, 2024 - May 15, 2024)
o Development (May 16, 2024 - June 30, 2024)
o Testing (July 1, 2024 - July 15, 2024)
o Deployment (July 16, 2024 - July 17, 2024)
o User Acceptance Testing (July 18, 2024 - July 22, 2024)
o Release (July 23, 2024 - July 24, 2024)
 Dependencies:
o Design depends on Requirement Gathering
o Development depends on Design
o Testing depends on Development
o Deployment depends on Testing
o User Acceptance Testing depends on Deployment
o Release depends on User Acceptance Testing

 Assignee: Team members can be assigned to tasks by tagging them directly in their
required tasks.
Risk Analysis for Android Expense Tracker
This document outlines the risk analysis for an Android Expense Tracker application, using the
following activities:
1. Risk Identification
In this phase, potential risks associated with the Android Expense Tracker are identified. Some
common risks include:
 Data Breach: Unauthorized access to sensitive user data, such as financial information.
 Inadequate Data Protection: Insufficient encryption or protection measures for user data.
 System Failure: The application may become unavailable due to technical issues or server
downtime.
 Inaccurate Data: The application may produce incorrect expense tracking data due to
bugs or misconfigurations.
 Poor User Experience: The application may not meet user expectations in terms of
usability or performance.
 Legal and Compliance Risks: The application may not comply with relevant financial
regulations or data protection laws.

2. Risk Analysis and Prioritization

In this phase, identified risks are analyzed and prioritized based on their likelihood and impact.

Risk Likelihood Impact Priority

Data Breach High High Critical
Inadequate Data Protection High Medium High
System Failure Medium High High
Inaccurate Data Medium Medium Medium
Poor User Experience Low Low Low
Legal and Compliance Risks Low High High
3. Risk Control
In this phase, measures are taken to mitigate or eliminate identified risks.
 Data Breach: Implement strong encryption, multi-factor authentication, and regular
security audits.
 Inadequate Data Protection: Implement robust encryption, access controls, and regular
security audits.
 System Failure: Implement redundancy, failover, and regular system maintenance.
 Inaccurate Data: Implement automated testing, code reviews, and user feedback
mechanisms.
 Poor User Experience: Implement user testing, feedback mechanisms, and regular
performance optimization.
 Legal and Compliance Risks: Consult with legal experts, implement compliance
measures, and conduct regular audits.

4. Risk Monitoring
In this phase, risks are continuously monitored and assessed for any changes in likelihood or
impact.
 Data Breach: Monitor security logs, conduct regular security audits, and respond to
security incidents promptly.
 Inadequate Data Protection: Monitor encryption and access control mechanisms, and
respond to security incidents promptly.
 System Failure: Monitor system performance, conduct regular maintenance, and respond
to system failures promptly.
 Inaccurate Data: Monitor data accuracy, conduct regular testing, and respond to data
inaccuracies promptly.
 Poor User Experience: Monitor user feedback, conduct regular user testing, and respond
to user experience issues promptly.
 Legal and Compliance Risks: Monitor regulatory changes, conduct regular audits, and
respond to compliance issues promptly.