Contents contributed and discussions participated by kuni katsuya

Simple Middle Filter: All | Bookmarks | Topics

Java Interfaces/Implementation naming convention - Stack Overflow - 0 views

stackoverflow.com/...plementation-naming-convention

java Interface NamingConvention BestPractices

shared by kuni katsuya on 19 Dec 12 - No Cached

Putting I in front is just crappy hungarian style notation tautology that adds nothing but more stuff to type to your code.
...

Cancel
An Interface in Java is a Type
...

Cancel
And the Impl suffix is just more noise as well
...

Cancel
...5 more annotations...
Everything that implements Truck is a Type of Truck.
...

Cancel
The name of the interface should describe the abstract concept the interface represents. Any implementation class should have some sort of specific traits that can be used to give it a more specific name.
...

Cancel
no justification to have an interface at all.
...

Cancel
If there is only one implementation class
...

Cancel
Java Interfaces/Implementation naming convention
...

Cancel

kuni katsuya on 19 Dec 12

"Putting I in front is just crappy hungarian style notation tautology that adds nothing but more stuff to type to your code"

<div class="cArrow"> </div><div class="cContentInner">"Putting I in front is just crappy hungarian style notation tautology that adds nothing but more stuff to type to your code"</div>

...

Cancel

Interface naming in Java - Stack Overflow - 0 views

stackoverflow.com/...interface-naming-in-java

java Interface NamingConvention BestPractices

shared by kuni katsuya on 19 Dec 12 - No Cached

interfaces define
...

Cancel
capabilities
- kuni katsuya on 19 Dec 12
  
  this is one sensible interface naming option, if the interface encapsulates a cohesive set of behaviors and yes, compared to blindly following the meaningless I+ convention, it requires some thought, but thinking of an appropriate name also forces you to (re)consider the interface's primary responsibility and how it fits into the overall design imho, a class diagram for a domain model should be almost fluently readable english
  
  <div class="cArrow"> </div><div class="cContentInner">this is one sensible interface naming option, if the interface encapsulates a cohesive set of behaviors and yes, compared to blindly following the meaningless I+ convention, it requires some thought, but thinking of an appropriate name also forces you to (re)consider the interface's primary responsibility and how it fits into the overall design imho, a class diagram for a domain model should be almost fluently readable english</div>
  
  ...
  
  Cancel
...

Cancel
not types
...

Cancel
...16 more annotations...
Comparable
...

Cancel
Runnable
...

Cancel
Serializable
...

Cancel
Sometimes an Adjective doesn't make sense, but I'd still generally be using interfaces to model behavior, actions, capabilities, properties, etc,... not types.
...

Cancel
Also, If you were really only going to make one User and call it User then what's the point of also having an IUser interface?
- kuni katsuya on 19 Dec 12
  
  another anti-pattern... blindly create an interface for every class, even if there's only one implementation!! arrgghhhh! consider introducing an interface when there are 2-3 well-distinguished, concrete implementations required
  
  <div class="cArrow"> </div><div class="cContentInner">another anti-pattern... blindly create an interface for every class, even if there's only one implementation!! arrgghhhh! consider introducing an interface when there are 2-3 well-distinguished, concrete implementations required</div>
  
  ...
  
  Cancel
...

Cancel
if you are going to have a few different types of users that need to implement a common interface, what does appending an "I" to the interface save you in choosing names of the implementations?
...

Cancel
prefer not to use a prefix on interfaces:
...

Cancel
hurts readability.
...

Cancel
interfaces names should be as short and pleasant as possible
...

Cancel
Implementing classes should be uglier to discourage their use.
- kuni katsuya on 19 Dec 12
  
  but they don't *have* to be ugly, like BlahImpl for specialized implementations, use descriptive adjective-noun combos
  
  <div class="cArrow"> </div><div class="cContentInner">but they don't *have* to be ugly, like BlahImpl for specialized implementations, use descriptive adjective-noun combos</div>
  
  ...
  
  Cancel
...

Cancel
Code using an instance of some type should never, ever care if that type is an interface or a class
...

Cancel
exposing such a detail in the name of the type is pointless and harmful to understanding
...

Cancel
several reasons Java does not generally use the IUser convention.
...

