Final Version

[kfirs127]

issues from the meeting of version 3:

1. diagrams: remake the architecture diagram, it needs to be layer-based and not a copy of the whiteboard diagram. in the whiteboard diagram, we should use regular lines and not arrows and such. need to write persistence on all the classes that use the DB.
2. need to make stronger tests for delayed notifications, and write tests for real-time notifications.
3. in all of the acceptance tests, we need to return the DB as we got him using tearDown and not inside the test. also need to run the tests on a different DB than the one for the system.
4. need to not connect to external system inside the tests.
5. need to add configuration file + init file (both should be external).
6. in connection to the external system we need to deal with errors/timeouts properly.
7. when a guest logged out from the system he should be removed from the DB/when a member logging in delete the guest user he was logged to.
8. need to add caching.
9. need to add a case when the DB is disconnected.
10. add the bidding purchase option

[kfirs127]

new requirments:

1. If an action in the system fails, need to explain to the user why it's failed. and if the action succeeded, need to tell the user that the action succeeded.
2. A new owner can be appointed only under an agreement, and only if all other owners agreed.
3. The system manager can view the action in the system on diffrent groups of users(the groups are specified in the document).
4. Need to add load and stress tests.

[orishac]

issues from meeting of version 3:

1. diagrams: remake the architecture diagram, it's need to be layer-base and not a copy of the white board diagram. in the white board diagram we should use regular lines and not arrows and such. need to write persistance on all the classes that use the DB.
2. need to make stronger tests for delayed notification, and write tests for real-time notifications.
3. in all of the acceptance tests, we need to return the DB as we got him using tearDown and not inside the test. also need to run the tests on a diffrent DB then the one for the system.
4. need not to connect to the external system inside the tests.
5. need to add configuration file + init file (both should be external).
6. in connection to the external system we need to deal with errors/timeouts properly.
7. when a guest logged out from the system he should be removed from the DB/when member logging in delete the guest user he was logged to.
8. need to add caching.
9. need to add a case when the DB is discconected.

1 + 7 done

[orishac]

issues from meeting of version 3:

1. diagrams: remake the architecture diagram, it's need to be layer-base and not a copy of the white board diagram. in the white board diagram we should use regular lines and not arrows and such. need to write persistance on all the classes that use the DB.
2. need to make stronger tests for delayed notification, and write tests for real-time notifications.
3. in all of the acceptance tests, we need to return the DB as we got him using tearDown and not inside the test. also need to run the tests on a diffrent DB then the one for the system.
4. need not to connect to the external system inside the tests.
5. need to add configuration file + init file (both should be external).
6. in connection to the external system we need to deal with errors/timeouts properly.
7. when a guest logged out from the system he should be removed from the DB/when member logging in delete the guest user he was logged to.
8. need to add caching.
9. need to add a case when the DB is discconected.

8 done

[kfirs127]

3. specified

new requirments:

1. If an action in the system fails, need to explain to the user why it's failed. and if the action succeeded, need to tell the user that the action succeeded.
2. A new owner can be appointed only under an agreement, and only if all other owners agreed.
3. The system manager can view the action in the system on diffrent groups of users(the groups are specified in the document).
4. Need to add load and stress tests.

3 is DONE

[orishac]

issues from meeting of version 3:

1. diagrams: remake the architecture diagram, it's need to be layer-base and not a copy of the white board diagram. in the white board diagram we should use regular lines and not arrows and such. need to write persistance on all the classes that use the DB.
2. need to make stronger tests for delayed notification, and write tests for real-time notifications.
3. in all of the acceptance tests, we need to return the DB as we got him using tearDown and not inside the test. also need to run the tests on a diffrent DB then the one for the system.
4. need not to connect to the external system inside the tests.
5. need to add configuration file + init file (both should be external).
6. in connection to the external system we need to deal with errors/timeouts properly.
7. when a guest logged out from the system he should be removed from the DB/when member logging in delete the guest user he was logged to.
8. need to add caching.
9. need to add a case when the DB is discconected.
10. add bidding purchase option

6 + 10 done

left to do: 2,3,4,5,9

[kfirs127]

new requirments:

1. If an action in the system fails, need to explain to the user why it's failed. and if the action succeeded, need to tell the user that the action succeeded.
2. A new owner can be appointed only under an agreement, and only if all other owners agreed.
3. The system manager can view the action in the system on diffrent groups of users(the groups are specified in the document).
4. Need to add load and stress tests.

2 is DONE

[orishac]

issues from meeting of version 3:

1. diagrams: remake the architecture diagram, it's need to be layer-base and not a copy of the white board diagram. in the white board diagram we should use regular lines and not arrows and such. need to write persistance on all the classes that use the DB.
2. need to make stronger tests for delayed notification, and write tests for real-time notifications.
3. in all of the acceptance tests, we need to return the DB as we got him using tearDown and not inside the test. also need to run the tests on a diffrent DB then the one for the system.
4. need not to connect to the external system inside the tests.
5. need to add configuration file + init file (both should be external).
6. in connection to the external system we need to deal with errors/timeouts properly.
7. when a guest logged out from the system he should be removed from the DB/when member logging in delete the guest user he was logged to.
8. need to add caching.
9. need to add a case when the DB is discconected.
10. add bidding purchase option

2 + 5 done (need to add tests for bid and owner agreement notifications) left: 3, 4, 9

[orishac]

after purchase: beside cleaning the bags of the user, we need to clean the cart also

[barroz1996]

updated all purchase cart tests to run with mock to extrnel systems