# data[].attributes.body
Does the format of the document containing the source files of the project have to be in the .doc format, or is .docx fine?

# data[].attributes.body
how would you represent the switch case within the UML? Would it be as a method and show the options of just a matter on method which is a switch case and thats it?

# data[].attributes.body
Is there a lecture on this?

# data[].attributes.body
how do we allow the item to become available again?

# data[].attributes.body
Cant connect my Book, Dvd classes to the main

# data[].attributes.body
Hi,have one question is it mandatory to do the challenges?

# data[].attributes.attachment_link.description
See all the wonderful things b_villarini has made

# data[].attributes.body
it is possible to have 2 books/DVD being in the library item. So the ISBN can be repeated right???

Also the same user can borrow more books so the ID can also be repeated right??

# data[].attributes.body
Hello professor, was lecture 09 from this week recorded?

# data[].attributes.body
can we store the mobile number as a string?

# data[].attributes.body
Hello
I'm not proud to say this but I have not been able to do the coursework yet as I've had some life problems. Could you please advice me on which lectures/tutorials that I need to go through in order to get a better understanding of how to do the coursework.
Thank you in advance.

# data[].attributes.body
Do the LibraryManager interface and the WestminsterLibraryManager concrete classes need to be represented in the UML diagram?

# data[].attributes.body
In the library manager class, do we have to write methods in them?

