IT Architecture bytes
Filed in Architecture on Mar.10, 2010
Design Principles at a glance. I will be adding more in coming days.
| KISS |
|
The KISS principle states that simplicity should be a key goal in design, and that unnecessary complexity should be avoided |
| YAGNI | You ain’t gonna need it | It is the principle in extreme programming that programmers should not add functionality until it is necessary |
| DRY |
|
Aimed at reducing repetition of information of all kinds. Every piece of knowledge must have a single, unambiguous, authoritative representation within a system. |
| SOC | Separation of Concerns | It is the process of separating a computer program into distinct features that overlap in functionality as little as possible |
| SRP | Single Responsibility Principle | Every object should have a single responsibility, and that responsibility should be entirely encapsulated by the class. All its services should be narrowly aligned with that responsibility. |
| TDD | Test Driven Development | Is a software development technique that relies on the repetition of a very short development cycle: First the developer writes a failing automated test case that defines a desired improvement or new function, then produces code to pass that test and finally refractors the new code to acceptable standards. |
| CI | Continuous Integration | continuous integration implements continuous processes of applying quality control - small pieces of effort, applied frequently. |
| BDD | Behavior Driven Development | Is an Agile software development technique that encourages collaboration between developers, QA and non-technical or business participants in a software project. |
| DDD | Domain Driven Design | Is an approach to developing software for complex needs by deeply connecting the implementation to an evolving model of the core business concepts. |
| POEAA | Patterns of Enterprise Application Architecture | A book by Martin Flower |
Related posts:
Tags: Architecture
Leave a Reply
You must be logged in to post a comment.