When Christopher Alexander (1977), trained both as a mathematician and an architect, published his seminal work “The Pattern Language” in the 1970's and introduced the concept of “pattern language”, computers were still in their infancy, CAD did not exist as we know it today, and computer information modelling was not even in the radar screen of researchers. Design communication simply meant manual drafting. With the concept of “pattern language” (http://www.patternlanguage.com/), Alexander proposed a systematic method for dealing with complexity, which proved itself to be more relevant than ever in the digital age. The concept is often cited by computer scientists as a precursor to object oriented modelling. This study explores the potential of “pattern languagei for structuring building information and design knowledge within the framework of the recent developments in building information modelling (BIM). In this article, comparisons to the approach taken by the software engineering industry who embraced the idea of “patternsi as a systematic way to software development are also made. While Alexanderis pattern language proposes a method with which the designer can incorporate his/her experiences and design vision systematically into the process of designing, software industryis approach to patterns describes a method for providing problem and solution patterns (i.e. prototypes) that can be used repeatedly during software development. There is obviously a significant difference between the original intent of the “pattern language” and the way it was later used in other fields including software engineering and business solutions. At the cross section of architectural design and software engineering, Building Information Modelling (BIM) software can benefit from carefully incorporating a combination of these two approaches into its structure as patterns.