Pattern Languages The idea of Pattern Languages, as a process for analyzing recurrent problems and a mechanism for capturing problems and archetypal solutions, was first outlined by architect Christopher Alexander [Alexander 1964] and [Alexander 1979]: value of a Pattern Language is that remains readable and “The engaging whilst providing basic hooks for further machine processing… [it] is not an ‘out-of-the-box’ solution but rather some patterns with which a team can work” [Brown 2011]. ‘familiar’ The exact configuration varies from one pattern language to another, and the pattern adopted in the TGF is structured as follows: the name of the pattern and a reference number; an introduction that sets the context and, optionally, indicates how the pattern contributes to a larger pattern; a headline statement that captures the essence of the need addressed; the body of the need being addressed; the recommended solution what needs to be done; – some notes on linkages, showing how each pattern links to related and more detailed patterns that further implement or extend the current pattern. In some cases this also includes references to external resources that are not part of the TGF. These patterns together make up an initial set of Patterns” of what is expected to be an evolving set “Core of TGF patterns. These form the core of the TGF standard, and it is against these that conformance criteria are set out in Section 9. Where closely related patterns have been grouped together in one section of this document for example, on Business Management, Service Management and Technology – and Digital Asset Management the relevant section also includes some additional introductory text to – help readers understand linkages more easily. This text, however, does not form part of the TGF Core Pattern Language. Guiding Principles There is one TGF Core Pattern on Guiding Principles. This is set out below. [GP1] Guiding Principles Context Development and delivery of a successful TGF program requires collaboration and change across a wide range of individuals, communities and organizations over a sustained period of time. An approach that is rooted in a set of clearly stated principles can help ensure that business decisions across those organizations align. In the TGF, we use the term to mean an enduring statement of values can used on a “principle” consistent basis to steer business decision by multiple stakeholders making over the long term, and which are: used to inform and underpin strategy; understood, agreed and owned by stakeholders.
Pattern Languages The idea of Pattern Languages, as a process for analyzing recurrent problems and a mechanism for capturing problems and archetypal solutions, was first outlined by architect Christopher Alexander [Alexander 1964] and [Alexander 1979]: “The value of a Pattern Language is that remains readable and engaging whilst providing basic hooks for further machine processing… [it] is not an ‘out-of-the-box’ solution but rather some ‘familiar’ patterns with which a team can work” [Brown 2011]. The exact configuration varies from one pattern language to another, and the pattern adopted in the TGF is structured as follows: the name of the pattern and a reference number; an introduction that sets the context and, optionally, indicates how the pattern contributes to a larger pattern; a headline statement that captures the essence of the need addressed; the body of the need being addressed; the recommended solution – what needs to be done; some notes on linkages, showing how each pattern links to related and more detailed patterns that further implement or extend the current pattern. In some cases this also includes references to external resources that are not part of the TGF. These patterns together make up an initial set of “Core Patterns” of what is expected to be an evolving set of TGF patterns. These form the core of the TGF standard, and it is against these that conformance criteria are set out in Section 9. Where closely related patterns have been grouped together in one section of this document – for example, on Business Management, Service Management and Technology and Digital Asset Management – the relevant section also includes some additional introductory text to help readers understand linkages more easily. This text, however, does not form part of the TGF Core Pattern Language. Guiding Principles There is one TGF Core Pattern on Guiding Principles. This is set out below. [GP1] Guiding Principles Context Development and delivery of a successful TGF program requires collaboration and change across a wide range of individuals, communities and organizations over a sustained period of time. An approach that is rooted in a set of clearly stated principles can help ensure that business decisions across those organizations align. In the TGF, we use the term “principle” to mean an enduring statement of values can used on a consistent basis to steer business decision by multiple stakeholders making over the long term, and which are: used to inform and underpin strategy; understood, agreed and owned by stakeholders.
Transformational_Government_Framework_Version_2.docx