Timeline for Loose Coupling in Object Oriented Design
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 21, 2013 at 1:55 | audit | Suggested edits | |||
| Jul 21, 2013 at 2:16 | |||||
| Jun 28, 2013 at 13:14 | vote | accept | Random42 | ||
| Jun 27, 2013 at 23:08 | history | tweeted | twitter.com/#!/StackProgrammer/status/350390149223432192 | ||
| Jun 27, 2013 at 18:07 | answer | added | Karl Bielefeldt | timeline score: 15 | |
| Jun 27, 2013 at 17:58 | comment | added | Dunk | As usual, toy examples don't demonstrate the concept very well. Especially in this case since track is probably just a data container. However, if track was implemented using a number of other classes, who could also be pulling in other classes then coupling becomes a big issue. If I want to reuse the Album class somewhere else, but I have to bring the track class and all the things it uses with it, it becomes a royal pain. IMO, coupling means little if the class is only ever used for the 1 specific situation it was created for. It's when you try to use it elsewhere then it's a big deal. | |
| Jun 27, 2013 at 17:33 | answer | added | KeithS | timeline score: 3 | |
| Jun 27, 2013 at 17:26 | comment | added | Patrick Hughes | No option for Album being a Track factory, the created Track object which you then fill in through the ITrack interface? Maybe I misunderstand the scope of the question. | |
| Jun 27, 2013 at 17:10 | answer | added | k3b | timeline score: 3 | |
| Jun 27, 2013 at 16:19 | answer | added | Tulains Córdova | timeline score: 10 | |
| Jun 27, 2013 at 16:17 | comment | added | JustinC | GRASP is apparently something that Craig Larman conceived of, or at least talked about, according to Wikipedia. The paper mimics, but expands on the Wiki page. | |
| Jun 27, 2013 at 16:14 | answer | added | Derek | timeline score: 4 | |
| Jun 27, 2013 at 16:13 | answer | added | Neil | timeline score: 3 | |
| Jun 27, 2013 at 16:06 | comment | added | Random42 | @AraK Reliable does not mean unquestionable; and that's what I'm doing here, questioning it. | |
| Jun 27, 2013 at 16:05 | comment | added | Khaled Alshaya | @m3th0dman "but since it was from a university I believe it is reliable." For me because it is from a university, I consider it unreliable. I don't trust someone who hasn't worked on multiyear projects talking about best-practices in software development. | |
| Jun 27, 2013 at 16:05 | history | edited | Random42 | CC BY-SA 3.0 | added 3 characters in body |
| Jun 27, 2013 at 16:03 | comment | added | Random42 | @Derek I found the document by searching Google for "grasp patterns example"; I do not who wrote it but since it was from a university I believe it is reliable. I am looking for an example based on the information given and ignoring the source. | |
| Jun 27, 2013 at 15:59 | comment | added | Khaled Alshaya | Honestly, whenever I read about "Best Practices" I take them with a grain of salt! | |
| Jun 27, 2013 at 15:58 | comment | added | Derek | Is this a document that was put together by a professor or trainer? Based on the URL of the link you provided, it looks like it was for a class, though I don't see any credit in the document as to who created it. If this was part of a class, I'd suggest you ask these questions of the person who provided the document. I do agree with your reasoning, by the way - it would seem apparent to me that an Album class would want to inherently know about a Track class. | |
| Jun 27, 2013 at 15:46 | history | edited | Random42 | CC BY-SA 3.0 | added 54 characters in body |
| Jun 27, 2013 at 15:40 | history | asked | Random42 | CC BY-SA 3.0 |