hisener / bbm487s2017g1 Goto Github PK

The system shall be able to issue a fine and informs the customer for late returns.
The customer shall be able to pay the fine.

We need to implement at least one use case for release 1. But we have written three use cases for this release and implemented two of them. According to the time limit, I think we should shift "Manipulate Book" to the release 2.

For this change, we need to update the table in Section 4.1 of Project Vision document.

• Manipulate Book Release 1 Release 2

PS: I will open a PR for "logout" as soon as possible.

• LBLS-TC-006 (Search Books)
• LBLS-TC-009 (Search Books)
• LBLS-TC-012 (Self Check-out)
• LBLS-TC-015 (Self Return)

failed.

Solution suggestion: Validation#isISBNValid(String) should be implemented.

We will start the implementation of the application with this iteration. I think we should change this setting:

https://github.com/hisener/bbm487s2017g1/settings/branches

• Protect master branch
  Disables force-pushes to this branch and prevents it from being deleted.
  • Require pull request reviews before merging
    When enabled, all commits must be made to a non-protected branch and submitted via a pull request with at least one approved review and no changes requested before it can be merged into master.
  • Require status checks to pass before merging
    Choose which status checks must pass before branches can be merged into master. When enabled, commits must first be pushed to another branch, then merged or pushed directly to master after status checks have passed.
  • Include administrators
    Enforce all configured restrictions for administrators.

More information: https://help.github.com/articles/defining-the-mergeability-of-pull-requests/

What do you think? @ahmed-samil @naciyeguzel

The waiting list shall provide better book reservation system. The user shall be able to add a book his/her waiting list and is notified of the book being available.

Make the queries related to login case sensitive.

When running maven commands, these warnings are generated:

• 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 50, column 21
• Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!

When a book is deleted, should we delete book from current owner?

We won't implement it. So we can remove this button.

Application should use operating system's default L&F.

The user shall be able to

• self-checkout
• self-return

and view his/her books.

How should we notify user on the waitlist, when book becomes available?

Some text doesn't fit in panels.

Username, password, forgot password etc. It's general, not specific to the login window.

Ubuntu GNOME 16.04.2 LTS
System Look and Feel: com.sun.java.swing.plaf.gtk.GTKLookAndFeel

• LBLS-TC-007
• LBLS-TC-010

failed.

BookContoller is not a singleton. Please see UserController.

column names and datas(They are constant, It does not show the books that the user has) should be edited on tablo of view tab.

Separate Query class to

• UserDAO
• BookDAO

When a customer is deleted:

• currently owned books should be returned
• fines can be neglected