Cancel
should not have to know whether the client is using an interface or an implementation class
...

Cancel
Java naming convention prefers longer names with actual meanings to Hungarian-style prefixes
...

Cancel
Interface naming in Java [closed]
...

Cancel

kuni katsuya on 19 Dec 12

"have interfaces define"

<div class="cArrow"> </div><div class="cContentInner">"have interfaces define"</div>

...

Cancel

UML 2 Class Diagram Guidelines - 0 views

www.agilemodeling.com/...classDiagram.htm

uml class diagram best practices

shared by kuni katsuya on 19 Dec 12 - Cached

UML 2 Class Diagram Guidelines
...

Cancel
1.        General Guidelines
...

Cancel
2.        Class Style Guidelines
...

Cancel
...49 more annotations...
Use Common Terminology for Names
...

Cancel
Prefer Complete Singular Nouns for Class Names
...

Cancel
Name Operations with a Strong Verb
...

Cancel
Name Attributes With a Domain-Based Noun
- kuni katsuya on 19 Dec 12
  
  don't just use the attribute's type with first character lower cased!!! argghhh! (eg. instead of Node node, Node parent)
  
  <div class="cArrow"> </div><div class="cContentInner">don't just use the attribute's type with first character lower cased!!! argghhh! (eg. instead of Node node, Node parent)</div>
  
  ...
  
  Cancel
...

Cancel
Do Not Model Scaffolding Code
...

Cancel
Include an Ellipsis ( … ) At The End of Incomplete Lists
...

Cancel
Develop Consistent Method Signatures
...

Cancel
Avoid Stereotypes Implied By Language Naming Conventions
...

Cancel
3.        Interfaces
...

Cancel
Name Interfaces According To Language Naming Conventions
- kuni katsuya on 19 Dec 12
  
  I+ is NOT an acceptable naming convention! this is a very dumb, thoughtless, pointless convention originated by microsoft
  
  <div class="cArrow"> </div><div class="cContentInner">I+ is NOT an acceptable naming convention! this is a very dumb, thoughtless, pointless convention originated by microsoft</div>
  
  ...
  
  Cancel
- kuni katsuya on 19 Dec 12
  
  see http://www.artima.com/objectsandjava/webuscript/PolymorphismInterfaces1.html, 'Interface Naming Conventions'
  
  <div class="cArrow"> </div><div class="cContentInner">see <a href="http://www.artima.com/objectsandjava/webuscript/PolymorphismInterfaces1.html" rel="nofollow" target="_blank">http://www.artima.com/objectsandjava/webuscript/PolymorphismInterfaces1.html</a>, 'Interface Naming Conventions'</div>
  
  ...
  
  Cancel
...

Cancel
Do Not Model the Operations and Attributes of an Interface in Your Classes
...

Cancel
Consider an Interface to Be a Contract
...

Cancel
4.        Relationship Guidelines
...

Cancel
Model Relationships Horizontally
...

Cancel
Depict Similar Relationships Involving A Common Class As A Tree
...

Cancel
Always Indicate the Multiplicity
...

Cancel
reduce clutter in the diagram
...

Cancel
Avoid a Multiplicity of “*”
...

Cancel
Replace Relationships By Indicating Attribute Types
- kuni katsuya on 19 Dec 12
  
  if dependency relationships were drawn between every class and the types of it's attributes, the class diagram becomes cluttered very quickly this dependency is obvious if the type is indicated for each attribute
  
  <div class="cArrow"> </div><div class="cContentInner">if dependency relationships were drawn between every class and the types of it's attributes, the class diagram becomes cluttered very quickly this dependency is obvious if the type is indicated for each attribute</div>
  
  ...
  
  Cancel
...

Cancel
Do Not Model Every Single Dependency
- kuni katsuya on 19 Dec 12
  
  generalization of #7 what you show/don't show depends on the main concepts you're trying to convey in any specific diagram
  
  <div class="cArrow"> </div><div class="cContentInner">generalization of #7 what you show/don't show depends on the main concepts you're trying to convey in any specific diagram</div>
  
  ...
  
  Cancel
...

Cancel
Write Concise Association Names In Active Voice
...

Cancel
Indicate Directionality To Clarify An Association Name
...

