Extreme programming expresses user requirements as stories, with each story written on the card.
Consider the disadvantages of this approach to the requirements description.
Below is the list of correct/incorrect items.
1. They represent a real situation that commonly arises, so the system will support the most common user operations.
2. Each functional user requirement is presented as a separate user story written on the card.
3. They represent increments of functionality - implementing a story delivers some value to the user.
4. It is easy for users to understand and critique the stories.
Please circle the most comprehensive answer: