Home
madness

Terminology Madness

The following are various terms you are likely to hear in the object-oriented, relational database, n-tier architecture, software development process, and other related tools. Over the coming months, I plan to provide definitions and comics around some of these words; meanwhile, a few good websites to find definitions for these words include:

Common Terms Used In Software Development

  1. ACID
  2. Aggregation
  3. Aspect Oriented Programming (AOP)
  4. Association
  5. Assurance
  6. Attribute
  7. Authentication
  8. Authorization
  9. Binding
  10. Business object
  11. Business Rule
  12. Cache
  13. Cardinality (multiplicity)
  14. Cascade
  15. Context
  16. Clustering
  17. Collaboration
  18. Component
  19. Composition
  20. Conceptual data models (domain model, application object model)
  21. Concrete class
  22. Connection pool
  23. Constraint
  24. Controller
  25. Coupling
  26. CRUD (create, read, update, delete)
  27. Data clobbering
  28. Data definition language (DDL)
  29. Data modeling
  30. Database lock – read, write, exclusive write
  31. Database purist?
  32. Declarative
  33. Delegation
  34. Denormalize
  35. Dependency Injection
  36. Detached object
  37. Dirty read
  38. Distributed transaction
  39. Domain
  40. Eager fetch/read
  41. Encapsulation
  42. Entity
  43. Failover
  44. Framework (API, library) – web, persistence, other
  45. Generative Programming (GP)
  46. Glossary
  47. Horizontal mapping
  48. Immutability (as in hash keys)
  49. Index – single, composite
  50. Information hiding
  51. Inheritance
  52. Interface
  53. Inversion of Control
  54. Key - primary key, foreign, alternate, surrogate
  55. Layer (tier) – ui, controller, business/service (domain), persistence, other
  56. Lazy fetch/read
  57. Logical data models
  58. Loosely Coupled
  59. Mapping
  60. Marshal/Unmarshal
  61. Message
  62. Messaging
  63. Meta data
  64. Modeling
  65. Mutator (setters)
  66. Nested transaction
  67. Normalize
  68. Object
  69. Object purist?
  70. OCL (Object Constraint Language)
  71. Operation
  72. Optimistic locking
  73. Orphan
  74. Pattern – architecture, design and database
  75. Persistence
  76. Persistence
  77. Persistent object
  78. Pessimistic locking
  79. Phantom read
  80. Physical data models (er diagram)
  81. POJO
  82. Programmatic
  83. Propagation
  84. Proxy
  85. Race condition
  86. Referential Integrity
  87. Repeatable read
  88. Reverse engineer
  89. Semantic Web
  90. Seminal (original)
  91. Serialization
  92. Service
  93. Service layer
  94. Service oriented architecture
  95. Single inheritance
  96. SOA
  97. Stereotype
  98. Stored Procedure
  99. Storyboard
  100. Testing – unit, interface, integration, regression, performance/stress, functional, user acceptance, system
  101. Transaction isolation - Read Uncommitted, Read Committed, Repeatable Read, Serializable
  102. Transaction management
  103. Transactional integrity
  104. Transient attributes (Shadow data)
  105. Trigger
  106. Tuple
  107. Two-phase commit
  108. Union mapping
  109. Use Case
  110. User Interface Flow
  111. User story
  112. Value Object
  113. Veritical mapping
  114. View
  115. Wireframe

Big-Up-Front Madness