# data[].attributes.body
Is WestminsterLibraryManager going to be the main class or should we create a separate main class? Also, do we have to provide setters for variables such as title, publication date and authors (which normally won't change) or can we set them only ones when calling the constructor?

# data[].attributes.body
Do we have to use super methods in the constructors, in the book and DVD classes if we already have all of the attributes from the LibraryItem in the sub classes?

# data[].attributes.body
The final challenge requires a change in my current implementation. Will I need to modify my UML diagram to reflect this?

# data[].attributes.headline
Borrow Library Item Question and Return Question 

# data[].attributes.subject
Borrow Library Item Question and Return Question 

# data[].attributes.body
To calculate the fees of a overdue library item do i need to take into account what time the book was borrowed or would just the date be fine?

# data[].attributes.body
do the methods in libraryManager need to have parameters

# data[].attributes.body
Is there a specific way or convention that the string returned by the toString method needs to formatted in, or is it fine as long as it clearly displays the objects fields?

# data[].attributes.body
How do you decided the multiplicity for the diagram? What format are the of the multiplicities e.g
1.1 implements 1..1
1:1 implements 1:1

# data[].attributes.headline
What should the GUI display on each item? Since there are different amount of information per item should we only include the libraryitem contents or also display the dvd/book contents 

# data[].attributes.subject
What should the GUI display on each item? Since there are different amount of information per item should we only include the libraryitem contents or also display the dvd/book contents 

# data[].attributes.body
Do all overloaded versions of a constructor have to be added in the UML diagram?

# data[].attributes.body
Why do we create two use case diagrams?

# data[].attributes.body
Would it be acceptable to create two constructors for this class, one with hours and minutes and the other one without or should the time be always specified? If it doesn't have to be, is there any default time (e.g. 00:00 or 12:00) that would be set if the time was not specified? It is relevant 

# data[].attributes.body
What do you mean by "are the ID or ISBN unique?"

# data[].attributes.body
Can I add more Set and get methods in The Library item class, dvd and books

# data[].attributes.body
In the course work description When Adding an Library Item you also have to add in relevant information.  So for a book i would have to add the generic attributes like ISBN, Title, ect and more specific attributes like Author, the number of pages ect. Is this correct?

# data[].attributes.body
Do DVDs have an ISBN?

# data[].attributes.body
Since Queue is abstract and cannot be instantiated, would using PriorityQueue be appropriate?

# data[].attributes.body
Hi,
In the class DVD we need to store info about available languages and subtitles. Is the data type String or int. And the description says actor(s). So, I should use Arraylist for the actors?

# data[].attributes.body
Can you point us in the right direction for calculating the current date and how many days are left an item has borrowed. It seems rather tricky to calculate without using any predefined library

# data[].attributes.body
Can ISBN be of type int or does it have to be String?

# data[].attributes.body
Are seconds relevant in this task or can only hours and minutes be specified?

# data[].attributes.body
Are we allowed to use this package or does this count as a predefined library

# data[].attributes.body
I am confused on how to implement the interface. Is the interface supposed to have abstract methods such as Add,delete, Borrow ,ect and then am i supposed to override them in the Westminster library manager?

# data[].attributes.body
hat does the variable sector mean? Like the sector of the library where the Library it

# data[].attributes.body
 you draw the actions that a user can perform with the system you implemented. (e.g. the u

# data[].attributes.body
Please check slide 52-55 in Lecture 02. It is a digram where you draw the actions that a user can perform with the system you implemented. (e.g. the user can add a library item, delete an ite, etc.)

# data[].attributes.body
For the Current Reader declaration in class LibraryItem is it a String or Is it referred to the Reader Class

# data[].attributes.headline
Should we be saving the readers details in an array or just update the variables for each item?

# data[].attributes.subject
Should we be saving the readers details in an array or just update the variables for each item?

# data[].attributes.body
As in should we be able to recall a reader from their name/id number if they are an existing reader or should every borrowed item require the full details regardless

# data[].attributes.body
Do we want to allow a deletion of the item that is currently borrowed? That would make it impossible to return it or calculate any fee.

# data[].attributes.body
I don't really understand interfaces much.

What's the use of one in our scenario and what advantages does it bring over not using one?
Thanks

# data[].attributes.body
Is the reader class, a subclass of LibraryItem?

# data[].attributes.body
When calculating the fee, should we take into account different number of days of certain months and leap years or is it expected to be simplified?

# data[].attributes.body
The DateTime class needs to be created for the project. It is not always necessary to specify time in real life (e.g. for the publication date). Would it be acceptable to create two constructors for this class, one with hours and minutes and the other one without or should the time be always specified? If it doesn't have to be, is there any default time (e.g. 00:00 or 12:00) that would be set if the time was not specified? It is relevant taking into account the fee. If the manager does not input time, just a date, from which hour will the fee be calculated? Or, if every DateTime needs to have time, even for a publishing, with only one constructor, should there be any default time for that?

# data[].attributes.body
Hello.
Sorry, but what are use cases?

# data[].attributes.body
You could solve the task in both ways but I would suggest to use one array list where you can store both DVDs and books.

# data[].attributes.body
When a item is borrowed and we try to borrow it again the predicted date when it is available again is it just the borrowed date plus the number of days it is allowed to be borrowed?

# data[].attributes.body
could you give a brief meaning of Encapsulation.

# data[].attributes.headline
Does the library store multiple copies of any items?

# data[].attributes.subject
Does the library store multiple copies of any items?

# data[].attributes.body
i.e. does the delete method remove all copies, or a specific copy of an entry?

# data[].attributes.body
Should the DVDs and Books be saved in the same array or in two separate arrays?

# data[].attributes.headline
Hello! Should the ISBN variable apply to all DVDs?

# data[].attributes.subject
Hello! Should the ISBN variable apply to all DVDs?

# data[].attributes.body
Are we at the stage we should be able to complete section 2 of the coursework or are there more lectures we should for before starting section 2?

# data[].attributes.body
Hello!
1. Are books and DVDs the only two types of items that are and will be available in the library or should be act as there could be different types in the future?
2. Is there a minimal year of the publishing of the book (e.g. year 1000, or 500, or 0, or even BC)?
3. Does the library have any  limit on the number of readers?
4. Would the library want to store information on every reader forever or should the option of deleting a reader be enabled?
5. If an item was borrowed at a certain time, e.g. 10:50, should it be returned until 10:50, 3 (or 7) days later or until midnight (as in a real-life library)?
Thank you!

# data[].attributes.body
Hello.
What does the variable sector mean? Like the sector of the library where the Library item exists or is it like a sector of a genre that the library item is based upon?