Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: proper use of .java files (layout) Date: Thu, 27 Dec 2012 11:51:36 +0100 Lines: 51 Message-ID: References: <20fa5c05-6fcc-47ed-9e80-a44975887928@googlegroups.com> <-7qdnc2dgM62l0bNnZ2dnUVZ_tKdnZ2d@earthlink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 9cx6x5BFdaluUgkCEz2yXAuHdlEJCL7opJzNHpU4rEL2qcx1x/FLhTr+xCMylorCY= Cancel-Lock: sha1:fTyVl87psND1E6QHJSP8HBB0LNs= User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:20722 On 26.12.2012 22:21, Lew wrote: > To describe the elephant from yet another projection, I use a combination > of intuitive and cognitive models derived from the linguistic space of the > application domain. > > The intuitive portion matches domain-specific language ("TPS Report") with > a ready-to-hand skill set of noun-verb object metamodels. > > "Hmm, a report /has-a/ {title, ...}, /is-a/ {Retrievable, Readable, ...}." > > The metamodel is the idea of "/has-a/" and "/is-a/", the notion of objects > having types, attributes, and behaviors, and the toolbox containing > polymorphism, assertions and all the panoply of design and programming skills. I find the CRC card approach quite nice here: those cards also capture major aspects without going in too much detail. I rarely use them physically but I use the concept to remind myself of R and C. > But it was exactly what Patricia describes. If you think structurally, it might > look like code - but hey, structure's structure however you describe it. Right. That's also the reason why I prefer Visio with the free set of stencils for UML modeling over any other UML tool (especially those with a proper UML model in the background or even roundtrip engineering) because I can add visual elements not part of UML standard to help getting ideas across. > As a fillip, I correlate Java elements to UML differently from (and therefore > superior to, by my definition :-') some. Java idiomatically, and > controversially, exposes all attributes as accessor and mutator (getter and > setter) methods. Some diagram 'getX()' and 'setX()' methods as methods under > UML. Tsk. They're still attributes - 'get' and 'set' are just conventions > for expressing their public face. Architecturally, at the level where UML > can hope to do any good, I diagram them as attributes. Same here. > I'm not religious about it. If a paycheck is at stake I'll diagram them > as blueberries if you like. I'd prefer strawberries - more space to write something. ;-) Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/