From pattern languages to a project language: a shift proposal from existing pattern community

Patterns and pattern languages are accepted worldwide and used in various areas of IT such as Design Patterns, Analysis Patterns, Domain Driven Developments, and AGILE SOFTWARE DEVELOPMENT. Although patterns are successful in such areas, they are less accepted in the areas of large development and planning projects. We suggest that large projects and communities should be responsible for identifying and documenting their own patterns instead of adopting those found in pattern libraries. This is consistent with Alexander's hope to use patterns and pattern languages as part of his emphasis on planning and community involvement. Our paper focuses on the beginnings of pattern language that we believe will facilitate the writing of appropriate patterns for different situations by those involved in solving and building in those same situations. Additionally we propose a Project Language as different form of Pattern Language, consisting of episodes and stories. In this paper, we have thus focus upon the essence of C. Alexander's Community Planning and centering process via pattern language. In this paper we argue for turn from the existing dominant ideas out how to use patterns by professionals to positive, community-centric way participants to think about and act on their own pattern languages. This new approach is, we believe, both urgent and indispensable at this time.