ianyong / pe Goto Github PK

On page 11 of the user guide PDF,

Searches only account for full words, e.g. Deploy will not match Deployment but Stand-up will match Up button and Laptop stand.

Hyphenated words are typically considered to be full words. The example provided is contradictory.

Because the TO parameter of the add command for the meeting mode does not take in a date, it is not possible to add meetings that cross over to the next day, such as from 11pm of today to 1am of tomorrow. This is a valid use case as some regional offices need to schedule meetings with the company HQ, which would take place during the timezone of the HQ.

Merge conflict marker found on page 3 of the developer guide. This is high severity as it indicates a lack of peer reviews before merging.

No scrollbars or any other indicators.

Commands input in deliverable mode:

find define
add t/Define marketing strategy by/12-12-2020 23:59 m/1.0 c/John Martin, Abby Li

After adding a new deliverable, the displayed list of deliverables is reset to show all deliverables. The same goes for editing. This behaviour is not defined anywhere and is inconsistent with other commands such as done which do not reset the displayed list.

consolidates is used along with manage which is inconsistent grammar.

Productiv is a one-stop desktop app for product managers like yourself to organise your
deliverables, meetings and contacts so that you can track your product’s development easily.

Productiv aims to be a one-stop desktop application. However, there is no link whatsoever between contacts, deliverables and meetings. This means that if the user wishes to look up a contact that is described in a deliverable or meeting, they would need to manually go over to the contacts mode and use the find command. Even then, there is no guarantee that the contact actually exists, as well as no way to disambiguate between contacts with the same name (in deliverables and meetings, only the name of each contact is meant to be recorded as per the user guide). This significantly reduces how helpful the application is in being a "one-stop desktop application".

When the feedback box has a very long output, the output is truncated. While it is possible for the user to scroll horizontally via highlighting the text, this is not ideal. There is no visual feedback to the user that this is at all possible (no scrollbars) and necessitates the use of a mouse.

Main has two classes called Main and MainApp.

This sentence is confusing as no context is given to the first instance of Main in the sentence. Nowhere is it stated that it is a component or a class, or whatever it is supposed to be.

The arrow from Command to Model appears to have its multiplicity defined twice.

On the deliverable mode, entering a large index such as view 999999999999999999999 results in the following message being displayed even though 999999999999999999999 is a positive integer:

Invalid command format! 
view: Displays the details of the deliverable identified by the index number used in the displayed deliverable list.
Parameters: INDEX (must be a positive integer)

When using the view command, there is duplicate information being displayed in both the feedback box and the right panel.

Every time the dashboard mode is switched to, the user needs to wait for the overall completion percentage animation to finish playing before the actual percentage is viewable. In the worst case of all the deliverables being completed, this is a process that takes up to 3 seconds. This defeats the point of it being a "quick overview" as stated in the user guide.

Page 14 of the developer guide.

Not sure if this is just due to the PDF file. Page 6 of the developer guide.

The following screenshot is Productiv upon first starting up (default sample data, screen resolution):

More than half of the sample titles are being cut off even though the entire right panel is empty. When the view command is not being used, the list should be expanded to take on the entire space of the application. This would allow the user to be able to glean much more information at a glance.

When the user types in the clear command, the data on the specific mode the user is on is irreversibly erased. This is quite dangerous as the user is not prompted on whether they wish to proceed.