Requirements per module
*All modules under dashboard should be able to navigate back to dashboard.
LOGIN
- should authenticate/verify the credential properly before having access to the
system.
- state incorrect fields generally (ex. Username or Password is incorrect)
DASHBOARD
- should navigate properly (including an exit button and/or logout button)
USER MANAGEMENT (Create/Register User)
- Try field validation
- Check for character lengths.
- Name fields should be greater than 2 characters. (minsan kasi may surname na
'Sy')
- Username should be greater than 3
- Password fields should be 8 characters long, WITH LETTERS AND NUMBERS (kahit eto
nlang muna sa password wag na yung check for uppercase at special characters)
- password should match verify password.
- lastly, check for duplicate user through usernames.
PRODUCT MANAGEMENT (Add, Edit, Delete)
- Check for duplicate products through its name. (Add and Edit)
- Added, edited, deleted item should reflect immediately in the table.
- Price should not be negative. (Add and Edit)
- (Add) Upon clicking the add button, price and product name should not be empty.
- (Edit) should navigate back to manage screen once updated.
- (Edit) Add cancel button to navigate back to Manage Screen.
STOCK MOVEMENT
- Quantity value should not be less than zero.
- Reason should not be empty.
- There should be a selected product upon submitting.
- (Decrease stock) Display warning message if the INPUT QUANTITY is greater than
the CURRENT QUANTITY/STOCK. (Kasi magiging negative yung stock kapag ganon)
STOCK MONITORING
- Properly Display all items including 0 stock items
- Try adding sort functionality in stocks and product name.
- When the stock is ZERO (0) try saying or displaying "out of stock" if possible.
If not it's fine.
(Pwede kasing yung Data Table ni Java, for example yung column header ay int, ang
tatanggapin niya lang na value ay int, kapag ganon hindi possible ma display yung
String kapag strict talaga si Java.)
TRANSACTION HISTORY
- Properly display all items in the transaction history.
- Default arrangement should always be newest to oldest transaction.
- Try adding the user who made the transaction and adding the time the transaction
was made that day.
