Here I am, sorry it is quite late, i just finished to study, me and Jay worked a lot tonight to make corrections on the diagram, here's what i'm sending to you: - Draft 1: is the original file produced on sunday - Draft 2: is the file that me and Jay made after reviewing the original, many classes and many relationships have been suppressed, this diagram is good, but it does not include any class that refers on the new movie list that the managers are supposed to browse and it does not have any class to show the orders for new movies that the managers make - Draft 3: In this file, i added the two missing classes above, separated from the rest of the diagram, there is a list of new movies, from this list, orders are made, managers can make new orders, but managers cannot automaticaly see if they have already copies of the movies they are going to order, becouse movies owned and movies from the suppliers, even being objects very similar, are in separate classes. - Draft 4: it's 5:43am now, and i finished this draft, i added some notation and i made the movie offered from the suppliers as a subclass of the class Movie. This means that i can own copies from the class "movie" but at the same time, the same movie can be in sale from a supplier; at the same time, there may be some movies for which i don't own any copy but that they are in sale from suppliers personally even if i think that there is no perfect draft (at least we should add strings to some attributes (like "ordinal" or "string" and those stuffs) but i do think that the draft 4 is way better than the others anyway, i'm sending you all the 4 draft so that we can decide toghether tomorrow goodnight, and good luck 4 tomorrow fabio 2006/11/13, Christian Arias <carias584@xxxxxxxxxxxxx>:
I'll be awake. Go ahead and send it Fabio -----Original Message----- From: ism6129proj-bounce@xxxxxxxxxxxxx [mailto:ism6129proj-bounce@xxxxxxxxxxxxx] On Behalf Of Fabio Graziani Sent: Monday, November 13, 2006 9:37 PM To: ism6129proj@xxxxxxxxxxxxx Subject: [ism6129proj] Re: Meeting on sunday you guys, at what time are you going to sleep? because, i think we should do some basic modifications, and i'm actually reading the book before to be sure of what i think we should modify...but if you'll stay awake i'll send you my version of the file in one hour or two hours and you'll tell me what do you think about that! Fabio 2006/11/13, csmall <csmall@xxxxxxx>: > I guess if no one has any changes you can just put our names on it and > print it out and bring it to class tomorrow > > One thing: make sure that there is a (disjoint, complete) line between > the employee class and the 2 subclasses. I can't remember if we put it > there or not. If it isn't, just add it. > > We were talking about putting more notes in but I don't think the > diagram will hold anymore stuff > > > > > Christian Arias wrote: > > Thanks Chris. That clears it up for me. Is there anything I can do before we > > the project is turned in tomorrow? > > > > Chris Arias > > > > -----Original Message----- > > From: ism6129proj-bounce@xxxxxxxxxxxxx > > [mailto:ism6129proj-bounce@xxxxxxxxxxxxx] On Behalf Of csmall > > Sent: Monday, November 13, 2006 1:02 PM > > To: ism6129proj@xxxxxxxxxxxxx > > Subject: [ism6129proj] Re: Meeting on sunday > > > > > >> Per the diagram, the manager updates the rental copy. What does that > >> > > update > > > >> correspond to? > >> > > There are 2 different movie classes. One is a movie database which > > records information (title, year, etc.) about the movies we rent. The > > manager uses this to answer queries There is another class made up of > > rental copies. These are the individual copies of movies that we rent > > out. The idea is that there would be data redundancy if we only had 1 > > class for movies. For each copy of a movie we rented out we would have > > to store title, year, etc. even though they are all the same (ie 10 > > copies of Mission Impossible would be the same with only a Movie ID > > changing.) Separating these enables us to reduce the redundancy, record > > how many times a rental copy is rented and also how popular a particular > > title is. > > > > When a manager updates a rental copy, he is adding a copy of a > > particular movie into the rental database. (ie, there are 10 copies of > > Mission Impossible and he wants to add an 11th) > > He doesn't need to update the movie database because it is already there. > > > > > >> What does the dashed line going from the employee super-class to the > >> > > rental > > > >> copy order represent? > >> > > > > An employee (manager or hourly) Scans in a movie (so there is a line > > between employee and movie) and that action updates the rental copy > > order for that movie. It records the return date and calculates late > > fees. We made the order an association class between the employee and > > the movie. The line should be coming from the line not from the employee > > class. > > > > > > > >> Is the rental copy > >> order the receipt given to a customer upon rental or a bill for late fees? > >> If it is a receipt given at initial check-out, would it be feasible to > >> > > have > > > >> a late fee operation seeing how no late fees would have accrued at that > >> point and time? I'm just unclear as to what we mean by rental copy order. > >> > > > > It is both. It records the transactions when a movie checked out and a > > physical receipt can be produced by the data that it records. Also, > > internally, it keeps track of the due dates and charges associated with > > that order. When a movie is returned, this order class is responsible > > for determining late charges and updating the costumer account > > > > > > > > > >> Also, I didn't see a class for payment system. Is that because we are just > >> going to say that we don't need to maintain any data related to the > >> > > payment > > > >> system and just include it as an operation in movie order form? I'm just > >> curious, but if that's the case, it sounds like a good idea to me. > >> > > > > We removed both the payment system and the billing system. We were > > thinking of the activities example that he gave in class. A student > > participates in activities and an university keeps track of the > > participation. However, since there is only 1 university and it never > > changes, there was no need for a university class. Same thing here. > > There is no need for a separate class which only performs functions and > > wouldn't have any attributes. We off-loaded those functions onto the > > rental order class and the new movie order class > > > > > > > > > > > > > > Christian Arias wrote: > > > >> Sorry my fourth question was cut-off before sending. Is the rental copy > >> order the receipt given to a customer upon rental or a bill for late fees? > >> If it is a receipt given at initial check-out, would it be feasible to > >> > > have > > > >> a late fee operation seeing how no late fees would have accrued at that > >> point and time? I'm just unclear as to what we mean by rental copy order. > >> > >> Thanks > >> > >> Chris Arias > >> > >> -----Original Message----- > >> From: Christian Arias [mailto:carias584@xxxxxxxxxxxxx] > >> Sent: Monday, November 13, 2006 9:19 AM > >> To: 'ism6129proj@xxxxxxxxxxxxx' > >> Subject: RE: [ism6129proj] Re: Meeting on sunday > >> > >> I looked over the class diagram and everything looks really well laid out. > >> > > I > > > >> just had a couple questions. > >> > >> Per the diagram, the manager updates the rental copy. What does that > >> > > update > > > >> correspond to? > >> > >> What does the dashed line going from the employee super-class to the > >> > > rental > > > >> copy order represent? > >> > >> Is the rental copy order the receipt given to customer upon renting the > >> video or a bill for late fees? If it is a recep > >> > >> Also, I didn't see a class for payment system. Is that because we are just > >> going to say that we don't need to maintain any data related to the > >> > > payment > > > >> system and just include it as an operation in movie order form? I'm just > >> curious, but if that's the case, it sounds like a good idea to me. > >> > >> > >> > >> > >> > >> > >> > >> > >> > > > > > > > > > > >