Cancel
Name Unidirectional Associations In The Same Direction
...

Cancel
Indicate Role Names When Multiple Associations Between Two Classes Exist
...

Cancel
Indicate Role Names on Recursive Associations
- kuni katsuya on 19 Dec 12
  
  eg. parent, child
  
  <div class="cArrow"> </div><div class="cContentInner">eg. parent, child</div>
  
  ...
  
  Cancel
...

Cancel
Make Associations Bi-Directional Only When Collaboration Occurs In Both Directions
...

Cancel
Question Multiplicities Involving Minimums And Maximums
- kuni katsuya on 19 Dec 12
  
  this just leads to stupid programming practices like hard-coding array sizes, making code more brittle
  
  <div class="cArrow"> </div><div class="cContentInner">this just leads to stupid programming practices like hard-coding array sizes, making code more brittle</div>
  
  ...
  
  Cancel
...

Cancel
6.        Inheritance Guidelines
...

Cancel
“is a”
...

Cancel
“is like” relationships
...

Cancel
Apply the Sentence Rule For Inheritance
...

Cancel
Place Subclasses Below Superclasses
...

Cancel
A Subclass Should Inherit Everything
- kuni katsuya on 19 Dec 12
  
  if a subclass sets an attribute to null, implements a method returning null or throwing a NotImplementedException, it really isn't a subclass, or the superclass needs to be decomposed
  
  <div class="cArrow"> </div><div class="cContentInner">if a subclass sets an attribute to null, implements a method returning null or throwing a NotImplementedException, it really isn't a subclass, or the superclass needs to be decomposed</div>
  
  ...
  
  Cancel
...

Cancel
7.        Aggregation and Composition Guidelines
...

Cancel
object is made up of other objects
...

Cancel
aggregation
...

Cancel
“is part of” relationships
...

Cancel
whole-part relationship between two objects
...

Cancel
Composition
...

Cancel
stronger form of aggregation where the whole and parts have
...

Cancel
coincident lifetimes, and it is very common for the whole to manage the lifecycle of its parts
...

Cancel
Apply the Sentence Rule for Aggregation
...

Cancel
Depict the Whole to the Left of the Part
...

Cancel
Don’t Worry About Getting the Diamonds Right
...

Cancel
associations, aggregation, composition, dependencies, inheritance, and realizations
...

Cancel
line on a UML class diagram
...

Cancel
defines a cohesive set of behaviors
...

Cancel
Indicate Visibility Only On Design Models
...

Cancel
Design Class Diagrams Should Reflect Language Naming Conventions
...

Cancel

Agile Modeling (AM) Home Page: Effective Practices for Modeling and Documentation - 0 views

www.agilemodeling.com

agile modeling methodology design

shared by kuni katsuya on 19 Dec 12 - Cached

TH03-EP01-US001 - Media Management, Media Upload, Media Item Fields (Groomed BE21, FE8)... - 0 views

confluence.visualfrenzy.com/...viewpage.action

UserStory ECM Cube MediaManagement

shared by kuni katsuya on 19 Dec 12 - No Cached

Media Management,
...

Cancel
upload a new media item
...

Cancel
syndication and encoding - not part of this user story
...

Cancel
...26 more annotations...
definition
- kuni katsuya on 19 Dec 12
  
  ie. attach the following metadata to the uploaded media item
  
  <div class="cArrow"> </div><div class="cContentInner">ie. attach the following metadata to the uploaded media item</div>
  
  ...
  
  Cancel
...

Cancel
Owner
...

Cancel
Rights of owner
- kuni katsuya on 19 Dec 12
  
  dependent on implementation of licensing/rights management system which is tbd, so these will be best guess stubs for now
  
  <div class="cArrow"> </div><div class="cContentInner">dependent on implementation of licensing/rights management system which is tbd, so these will be best guess stubs for now</div>
  
  ...
  
  Cancel
...

Cancel
Rights expiry date
- kuni katsuya on 19 Dec 12
  
  dependent on implementation of licensing/rights management system which is tbd, so these will be best guess stubs for now
  
  <div class="cArrow"> </div><div class="cContentInner">dependent on implementation of licensing/rights management system which is tbd, so these will be best guess stubs for now</div>
  
  ...
  
  Cancel
...

