Incorrect command

[xiaohan28]

Should be "java -jar .\CS2113-W13-4-HealthBuds.jar", unable to run with java -jar tp.jar from unzipped file

[nus-se-script]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Thank you for raising this issue regarding the java -jar command. While we understand that the discrepancy between the expected tp.jar and the actual JAR filename (e.g., CS2113-W13-4-HealthBuds.jar) may cause some initial confusion, this issue does not impact the core functionality of the application. It arises from a documentation oversight rather than a functional flaw.

Issue Explanation:
The reported issue concerns the inability to run the program using the command java -jar tp.jar, as the actual file name differs (e.g., CS2113-W13-4-HealthBuds.jar) in the unzipped archive.

Expected vs Actual:

• Expected: Users should be able to run the app using the documented command java -jar tp.jar.
• Actual: The file provided in the zipped release has a different filename, requiring the user to modify the command accordingly.

Root Cause:
This issue stems from an inconsistency between the filename shown in the User Guide and the actual release artifact name. The UG references tp.jar as a placeholder name, which may not match the actual filename in GitHub releases. (see attached photo)

Bug Classification:
We classify this as a DocumentationBug, as the application itself runs correctly when the correct filename is specified. The issue lies in the instruction format, not in functionality or behavior.

Severity Reclassification Justification:
We propose reclassifying this issue to VeryLow severity based on the following reasoning:

• No Functional Impact: The application runs as expected once the correct filename is specified. There is no breakage or crash.
• Easily Discoverable and Fixable: Users can trivially resolve this by checking the filename before executing the command. Java returns a clear “file not found” error if the name is incorrect.
• Aligned with PE Guidelines: As per the PE triaging guidelines, issues that cause only “minor inconvenience” and are “easily recoverable by user” fall under VeryLow severity.
• Documented in Help Channels: We have updated the documentation post-release and plan to include a future disclaimer encouraging users to verify the filename.

Next Steps:
We will update the User Guide to include a note clarifying that the filename may vary, and users should verify the actual .jar filename before running the command. This improvement will enhance clarity but does not warrant a functionality fix or structural change to the app.

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: The incorrect command is within the scope of the submitted product version because it appears in the User Guide (UG) under the Launch Instructions, which is part of the deliverables for v2.1. Users are expected to follow this guide to start the application.

The java -jar command is incorrect, which is considered a UG bug under inaccuracies in the correctness section as seen below, not a future feature request or unrelated enhancement. Thus, the response should be Accepted, not NotInScope, because the incorrect command hinders user's ability to start the CLI app, a basic operation.

---

❓ Issue type

Team chose [type.DocumentationBug]
Originally [type.FeatureFlaw]

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue severity

Team chose [severity.Low]
Originally [severity.Medium]

• I disagree

Reason for disagreement: While the fix is simple (renaming the .jar), the impact is not minor. The user is unable to start the application at all without manual intervention or prior knowledge to check the actual .jar name. It blocks a core user journey (i.e. starting the app) and also would confuse newer users unfamiliar with CLI or .jar conventions.

Users can still use the product, but only after figuring out the actual .jar name on their own — which not all users will know how to do. This is more than a “minor inconvenience” (as per severity.Low). The issue breaks an essential onboarding experience and impacts usability until manually corrected, which aligns with the severity.Medium issue that "cause occasional inconvenience to some users" (as highlighted in orange).

---