Add more sample debts and change PersonBuilder#withDebts to take in vararg of Debt instead of a pre-constructed DebtList

• Number the use cases
• Extract common scenarios to refer to other use cases by number

Give use cases (textual form) for a few representative user stories that need multiple steps to complete. e.g. Adding a tag to a person (assume the user needs to find the person first)

Avoid:

• Important use cases missing (a use case is important if it involves a user interaction that is worthy of documenting e.g., it has multiple extensions -- this is not the same as the feature being important)
• Formatting/notational errors
• Incorrect step numbering
• Unnecessary UI details mentioned
• Missing/unnecessary steps
• Missing extensions

As a user, I can specify if an amount of money in the debt is inclusive or exclusive of GST and service charge, so that I do not have to manually calculate the final debt amount.

As a user I can search for a person by his debt description so that I can easily contact him to repay the debt

Move preparePredicate to ParserUtil class

Note: Many of the given project constraints can be considered NFRs. You can add more. e.g. performance requirements, usability requirements, scalability requirements, etc.

Avoid:

• Not really a Non-Functional Requirement
• Not scoped clearly (i.e., hard to decide when it has been met)
• Not reasonably achievable
• Highly relevant NFRs missing

Create a skeletal version of your Project Portfolio Page (PPP).

• Just the headings are enough. Write to be added soon as placeholders for content.
• PDF conversion not required.
• Follow the details in the panel below this

StorageManager#saveAddressBook throws IllegalArgumentException

As a user I can remove debts so that I do not mistakenly think I have not yet been paid.

As a user I can remove debts so that I do not mistakenly think I have not yet been paid

DebtListBuilder currently starts with a CHICKEN_RICE debt by default, and since there is no way to remove or replace debts from a DebtListBuilder, constructing a DebtListBuilder with no debt to start with (or no CHICKEN_RICE debt) is more difficult (as we have to also construct an empty DebtList and pass it into the constructor)

As a user, I want to be able to sort the list of contacts by name, amount owed and how long they have owed the debt, so that I can quickly decide who to prioritize chasing for debts.

    Should this be a static method of `Debt` instead?

Originally posted by @tsammeow in #67 (comment)

Submission [optional] for Week 6 tP Task 5: Tutorial 1 - Tracing a Command Execution Path

Define terms that are worth recording.

Avoid

• Unnecessary terms missing
• Important terms missing

The methods within ClearDebtCommandTest use the Person constructor instead of PersonBuilder to create a new Person.

Should say cleardebts 3 under example

As a user, I can add debts of the same type to multiple people at once, so that I do not have to spend a long time adding debts into the app.

Update the target user profile and value proposition to match the project direction you have selected.

Give a list of the user stories (and update/delete existing ones, if applicable), including priorities. This can include user stories considered but will not be included in the final product.

Avoid:

• Incorrect format
• All three parts are not present
• The three parts do not match with each other
• Important user stories missing

As a user I can see how much I am owed in total so that I know how much I expect to be paid

As a user I can see an overview of all the debts owed so that I am in better control of my overall financial situation

As a user I can keep track of debts so that I know who owes me money and for what