Cancel
Syndication
- kuni katsuya on 19 Dec 12
  
  dumbed down, feature parity implementation is just a list of idss allowed distribution (i believe) use existing legacy infrastructure? ultimate syndication system will depend on: - licensing - explicit list of syndication channels (much like legacy) - rule-based routing
  
  <div class="cArrow"> </div><div class="cContentInner">dumbed down, feature parity implementation is just a list of idss allowed distribution (i believe) use existing legacy infrastructure? ultimate syndication system will depend on: - licensing - explicit list of syndication channels (much like legacy) - rule-based routing</div>
  
  ...
  
  Cancel
...

Cancel
Caption
...

Cancel
Category
- kuni katsuya on 19 Dec 12
  
  ota category assumed
  
  <div class="cArrow"> </div><div class="cContentInner">ota category assumed</div>
  
  ...
  
  Cancel
...

Cancel
Seasonality display rules
- kuni katsuya on 19 Dec 12
  
  this is one (simple) example of rule-based syndication: rule type: temporal (which could include: time range, recurrence, end time, etc) rule: syndicate while startDate>=now() and endDate<=now()
  
  <div class="cArrow"> </div><div class="cContentInner">this is one (simple) example of rule-based syndication: rule type: temporal (which could include: time range, recurrence, end time, etc) rule: syndicate while startDate>=now() and endDate<=now()</div>
  
  ...
  
  Cancel
...

Cancel
Short description
...

Cancel
Long description
...

Cancel
Search keywords
...

Cancel
Associated with
- kuni katsuya on 19 Dec 12
  
  huh?
  
  <div class="cArrow"> </div><div class="cContentInner">huh?</div>
  
  ...
  
  Cancel
...

Cancel
in the media library
...

Cancel
can be viewed by users
- kuni katsuya on 19 Dec 12
  
  not only new ecm users, but legacy viewers as well ie. content uploaded via ecm must be available for display in legacy viewers, at least until legacy system is replaced and shutdown for good
  
  <div class="cArrow"> </div><div class="cContentInner">not only new ecm users, but legacy viewers as well ie. content uploaded via ecm must be available for display in legacy viewers, at least until legacy system is replaced and shutdown for good</div>
  
  ...
  
  Cancel
...

Cancel
Uploaded by
...

Cancel
Date uploaded
...

Cancel
Date modified
...

Cancel
Last modified by
...

Cancel
Status
- kuni katsuya on 19 Dec 12
  
  TO DO: for new domain model, should define explicit content life cycle with state diagram
  
  <div class="cArrow"> </div><div class="cContentInner">TO DO: for new domain model, should define explicit content life cycle with state diagram</div>
  
  ...
  
  Cancel
...

Cancel
File type
...

Cancel
Media type
...

Cancel
Dimensions
...

Cancel
Aspect ratio
- kuni katsuya on 19 Dec 12
  
  aspect ratio doesn't need to be stored in db as metadata, since it can be calculated cheaply based on the dimensions
  
  <div class="cArrow"> </div><div class="cContentInner">aspect ratio doesn't need to be stored in db as metadata, since it can be calculated cheaply based on the dimensions</div>
  
  ...
  
  Cancel
...

Cancel
File size
- kuni katsuya on 19 Dec 12
  
  units: bytes
  
  <div class="cArrow"> </div><div class="cContentInner">units: bytes</div>
  
  ...
  
  Cancel
...

Cancel
File name
- kuni katsuya on 19 Dec 12
  
  is this the original name of the file that was uploaded? if not, and it supposed to be the medlib file name, imho, should not be exposed. the medlib file name should be immaterial to the ecm user and generally, vfml should treat them as opaque to allow future changes without customer dependencies the only time an ecm user should care about a 'file name' is when they're uploading or downloading. but... once the file is uploaded, who cares what the original file name was? it will be recorded, but should be inconsequential to anything since it would never, ever be referred to again on download, (save as...) the original file name *could* be used, but any file name is just as good, since the downloader would also be given the option to rename the file
  
  <div class="cArrow"> </div><div class="cContentInner">is this the original name of the file that was uploaded? if not, and it supposed to be the medlib file name, imho, should not be exposed. the medlib file name should be immaterial to the ecm user and generally, vfml should treat them as opaque to allow future changes without customer dependencies the only time an ecm user should care about a 'file name' is when they're uploading or downloading. but... once the file is uploaded, who cares what the original file name was? it will be recorded, but should be inconsequential to anything since it would never, ever be referred to again on download, (save as...) the original file name *could* be used, but any file name is just as good, since the downloader would also be given the option to rename the file</div>
  
  ...
  
  Cancel
