Writing Product Requirements/poorly written functional requirement statements

From Wikiversity
Jump to navigation Jump to search

Revise each of these poorly written functional requirement statements so that the meet the criteria for well-written statements.[1]

  1. Poorly written functional requirement 1: "The website should look nice and modern."
  2. Poorly written functional requirement 2: "The app needs to be user-friendly and easy to use."
  3. Poorly written functional requirement 3: "The system should be secure."
  4. Poorly written functional requirement 4: "Improve the performance of the application."
  5. Poorly written functional requirement 5: "The website should be compatible with all devices."
  6. Poorly written functional requirement 6: "The app should have good functionality."
  7. Poorly written functional requirement 7: "The system needs to have a strong database."
  8. Poorly written functional requirement 8: "Make the user interface more appealing."
  9. Poorly written functional requirement 9: "The website should load quickly."
  10. Poorly written functional requirement 10: "The app should work offline."
  1. ↑ These statements were provided by ChatGPT in response to the prompt: Provide a variety of poorly written functional requirements statements.
Retrieved from "https://en.wikiversity.org/w/index.php?title=Writing_Product_Requirements/poorly_written_functional_requirement_statements&oldid=2539429"