UML

• careful written specification
• use case
• domain model
• architecture diagram 
• model driven architecture
• 
  

• agile modeling classDiagram
• association class 
• c_unidir_bidir_relationships.html 
•  One rule in database design is that a running system should never require a design change just to add data (changes to the design do occur, of course, just not in response to a new data value).
•  association
  aggregation
  dependency
  weak entity
  
  association class
  abstraction through interface
  abstract class
  cardinality
  unidirectional vs bidirectional relationships
  
  
  constraints and validation
  data binding
  type conversion
  
  
  component diagram
  deployment diagram
  
  use case diagrams
  
  ================================
  
  
  OOAD
  UML
  Agile modelling
  Design Pattern
  JPA
  hibernate
  
  Iconix
  RUP
  ====================
  the best practices of above all
  
  book JPA with hibernate by gavin king
  
  
  •  sequence diagram
  • dependency vs association
  • it's a best practice to prefer unidirectional relationships in a model whenever possible
  • if we group similar attributes in the form of a multiple classes then the change in one wont change all the clases. instead if there is a single class then if any change is made then whole class is affected
  •