How does OIAm work: Difference between revisions
Jump to navigation
Jump to search
(table of content started) |
(used Docbooklinks) |
||
| Line 1: | Line 1: | ||
In essence, OIAm as a method makes use of a number of premises, the most important ones are presented below: | In essence, OIAm as a method makes use of a number of premises, the most important ones are presented below: | ||
{{Docbooklink|page=Architecture is overarching design}} | |||
{{Docbooklink|start=The main principle:|page=Functionality before construction|title=functionality before construction}} | |||
{{Docbooklink|page=The OIAm workflow}} | |||
{{Docbooklink|page=Architecture modelling using standardized content}} | |||
{{Docbooklink|page=ArchiMate as the infrastructure modelling language}} | |||
{{Docbooklink|page=The OIAm quality attributes}} | |||
{{Docbooklink|page=Using the generic OIAm infrastructure landscape}} | |||
{{Docbooklink|page=Mapping the actual infrastructure landscape}} | |||
{{Docbooklink|page=Tailoring infrastructure architecture products to stakeholders}} | |||
{{Docbooklink|page=Embedding infrastructure architecture in the organization}} | |||
Latest revision as of 17:43, 15 August 2013
In essence, OIAm as a method makes use of a number of premises, the most important ones are presented below:
Architecture is overarching design
The main principle:functionality before construction
Architecture modelling using standardized content
ArchiMate as the infrastructure modelling language
Using the generic OIAm infrastructure landscape
Mapping the actual infrastructure landscape
Tailoring infrastructure architecture products to stakeholders