Its long time in my career and sometimes we flumble with the basics, concepts and fundamentals.
Here is the list of few design patterns or terminology where we come across during day to day SDLC life cycle. I will try updating this particular post in future to include the most favourable one.
Facade: It provides simplied interface to a larger body of code-class library. In simple terms a group of class library or dll referenced in single interface and this later expose to calling events or client.
Purpose - It wraps poorly designed collections of API into or with single well designed API.
Adapter : Is also called Wrapper pattern or Decorative pattern (GOF ). The actual usuage or orgin, when one should coin this- This is to be used when we have module which is to be used but incompatible with other module. At such places we create interface out of the class and create compatible bridge to use across.
Boiler Plate Code- Is a section of code that can be included in many place with no or minimal changes.
Here is the list of few design patterns or terminology where we come across during day to day SDLC life cycle. I will try updating this particular post in future to include the most favourable one.
Facade: It provides simplied interface to a larger body of code-class library. In simple terms a group of class library or dll referenced in single interface and this later expose to calling events or client.
Purpose - It wraps poorly designed collections of API into or with single well designed API.
Adapter : Is also called Wrapper pattern or Decorative pattern (GOF ). The actual usuage or orgin, when one should coin this- This is to be used when we have module which is to be used but incompatible with other module. At such places we create interface out of the class and create compatible bridge to use across.
Boiler Plate Code- Is a section of code that can be included in many place with no or minimal changes.
- Shotgun Debugging- To apply too many solution at a time to solve issue.Troubleshoot.
- Spaghetti Code- To many branching of code, difficult to read and understand
- Smoke Testing- To do high level testing to ensure system do not break. This ignores finer level of testing. Imagine a smoke pass into pipe to check leak
- Regression Testing-Testing to ensure new changes do not break existing functionality.
- Write Only Code- Difficult to read
- Runtime-
- Break Fix-
- Service Pack
- Drivers
- HotFix-
- Refactoring- Change system internally without affecting functionality.
- Pilot
- Prototype
- Proof of Concept
- Psuedo Code- Code that is written in user readable format unlike programming language.
- Peer Review
- Patch
- Plumbing work
- Legacy System
- Gold Code- Code that is live and burn in disc. Final release product.
- Gap Analysis
- Impact Analysis
- Evaluation
- Feasibility Check
- AntiPattern- In appropiate solution for a problem but still used as temporary setup.
No comments :
Post a Comment