Thursday, May 5, 2011

Oops. Time for Design patterns

Introduction of lovely world of Object oriented programming has been a blessing so far.Object Oriented Programming is not very radical compared to conventional programming.
For OOps refer to Click Here

Now lets us talk about Design patterns, Lets us start by putting some questions across the table....
1.What is a Design Pattern?
2.What are different Design patterns?
3.Why do i need it?
4.How do you know when to use design patterns?

I will be discussing more questions in this blog but for now lets Proceed
Good to go.......

Developers around the world face some common problems and these common problems ideally should have a common solution too,It is this solution when documented and used over and over becomes a design pattern.Design pattern describes a problem which occurs over and over again in our environment, and describes its solution in such a way that this solution can be used to solve the problem whenever need is.Design patterns are problem specific and thereby are implemented after knowing the behavior of project, on which the design pattern needs to be implemented.Thus there needs to be lots of thought process when choosing for design pattern of project ex:-

1.We need to understand the problem at hand. Break it down to finer grained problems. Each design pattern is meant to solve certain kinds of problems. This would narrow down our search for design patterns.

2.Read the problem statement again along with the solution which the design pattern will provide. This may instigate to change a few patterns that we are to use.

3.Now figure out the interrelations between different patterns. Also decide what all patterns will remain stable in the application and what all need to change (with respect to Change Requests received from the clients).

Types Of Software Patterns
Riehle and Zullighoven in “Understanding and Using Patterns in Software Development” mention three types of software patterns
l Conceptual Pattern
Pattern whose form is described by means of terms and concepts from the application domain

2 Design Pattern
Pattern whose form is described by means of software design constructs,
such as objects, classes, inheritance and aggregation

3 Programming Pattern (Programming Idiom)
Pattern whose form is described by means of programming language
constructs

Our focus will be on the design patterns and what we will try to understand is types of Patterns, Levels Of Abstraction of design patterns and how can we implement these patterns in our software projects..................

Types Of Design Patterns

1. Creational Patterns
  • Factory Pattern
  • Abstract Factory Pattern
  • Singleton Pattern
  • Builder Pattern
  • Prototype Pattern


2. Structural Patterns

  • Adapter Pattern
  • Bridge Pattern
  • Composite Pattern
  • Decorator Pattern
  • Facade Pattern
  • Flyweight Pattern
  • Proxy Pattern

3. Behavioral Patterns

  • Chain of Responsibility Pattern
  • Command Pattern
  • Interpreter Pattern
  • Iterator Pattern
  • Mediator Pattern
  • Memento Pattern
  • Observer Pattern
  • State Pattern
  • Strategy Pattern
  • Template Pattern
  • Visitor Pattern

A creational pattern abstracts the instantiation process.
A structural pattern groups objects into larger structures.
A behavioral pattern defines better communication among objects



Saturday, September 26, 2009

Building a Sense of Competence

To develop you member’s performance, you need to build a sense of competence among your team members. There are five strategies to accomplish this:
- Providing Knowledge
- Giving Positive feedback
- Skill Recognition
- Challenge
- High, non comparative standards
Providing Knowledge
Over time, workers gain a great deal of knowledge through their own experience with a task through experimentation and feedback. Some of this knowledge is implicit or tacit, difficult to express, like how to perform a physical skill gracefully. The rest is explicit knowledge that can be expressed and shared. This explicit knowledge includes learning’s about techniques, best practices, and rules of thumb that contribute to competent performance. Adding to this knowledge can be a relatively quick way of increasing competence? Allowing workers to jump ahead of where they would otherwise be on their own learning curve.
Providing Appreciative Feedback
Workers must be able to monitor the competence of their ongoing activities in order to make adjustments in their performance. Much of this feedback is available to workers as they interact with a product or customer, but some needs to be measured more elaborately. Under self-management, workers need to be given the tools and data needed to assess the quality of their performance and to make adjustments themselves whenever possible.
Recognizing Skill
When you give team members recognition for the competence of their work, you are doing a number of important things. For example, you are strengthening the message that good work is important, valued, and noticed. You are appreciating the effort and accomplishment involved ? providing a kind of "thank you" for a team member's contribution on behalf of the team and the organization. But perhaps most important, you are also validating and amplifying that team member's sense of competence. For a moment, the two of you step back from the task activity, view the work in perspective, and together appreciate how well it was done.
Managing Challenge
People perform best when there is a fit between their ability and the task difficulty, or challenge. If the task is too easy, their attention wanders and they become bored. If it's too difficult, they get anxious and do less than their best work. An ideally challenging task is just manageable and requires full concentration. Because the task is challenging, it inspires even more satisfaction when it is performed well.