Description
– As a user, I want to change my password and/or full name.
– As an admin, I want to add a new user into the system.
– As an admin, I want to update the type/class of a user into the system (e.g., from cashier to manager).
– As a manager, I want to add a new product or update a current product in the system.
– As a manager, I want to view a summary report of sales from the system.
– As a cashier, I want to add a new customer or update a current customer in the system.
– As a cashier, I want to add a new purchase or update a current purchase (only price and quantity) in the system.
– As a customer, I want to add a new purchase into the system.
– As a customer, I want to view my purchase history into the system.
– As a customer, I want to search for product information (based on name, price) in
Tasks:
Rewrite two common use cases for each user story. Sketch the screens the system should display in each use case.
Redesign the Data Access layer at the client side that can load/save data to a remote server component
Case1
Case2
Design the server component to perform load/save requests from the Data Access layer at the client side. Describe the protocol for two sides: client and server
Client:
Use Java swing to design interface, and use socket to connect server. first send a request to server check login user account isn’t decided what type user is, for each type of user, display things they can do. And send a request to server changing the server database.
Server:
Server use socket to connect client, and to store the database about user login information and product data, and process Request from a client side and change the database.
Implement the system and test see screen shots