...

Cancel
Media units consumed
- kuni katsuya on 19 Dec 12
  
  calculated/cached value pull from legacy system in future sprints, could start to build phased shell of the marketing xxx system 1. getMediaUnits()
  
  <div class="cArrow"> </div><div class="cContentInner">calculated/cached value pull from legacy system in future sprints, could start to build phased shell of the marketing xxx system 1. getMediaUnits()</div>
  
  ...
  
  Cancel
- kuni katsuya on 19 Dec 12
  
  TODO: confirm with david and/or henry.wu where/how to obtain 'media units consumed' for a media item
  
  <div class="cArrow"> </div><div class="cContentInner">TODO: confirm with david and/or henry.wu where/how to obtain 'media units consumed' for a media item</div>
  
  ...
  
  Cancel
...

Cancel

Home - JDEclipse-Realign - Mchr3k - 0 views

mchr3k.github.com/jdeclipse-realign

java decompiler eclipse-plugin

shared by kuni katsuya on 14 Dec 12 - No Cached

3 simple steps to Ubiquitous Language - Invisible to the eye - 0 views

www.giorgiosironi.com/...ps-to-ubiquitous-language.html

DDD DomainDrivenDesign DomainModel UbiquitousLanguage

shared by kuni katsuya on 14 Dec 12 - No Cached

3 simple steps to Ubiquitous Language
...

Cancel

Supported Place Types - Google Places API (Experimental) - Google Developers - 0 views

developers.google.com/...supported_types

DDD DomainDrivenDesign DomainModel UbiquitousLanguage

shared by kuni katsuya on 14 Dec 12 - No Cached

Place Types
...

Cancel
Google Places API
...

Cancel
supported types for Place searches and Place adds
...

Cancel
...30 more annotations...
Additional types listed in table #2 can be used when searching for a Place,
...

Cancel
but not when adding a Place
- kuni katsuya on 14 Dec 12
  
  so, not treated as a 'full-blown' place type(?) in cube domain model, would this be similar to relationship between hotel ('primary' subject type) and neighborhood ('secondary' subject type, since content can be attached to it, but it would never 'drive' of this relationship)
  
  <div class="cArrow"> </div><div class="cContentInner">so, not treated as a 'full-blown' place type(?) in cube domain model, would this be similar to relationship between hotel ('primary' subject type) and neighborhood ('secondary' subject type, since content can be attached to it, but it would never 'drive' of this relationship)</div>
  
  ...
  
  Cancel
...

Cancel
airport
...

Cancel
amusement_park
...

Cancel
art_gallery
...

Cancel
shopping_mall
...

Cancel
restaurant
...

Cancel
museum
...

Cancel
night_club
...

Cancel
place_of_worship
...

Cancel
train_station
...

Cancel
lodging
...

Cancel
hospital
...

Cancel
These types cannot be used when adding a new Place
...

Cancel
floor
...

Cancel
geocode
...

Cancel
intersection
...

Cancel
locality
...

Cancel
neighborhood
...

Cancel
point_of_interest
...

Cancel
postal_code
...

Cancel
postal_code_prefix
...

Cancel
route
...

Cancel
street_address
...

Cancel
street_number
...

Cancel
sublocality
...

Cancel
subpremise
...

Cancel
country
...

Cancel
administrative_area_level_1 administrative_area_level_2 administrative_area_level_3
...

Cancel
premise
...

Cancel

jiramap.jpg (1007×778) - 0 views

confluence.atlassian.com/...jiramap.jpg

jira DataModel

shared by kuni katsuya on 14 Dec 12 - No Cached

JIRA_Ent_Diagram.jpg (764×353) - 0 views

confluence.atlassian.com/...JIRA_Ent_Diagram.jpg

jira DataModel

shared by kuni katsuya on 14 Dec 12 - No Cached