|
|
| Line 1: |
Line 1: |
| − | [[DADI]] (also known as [[DADI pattern]]; hereinafter, the ''Pattern'') is the enterprise development pattern that divides enterprise development activities in four consecutive batches: [[Discovery DADI|'''D'''iscovery]] (D), [[Analysis DADI|'''A'''nalysis]] (A), [[Design DADI|'''D'''esign]] (D), and [[Implementation DADI|'''I'''mplementation]] (I). The name of the ''Pattern'' is the abbreviation of four verbs: [[Discovery DADI|'''D'''iscover]], [[Analysis DADI|'''A'''nalyze]], [[Design DADI|'''D'''esign]], [[Implementation DADI|'''I'''mplement]].
| |
| | | | |
| − | The ''Pattern'' is used in any development in two ways:
| |
| − | #Being '''complex''', ''Pattern'' can serve as a canvas for the development cycle as a whole. In this case, one bigger ''complex Pattern'' may consist of a number of smaller ''Patterns'', which are called ''basic''; and
| |
| − | #Being '''basic''', ''Pattern'' can serve as a layout for simple actions in [[new product development]], [[problem solving]], [[competitive strategy]], [[business analysis]], [[systems engineering]], [[project management]], etc. A combination of those ''basic Patterns'' can be presented as a ''complex Pattern.''
| |
| − |
| |
| − | [[#In education|In education]], [[Bracka School]] also deploys the ''Pattern'' while building the curricula on multiple sets of four quarters, each of which represents one batch of the ''Pattern''.
| |
| − |
| |
| − |
| |
| − | ==Classifications==
| |
| − | Classifications of the ''Patterns'' are tentative. Every ''Pattern'' has some agility and no ''Pattern'' can fully fall in one exact category. Thus, the taxonomies below serve to demonstrate various directions of various ''Patterns'' rather than precise classifications.
| |
| − |
| |
| − | ===Basic vs complex===
| |
| − | ::Ideally, a '''basic''' ''Pattern'' is any development pattern that doesn't include other ''Patterns''. For example, a generic reply like "Oh, really?" in a common conversation can be considered as basic. The listener (a) listens (or ''discovers'') to its conversational partner, (b) ''analyzes'' what he or she has said, (c) decides what to reply (or ''designs'' the reply), and (d) delivers (or ''implements'') it;
| |
| − | ::Ideally, a '''complex''' ''Pattern'' is any development pattern that includes other ''Patterns''. For example, development of a new space ship requires millions should be considered as complex because it includes millions and millions ''basic Patterns''.
| |
| − |
| |
| − | ===Complete vs partial===
| |
| − | :*Ideally, a '''complete''' ''Pattern'' is any development pattern that includes all four batches from [[Discovery Batch]] to [[Implementation Batch|Implementation one]]. For example, a generic reply like "Oh, really?" in a common conversation can be considered as complete because the entry data for this reply was collected, analyzed, the reply was designed and delivered;
| |
| − | :*Ideally, a '''partial''' ''Pattern'' is any development pattern that doesn't include [[Implementation Batch]]. This ''Pattern'' may or may not include [[enterprise design]] if the ''Pattern'' includes [[enterprise analysis]]. This ''Pattern'' may or may not include [[enterprise analysis]], but always include [[enterprise discovery]]. For example, development of a new space ship was ordered, but the project was stopped in the middle because of the lack of funding.
| |
| − |
| |
| − | ===Transitional vs terminal===
| |
| − | :*Ideally, a '''transitional''' ''Pattern'' is undertaken in order to get some deliverable, which will be used in some ''Pattern'' in the future. For instance, a traveler takes a taxi in hopes that his or her driver would give more information on what to visit in a city, which hasn't been known to him or her yet. The traveler's airplane is unexpectedly delayed for one day;
| |
| − | :*Ideally, a '''terminal''' ''Pattern'' is undertaken in order to get with some deliverable, which will not be used in the future by the undertaker. For instance, someone delivers a pack of generic Vitamin C to its buyer.
| |
| − |
| |
| − | ===Predefined-deliverable vs unexplored-deliverable===
| |
| − | :*Ideally, a '''predefined-deliverable''' ''Pattern'' is undertaken in order to get with some deliverable, which features are defined before the ''Pattern'' starts. For instance, someone needs to buy a pack of generic Vitamin C;
| |
| − | :*Ideally, an '''unexplored-deliverable''' ''Pattern'' is undertaken in order to get some deliverable, which features cannot be exactly defined before the ''Pattern'' starts. For instance, a traveler takes a taxicab in order to get to a city, which hasn't been known to him or her yet, because the traveler's airplane is unexpectedly delayed for one day and he or she is looking for ideas how to spend that "extra" day.
| |
| − |
| |
| − | ==Components==
| |
| − | ===Discovery DADI===
| |
| − | ::''Main wikipage: [[Discovery DADI]]''
| |
| − |
| |
| − | ::The first batch of the ''Pattern'' is [[Discovery DADI]]. It includes all activities resulted in discovery of any data relevant to the further enterprise development. These data include some statement of the [[business need]] that is sought to be satisfied as the key outcome from that enterprise as a whole.
| |
| − |
| |
| − | ===Analysis DADI===
| |
| − | ::''Main wikipage: [[Analysis DADI]]''
| |
| − |
| |
| − | ::The second batch of the ''Pattern'' is [[Analysis DADI]]. It includes all activities needed to process the data discovered in [[Discovery DADI]] in order to provide [[Design DADI]] with detailed requirements for the future outcome from the ''Pattern''.
| |
| − |
| |
| − | ===Enterprise design===
| |
| − | ::''Main wikipage: [[Enterprise design]]''
| |
| − |
| |
| − | ::The third batch of the ''Pattern'' is [[enterprise design]]. It includes all activities needed to conceptualize, design, scratch, model, map, plan, project, and/or detail the ''Pattern'''s outcome and/or finalize the architecture or layout for this outcome.
| |
| − |
| |
| − | ===Enterprise implementation===
| |
| − | ::''Main wikipage: [[Enterprise implementation]]''
| |
| − |
| |
| − | ::The fourth batch of the ''Pattern'' is [[enterprise implementation]]. It includes all activities needed to create and deliver the ''Pattern'''s outcome based on its architecture or layout made in [[enterprise design]].
| |
| − |
| |
| − | ==Applications==
| |
| − | [[New product development]], [[problem solving]], [[competitive strategy]], [[portfolio management]], [[business analysis]], [[systems engineering]], [[project management]] and many other concepts are built on the ''basic Patterns''. ''Complete complex terminal Patterns'' seem to have strong correlations with other concepts as well.
| |
| − |
| |
| − | ===In project management===
| |
| − | ::With one exception of discovering a business need, which project deliverables shall satisfy, the ''complex Pattern'' can serve as a [[project management]] canvas itself. One or more the ''basic Patterns'' can be used in order to create or modify any output of any [[project management process]] such as a [[project charter]], [[stakeholder register]], [[acceptance criteria]], etc.
| |
| − |
| |
| − | ===Complex Patterns vs other development concepts===
| |
| − | ::Although the table below is not intended to be complete, it addresses some tendencies and correlations between the complete complex terminal ''Patterns'', on the one hand, and some other other development concepts, on the other hand:
| |
| − | ::{|class="wikitable" width=100% style="text-align:center;"
| |
| − | |colspan="2" style="background:#fff;"|'''[[Enterprise discovery|Discovery]]'''||rowspan="2" style="background:#fff; vertical-align:top;"|'''[[Enterprise analysis|Analysis]]'''||rowspan="2" style="background:#fff; vertical-align:top;"|'''[[Enterprise design|Design]]'''||rowspan="2" style="background:#fff; vertical-align:top;"|'''[[Enterprise implementation|implementation]]'''
| |
| − | |-
| |
| − | |style="background:#fff;"|[[Business need|Business need]]|| style="background:#fff;"|[[Requirements data|Requirements data]]
| |
| − | |-
| |
| − | |colspan="5" style="background:#ffe6e6;"|'''[[Portfolio management]]'''
| |
| − | |-
| |
| − | |rowspan="4" style="background:#f6f6f6;"|Usually, [[c-level executive]]s define the needs at the organizational level, as well as [[frontline manager]]s at the lower levels and [[middle managers]] in between those levels||colspan="4" style="background:#e6ffe6;"|'''[[New product development]]'''
| |
| − | |-
| |
| − | |colspan="4" style="background:#e6e6ff;"|'''[[Project management]]'''
| |
| − | |-
| |
| − | |colspan="3" style="background:#ffe6e6;"|'''[[Systems engineering]]'''||rowspan="3" style="background:#f6f6f6;"|Usually, project teams or functional departments execute implementations
| |
| − | |-
| |
| − | |colspan="2" style="background:#e6ffe6;"|'''[[Business analysis]]'''||style="background:#f6f6f6;"|[[Solution architect]]s or others can design the solution
| |
| − | |-
| |
| − | |colspan="4" style="background:#e6e6ff;"|'''[[Competitive strategy]]'''
| |
| − | |-
| |
| − | |style="background:#fff;"|[[Business need|Business need]]|| style="background:#fff;"|[[Requirements data|Requirements data]]||rowspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise analysis|Analysis]]'''||rowspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise design|Design]]'''||rowspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise implementation|implementation]]'''
| |
| − | |-
| |
| − | |colspan="2" style="background:#fff; vertical-align:bottom;"|'''[[Enterprise discovery|Discovery]]'''
| |
| − | |-
| |
| − | |}
| |
| − |
| |
| − | ===In education===
| |
| − | ::[[Bracka School]] has built its [[Septem Artes Administrativi]] curriculum on seven sets of four quarters. Each set is called [[quadrivium]] and designed around the ''Pattern''.
| |
