Netmar http://localhost/wiki/index.php/Main_Page MediaWiki 1.18alpha first-letter Media Special Talk User User talk Netmar Netmar talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk Property Property talk Type Type talk Form Form talk Concept Concept talk 1 1 2010-12-23T10:44:13Z MediaWiki Default '''MediaWiki has been successfully installed.''' Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] 2 2010-12-23T10:48:53Z 109.76.62.108 '''MediaWiki has been successfully installed.''' Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] [[test::hello]] 3 2010-10-29T15:00:40Z MediaWiki default <big>'''MediaWiki has been successfully installed.'''</big> Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] 4 2010-11-01T15:46:11Z WikiSysop = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]]}} 5 2010-11-01T15:47:24Z WikiSysop = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis] |?Scenario |?Stimulus |?Response}} 6 2010-11-01T15:48:25Z WikiSysop = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Scenario |?Stimulus |?Response }} 7 2010-11-01T15:48:41Z WikiSysop = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Scenario |?Stimulus |?Response }} 8 2010-11-02T16:59:53Z Anthony 1 /* Analysis */ = Projects = == NETMAR == === Utility Tree Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} ==== Service Visibility ==== ===== Service Reachability ===== {{#ask: [[Category:Analysis]] [[Attribute::Service Reachability]] |?Scenario |?Stimulus |?Response }} 9 2010-11-04T12:47:34Z Anthony 1 /* Utility Tree Analysis */ = Projects = == NETMAR == === Utility Tree Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} ==== Service Visibility ==== {{#ask: [[Category:Analysis]] [[Attribute::Service Reachability]] |?Scenario |?Stimulus |?Response }} ==== Flexibility ==== {{#ask: [[Category:Analysis]] [[Attribute::Flexibility]] |?Scenario |?Stimulus |?Response }} 10 2010-11-04T14:39:27Z Anthony 1 /* NETMAR */ = Projects = == NETMAR == === Utility Tree Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis] |?Attribute |?Scenario |?Stimulus |?Response }} 11 2010-11-04T14:40:20Z Anthony 1 = Projects = == NETMAR == === Utility Tree Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} 12 2010-11-25T10:27:17Z Anthony 1 = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} === Decisions === {{#ask: [[Decision::]] |mainlabel=- |format=ul |?Decision= }} 13 2010-11-25T12:59:03Z Anthony 1 /* Decisions */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| '''Decisions {{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |- '''Sensitivity Points {{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |} 14 2010-11-25T13:02:40Z Anthony 1 /* Analysis */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| |'''Decisions {{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |'''Risks {{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |'''Non-risks {{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |'''Tradeoffs {{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |'''Sensitivity Points {{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |} 15 2010-11-25T13:13:05Z Anthony 1 /* Analysis */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |} 16 2010-11-25T14:28:24Z Anthony 1 /* Analysis */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern }} 17 2010-11-25T15:31:35Z Anthony 1 /* Patterns used */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |mainlabel=Decision |?Pattern }} 18 2010-11-25T15:32:36Z Anthony 1 /* Analysis */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |mainlabel=Decision |?Pattern }} 19 2010-11-25T15:53:23Z WikiSysop Protected "[[Main Page]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |mainlabel=Decision |?Pattern }} 20 2010-11-25T15:55:11Z WikiSysop Changed protection level for "[[Main Page]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) [cascading] = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |mainlabel=Decision |?Pattern }} 21 2010-11-25T15:56:14Z WikiSysop Changed protection level for "[[Main Page]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |mainlabel=Decision |?Pattern }} 22 2010-11-25T16:52:42Z WikiSysop Unprotected "[[Main Page]]" = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |mainlabel=Decision |?Pattern }} 23 2010-11-25T16:54:29Z Anthony 1 /* Patterns used */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 24 2010-11-25T17:37:44Z Anthony 1 /* Analysis */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ol |?Decision= }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 25 2010-11-25T17:38:51Z Anthony 1 /* Analysis */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ol |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 26 2010-11-25T17:55:28Z Anthony 1 /* Analysis */ = Projects = == NETMAR == === Analysis === {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 27 2010-11-30T15:35:57Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. information is added through the Architectural Approach description button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 28 2010-11-30T15:38:51Z Anthony 1 /* Introduction */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 29 2010-11-30T15:41:40Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 30 2010-11-30T15:49:14Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 31 2010-12-07T17:27:50Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#set_internal:From Decision |Count={{#ask: [[Decision::Common metadata standards]]|mainlabel=-|?Decision|format=count}} |Description=Common metadata standard }} {{#ask: [[From Decision::+]] |?Count |?Description |mainlabel=- }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 32 2010-12-07T17:33:31Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#set_internal:From Decision |Common metadata standard={{#ask: [[Decision::Common metadata standards]]|mainlabel=-|?Decision|format=count}} }} {{#ask: [[From Decision::+]] |?Common metadata standard |mainlabel=- }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 33 2010-12-08T08:40:42Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#set_internal:From Decision |Common metadata standard={{#ask: [[Decision::Common metadata standards]]|mainlabel=-|?Decision}} }} {{#ask: [[From Decision::+]] |?Common metadata standard |mainlabel=- }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 34 2010-12-08T08:42:45Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#set_internal:From Decision |Common metadata standard={{#ask: [[Decision::Common metadata standards]]|mainlabel=-|?Decision}} }} {{#ask: [[From Decision::+]] |?Common metadata standards |mainlabel=- }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 35 2010-12-08T08:46:55Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#set_internal:From Decision |Common metadata standard={{#ask: [[Decision::Common metadata standards]]}} }} {{#ask: [[From Decision::+]] }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 36 2010-12-08T08:51:36Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap:{{#ask: [[Decision::Common metadata standards]]}}|,|%%|{{#set_internal:From Decision |Common metadata standard=%%|,}} }} {{#ask: [[From Decision::+]] }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 37 2010-12-08T08:59:28Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} {{#ask: [[From Decision::+]] [[Common metadata standards::+]] |format=count }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 38 2010-12-08T09:18:08Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 39 2010-12-08T09:45:08Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made:+]]|,|%%|[[Decision::!%%]]| | }} }} }} |,|%%| {{#set_internal:Existing Decision|Decision Made=^^|,| }} }} {{#ask: [[Decision Made::+]] |?Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 40 2010-12-08T09:55:45Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made:+]]|,|%%|[[Decision::! {{#show: %%|?Decision }}]]| | }} }} }} |,|^^| {{#set_internal:Existing Decision|Decision Made=^^|,| }} }} {{#ask: [[Decision Made::+]] |?Decision }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 41 2010-12-08T10:05:18Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made:+]]|,|%%|[[Decision::!%%]]| | }} }} }} |,|^^| {{#set_internal:Existing Decision|Decision Made={{#show:^^|?Decision}}|,| }} }} {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 42 2010-12-08T10:13:01Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made:+]]|,|%%|[[Decision::!{{#show:%%|?Decision Made}}]]| | }} }} }} |,|^^| {{#set_internal:Existing Decision|Decision Made={{#show:^^|?Decision}}|,| }} }} {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 43 2010-12-08T10:34:17Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made:+]]|,|%%|[[Decision::!{{#show:%%|?Decision Made}}]]| | }} }} }} |,|^^| {{#set_internal:Existing Decision|Decision Made={{#show:^^|?Decision=|mainlabel=-}}|,| }} }} {{#ask: [[Decision::+]] [[Decision::!Common metadata standards]]|?Decision=|mainlabel=-}} {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 44 2010-12-08T10:44:38Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made:+]]|,|%%|[[Decision::!{{#ask:%%|?Decision Made=|mainlabel=-}}]]| | }} }} }} |,|^^| {{#set_internal:Existing Decision|Decision Made={{#ask:^^|?Decision=|mainlabel=-}}|,| }} }} {{#ask: [[Decision::+]] [[Decision::!Common metadata standards]]|?Decision=|mainlabel=-}} {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 45 2010-12-08T10:52:16Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made:+]]|,|%%|[[Decision::!{{#ask:%%|?Decision Made=|mainlabel=-}}]]| | }} }} }} |,|^^| {{#ask:^^|?Decision=|mainlabel=-}}|{{#set_internal:Existing Decision|Decision Made={{#ask:^^|?Decision=|mainlabel=-}}|,| }} }} ========= {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 46 2010-12-08T11:14:40Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) 1 {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }}|,|%%|%%| | }} 2 {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }}|,|%%|[[Decision::!%%]]| | }} }} |,|^^| |^^{{#set_internal:Existing Decision|Decision Made={{#ask:^^|?Decision=|mainlabel=-}}|,| }} }} ========= {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 47 2010-12-08T11:28:09Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) >>>{{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }}|,|%%| [[Decision::!%%]]| | }}|?Decision=|mainlabel=- }}<<< {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }}|,|%%| [[Decision::!%%]]| | }}|?Decision=|mainlabel=- }} |,|%%| |%%{{#set_internal:Existing Decision|Decision Made={{#ask:^^|?Decision=|mainlabel=-}}|,| }} }} ========= {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 48 2010-12-08T11:36:37Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }}|,|%%|[[Decision::!%%]]| | }}|?Decision=|mainlabel=- }} |,|%%| |{{#set_internal:Existing Decision|Decision Made={{#ask:%%|?Decision=|mainlabel=-}}|,| }} }} ========= {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 49 2010-12-08T11:44:49Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=- }} |,|%%|{{#set_internal:Existing Decision|Decision Made={{#ask:%%|?Decision=|mainlabel=-}}| }} }} ========= {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 50 2010-12-08T11:55:18Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) <<< {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=- }} |,|%%|%% }} >>> {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=- }} |,|%%|{{#set_internal:Existing Decision|Decision Made=%% }} }} ========= {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 51 2010-12-08T12:05:20Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) <<< {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=- }} |,|%%|%% }} >>> {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=- }} |,|%%|%%{{#set_internal:Existing Decision|Decision Made=%%}} }} ========= {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 52 2010-12-08T12:13:53Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) <<< {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=- }} |,|%%|%% }} >>> {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=- }} |,|%%|..%%{{#set_internal:Existing Decision|Decision Made=%%}} }} ========= {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 53 2010-12-08T12:16:11Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) <<< {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=- }} |,|%%|%% }} >>> {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=- }} |,|%%|[[Decision Made::%%]]}} }} ========= {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 54 2010-12-08T12:28:16Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=-|link=none }} |,|%%|%%{{set_internal_object:Existing Decision|Decision Made=%%}} }} {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 55 2010-12-08T12:29:02Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=-|link=none }} |,|%%|{{set_internal:Existing Decision|Decision Made=%%}} }} {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 56 2010-12-08T12:29:30Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=-|link=none }} |,|%%|{{#set_internal:Existing Decision|Decision Made=%%}} }} {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 57 2010-12-08T12:51:18Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::Common metadata standards]] }} |,|%%| {{#set_internal:From Decision|Common metadata standards=%%|,| }} }} [[Common metadata standards]] ( {{#ask: [[Common metadata standards::+]] |format=count }} ) {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=-|link=none }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=-|link=none }} |,|%%|{{#set_internal:Existing Decision|Decision Made=%%}} }} {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 58 2010-12-08T13:04:32Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#arraymap: {{#ask: [[Decision::+]] {{#arraymap: {{#ask: [[Decision Made::+]]|?Decision Made=|mainlabel=- }} |,|%%|[[Decision::!%%]] }} |?Decision=|mainlabel=-|link=none }} |,|%%|{{#set_internal:Existing Decision|Decision Made=%%}} }} {{#ask: [[Decision Made::+]] |?Decision Made }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 59 2010-12-08T14:01:06Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 60 2010-12-08T15:09:10Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 61 2010-12-15T12:33:53Z Anthony 1 /* Summaries */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision |userparam=unique }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 62 2010-12-15T16:14:11Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision |userparam=unique }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 221 2010-12-23T14:03:32Z Anthony 1 Reverted edits by [[Special:Contributions/109.76.62.108|109.76.62.108]] ([[User talk:109.76.62.108|talk]]) to last revision by [[User:MediaWiki Default|MediaWiki Default]] '''MediaWiki has been successfully installed.''' Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] 222 2010-12-23T14:04:23Z Anthony 1 Reverted edits by [[Special:Contributions/Anthony|Anthony]] ([[User talk:Anthony|talk]]) to last revision by [[User:109.76.62.108|109.76.62.108]] '''MediaWiki has been successfully installed.''' Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] [[test::hello]] 223 2010-12-23T14:04:56Z Anthony 1 Undo revision 222 by [[Special:Contributions/Anthony|Anthony]] ([[User talk:Anthony|talk]]) '''MediaWiki has been successfully installed.''' Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] 224 2010-12-23T14:09:51Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision |userparam=unique }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} 248 2011-01-26T10:52:29Z Anthony 1 /* Patterns used */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision |userparam=unique }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] 271 2011-02-08T14:25:41Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision |userparam=unique }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] 292 2011-02-09T11:30:59Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision |userparam=unique }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] 297 2011-02-09T13:45:27Z Anthony 1 /* Introduction */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and governance of the NETMAR system architecture. This page contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR. Information is added through the 'Add an Architectural Approach Description' button below. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision |userparam=unique }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] 299 2011-02-09T14:13:46Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. This will == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision |userparam=unique }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 300 2011-02-09T15:05:52Z Anthony 1 = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. This will == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#ask: [[Decision::+]] |mainlabel=- |format=ul |?Decision= |sort=Decision |userparam=unique }} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 301 2011-02-09T16:06:47Z Anthony 1 /* Summaries */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. This will == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions|{{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |,|unique}} {{#arrayprint:decisions|<br/>}} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 302 2011-02-09T16:16:26Z Anthony 1 /* Summaries */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. This will == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |,|unique}} {{#arrayprint:decisions|<br/>}} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 303 2011-02-09T16:20:34Z Anthony 1 /* Summaries */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. This will == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uniquify --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |,|unique}} {{#arrayprint:decisions|<br/>}} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 304 2011-02-09T16:22:22Z Anthony 1 /* Summaries */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. This will == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#ask: [[Risk::+]] |mainlabel=- |format=ul |?Risk= }} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 305 2011-02-09T16:23:56Z Anthony 1 /* Summaries */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. This will == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#ask: [[Non-risk::+]] |mainlabel=- |format=ul |?Non-risk= }} |{{#ask: [[Sensitivity::+]] |mainlabel=- |format=ul |?Sensitivity= }} |{{#ask: [[Tradeoff::+]] |mainlabel=- |format=ul |?Tradeoff= }} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 306 2011-02-09T16:28:57Z Anthony 1 /* Summaries */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. This will == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 307 2011-02-11T12:19:33Z Anthony 1 /* Methodology */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. * The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. * Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. * We will construct an RM-ODP model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. * The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. * == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 308 2011-02-11T12:24:54Z Anthony 1 /* Methodology */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. * The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. * Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. * We will construct an RM-ODP model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. * The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. * A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 309 2011-02-11T12:37:20Z Anthony 1 /* Methodology */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 310 2011-02-11T12:38:46Z Anthony 1 /* Methodology */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are all the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 311 2011-02-11T13:09:14Z Anthony 1 /* Analysis */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 327 2011-02-11T16:07:43Z Anthony 1 /* Methodology */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref><ref name="Nilsson2010From"/> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 328 2011-02-11T16:08:23Z Anthony 1 /* Methodology */ = Architectural Analysis for NETMAR = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 329 2011-02-11T16:10:05Z Anthony 1 /* Architectural Analysis for NETMAR */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 362 2011-02-17T14:29:03Z Anthony 1 /* Methodology */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|800px]] == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 364 2011-02-17T14:42:30Z Anthony 1 /* Methodology */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|center|800px]] == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 406 2011-02-21T10:54:49Z Anthony 1 /* Methodology */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|center|800px]] === Description === The descriptive efforts will focus largely on the use of RM-ODP, and particularly UML4ODP, to model NETMAR as a system of interconnected Spatial Data Infrasructures. The description will build on previous work<ref>R. Béjar, P. R. Muro-Medrano, and J. Nogueras-Iso, "Contributions to the modelling of spatial data infrastructures and their portrayal services," 2009.</ref> modelling SDIs using a hybrid of the Shared Data and Client Server architectural styles. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 407 2011-02-21T10:57:36Z Anthony 1 /* Description */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|center|800px]] === Description === The descriptive efforts will focus largely on the use of RM-ODP, and particularly UML4ODP, to model NETMAR as a system of interconnected Spatial Data Infrasructures. The description will build on previous work<ref>R. Béjar, P. R. Muro-Medrano, and J. Nogueras-Iso, "Contributions to the modelling of spatial data infrastructures and their portrayal services," 2009. [Online]. Available: http://webdiis.unizar.es/~rbejar/thesis_rbejar.pdf</ref> modelling SDIs using a hybrid of the Shared Data and Client Server architectural styles. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 408 2011-02-21T10:59:27Z Anthony 1 /* Description */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|center|800px]] === Description === The descriptive efforts will focus largely on the use of RM-ODP, and particularly UML4ODP, to model NETMAR as a system of interconnected Spatial Data Infrastructures. The description will build on previous work<ref>R. Béjar, P. R. Muro-Medrano, and J. Nogueras-Iso, "Contributions to the modelling of spatial data infrastructures and their portrayal services," 2009. [Online]. Available: http://webdiis.unizar.es/~rbejar/thesis_rbejar.pdf</ref> modelling SDIs using a hybrid of the Shared Data and Client Server architectural styles. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 417 2011-02-22T14:57:43Z Anthony 1 /* Description */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|center|800px]] === Description === The descriptive efforts will focus largely on the use of RM-ODP, and particularly UML4ODP, to model NETMAR as a system of interconnected Spatial Data Infrastructures. The description will build on previous work<ref>R. Béjar, P. R. Muro-Medrano, and J. Nogueras-Iso, "Contributions to the modelling of spatial data infrastructures and their portrayal services," 2009. [Online]. Available: http://webdiis.unizar.es/~rbejar/thesis_rbejar.pdf</ref> modelling SDIs using a hybrid of the Shared Data and Client Server architectural styles. === Planning === '''Iteration 1: (Complete)''' The initial effort consisted of the use of RM-ODP, and particularly UML4ODP, to model an end-to-end snapshot of the state of NETMAR during year 1 of the project. This was not intended to be exhaustive but to illustrate the use of architectural views to explain salient points of the system architecture to an internal and external audience. The end of this iteration was marked by the completion of the 'Draft System Architecture' deliverable. '''Iteration 2: (In Progress)''' We are currently performing analysis of the system architecture requirements in order to form a basis for architectural decision-making, using the ATAM method. The end of this iteration will be marked by the delivery of an initial architectural governance report to the governance board. '''Iteration 3: (Planned)''' A deeper analysis of relevant Foundation Architectures, Common System Architectures<ref>"The open group architecture framework (TOGAF), version 9 enterprise edition," The Open Group, Tech. Rep., Feb. 2009. [Online]. Available: http://www.opengroup.org/togaf</ref>, and their corresponding reference architectures<ref>B. Ellinger, N. Grumman, L. Fehskens, C. Harding, E. Harrington, F. McCabe, and B. Miner, "Navigating the SOA Open Standards Landscape Around Architecture." [Online]. Available: http://www.adobe.com/content/dam/Adobe/en/devnet/livecycle/pdfs/soa_standards.pdf</ref> will be made in order to ensure that NETMAR is using the available SOA guidance as effectively as possible. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 418 2011-02-22T15:20:08Z Anthony 1 /* Planning */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|center|800px]] === Description === The descriptive efforts will focus largely on the use of RM-ODP, and particularly UML4ODP, to model NETMAR as a system of interconnected Spatial Data Infrastructures. The description will build on previous work<ref>R. Béjar, P. R. Muro-Medrano, and J. Nogueras-Iso, "Contributions to the modelling of spatial data infrastructures and their portrayal services," 2009. [Online]. Available: http://webdiis.unizar.es/~rbejar/thesis_rbejar.pdf</ref> modelling SDIs using a hybrid of the Shared Data and Client Server architectural styles. === Planning === '''Iteration 1: (Complete)''' A survey was conducted of the state-of-the-art in the marine spatial domain culminating in the deliverable 'Review of projects, Initiatives and Technologies'. '''Iteration 2: (Complete)''' The initial effort consisted of the use of RM-ODP, and particularly UML4ODP, to model an end-to-end snapshot of the state of NETMAR during year 1 of the project. This was not intended to be exhaustive but to illustrate the use of architectural views to explain salient points of the system architecture to an internal and external audience. The end of this iteration was marked by the completion of the 'Draft System Architecture' deliverable. '''Iteration 3: (In Progress)''' We are currently performing analysis of the system architecture requirements in order to form a basis for architectural decision-making, using the ATAM method. We will be evaluating the ATAM's suitability as part of the architectural governance process, by using it to synthesise opinions and architectural needs from the NETMAR partners. The end of this iteration will be marked by the delivery of an initial architectural governance report to the governance board. '''Iteration 4: (Planned)''' A deeper analysis of relevant Foundation Architectures, Common System Architectures<ref>"The open group architecture framework (TOGAF), version 9 enterprise edition," The Open Group, Tech. Rep., Feb. 2009. [Online]. Available: http://www.opengroup.org/togaf</ref>, and their corresponding reference architectures<ref>B. Ellinger, N. Grumman, L. Fehskens, C. Harding, E. Harrington, F. McCabe, and B. Miner, "Navigating the SOA Open Standards Landscape Around Architecture." [Online]. Available: http://www.adobe.com/content/dam/Adobe/en/devnet/livecycle/pdfs/soa_standards.pdf</ref> will be made in order to ensure that NETMAR is using the available SOA guidance as effectively as possible. '''Iteration 5:''' (Planned)''' An Organization Specific architecture will be completed describing in detail the NETMAR system architecture. Deliverable - 'NETMAR System Architecture - Final version' '''Iteration 6: (Planned)''' An Industry architecture will be completed for environmental information systems. Deliverable 'Authoritative specification of NETMAR system architecture - first version'. '''Iteration 7+: (TBD)''' Deliverable 'Authoritative specification of NETMAR system architecture - Final version'. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 419 2011-02-22T15:21:22Z Anthony 1 /* Planning */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|center|800px]] === Description === The descriptive efforts will focus largely on the use of RM-ODP, and particularly UML4ODP, to model NETMAR as a system of interconnected Spatial Data Infrastructures. The description will build on previous work<ref>R. Béjar, P. R. Muro-Medrano, and J. Nogueras-Iso, "Contributions to the modelling of spatial data infrastructures and their portrayal services," 2009. [Online]. Available: http://webdiis.unizar.es/~rbejar/thesis_rbejar.pdf</ref> modelling SDIs using a hybrid of the Shared Data and Client Server architectural styles. === Planning === '''Iteration 1: (Complete)''' A survey was conducted of the state-of-the-art in the marine spatial domain culminating in the deliverable 'Review of projects, Initiatives and Technologies'. '''Iteration 2: (Complete)''' The initial effort consisted of the use of RM-ODP, and particularly UML4ODP, to model an end-to-end snapshot of the state of NETMAR during year 1 of the project. This was not intended to be exhaustive but to illustrate the use of architectural views to explain salient points of the system architecture to an internal and external audience. The end of this iteration was marked by the completion of the 'Draft System Architecture' deliverable. '''Iteration 3: (In Progress)''' We are currently performing analysis of the system architecture requirements in order to form a basis for architectural decision-making, using the ATAM method. We will be evaluating the ATAM's suitability as part of the architectural governance process, by using it to synthesise opinions and architectural needs from the NETMAR partners. The end of this iteration will be marked by the delivery of an initial architectural governance report to the governance board. '''Iteration 4: (Planned)''' A deeper analysis of relevant Foundation Architectures, Common System Architectures<ref>"The open group architecture framework (TOGAF), version 9 enterprise edition," The Open Group, Tech. Rep., Feb. 2009. [Online]. Available: http://www.opengroup.org/togaf</ref>, and their corresponding reference architectures<ref>B. Ellinger, N. Grumman, L. Fehskens, C. Harding, E. Harrington, F. McCabe, and B. Miner, "Navigating the SOA Open Standards Landscape Around Architecture." [Online]. Available: http://www.adobe.com/content/dam/Adobe/en/devnet/livecycle/pdfs/soa_standards.pdf</ref> will be made in order to ensure that NETMAR is using the available SOA guidance as effectively as possible. '''Iteration 5: (Planned)''' An Organization Specific architecture will be completed describing in detail the NETMAR system architecture. Deliverable - 'NETMAR System Architecture - Final version' '''Iteration 6: (Planned)''' An Industry architecture will be completed for environmental information systems. Deliverable 'Authoritative specification of NETMAR system architecture - first version'. '''Iteration 7+: (TBD)''' Deliverable 'Authoritative specification of NETMAR system architecture - Final version'. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 420 2011-02-22T16:42:39Z Anthony 1 /* Planning */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|center|800px]] === Description === The descriptive efforts will focus largely on the use of RM-ODP, and particularly UML4ODP, to model NETMAR as a system of interconnected Spatial Data Infrastructures. The description will build on previous work<ref>R. Béjar, P. R. Muro-Medrano, and J. Nogueras-Iso, "Contributions to the modelling of spatial data infrastructures and their portrayal services," 2009. [Online]. Available: http://webdiis.unizar.es/~rbejar/thesis_rbejar.pdf</ref> modelling SDIs using a hybrid of the Shared Data and Client Server architectural styles. === Planning === '''Iteration 1, Maury: (Complete)''' A survey was conducted of the state-of-the-art in the marine spatial domain culminating in the deliverable 'Review of projects, Initiatives and Technologies'. '''Iteration 2, Edoras: (Complete)''' The initial effort consisted of the use of RM-ODP, and particularly UML4ODP, to model an end-to-end snapshot of the state of NETMAR during year 1 of the project. This was not intended to be exhaustive but to illustrate the use of architectural views to explain salient points of the system architecture to an internal and external audience. The end of this iteration was marked by the completion of the 'Draft System Architecture' deliverable. '''Iteration 3, Feni: (In Progress)''' We are currently performing analysis of the system architecture requirements in order to form a basis for architectural decision-making, using the ATAM method. We will be evaluating the ATAM's suitability as part of the architectural governance process, by using it to synthesise opinions and architectural needs from the NETMAR partners. The end of this iteration will be marked by the delivery of an initial architectural governance report to the governance board. '''Iteration 4, Goban: (Planned)''' A deeper analysis of relevant Foundation Architectures, Common System Architectures<ref>"The open group architecture framework (TOGAF), version 9 enterprise edition," The Open Group, Tech. Rep., Feb. 2009. [Online]. Available: http://www.opengroup.org/togaf</ref>, and their corresponding reference architectures<ref>B. Ellinger, N. Grumman, L. Fehskens, C. Harding, E. Harrington, F. McCabe, and B. Miner, "Navigating the SOA Open Standards Landscape Around Architecture." [Online]. Available: http://www.adobe.com/content/dam/Adobe/en/devnet/livecycle/pdfs/soa_standards.pdf</ref> will be made in order to ensure that NETMAR is using the available SOA guidance as effectively as possible. '''Iteration 5, Porcupine: (Planned)''' An Organization Specific architecture will be completed describing in detail the NETMAR system architecture. Deliverable - 'NETMAR System Architecture - Final version' '''Iteration 6, Rockall: (Planned)''' An Industry architecture will be completed for environmental information systems. Deliverable 'Authoritative specification of NETMAR system architecture - first version'. '''Iteration 7+: (TBD)''' Deliverable 'Authoritative specification of NETMAR system architecture - Final version'. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- }} = Project Information = [[Project Page]] ==Notes== <references/> 428 2011-03-14T16:32:53Z Anthony 1 /* Patterns used */ = NETMAR System Architecture = == Introduction == Welcome to the NETMAR architecture wiki. This wiki contains information on the methodology, description, and analysis of the NETMAR system architecture. === Methodology === NETMAR architecture development will follow the Constructive Research <ref>G. Crnkovic, "Constructive Research and Info-Computational Knowledge Generation," Model-Based Reasoning in Science and Technology, pp. 359-380, 2010. [Online]. Available: http://www.springerlink.com/index/4665535318660J02.pdf</ref> methodology. # The practical relevance of the research comes from the real-world [http://netmar.nersc.no/?q=node/36 use-cases] supplied by the NETMAR partners, and from the quality attributes prioritised by the partners describing how they want the system to be built. # Several theoretical areas are relevant to the research, including architectural description languages and views, tradeoff analysis, design patterns and pattern languages, and metadata harmonization and interoperability design. # We will construct an RM-ODP<ref>ITU-T X.903 | ISO/IEC 10746-3 Information Technology – Open Distributed Processing – Reference Model – Architecture</ref> model of the proposed solution to the problems. We will conduct ATAM analysis which will be captured in this wiki in order to couple the design to the prioritised quality attributes. # The practicality of the solution will be demonstrated by the construction of the NETMAR demonstration system. This will consist of existing software adapted to meet the NETMAR objectives and new software, in particular a [http://nport.nersc.no:8080/ portal] which can be shown to a variety of end-users. It will not be feasible to demonstrate every aspect of the solution in this way. Where there are gaps we will attempt to suggest practical future roadmaps for implementing the solution. # A description of the architecture will be submitted to an appropriate standards body at the end of the project in order to advance the theoretical understanding of the problem area. The analysis tools and the knowledge base resulting from the analysis process will be made available in the public domain. Steps 3 & 4 will be performed iteratively in order to grow the theoretical model as we learn from practice. [[File:NetmarCommunity.png|center|800px]] === Description === The descriptive efforts will focus largely on the use of RM-ODP, and particularly UML4ODP, to model NETMAR as a system of interconnected Spatial Data Infrastructures. The description will build on previous work<ref>R. Béjar, P. R. Muro-Medrano, and J. Nogueras-Iso, "Contributions to the modelling of spatial data infrastructures and their portrayal services," 2009. [Online]. Available: http://webdiis.unizar.es/~rbejar/thesis_rbejar.pdf</ref> modelling SDIs using a hybrid of the Shared Data and Client Server architectural styles. === Planning === '''Iteration 1, Maury: (Complete)''' A survey was conducted of the state-of-the-art in the marine spatial domain culminating in the deliverable 'Review of projects, Initiatives and Technologies'. '''Iteration 2, Edoras: (Complete)''' The initial effort consisted of the use of RM-ODP, and particularly UML4ODP, to model an end-to-end snapshot of the state of NETMAR during year 1 of the project. This was not intended to be exhaustive but to illustrate the use of architectural views to explain salient points of the system architecture to an internal and external audience. The end of this iteration was marked by the completion of the 'Draft System Architecture' deliverable. '''Iteration 3, Feni: (In Progress)''' We are currently performing analysis of the system architecture requirements in order to form a basis for architectural decision-making, using the ATAM method. We will be evaluating the ATAM's suitability as part of the architectural governance process, by using it to synthesise opinions and architectural needs from the NETMAR partners. The end of this iteration will be marked by the delivery of an initial architectural governance report to the governance board. '''Iteration 4, Goban: (Planned)''' A deeper analysis of relevant Foundation Architectures, Common System Architectures<ref>"The open group architecture framework (TOGAF), version 9 enterprise edition," The Open Group, Tech. Rep., Feb. 2009. [Online]. Available: http://www.opengroup.org/togaf</ref>, and their corresponding reference architectures<ref>B. Ellinger, N. Grumman, L. Fehskens, C. Harding, E. Harrington, F. McCabe, and B. Miner, "Navigating the SOA Open Standards Landscape Around Architecture." [Online]. Available: http://www.adobe.com/content/dam/Adobe/en/devnet/livecycle/pdfs/soa_standards.pdf</ref> will be made in order to ensure that NETMAR is using the available SOA guidance as effectively as possible. '''Iteration 5, Porcupine: (Planned)''' An Organization Specific architecture will be completed describing in detail the NETMAR system architecture. Deliverable - 'NETMAR System Architecture - Final version' '''Iteration 6, Rockall: (Planned)''' An Industry architecture will be completed for environmental information systems. Deliverable 'Authoritative specification of NETMAR system architecture - first version'. '''Iteration 7+: (TBD)''' Deliverable 'Authoritative specification of NETMAR system architecture - Final version'. == Analysis == {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button}} This section contains summary information relating to the [http://www.sei.cmu.edu/architecture/tools/atam/ ATAM] method being used in NETMAR These are some of the Architectural Approach Descriptions entered so far. Click in the 'Edit...' column to see more details and to modify an existing description. To add a new description based on a new scenario, click on the button above. Unfortunately, this page won't update immediately you come back to it, so you'll have to click on the 'Edit' tab and save the page to see your new scenario. The descriptions are also broken down by themes so that you can view related descriptions together. The themes entered so far are: {{#arraydefine: themes|{{#ask: [[Theme::+]]|?Theme|mainlabel=-|headers=hide|format=list}} }}{{#arrayunique:themes}}{{#arrayprint:themes}}. {{#ask: [[Category:Analysis]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |limit=5 |order=desc }} {{#ask: [[Category:Analysis]] |mainlabel=- |?Scenario |?Attribute=Quality Attribute |?Stimulus |?Response |?Reasoning |?Diagram |format=rss |searchlabel=RSS Feed of descriptions }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[Decision::+]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[Risk::+]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[Non-risk::+]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[Sensitivity::+]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[Tradeoff::+]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} = Project Information = [[Project Page]] ==Notes== <references/> 2 63 2010-11-01T10:50:16Z WikiSysop Created page with '<includeonly> {{#set_internal:Relates to Software |Decision={{{Decision|}}} |Risk={{{Risk|}}} |Sensitivity={{{Sensitivity|}}} |Tradeoff={{{Tradeoff|}}} }} </includeonly>' <includeonly> {{#set_internal:Relates to Software |Decision={{{Decision|}}} |Risk={{{Risk|}}} |Sensitivity={{{Sensitivity|}}} |Tradeoff={{{Tradeoff|}}} }} </includeonly> 64 2010-11-01T12:41:16Z Anthony 1 <includeonly> {{#set_internal:From Scenario |Decision={{{Decision|}}} |Risk={{{Risk|}}} |Sensitivity={{{Sensitivity|}}} |Tradeoff={{{Tradeoff|}}} }} </includeonly> 65 2010-11-22T14:35:40Z Anthony 1 <includeonly> {{#set_internal:From Scenario |Decision={{{Decision|}}} |Risk={{{Risk|}}} |Non-risk={{{Non-risk|}}} |Sensitivity={{{Sensitivity|}}} |Tradeoff={{{Tradeoff|}}} }} </includeonly> 403 2011-02-18T17:00:11Z Anthony 1 <includeonly> {{#set_internal:From Scenario |Decision={{{Decision|}}} |Risk={{{Risk|}}} |Non-risk={{{Non-risk|}}} |Sensitivity={{{Sensitivity|}}} |Tradeoff={{{Tradeoff|}}} |Pattern={{{Pattern|}}} }} </includeonly> 3 66 2010-11-01T10:55:14Z WikiSysop Created page with '<includeonly> {| class="wikitable" ! Scenario | [[Scenario::{{{Scenario|}}}]] ! Attribute | [[Attribute::{{{Attribute|}}}]] ! Environment | [[Environment::{{{Environment|}}}]] ! …' <includeonly> {| class="wikitable" ! Scenario | [[Scenario::{{{Scenario|}}}]] ! Attribute | [[Attribute::{{{Attribute|}}}]] ! Environment | [[Environment::{{{Environment|}}}]] ! Stimulus | [[Stimulus::{{{Stimulus|}}}]] ! Response | [[Response::{{{Response|}}}]] |} 67 2010-11-01T11:02:01Z WikiSysop <includeonly> {| class="wikitable" ! Scenario | [[Scenario::{{{Scenario|}}}]] ! Attribute | [[Attribute::{{{Attribute|}}}]] ! Environment | [[Environment::{{{Environment|}}}]] ! Stimulus | [[Stimulus::{{{Stimulus|}}}]] ! Response | [[Response::{{{Response|}}}]] |} </includeonly> 68 2010-11-01T12:41:47Z Anthony 1 <includeonly> {| class="wikitable" ! Scenario | [[Scenario::{{{Scenario|}}}]] ! Attribute | [[Attribute::{{{Attribute|}}}]] ! Environment | [[Environment::{{{Environment|}}}]] ! Stimulus | [[Stimulus::{{{Stimulus|}}}]] ! Response | [[Response::{{{Response|}}}]] |} {{#ask: [[From Scenario::{{PAGENAME}}]] |mainlabel=- |?Decision |?Risk |?Sensitivity |?Tradeoff }} </includeonly> 69 2010-11-01T14:13:32Z WikiSysop <includeonly> {| class="wikitable" ! Scenario | [[Scenario::{{{Scenario|}}}]] ! Attribute | [[Attribute::{{{Attribute|}}}]] ! Environment | [[Environment::{{{Environment|}}}]] ! Stimulus | [[Stimulus::{{{Stimulus|}}}]] ! Response | [[Response::{{{Response|}}}]] |} {{#ask: [[From Scenario::{{PAGENAME}}]] |mainlabel=- |?Decision |?Risk |?Sensitivity |?Tradeoff }} [[Category:Analysis]] </includeonly> 70 2010-11-01T14:17:32Z WikiSysop <includeonly> '''Scenario:''' [[Scenario::{{{Scenario|}}}]] '''Attribute:'''[[Attribute::{{{Attribute|}}}]] '''Environment:''' [[Environment::{{{Environment|}}}]] '''Stimulus:''' [[Stimulus::{{{Stimulus|}}}]] '''Response:''' [[Response::{{{Response|}}}]] {{#ask: [[From Scenario::{{PAGENAME}}]] |mainlabel=- |?Decision |?Risk |?Sensitivity |?Tradeoff }} [[Category:Analysis]] </includeonly> 71 2010-11-01T14:18:39Z WikiSysop <includeonly> '''Scenario:''' [[Scenario::{{{Scenario|}}}]] '''Attribute:'''[[Attribute::{{{Attribute|}}}]] '''Environment:''' [[Environment::{{{Environment|}}}]] '''Stimulus:''' [[Stimulus::{{{Stimulus|}}}]] '''Response:''' [[Response::{{{Response|}}}]] {{#ask: [[From Scenario::{{PAGENAME}}]] |mainlabel=- |?Decision |?Risk |?Sensitivity |?Tradeoff }} [[Category:Analysis]] </includeonly> 72 2010-11-22T14:38:29Z Anthony 1 <includeonly> '''Scenario:''' [[Scenario::{{{Scenario|}}}]] '''Attribute:'''{{#arraymap:{{{Attribute|}}}|%%|[[Attribute::%%]]|}} '''Environment:''' [[Environment::{{{Environment|}}}]] '''Stimulus:''' [[Stimulus::{{{Stimulus|}}}]] '''Response:''' [[Response::{{{Response|}}}]] {{#ask: [[From Scenario::{{PAGENAME}}]] |mainlabel=- |?Decision |?Risk |?Sensitivity |?Tradeoff }} [[Category:Analysis]] </includeonly> 73 2010-11-22T14:46:01Z Anthony 1 <includeonly> '''Scenario:''' [[Scenario::{{{Scenario|}}}]] '''Attribute:'''{{#arraymap:{{{Attribute|}}}|,|%%|[[Attribute::%%]]|}} '''Environment:''' [[Environment::{{{Environment|}}}]] '''Stimulus:''' [[Stimulus::{{{Stimulus|}}}]] '''Response:''' [[Response::{{{Response|}}}]] {{#ask: [[From Scenario::{{PAGENAME}}]] |mainlabel=- |?Decision |?Risk |?Sensitivity |?Tradeoff }} [[Category:Analysis]] </includeonly> 74 2010-11-22T15:06:35Z Anthony 1 <includeonly> '''Scenario:''' [[Scenario::{{{Scenario|}}}]] '''Attribute:'''{{#arraymap:{{{Attribute|}}}|,|%%|[[Attribute::%%]]|,}} '''Environment:''' [[Environment::{{{Environment|}}}]] '''Stimulus:''' [[Stimulus::{{{Stimulus|}}}]] '''Response:''' [[Response::{{{Response|}}}]] {{#ask: [[From Scenario::{{PAGENAME}}]] |mainlabel=- |?Decision |?Risk |?Non-risk |?Sensitivity |?Tradeoff }} [[Category:Analysis]] </includeonly> 402 2011-02-18T16:59:34Z Anthony 1 <includeonly> '''Scenario:''' [[Scenario::{{{Scenario|}}}]] '''Attribute:'''{{#arraymap:{{{Attribute|}}}|,|%%|[[Attribute::%%]]|,}} '''Environment:''' [[Environment::{{{Environment|}}}]] '''Stimulus:''' [[Stimulus::{{{Stimulus|}}}]] '''Response:''' [[Response::{{{Response|}}}]] {{#ask: [[From Scenario::{{PAGENAME}}]] |mainlabel=- |?Decision |?Risk |?Non-risk |?Sensitivity |?Tradeoff |?Pattern }} [[Category:Analysis]] </includeonly> 4 75 2010-11-01T10:57:11Z WikiSysop Created page with '<includeonly> {| class="wikitable" ! Reasoning | [[Reasoning::{{{Reasoning|}}}]] ! Architectural Diagram | [[Diagram::{{{Diagram|}}}]] |} </includeonly>' <includeonly> {| class="wikitable" ! Reasoning | [[Reasoning::{{{Reasoning|}}}]] ! Architectural Diagram | [[Diagram::{{{Diagram|}}}]] |} </includeonly> 76 2010-11-01T15:32:29Z WikiSysop <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [[Diagram::{{{Diagram|}}}]] </includeonly> 77 2010-11-01T15:33:15Z WikiSysop <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [[Diagram::{{{Diagram|}}}]] </includeonly> 78 2010-11-22T14:28:30Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [{{{Diagram|}}}] </includeonly> 79 2010-11-22T14:46:47Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' {{{Diagram|}}} </includeonly> 80 2010-11-22T14:56:51Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [{{{Diagram|}}}] </includeonly> 81 2010-11-22T14:58:49Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' {{{Diagram|}}} </includeonly> 82 2010-11-22T15:03:34Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' {{{Diagram|}}} </includeonly> 230 2010-12-23T14:55:35Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [[File:{{{Diagram|}}}]] </includeonly> 284 2011-02-09T10:35:01Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [[File:{{{Diagram|}}}]] '''Themes:''' {{#arraymap: {{{Theme|}}}|,|%%|Theme::%%|}} </includeonly> 290 2011-02-09T11:09:28Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [[File:{{{Diagram|}}}]] '''Themes:''' {{#arraymap: {{{Theme|}}}|,|%%|[[Theme::%%]]|}} </includeonly> 356 2011-02-14T16:55:22Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [[File:{{{Diagram|}}}]] '''Themes:''' {{#arraymap: {{{Theme|}}}|,|%%|[[Theme::%%]]|}} {{#ask: [[Theme::{{PAGENAME}}]] |?Theme |format=graph }} </includeonly> 357 2011-02-14T16:56:47Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [[File:{{{Diagram|}}}]] '''Themes:''' {{#arraymap: {{{Theme|}}}|,|%%|[[Theme::%%]]|}} {{#ask: [[Theme::{{{Theme|}}}]] |?Theme |format=graph }} </includeonly> 358 2011-02-14T16:57:55Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [[File:{{{Diagram|}}}]] '''Themes:''' {{#arraymap: {{{Theme|}}}|,|%%|[[Theme::%%]]|}} '''Related Scenarios:''' {{#ask: [[Theme::{{{Theme|}}}]] |?Theme |?Scenario |format=graph }} </includeonly> 359 2011-02-14T16:59:43Z Anthony 1 <includeonly> '''Reasoning:''' [[Reasoning::{{{Reasoning|}}}]] '''Architectural Diagram:''' [[File:{{{Diagram|}}}]] '''Themes:''' {{#arraymap: {{{Theme|}}}|,|%%|[[Theme::%%]]|}} </includeonly> 5 83 2010-11-01T10:59:46Z WikiSysop Created page with '<noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit t…' <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} '''Decision:''' {{{field|Decision}}} '''Risk:''' {{{field|Risk}}} '''Sensitivity:''' {{{field|Sensitivity}}} '''Tradeoff:''' {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} '''Free text:''' {{{standard input|free text|rows=10}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 84 2010-11-01T12:53:11Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis}}} '''Decision:''' {{{field|Decision}}} '''Risk:''' {{{field|Risk}}} '''Sensitivity:''' {{{field|Sensitivity}}} '''Tradeoff:''' {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} '''Free text:''' {{{standard input|free text|rows=10}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 85 2010-11-01T12:55:33Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| class="formtable" |{{{field|Decision}}} |{{{field|Risk}}} |{{{field|Sensitivity}}} |{{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} '''Free text:''' {{{standard input|free text|rows=10}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 86 2010-11-01T12:56:17Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| class="formtable" |{{{field|Decision}}} |{{{field|Risk}}} |{{{field|Sensitivity}}} |{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} '''Free text:''' {{{standard input|free text|rows=10}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 87 2010-11-01T12:58:11Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|}}} {| class="formtable" |{{{field|Decision}}} |{{{field|Risk}}} |{{{field|Sensitivity}}} |{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} '''Free text:''' {{{standard input|free text|rows=10}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 88 2010-11-01T13:02:36Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|label=Analysis|multiple}}} {| class="formtable" |{{{field|Decision}}} |{{{field|Risk}}} |{{{field|Sensitivity}}} |{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} '''Free text:''' {{{standard input|free text|rows=10}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 89 2010-11-01T13:44:43Z 143.239.7.3 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|label=Analysis|multiple}}} {| class="formtable" |{{{field|Decision}}} |{{{field|Risk}}} |{{{field|Sensitivity}}} |{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 90 2010-11-01T13:52:57Z 143.239.7.3 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude><includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|label=Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 91 2010-11-01T13:54:04Z 143.239.7.3 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision|multiple}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|label=Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 92 2010-11-01T14:08:26Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision|}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 93 2010-11-01T14:20:20Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> <div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div> {{{for template|Decision|}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 94 2010-11-01T15:22:04Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 95 2010-11-01T15:30:08Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 96 2010-11-01T15:50:46Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 97 2010-11-01T15:57:08Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !Architectural decision !Risk !Sensitivity !Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 98 2010-11-01T15:59:53Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !Architectural decision|size=35 !Risk|size=35 !Sensitivity|size=35 !Tradeoff|size=35 |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 99 2010-11-01T16:01:52Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !size=35|Architectural decision !size=35|Risk !size=35|Sensitivity !size=35|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 100 2010-11-01T16:04:57Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width=350|Architectural decision !width=350|Risk !width=350|Sensitivity !width=350|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 101 2010-11-01T16:05:56Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width=35|Architectural decision !width=35|Risk !width=35|Sensitivity !width=35|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 102 2010-11-01T16:08:01Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width="35em"|Architectural decision !width="35em"|Risk !width="35em"|Sensitivity !width="35em"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 103 2010-11-01T16:13:20Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width="150"|Architectural decision !width="150"|Risk !width="150"|Sensitivity !width="150"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 104 2010-11-01T16:14:09Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width="200"|Architectural decision !width="200"|Risk !width="200"|Sensitivity !width="200"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 105 2010-11-01T16:15:22Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width="225"|align="left"|Architectural decision !width="225"|align="left"|Risk !width="225"|align="left"|Sensitivity !width="225"|align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 106 2010-11-01T16:17:28Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width="225" align="left"|Architectural decision !width="225" align="left"|Risk !width="225" align="left"|Sensitivity !width="225" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 107 2010-11-01T16:18:18Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width="250" align="left"|Architectural decision !width="250" align="left"|Risk !width="250" align="left"|Sensitivity !width="250" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 108 2010-11-01T16:19:29Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 109 2010-11-01T16:21:27Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=500}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 110 2010-11-01T16:21:59Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=200}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment}}} |- ! Stimulus: | {{{field|Stimulus}}} |- ! Response: | {{{field|Response}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 111 2010-11-01T16:22:52Z WikiSysop <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100}}} |- ! Attribute: | {{{field|Attribute}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 112 2010-11-02T12:24:37Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision|autocomplete on property=Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 113 2010-11-02T12:27:21Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|input type=combobox}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {{{field|Decision|autocomplete on property=Decision}}} {{{field|Risk}}} {{{field|Sensitivity}}} {{{field|Tradeoff}}} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 114 2010-11-03T09:53:48Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|input type=combobox}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {| |width="240"|{{{field|Decision|autocomplete on property=Decision}}} |width="240"|{{{field|Risk}}} |width="240"|{{{field|Sensitivity}}} |width="240"|{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 115 2010-11-22T14:12:06Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|input type=combobox|multiple}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {| |width="240"|{{{field|Decision|autocomplete on property=Decision}}} |width="240"|{{{field|Risk}}} |width="240"|{{{field|Sensitivity}}} |width="240"|{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 116 2010-11-22T14:13:38Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|input type=combobox|multiple}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {| |width="240"|{{{field|Decision|autocomplete on property=Decision}}} |width="240"|{{{field|Risk}}} |width="240"|{{{field|Non-risk}}} |width="240"|{{{field|Sensitivity}}} |width="240"|{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 117 2010-11-22T14:31:42Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|multiple}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {| |width="240"|{{{field|Decision|autocomplete on property=Decision}}} |width="240"|{{{field|Risk}}} |width="240"|{{{field|Non-risk}}} |width="240"|{{{field|Sensitivity}}} |width="240"|{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 118 2010-11-25T14:08:16Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|multiple}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="240" align="left"|Architectural decision !width="240" align="left"|Risk !width="240" align="left"|Non-risk !width="240" align="left"|Sensitivity !width="240" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {| |width="240"|{{{field|Decision|autocomplete on property=Decision}}} |width="240"|{{{field|Risk}}} |width="240"|{{{field|Non-risk}}} |width="240"|{{{field|Sensitivity}}} |width="240"|{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 119 2010-11-25T14:10:03Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|multiple}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="200" align="left"|Architectural decision !width="200" align="left"|Risk !width="200" align="left"|Non-risk !width="200" align="left"|Sensitivity !width="200" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {| |width="200"|{{{field|Decision|autocomplete on property=Decision}}} |width="200"|{{{field|Risk}}} |width="200"|{{{field|Non-risk}}} |width="200"|{{{field|Sensitivity}}} |width="200"|{{{field|Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 120 2010-11-25T14:13:24Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|multiple}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {| !width="200" align="left"|Architectural decision !width="200" align="left"|Risk !width="200" align="left"|Non-risk !width="200" align="left"|Sensitivity !width="200" align="left"|Tradeoff |} {{{for template|Analysis|multiple}}} {| !width="200" align="left"|Architectural decision !width="200" align="left"|Risk !width="200" align="left"|Non-risk !width="200" align="left"|Sensitivity !width="200" align="left"|Tradeoff |- |width="200"|{{{field|Decision|autocomplete on property=Decision}}} |width="200"|{{{field|Risk|autocomplete on property=Risk}}} |width="200"|{{{field|Non-risk|autocomplete on property=Non-risk}}} |width="200"|{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |width="200"|{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 121 2010-11-25T14:15:02Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|multiple}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 122 2010-12-15T14:42:41Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|multiple}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff|multiple}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 123 2010-12-15T14:52:55Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff|multiple}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 124 2010-12-15T14:55:32Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 125 2010-12-15T15:38:05Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 126 2010-12-15T15:44:49Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 225 2010-12-23T14:22:32Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 285 2011-02-09T10:36:46Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |- Themes ! {{{field|Theme|multiple|}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 286 2011-02-09T11:03:45Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |- Themes ! {{{field|Theme|multiple|}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 287 2011-02-09T11:07:41Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |- !Themes ! {{{field|Theme|multiple|}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 288 2011-02-09T11:07:59Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |- !Themes | {{{field|Theme|multiple|}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 401 2011-02-18T16:58:50Z Anthony 1 <noinclude> This is the "Analysis" form. To create a page with this form, enter the page name below; if a page with that name already exists, you will be sent to a form to edit that page. {{#forminput:form=Analysis}} </noinclude> <includeonly> {{{for template|Decision|}}} {{{info|page name=Approach Description <unique number;start=1>}}} {| class="formtable" ! Scenario: | {{{field|Scenario|mandatory|size=100|autocomplete on property=Scenario}}} |- ! Attribute: | {{{field|Attribute|autocomplete on property=Attribute|list}}} |- ! Environment: | {{{field|Environment|size=100}}} |- ! Stimulus: | {{{field|Stimulus|size=100}}} |- ! Response: | {{{field|Response|size=100}}} |} {{{end template}}} {{{for template|Analysis|multiple}}} {| !align="left"|Architectural decision !align="left"|Risk !align="left"|Non-risk !align="left"|Sensitivity !align="left"|Tradeoff !align="left"|Pattern |- |{{{field|Decision|autocomplete on property=Decision}}} |{{{field|Risk|autocomplete on property=Risk}}} |{{{field|Non-risk|autocomplete on property=Non-risk}}} |{{{field|Sensitivity|autocomplete on property=Sensitivity}}} |{{{field|Tradeoff|autocomplete on property=Tradeoff}}} |{{{field|Pattern}}} |} {{{end template}}} {{{for template|Reasoning}}} {| class="formtable" ! Reasoning: | {{{field|Reasoning}}} |- ! Diagram: | {{{field|Diagram|uploadable}}} |- !Themes | {{{field|Theme|multiple|}}} |} {{{end template}}} {{{standard input|summary}}} {{{standard input|minor edit}}} {{{standard input|watch}}} {{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}} </includeonly> 6 127 2010-11-01T14:14:31Z WikiSysop Created page with "[[Has default form::Analysis]]" [[Has default form::Analysis]] 252 2011-01-26T16:25:08Z Anthony 1 [[Has default form::Analysis]] [[imported from::atam:ApproachDescription]] 7 128 2010-11-01T15:35:49Z WikiSysop Created page with "[[has type::Type:text]]" [[has type::Type:text]] 129 2010-11-01T15:36:25Z WikiSysop [[has type::Type:Text]] 130 2010-11-01T15:37:30Z WikiSysop [[Has type::Type:Text]] 131 2010-11-01T15:39:09Z WikiSysop [[Has type::Text]] 132 2010-11-01T15:40:00Z WikiSysop [[Has type::text]] 8 133 2010-11-01T16:57:06Z Anthony 1 Created page with "{{Decision |Scenario=Service provider adds a new service |Attribute=Modifiability |Environment=NETMAR is operational. Service provider is authorised to add service. |Stimulus=Re..." {{Decision |Scenario=Service provider adds a new service |Attribute=Modifiability |Environment=NETMAR is operational. Service provider is authorised to add service. |Stimulus=Registration of service with NETMAR |Response=Service discoverable and usable by end users }} {{Analysis |Decision=Common Service Registry }} {{Analysis |Decision=Common metadata standards }} {{Reasoning}} 134 2010-11-01T17:00:13Z Anthony 1 {{Decision |Scenario=Service provider adds a new service |Attribute=Modifiability |Environment=NETMAR is operational. Service provider is authorised to add service. |Stimulus=Registration of service with NETMAR |Response=Service discoverable and usable by end users }} {{Analysis |Decision=Common Service Registry }} {{Analysis |Decision=Common metadata standards }} {{Reasoning}} 135 2010-11-02T12:19:22Z Anthony 1 {{Decision |Scenario=Service provider adds a new service |Attribute=Service Reachability |Environment=NETMAR is operational. Service provider is authorised to add service. |Stimulus=Registration of service with NETMAR |Response=Service discoverable and usable by end users }} {{Analysis |Decision=Common Service Registry }} {{Analysis |Decision=Common metadata standards }} {{Reasoning}} 136 2010-11-03T10:09:10Z Anthony 1 {{Decision |Scenario=Service provider adds a new service |Attribute=Service Reachability |Environment=NETMAR is operational. Service provider is authorised to add service. |Stimulus=Registration of service with NETMAR |Response=Service discoverable and usable by end users }} {{Analysis |Decision=Common service registry |Sensitivity=Service description quality }} {{Analysis |Decision=Common metadata standards |Sensitivity=Level of expressiveness }} {{Reasoning |Reasoning=* Common service registry for Netmar ensures the provider knows where to publish the service description so the consumer can find it }} 137 2010-11-03T10:13:14Z Anthony 1 {{Decision |Scenario=Service provider adds a new service |Attribute=Service Reachability |Environment=NETMAR is operational. Service provider is authorised to add service. |Stimulus=Registration of service with NETMAR |Response=Service discoverable and usable by end users }} {{Analysis |Decision=Common service registry |Sensitivity=Service description quality }} {{Analysis |Decision=Common metadata standards |Sensitivity=Level of expressiveness }} {{Analysis |Decision=Service level agreements |Sensitivity=Level of trust }} {{Reasoning |Reasoning= * Common service registry for Netmar ensures the provider knows where to publish the service description so the consumer can find it * Common metadata standards ensure that service descriptions are machine readable * SLAs offer guarantees that the service is fit for the consumer's purpose }} 138 2010-11-03T10:14:06Z Anthony 1 {{Decision |Scenario=Service provider adds a new service |Attribute=Service Reachability |Environment=NETMAR is operational. Service provider is authorised to add service. |Stimulus=Registration of service with NETMAR |Response=Service discoverable and usable by end users }} {{Analysis |Decision=Common service registry |Sensitivity=Service description quality }} {{Analysis |Decision=Common metadata standards |Sensitivity=Level of expressiveness }} {{Analysis |Decision=Service level agreements |Sensitivity=Level of trust }} {{Reasoning |Reasoning=- * Common service registry for Netmar ensures the provider knows where to publish the service description so the consumer can find it * Common metadata standards ensure that service descriptions are machine readable * SLAs offer guarantees that the service is fit for the consumer's purpose }} 139 2010-11-25T13:39:10Z Anthony 1 {{Decision |Scenario=Service provider adds a new service |Attribute=Service Discoverability |Environment=NETMAR is operational. Service provider is authorised to add service. |Stimulus=Registration of service with NETMAR |Response=Service discoverable and usable by end users }} {{Analysis |Decision=Common service registry |Sensitivity=Service description quality }} {{Analysis |Decision=Common metadata standards |Sensitivity=Level of expressiveness }} {{Analysis |Decision=Service level agreements |Sensitivity=Level of trust }} {{Reasoning |Reasoning=- * Common service registry for Netmar ensures the provider knows where to publish the service description so the consumer can find it * Common metadata standards ensure that service descriptions are machine readable * SLAs offer guarantees that the service is fit for the consumer's purpose }} 257 2011-01-26T17:22:07Z Anthony 1 {{Decision |Scenario=Service provider adds a new service |Attribute=Service Discoverability |Environment=NETMAR is operational. Service provider is authorised to add service. |Stimulus=Registration of service with NETMAR |Response=Service discoverable and usable by end users }} {{Analysis |Decision=Common service registry |Sensitivity=Service description quality }} {{Analysis |Decision=Common metadata standards |Sensitivity=Level of expressiveness }} {{Analysis |Decision=Service level agreements |Sensitivity=Level of trust }} {{Analysis |Decision=Metadata backward compatibility }} {{Reasoning |Reasoning=- * Common service registry for Netmar ensures the provider knows where to publish the service description so the consumer can find it * Common metadata standards ensure that service descriptions are machine readable * SLAs offer guarantees that the service is fit for the consumer's purpose }} 9 140 2010-11-01T17:05:20Z Anthony 1 Created page with "[[Has type::string]]" [[Has type::string]] 10 141 2010-11-01T17:05:41Z Anthony 1 Created page with "[[Has type::string]]" [[Has type::string]] 11 142 2010-11-01T17:05:52Z Anthony 1 Created page with "[[Has type::string]]" [[Has type::string]] 254 2011-01-26T16:39:20Z Anthony 1 [[Has type::string]] [[imported from::atam:scenario]] 12 143 2010-11-01T17:06:04Z Anthony 1 Created page with "[[Has type::string]]" [[Has type::string]] 13 144 2010-11-01T17:07:32Z Anthony 1 Created page with "[[Category:Utility]]" [[Category:Utility]] 14 145 2010-11-03T09:29:48Z Anthony 1 Created page with "Service Reachability is defined in [[Defined in::OASIS SOA-RM]] as the ability of a service consumer and provider to interact. Reachability is an aspect of [[Broader::Service Vis..." Service Reachability is defined in [[Defined in::OASIS SOA-RM]] as the ability of a service consumer and provider to interact. Reachability is an aspect of [[Broader::Service Visibility]]. 146 2010-11-03T09:30:15Z Anthony 1 '''Service Reachability''' is defined in [[Defined in::OASIS SOA-RM]] as the ability of a service consumer and provider to interact. Reachability is an aspect of [[Broader::Service Visibility]]. 15 147 2010-11-03T09:34:22Z Anthony 1 Created page with "'''Service visibility''' is defined in [[Defined in::OASIS SOA-RM]] as the capacity of those with needs and those with capabilities to be able to interact with each other. Visibi..." '''Service visibility''' is defined in [[Defined in::OASIS SOA-RM]] as the capacity of those with needs and those with capabilities to be able to interact with each other. Visibility is one of our first-level measures of [[Broader::Utility]]. 16 148 2010-11-03T10:17:39Z Anthony 1 Created page with "[[URL::http://www.google.ie/url?sa=t&source=web&cd=2&ved=0CB0QFjAB&url=http%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F19679%2Fsoa-rm-cs.pdf&ei=lTbRTMaeF4Tv4gaz5KWH..." [[URL::http://www.google.ie/url?sa=t&source=web&cd=2&ved=0CB0QFjAB&url=http%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F19679%2Fsoa-rm-cs.pdf&ei=lTbRTMaeF4Tv4gaz5KWHDQ&usg=AFQjCNHANxUN9auHo3ElI1ir2yOHIaS1dg&sig2=d5wLX6Ak0UGZRsWqfikadg]] 149 2010-11-03T10:30:24Z Anthony 1 [[URL::http://www.google.ie/url?sa=t&source=web&cd=2&ved=0CB0QFjAB&url=http%3A%2F%2Fwww.oasis-open.org%2Fcommittees%2Fdownload.php%2F19679%2Fsoa-rm-cs.pdf&ei=lTbRTMaeF4Tv4gaz5KWHDQ&usg=AFQjCNHANxUN9auHo3ElI1ir2yOHIaS1dg&sig2=d5wLX6Ak0UGZRsWqfikadg|link]] to OASIS SOA Reference model. 17 150 2010-11-03T10:18:56Z Anthony 1 Created page with "[[Has type::URL]]" [[Has type::URL]] 18 151 2010-11-03T16:05:33Z 143.239.7.1 Created page with "A sensitivity point, as defined in the [[Defined in::ATAM]], is a property of one or more components (and/or component relationships) that is critical for achieving a particular ..." A sensitivity point, as defined in the [[Defined in::ATAM]], is a property of one or more components (and/or component relationships) that is critical for achieving a particular quality attribute response. This property is of type [[Has type::string]] 152 2010-11-25T13:16:47Z Anthony 1 A sensitivity point, as defined in the [[Defined in::ATAM]], is a property of one or more components (and/or component relationships) that is critical for achieving a particular quality attribute response. This property is of type [[Has type::page]] 153 2010-11-25T13:18:24Z Anthony 1 A sensitivity point, as defined in the [[Defined in::ATAM]], is a property of one or more components (and/or component relationships) that is critical for achieving a particular quality attribute response. This property is of type [[Has type::string]] 233 2011-01-17T12:40:24Z Anthony 1 A sensitivity point, as defined in the [[Defined in::ATAM]], is a property of one or more components (and/or component relationships) that is critical for achieving a particular quality attribute response. This property is of type [[Has type::page]] 19 154 2010-11-03T16:09:31Z Anthony 1 Created page with "The [[http://www.sei.cmu.edu/reports/00tr004.pdf::|Architecture Tradeoff Analysis Method]] is a lighweight process defined by the Software Engineering Institute (SEI). <b>The pu..." The [[http://www.sei.cmu.edu/reports/00tr004.pdf::|Architecture Tradeoff Analysis Method]] is a lighweight process defined by the Software Engineering Institute (SEI). <b>The purpose of the ATAM is to assess the consequences of architectural decisions in light of quality attribute requirements.</b> 155 2010-11-25T13:21:00Z Anthony 1 The [http://www.sei.cmu.edu/reports/00tr004.pdf Architecture Tradeoff Analysis Method] is a lighweight process defined by the Software Engineering Institute (SEI). <b>The purpose of the ATAM is to assess the consequences of architectural decisions in light of quality attribute requirements.</b> 20 156 2010-11-03T16:13:36Z Anthony 1 Created page with "According to the [[Defined in::ATAM]], risks are potentially problematic architectural decisions." According to the [[Defined in::ATAM]], risks are potentially problematic architectural decisions. 21 157 2010-11-03T16:28:46Z Anthony 1 Created page with "A tradeoff point, as defined in the [[Defined in::ATAM]], is a property that affects more than one attribute and is a sensitivity point for more than one attribute. This propert..." A tradeoff point, as defined in the [[Defined in::ATAM]], is a property that affects more than one attribute and is a sensitivity point for more than one attribute. This property is of type [[Has type::string]] 158 2010-11-25T13:15:26Z Anthony 1 A tradeoff point, as defined in the [[Defined in::ATAM]], is a property that affects more than one attribute and is a sensitivity point for more than one attribute. This property is of type [[Has type::page]] 22 159 2010-11-04T12:44:49Z Anthony 1 Created page with "{{Decision |Scenario=Service provider offers a new capability |Attribute=Flexibility |Environment=Netmar is operational. Capability fits easily within OGC model |Stimulus=Provide..." {{Decision |Scenario=Service provider offers a new capability |Attribute=Flexibility |Environment=Netmar is operational. Capability fits easily within OGC model |Stimulus=Provider attempts to provide capability as service |Response=Service definition can be completed within one man-month }} {{Analysis |Decision=Common metadata standards |Sensitivity=Provider's knowledge of standards }} {{Analysis |Decision=Common service registry |Sensitivity=Governance process }} {{Reasoning |Reasoning=Common metadata standards can help with adding a service, provided the service fits easily into the existing metamodel and the service provider has knowledge of the standards. Having knowledge of the standards can be taken to mean having easy access to documentation describing the standards, and examples to follow. A common service registry can help with exposing an existing capability, but this is sensitive to qualities of the governance process for adding services, e.g. transparency. }} 23 160 2010-11-04T14:37:31Z Anthony 1 Created page with "{{Decision |Scenario=Service provider offers a new capability |Attribute=Flexibility |Environment=Netmar is operational. Capability does not fit within OGC model, but is well des..." {{Decision |Scenario=Service provider offers a new capability |Attribute=Flexibility |Environment=Netmar is operational. Capability does not fit within OGC model, but is well described and understood. |Stimulus=Provider attempts to provide capability as service |Response=Service can be added to registry within 3 man-months }} {{Analysis |Decision=Common metadata standards }} {{Reasoning}} 24 161 2010-11-22T14:07:27Z Anthony 1 Created page with "{{Decision |Scenario=ICAN Decision Maker |Attribute=Usability, Service Reusability }} {{Analysis |Decision=EUMIS as UI Mediator }} {{Reasoning}}" {{Decision |Scenario=ICAN Decision Maker |Attribute=Usability, Service Reusability }} {{Analysis |Decision=EUMIS as UI Mediator }} {{Reasoning}} 162 2010-11-22T14:13:44Z Anthony 1 {{Decision |Scenario=ICAN Decision Maker |Attribute=Usability, Service Reusability }} {{Analysis |Decision=EUMIS as UI Mediator }} {{Reasoning |Diagram=http://t.uig.im/wiki/lib/exe/fetch.php?hash=a9e1a8&media=http%3A%2F%2Fnetmar.ucc.ie%2Fuml%2Fcontent%2F_16_9beta_17160442_1282214733786_525316_41235.png }} 163 2010-11-22T15:03:06Z Anthony 1 {{Decision |Scenario=ICAN Decision Maker |Attribute=Usability, Service Reusability }} {{Analysis |Decision=EUMIS as UI Mediator }} {{Reasoning |Diagram=http://netmar.ucc.ie/uml/content/_16_9beta_17160442_1282214733786_525316_41235.png }} 164 2010-11-22T17:40:30Z Anthony 1 {{Decision |Scenario=ICAN Decision Maker |Attribute=service reusability, }} {{Analysis |Decision=EUMIS as UI Mediator }} {{Reasoning |Diagram=http://netmar.ucc.ie/uml/content/_16_9beta_17160442_1282214733786_525316_41235.png }} 165 2010-11-22T17:41:13Z Anthony 1 {{Decision |Scenario=ICAN Decision Maker |Attribute=Service Reusability }} {{Analysis |Decision=EUMIS as UI Mediator }} {{Reasoning |Diagram=http://netmar.ucc.ie/uml/content/_16_9beta_17160442_1282214733786_525316_41235.png }} 166 2010-11-22T17:42:49Z Anthony 1 {{Decision |Scenario=ICAN Decision Maker |Attribute=Service Reusability }} {{Analysis |Decision=EUMIS as [[soapattern:UI Mediator]] }} {{Reasoning |Diagram=http://netmar.ucc.ie/uml/content/_16_9beta_17160442_1282214733786_525316_41235.png }} 167 2010-11-22T17:47:12Z Anthony 1 {{Decision |Scenario=ICAN Decision Maker |Attribute=Service Reusability }} {{Analysis |Decision=EUMIS as UI Mediator }} {{Reasoning |Diagram=http://netmar.ucc.ie/uml/content/_16_9beta_17160442_1282214733786_525316_41235.png }} 168 2010-11-25T14:01:51Z Anthony 1 {{Decision |Scenario=ICAN Decision Maker uses Semantic Discovery |Attribute=Service Reusability |Environment=NETMAR operational. User has performed a number of semantic discovery operations |Stimulus=User carries out steps as in ICAN discovery use case |Response=User should receive a response within three seconds }} {{Analysis |Decision=EUMIS as UI Mediator }} {{Analysis |Decision=Cache responses at client }} {{Reasoning |Diagram=http://netmar.ucc.ie/uml/content/_16_9beta_17160442_1282214733786_525316_41235.png }} 169 2010-11-25T14:49:16Z Anthony 1 {{Decision |Scenario=ICAN Decision Maker uses Semantic Discovery |Attribute=Service Reusability, Performance |Environment=NETMAR operational. User has performed a number of semantic discovery operations |Stimulus=User carries out steps as in ICAN discovery use case |Response=User should receive a response within three seconds }} {{Analysis |Decision=EUMIS as UI Mediator |Tradeoff=Service distribution & asychronicity can lead to poor latency }} {{Analysis |Decision=Cache responses at client |Risk=Response lifetimes not modelled |Sensitivity=Service endpoint granularity }} {{Reasoning |Diagram=http://netmar.ucc.ie/uml/content/_16_9beta_17160442_1282214733786_525316_41235.png }} 170 2010-11-25T14:50:32Z Anthony 1 {{Decision |Scenario=ICAN Decision Maker uses Semantic Discovery |Attribute=Service Reusability, Performance |Environment=NETMAR operational. User has performed a number of semantic discovery operations |Stimulus=User carries out steps as in ICAN discovery use case |Response=User should receive a response within three seconds }} {{Analysis |Decision=EUMIS as UI Mediator |Tradeoff=Service distribution & asynchronicity can lead to poor latency }} {{Analysis |Decision=Cache responses at client |Risk=Response lifetimes not modelled |Sensitivity=Service endpoint granularity }} {{Reasoning |Diagram=http://netmar.ucc.ie/uml/content/_16_9beta_17160442_1282214733786_525316_41235.png }} 25 171 2010-11-22T14:16:06Z Anthony 1 Created page with "[[Has type::URL]]" [[Has type::URL]] 172 2010-11-22T17:36:49Z Anthony 1 Blanked the page 26 173 2010-11-22T16:26:31Z Anthony 1 Created page with "From [[SOA Pattern::http://www.soaprinciples.com/service_reusability.php]]. The principle of Service Reusability emphasizes the positioning of services as enterprise resources w..." From [[SOA Pattern::http://www.soaprinciples.com/service_reusability.php]]. The principle of Service Reusability emphasizes the positioning of services as enterprise resources with agnostic functional contexts. Numerous design considerations are raised to ensure that individual service capabilities are appropriately defined in relation to an agnostic service context, and to guarantee that they can facilitate the necessary reuse requirements. 174 2010-11-22T16:45:29Z Anthony 1 Redirected page to [[SOAPrinciples::service reusability]] #REDIRECT [[SOAPrinciples::service reusability]] From [[SOA Pattern::http://www.soaprinciples.com/service_reusability.php]]. The principle of Service Reusability emphasizes the positioning of services as enterprise resources with agnostic functional contexts. Numerous design considerations are raised to ensure that individual service capabilities are appropriately defined in relation to an agnostic service context, and to guarantee that they can facilitate the necessary reuse requirements. 175 2010-11-22T16:46:55Z Anthony 1 Redirected page to [[SOAPrinciples:service reusability]] #REDIRECT [[SOAPrinciples:service reusability]] From [[SOA Pattern::http://www.soaprinciples.com/service_reusability.php]]. The principle of Service Reusability emphasizes the positioning of services as enterprise resources with agnostic functional contexts. Numerous design considerations are raised to ensure that individual service capabilities are appropriately defined in relation to an agnostic service context, and to guarantee that they can facilitate the necessary reuse requirements. 176 2010-11-22T16:47:35Z Anthony 1 From [[SOA Pattern::SOAPrinciples:service_reusability]]. The principle of Service Reusability emphasizes the positioning of services as enterprise resources with agnostic functional contexts. Numerous design considerations are raised to ensure that individual service capabilities are appropriately defined in relation to an agnostic service context, and to guarantee that they can facilitate the necessary reuse requirements. 177 2010-11-22T16:48:24Z Anthony 1 From [[SOA Pattern::SOAPrinciples:service_reusability]]. The principle of Service Reusability emphasizes the positioning of services as enterprise resources with agnostic functional contexts. Numerous design considerations are raised to ensure that individual service capabilities are appropriately defined in relation to an agnostic service context, and to guarantee that they can facilitate the necessary reuse requirements. [[SOAPrinciples:service_reusability|service_reusability]] 178 2010-11-22T17:07:41Z Anthony 1 Redirected page to [[soaprinciples:service reusability]] #REDIRECT [[SOAPrinciples:service_reusability]] The principle of Service Reusability emphasizes the positioning of services as enterprise resources with agnostic functional contexts. Numerous design considerations are raised to ensure that individual service capabilities are appropriately defined in relation to an agnostic service context, and to guarantee that they can facilitate the necessary reuse requirements. [[soaprinciples:service_reusability|service_reusability]] 27 179 2010-11-22T17:50:23Z Anthony 1 Created page with "[[Has type::String]]" [[Has type::String]] 180 2010-11-22T17:51:40Z Anthony 1 Blanked the page 181 2010-11-22T17:54:27Z Anthony 1 [[has default form::Form:Decision]] 182 2010-11-25T09:50:55Z Anthony 1 Blanked the page 255 2011-01-26T16:56:51Z Anthony 1 [[imported from::atam:decision]] 28 183 2010-11-25T10:03:57Z Anthony 1 Created page with "This is an instance of the [[soapatterns::ui mediator]] pattern. The NETMAR partners will concentrate on building reusable, loosely coupled services. The role of the NETMAR EUMIS..." This is an instance of the [[soapatterns::ui mediator]] pattern. The NETMAR partners will concentrate on building reusable, loosely coupled services. The role of the NETMAR EUMIS will be to make these appear to an end-user as a coherent product. 184 2010-11-25T10:04:47Z Anthony 1 This is an instance of the [[soapatterns:ui mediator]] pattern. The NETMAR partners will concentrate on building reusable, loosely coupled services. The role of the NETMAR EUMIS will be to make these appear to an end-user as a coherent product. 185 2010-11-25T14:30:35Z Anthony 1 This is an instance of the [[Pattern::soapatterns:ui mediator]] pattern. The NETMAR partners will concentrate on building reusable, loosely coupled services. The role of the NETMAR EUMIS will be to make these appear to an end-user as a coherent product. 29 186 2010-11-25T13:36:36Z Anthony 1 Redirected page to [[soaprinciples:service reusability]] #REDIRECT [[soaprinciples:service reusability]] 30 187 2010-11-25T13:39:48Z Anthony 1 Redirected page to [[soaprinciples:service discoverability]] #REDIRECT [[soaprinciples:service discoverability]] 31 188 2010-11-25T14:26:27Z Anthony 1 Created page with "This is an instance of the [[Pattern::soapatterns:response caching]] pattern." This is an instance of the [[Pattern::soapatterns:response caching]] pattern. 32 189 2010-11-25T14:29:38Z Anthony 1 Redirected page to [[soaprinciples:service discoverability]] #REDIRECT [[soaprinciples:service discoverability]] 33 190 2010-11-25T15:25:20Z Anthony 1 Created page with "Successful caching strategies rely on a good understanding of resource lifetimes, i.e which resources can be cached and for how long, and how does the server notify the client th..." Successful caching strategies rely on a good understanding of resource lifetimes, i.e which resources can be cached and for how long, and how does the server notify the client that the cached data is no longer valid. Without understanding this caching may not deliver the desired performance benefits, or may result in stale data being served to the user. 34 191 2010-11-25T15:45:18Z Anthony 1 Created page with "Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * h..." Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) 370 2011-02-18T11:45:49Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask:: [[Pattern::+]]}}|Pattern Usage|,|,}} 372 2011-02-18T11:51:53Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask: [[Pattern::+]]}}|Pattern Usage|,|,}} 374 2011-02-18T11:55:45Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask: [[Pattern::+]]}}|Pattern Usage|,|}} {{#ask: [[Uses Pattern::+]]|?Pattern|?Usage}} 378 2011-02-18T13:38:14Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask: [[Pattern::+]]|?Pattern}}|Pattern Usage|,|}} {{#ask: [[Uses Pattern::+]]|?Pattern|?Usage}} 382 2011-02-18T13:49:01Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask: [[Pattern::+]]|?Pattern}}|Pattern Usage|,|}} }} {{#ask: [[Uses Pattern::+]]|?Pattern|?Usage}} 384 2011-02-18T13:51:13Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask: [[Pattern::+]]|?Pattern?=Decision}}|Pattern Usage|,|,}} {{#ask: [[Uses Pattern::+]]|?Pattern|?Usage}} 385 2011-02-18T13:52:19Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask: [[Pattern::+]]|?Pattern|?=Decision}}|Pattern Usage|,|,}} {{#ask: [[Uses Pattern::+]]|?Pattern|?Usage}} 389 2011-02-18T14:17:55Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask: [[Pattern::+]]|?Pattern|sep=,|mainlabel=-|link=none|?=Decision|format=list}}|Pattern Usage|,|,}} {{#ask: [[Uses Pattern::+]]|?Pattern|?Usage}} 391 2011-02-18T14:24:35Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask: [[Pattern::+]]|?Pattern|sep=,|mainlabel=-|link=none|headers=hide|?=Decision|format=list}}|Pattern Usage|,|,}} {{#ask: [[Uses Pattern::+]]|?Pattern|?Usage}} 392 2011-02-18T14:26:15Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#arraymaptemplate: {{#ask: [[Pattern::+]]|?Pattern|sep=,|link=none|headers=hide|format=list}}|Pattern Usage|,|,}} {{#ask: [[Uses Pattern::+]]|?Pattern|?Usage}} 396 2011-02-18T14:42:22Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) {{#ask: [[Pattern::+]]|sep=,|link=none|headers=hide|format=template|template=Pattern Usage|?Pattern|?=Decision}} {{#ask: [[Uses Pattern::+]]|?Pattern|?Usage}} 400 2011-02-18T14:50:36Z Anthony 1 Where possible, we relate each decision made to a known pattern from a public pattern repository or published book or paper. The pattern repositories used for NETMAR include * http://SOAPatterns.org (interwiki:soapatterns) 35 192 2010-11-25T16:42:00Z Anthony 1 Created page with "NETMAR will adopt the [[Pattern::soapatterns:domain inventory]] pattern in order to have an independently standardised, governed and owned inventory of services." NETMAR will adopt the [[Pattern::soapatterns:domain inventory]] pattern in order to have an independently standardised, governed and owned inventory of services. 36 193 2010-11-25T18:06:19Z Anthony 1 Created page with "testing cron job.." testing cron job.. 235 2011-01-24T15:15:25Z Anthony 1 Blanked the page 236 2011-01-24T15:16:09Z Anthony 1 g 237 2011-01-24T15:45:54Z Anthony 1 {{#sparql:select * where { ?x ?y ?z . } LIMIT 5 }} 238 2011-01-24T15:55:27Z Anthony 1 Adding [[a new property::and value]] to this page {{#sparql:select * where { ?x ?y ?z . } LIMIT 5 }} 241 2011-01-24T16:07:51Z Anthony 1 Adding [[a new property::and value]] to this page {{#sparql:PREFIX owl:<http://www.w3.org/2002/07/owl#>select * where { ?x owl:sameAs ?z . } LIMIT 5 }} 242 2011-01-24T16:22:57Z Anthony 1 Adding [[a new property::and value]] to this page {{#sparql:PREFIX owl:<http://www.w3.org/2002/07/owl#> select * where { ?x <http://netmar.cmrc.ie/wiki/index.php/Special:URIResolver/Property:Broader> ?z . } LIMIT 5 }} 313 2011-02-11T14:43:36Z Anthony 1 Adding [[a new property::and value]] to this page {{#sparql:PREFIX owl:<http://www.w3.org/2002/07/owl#> select * where { ?x <http://netmar.cmrc.ie/wiki/index.php/Special:URIResolver/Property:Broader> ?z . } LIMIT 5 }} [[From Scenario.Theme::Licensing]] 314 2011-02-11T14:44:03Z Anthony 1 Adding [[a new property::and value]] to this page {{#sparql:PREFIX owl:<http://www.w3.org/2002/07/owl#> select * where { ?x <http://netmar.cmrc.ie/wiki/index.php/Special:URIResolver/Property:Broader> ?z . } LIMIT 5 }} {{#ask: [[From Scenario.Theme::Licensing]]}} 315 2011-02-11T14:48:21Z Anthony 1 Adding [[a new property::and value]] to this page {{#sparql:PREFIX owl:<http://www.w3.org/2002/07/owl#> select * where { ?x <http://netmar.cmrc.ie/wiki/index.php/Special:URIResolver/Property:Broader> ?z . } LIMIT 5 }} {{#ask: [[From Scenario.Theme::Licensing]]}} {{#ask: [[From Scenario<q>[[Theme::Licensing]]</q>]]}} 316 2011-02-11T14:48:45Z Anthony 1 Adding [[a new property::and value]] to this page {{#sparql:PREFIX owl:<http://www.w3.org/2002/07/owl#> select * where { ?x <http://netmar.cmrc.ie/wiki/index.php/Special:URIResolver/Property:Broader> ?z . } LIMIT 5 }} {{#ask: [[Theme::Licensing]]}} {{#ask: [[From Scenario<q>[[Theme::Licensing]]</q>]]}} 332 2011-02-14T15:28:38Z Anthony 1 Adding [[a new property::and value]] to this page {{#ask: [[Category:Person]] | ?has child | ?knows | format=graph | graphcolor=Yes | graphlink=Yes | graphname=PeopleKnows | graphlegend=Yes | graphlabel=No | graphsize=10,10 | rankdir=TB 333 2011-02-14T15:28:56Z Anthony 1 Adding [[a new property::and value]] to this page {{#ask: [[Category:Person]] | ?has child | ?knows | format=graph | graphcolor=Yes | graphlink=Yes | graphname=PeopleKnows | graphlegend=Yes | graphlabel=No | graphsize=10,10 | rankdir=TB }} 334 2011-02-14T15:29:42Z Anthony 1 Adding [[a new property::and value]] to this page {{#ask: [[Category:Person]] | ?email | format=graph | graphcolor=Yes | graphlink=Yes | graphname=PeopleKnows | graphlegend=Yes | graphlabel=No | graphsize=10,10 | rankdir=TB }} 335 2011-02-14T15:34:48Z Anthony 1 Adding [[a new property::and value]] to this page {{#ask: [[Category:Person]] | ?email | format=graph | graphcolor=Yes | graphlink=Yes | graphname=PeopleKnows | graphlegend=Yes | graphlabel=No | graphsize=10,10 | rankdir=TB }} <graphviz border='frame' format='png'> digraph example1 {Hello->World!} </graphviz> 336 2011-02-14T15:46:20Z Anthony 1 Adding [[a new property::and value]] to this page {{#ask: [[Category:Person]] | ?email | format=graph }} {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |?Decision= |format=graph}} 337 2011-02-14T15:51:10Z Anthony 1 Adding [[a new property::and value]] to this page {{#ask: [[From Scenario.Theme::Licensing]] |?Decision |?Risk |format=graph}} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |format=graph |graphlabel=yes |graphlink=yes }} 338 2011-02-14T15:52:19Z Anthony 1 Adding [[a new property::and value]] to this page {{#ask: [[From Scenario.Theme::Licensing]] |?Decision |?Risk |format=graph}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response |format=graph |graphlabel=yes |graphlink=yes }} 339 2011-02-14T15:53:41Z Anthony 1 Adding [[a new property::and value]] to this page {{#ask: [[From Scenario.Theme::Licensing]] |?Decision |?Risk |format=graph}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |?Attribute |?Scenario |?Stimulus |?Response |format=graph |graphlabel=yes |graphlink=yes |graphsize=640,480 }} 340 2011-02-14T15:57:16Z Anthony 1 Adding [[a new property::and value]] to this page {{#ask: [[From Scenario.Theme::Licensing]] |?Decision |?Risk |format=graph}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |?Attribute |?Scenario |?Stimulus |?Response |format=graph |graphlabel=yes |graphlink=yes |graphsize=10,10 |rankdir=TB }} 341 2011-02-14T15:58:12Z Anthony 1 {{#ask: [[From Scenario.Theme::Licensing]] |?Decision |?Risk |format=graph}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |?Attribute |?Scenario |?Stimulus |?Response |format=graph |graphlabel=yes |graphlink=yes |graphsize=10,30 |rankdir=TB }} 342 2011-02-14T16:04:11Z Anthony 1 {{#ask: [[Category:Analysis]] |?Attribute |?Scenario |format=graph |graphlabel=yes |graphlink=yes |graphsize=20,100 |rankdir=LR }} 343 2011-02-14T16:25:37Z Anthony 1 {{#ask: [[From Scenario.Theme::+]] [[Pattern::+]] |format=graph |?Pattern |?Decision |graphlabel=yes |graphlink=yes }} 344 2011-02-14T16:26:53Z Anthony 1 {{#ask: [[From Scenario.Theme::+]] OR [[Pattern::+]] |format=graph |?Pattern |?Decision |graphlabel=yes |graphlink=yes }} 345 2011-02-14T16:27:56Z Anthony 1 {{#ask: [[From Scenario.Theme::+]] |format=graph |?Pattern |?Decision |graphlabel=yes |graphlink=yes }} 347 2011-02-14T16:34:08Z Anthony 1 {{#ask: [[From Scenario.Theme::+]] OR [[Theme::+]] |format=graph |?Decision |?Attribute |?From Scenario |graphlabel=yes |graphlink=yes }} 348 2011-02-14T16:35:30Z Anthony 1 {{#ask: [[From Scenario.Theme::+]] OR [[Theme::+]] |format=graph |?Decision |?Attribute |?From Scenario |?Theme |graphlabel=yes |graphlink=yes }} 349 2011-02-14T16:37:46Z Anthony 1 {{#ask: [[From Scenario.Theme::Licensing]] OR [[Theme::Licensing]] |format=graph |?Decision |?Attribute |?From Scenario |?Theme |graphlabel=yes |graphlink=yes }} 351 2011-02-14T16:42:46Z Anthony 1 {{#ask: [[From Scenario.Theme::Licensing]] OR [[Theme::Licensing]] |format=graph |?Decision |?Attribute |?From Scenario |?Theme |?Pattern |graphlabel=yes |graphlink=yes }} 352 2011-02-14T16:43:13Z Anthony 1 {{#ask: [[From Scenario.Theme::+]] OR [[Theme::+]] |format=graph |?Decision |?Attribute |?From Scenario |?Theme |?Pattern |graphlabel=yes |graphlink=yes }} 353 2011-02-14T16:43:53Z Anthony 1 {{#ask: [[From Scenario.Theme::+]] OR [[Theme::+]] OR [[Pattern::+]] |format=graph |?Decision |?Attribute |?From Scenario |?Theme |?Pattern |graphlabel=yes |graphlink=yes }} 355 2011-02-14T16:47:48Z Anthony 1 {{#ask: [[From Scenario.Theme::+]] OR [[Theme::+]] OR [[Pattern::+]] |format=graph |?Decision |?Attribute |?From Scenario |?Theme |?Pattern |graphlabel=yes |graphlink=yes |graphsize=10,10 }} 37 194 2010-12-03T09:31:32Z Morten Created page with "{{Decision |Scenario=Scientist uses ice area and extent from SSMI |Attribute=Service reliability and robustness |Environment=NETMAR operational. |Stimulus=User accesses latest i..." {{Decision |Scenario=Scientist uses ice area and extent from SSMI |Attribute=Service reliability and robustness |Environment=NETMAR operational. |Stimulus=User accesses latest ice area and ice extent estimates. |Response=User receives near real time data. Last validated data set is displayed. }} {{Reasoning}} 195 2010-12-08T14:46:52Z Torill {{Decision |Scenario=Scientist uses ice area and extent from SSMI |Attribute=Service reliability, Service robustness |Environment=NETMAR operational. |Stimulus=User accesses latest ice area and ice extent estimates. |Response=User receives near real time data. Last validated data set is displayed. }} {{Reasoning}} 196 2010-12-08T14:53:23Z Torill {{Decision |Scenario=Scientist uses ice area and extent from SSMI |Attribute=Service reliability, Service robustness |Environment=NETMAR operational. |Stimulus=User accesses latest ice area and ice extent estimates, and obtains information about last date included. |Response=User receives near real time data. Last validated data set is displayed. }} {{Reasoning}} 197 2010-12-08T15:00:03Z Torill {{Decision |Scenario=Scientist uses ice area and extent from SSMI |Attribute=Service reliability, Service robustness |Environment=NETMAR operational. |Stimulus=User accesses latest ice area and ice extent estimates, and obtains information about last date included. |Response=System displays a graph of ice area and extent, up to and including the last valid data set. The plot is updated when new data are found. Days with invalid data are not included in the plot. }} {{Reasoning}} 38 198 2010-12-03T09:43:41Z Morten Created page with "{{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Service performance |Environment=NETMAR operational. User selects latest data from the area of intere..." {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Service performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map. The selected file is downloaded in a couple of minutes. }} {{Reasoning}} 199 2010-12-03T14:22:14Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Service performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map. The selected file is downloaded in a couple of minutes. }} {{Reasoning}} 200 2010-12-03T14:23:22Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Service performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map. The selected file is downloaded in a couple of minutes. }} {{Analysis}} {{Reasoning}} 201 2010-12-08T15:07:02Z Torill {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map. The selected file is downloaded in a couple of minutes. }} {{Analysis}} {{Reasoning}} 202 2010-12-08T15:11:31Z Torill {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis}} {{Reasoning}} 203 2010-12-08T15:17:52Z Torill {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis}} {{Reasoning}} 204 2010-12-15T12:11:41Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis |Decision=Replicate data based on user requirements |Non-risk=Download can be scheduled at optimal time |Sensitivity=Interval between availability of coverage and user request }} {{Reasoning}} 205 2010-12-15T14:32:41Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis |Decision=Replicate data based on user requirements |Non-risk=Download can be scheduled at optimal time |Sensitivity=Interval between availability of coverage and user request |Tradeoff=Increased burden of business state management, Increased local storage consumption }} {{Reasoning}} 206 2010-12-15T14:37:53Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis |Decision=Replicate data based on user requirements |Non-risk=Download can be scheduled at optimal time |Sensitivity=Interval between availability of coverage and user request |Tradeoff=Increased burden of business state management }} {{Reasoning}} 207 2010-12-15T14:43:20Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis |Decision=Replicate data based on user requirements |Non-risk=Download can be scheduled at optimal time |Sensitivity=Interval between availability of coverage and user request |Tradeoff=Increased state management, Increased resource consumption }} {{Reasoning}} 208 2010-12-15T14:55:02Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance, Resource consumption, Latency |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis |Decision=Replicate data based on user requirements |Non-risk=Download can be scheduled at optimal time |Sensitivity=Interval between availability of coverage and user request |Tradeoff=Increased state management, Increased resource consumption }} {{Reasoning}} 209 2010-12-15T15:02:09Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance, Resource consumption, Latency |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis |Decision=Replicate data based on user requirements |Non-risk=Download can be scheduled at optimal time |Sensitivity=Interval between availability of coverage and user request |Tradeoff=Increased state management }} {{Reasoning |Reasoning=The ship's captain may not always have a fast or reliable connection to the data source. Therefore we provide a service which may be run locally on the ship, which combines caching and business logic to preemptively download the latest coverage data and archive it for a period of time, in order to improve latency. }} 210 2010-12-15T15:44:29Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance, Resource consumption, Latency |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis |Decision=Replicate data based on user requirements |Non-risk=Download can be scheduled at optimal time |Sensitivity=Interval between availability of coverage and user request |Tradeoff=Increased state management }} {{Reasoning |Reasoning=The ship's captain may not always have a fast or reliable connection to the data source. Therefore we provide a service which may be run locally on the ship, which combines caching and business logic to preemptively download the latest coverage data and archive it for a period of time, in order to improve latency. |Diagram=http://t.uig.im/wiki/lib/exe/fetch.php?media=sar_image_replication.png }} 229 2010-12-23T14:53:11Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance, Resource consumption, Latency |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis |Decision=Replicate data based on user requirements |Non-risk=Download can be scheduled at optimal time |Sensitivity=Interval between availability of coverage and user request |Tradeoff=Increased state management }} {{Reasoning |Reasoning=The ship's captain may not always have a fast or reliable connection to the data source. Therefore we provide a service which may be run locally on the ship, which combines caching and business logic to preemptively download the latest coverage data and archive it for a period of time, in order to improve latency. |Diagram=Sar image replication.png }} 354 2011-02-14T16:46:14Z Anthony 1 {{Decision |Scenario=Ship captain downloads the latest SAR image |Attribute=Performance, Resource consumption, Latency |Environment=NETMAR operational. User selects latest data from the area of interest. |Stimulus=User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. |Response=The system shows a coverage map with dates of images. The selected file is downloaded in a couple of minutes. While downloading the system shows a progress bar. }} {{Analysis |Decision=Replicate data based on user requirements |Non-risk=Download can be scheduled at optimal time |Sensitivity=Interval between availability of coverage and user request |Tradeoff=Increased state management }} {{Reasoning |Reasoning=The ship's captain may not always have a fast or reliable connection to the data source. Therefore we provide a service which may be run locally on the ship, which combines caching and business logic to preemptively download the latest coverage data and archive it for a period of time, in order to improve latency. |Diagram=Sar image replication.png |Theme=Caching }} 39 211 2010-12-07T14:36:51Z Anthony 1 Created page with "== first draft == Scenario: Scientist uses ice area and extent from SSMI Attribute:Service reliability and robustness :It's not clear to me if you're trying to add two quality..." == first draft == Scenario: Scientist uses ice area and extent from SSMI Attribute:Service reliability and robustness :It's not clear to me if you're trying to add two quality attributes, or creating a compound one. If you're referencing two quality attributes you can separate them by using a comma, i.e. 'Service reliability, Service robustness'. In this case, robustness seems like a sub-attribute of reliability (reliability in the face of failure), so you could just use the narrower term. --[[User:Anthony|Anthony]] 14:36, 7 December 2010 (UTC) Environment: NETMAR operational. Stimulus: User accesses latest ice area and ice extent estimates. Response: User receives near real time data. Last validated data set is displayed. :The stimulus and response could be reworded to express the relationship to the quality attribute better. Does receiving this response in a test show clearly that the system is robust? You might want to incorporate the idea of testing continuously and putting a threshold on failures within a certain time period. A possible source for related scenarios would be to consider robustness in the face of a number of different failure modes or environmental conditions, and create a scenario for each, e.g. what expectations would we have of the system if the network were slow or unreliable; how would it behave if the datasets were not available for disply, etc. --[[User:Anthony|Anthony]] 14:36, 7 December 2010 (UTC) 212 2010-12-08T14:42:25Z Torill /* first draft */ == first draft == Scenario: Scientist uses ice area and extent from SSMI Attribute:Service reliability and robustness :It's not clear to me if you're trying to add two quality attributes, or creating a compound one. If you're referencing two quality attributes you can separate them by using a comma, i.e. 'Service reliability, Service robustness'. In this case, robustness seems like a sub-attribute of reliability (reliability in the face of failure), so you could just use the narrower term. --[[User:Anthony|Anthony]] 14:36, 7 December 2010 (UTC) :We agree these attributes should be separated, i.e. service reliability and service robustness. Both are important to us. Reliability to ensure that users will get results from the service on a regular (anticipated) basis. Robustness to ensure the underlying algorithm is handling e.g. lacking/invalid input data. Robustness is a subset of reliability (ref. Bruegge and Dutiot: Object-Oriented Software Engineerning using UML and Patterns).--[[User:Torill|Torill]] [[User:Morten|Morten]] 14:41, 8 December 2010 (UTC) Environment: NETMAR operational. Stimulus: User accesses latest ice area and ice extent estimates. Response: User receives near real time data. Last validated data set is displayed. :The stimulus and response could be reworded to express the relationship to the quality attribute better. Does receiving this response in a test show clearly that the system is robust? You might want to incorporate the idea of testing continuously and putting a threshold on failures within a certain time period. A possible source for related scenarios would be to consider robustness in the face of a number of different failure modes or environmental conditions, and create a scenario for each, e.g. what expectations would we have of the system if the network were slow or unreliable; how would it behave if the datasets were not available for disply, etc. --[[User:Anthony|Anthony]] 14:36, 7 December 2010 (UTC) 213 2010-12-08T15:02:08Z Torill /* first draft */ == first draft == Scenario: Scientist uses ice area and extent from SSMI Attribute:Service reliability and robustness :It's not clear to me if you're trying to add two quality attributes, or creating a compound one. If you're referencing two quality attributes you can separate them by using a comma, i.e. 'Service reliability, Service robustness'. In this case, robustness seems like a sub-attribute of reliability (reliability in the face of failure), so you could just use the narrower term. --[[User:Anthony|Anthony]] 14:36, 7 December 2010 (UTC) :We agree these attributes should be separated, i.e. service reliability and service robustness. Both are important to us. Reliability to ensure that users will get results from the service on a regular (anticipated) basis. Robustness to ensure the underlying algorithm is handling e.g. lacking/invalid input data. Robustness is a subset of reliability (ref. Bruegge and Dutiot: Object-Oriented Software Engineerning using UML and Patterns).--[[User:Torill|Torill]] [[User:Morten|Morten]] 14:41, 8 December 2010 (UTC) Environment: NETMAR operational. Stimulus: User accesses latest ice area and ice extent estimates. Response: User receives near real time data. Last validated data set is displayed. :The stimulus and response could be reworded to express the relationship to the quality attribute better. Does receiving this response in a test show clearly that the system is robust? You might want to incorporate the idea of testing continuously and putting a threshold on failures within a certain time period. A possible source for related scenarios would be to consider robustness in the face of a number of different failure modes or environmental conditions, and create a scenario for each, e.g. what expectations would we have of the system if the network were slow or unreliable; how would it behave if the datasets were not available for disply, etc. --[[User:Anthony|Anthony]] 14:36, 7 December 2010 (UTC) :We have rephrased the input/output. Please review. --[[User:Torill|Torill]] [[User:Morten|Morten]] 15:01, 8 December 2010 (UTC) 40 214 2010-12-07T16:11:04Z Anthony 1 Created page with "== Comments on first draft == Scenario: Ship captain downloads the latest SAR image Attribute:Service performance :I try to reserve the attributes 'service ...' for ones mention..." == Comments on first draft == Scenario: Ship captain downloads the latest SAR image Attribute:Service performance :I try to reserve the attributes 'service ...' for ones mentioned in http://SOAPrinciples.com, or otherwise directly linkable with service orientation. 'Performance' is a more generic attribute, so should just be used on its own.--[[User:Anthony|Anthony]] 16:11, 7 December 2010 (UTC) Environment: NETMAR operational. User selects latest data from the area of interest. Stimulus: User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. Response: The system shows a coverage map. The selected file is downloaded in a couple of minutes. :As a further scenario, consider what happens during those couple of minutes. Is it possible to show the user a partial representation within a few seconds? That could help to improve perceived performance. Even of that's not within scope for the pilot, it's important to show that we've considered usability factors like that as part of a fully operational system.--[[User:Anthony|Anthony]] 16:11, 7 December 2010 (UTC) 215 2010-12-08T15:06:10Z Torill /* Comments on first draft */ == Comments on first draft == Scenario: Ship captain downloads the latest SAR image Attribute:Service performance :I try to reserve the attributes 'service ...' for ones mentioned in http://SOAPrinciples.com, or otherwise directly linkable with service orientation. 'Performance' is a more generic attribute, so should just be used on its own.--[[User:Anthony|Anthony]] 16:11, 7 December 2010 (UTC) :OK. We follow your example. [[User:Torill|Torill]] [[User:Morten|Morten]] 15:05, 8 December 2010 (UTC) Environment: NETMAR operational. User selects latest data from the area of interest. Stimulus: User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. Response: The system shows a coverage map. The selected file is downloaded in a couple of minutes. :As a further scenario, consider what happens during those couple of minutes. Is it possible to show the user a partial representation within a few seconds? That could help to improve perceived performance. Even of that's not within scope for the pilot, it's important to show that we've considered usability factors like that as part of a fully operational system.--[[User:Anthony|Anthony]] 16:11, 7 December 2010 (UTC) 216 2010-12-08T15:14:48Z Torill /* Comments on first draft */ == Comments on first draft == Scenario: Ship captain downloads the latest SAR image Attribute:Service performance :I try to reserve the attributes 'service ...' for ones mentioned in http://SOAPrinciples.com, or otherwise directly linkable with service orientation. 'Performance' is a more generic attribute, so should just be used on its own.--[[User:Anthony|Anthony]] 16:11, 7 December 2010 (UTC) :OK. We follow your example. --[[User:Torill|Torill]] [[User:Morten|Morten]] 15:05, 8 December 2010 (UTC) Environment: NETMAR operational. User selects latest data from the area of interest. Stimulus: User carries out the steps in use case: Assess current ice situation for planning optimal sailing route. Response: The system shows a coverage map. The selected file is downloaded in a couple of minutes. :As a further scenario, consider what happens during those couple of minutes. Is it possible to show the user a partial representation within a few seconds? That could help to improve perceived performance. Even of that's not within scope for the pilot, it's important to show that we've considered usability factors like that as part of a fully operational system.--[[User:Anthony|Anthony]] 16:11, 7 December 2010 (UTC) :There should of course be a progress bar displayed while the downloading is going on. Added this now. --[[User:Torill|Torill]] [[User:Morten|Morten]] 15:12, 8 December 2010 (UTC) 41 217 2010-12-07T16:12:23Z Anthony 1 Created page with "[[email::a.patterson@ucc.ie]]" [[email::a.patterson@ucc.ie]] 231 2011-01-05T16:52:01Z Anthony 1 [[email::a.patterson@ucc.ie]] test backup script 244 2011-01-26T10:41:35Z Anthony 1 [[email::a.patterson@ucc.ie]] test backup script [[Category:Person]] 245 2011-01-26T10:41:53Z Anthony 1 [[email::a.patterson@ucc.ie]] [[Category:Person]] 259 2011-01-27T16:56:13Z Anthony 1 [[email::a.patterson@ucc.ie]] [[Category:Person]] {{#sparql: PREFIX atam: <http://netmar.cmrc.ie/atam#> select ?scenario ?decision where { ?x atam:fromScenario ?z . ?z atam:scenario ?scenario . ?x atam:decision ?decision } limit 10 | format=graph }} 260 2011-01-27T17:13:21Z Anthony 1 [[email::a.patterson@ucc.ie]] [[Category:Person]] {{#sparql: PREFIX atam: <http://netmar.cmrc.ie/atam#> select ?scenario ?decision where { ?x atam:fromScenario ?z . ?z atam:scenario ?scenario . ?x atam:decision ?decision } limit 10 }} 261 2011-01-27T17:14:19Z Anthony 1 [[email::a.patterson@ucc.ie]] [[Category:Person]] {{#sparql: PREFIX atam: <http://netmar.cmrc.ie/atam#> select ?scenario ?decision where { ?x atam:fromScenario ?z . ?z atam:scenario ?scenario . ?x atam:decision ?decision } limit 10 | tablestyle=border-width:1px; border-spacing:0px; border-style:outset; border-color:black; border-collapse:collapse; | rowstyle=padding:2px; | oddrowstyle=background-color:Lavender | evenrowstyle=background-color:white | headerstyle=background-color:CornflowerBlue; color: white }} 262 2011-01-27T17:20:01Z Anthony 1 [[email::a.patterson@ucc.ie]] [[Category:Person]] {{#sparql: PREFIX atam: <http://netmar.cmrc.ie/atam#> select ?scenario ?decision where { ?x atam:fromScenario ?z . ?z atam:scenario ?scenario . ?x atam:decision ?decision } limit 10 | }} 263 2011-01-27T17:20:19Z Anthony 1 [[email::a.patterson@ucc.ie]] [[Category:Person]] {{#sparql: PREFIX atam: <http://netmar.cmrc.ie/atam#> select ?scenario ?decision where { ?x atam:fromScenario ?z . ?z atam:scenario ?scenario . ?x atam:decision ?decision } limit 10 }} 264 2011-01-27T17:21:59Z Anthony 1 [[email::a.patterson@ucc.ie]] [[Category:Person]] {{#sparql: select ?page where { ?page rdf:type cat:Cat } }} 265 2011-01-27T17:22:27Z Anthony 1 [[email::a.patterson@ucc.ie]] [[Category:Person]] 42 218 2010-12-07T16:12:59Z Anthony 1 Created page with "[[has type::email]]" [[has type::email]] 247 2011-01-26T10:44:26Z Anthony 1 [[has type::email]] [[imported from::foaf:mbox]] 43 219 2010-12-08T12:39:45Z Anthony 1 Created page with "[[has type::String]]" [[has type::String]] 44 220 2010-12-15T12:15:31Z Anthony 1 Created page with "This is an example of the [[Pattern::soapatterns:service data replication]] pattern. It is used to increase the autonomy and behavioural predictability of the (e.g. coverage) se..." This is an example of the [[Pattern::soapatterns:service data replication]] pattern. It is used to increase the autonomy and behavioural predictability of the (e.g. coverage) service in the face of network performance issues. 45 226 2010-12-23T14:23:00Z Anthony 1 227 2010-12-23T14:51:50Z Anthony 1 uploaded a new version of &quot;[[File:Sar image replication.png]]&quot; 228 2010-12-23T14:53:05Z Anthony 1 uploaded a new version of &quot;[[File:Sar image replication.png]]&quot; 46 232 2011-01-11T12:42:02Z Anthony 1 Created page with "* navigation ** mainpage|mainpage-description ** http://nport.nersc.no:8080|NETMAR Portal ** http://netmar.nersc.no/|Public Website ** recentchanges-url|recentchanges ** randompa..." * navigation ** mainpage|mainpage-description ** http://nport.nersc.no:8080|NETMAR Portal ** http://netmar.nersc.no/|Public Website ** recentchanges-url|recentchanges ** randompage-url|randompage ** helppage|help * SEARCH * TOOLBOX * LANGUAGES 258 2011-01-27T10:47:07Z Anthony 1 * navigation ** mainpage|mainpage-description ** http://nport.nersc.no:8080|NETMAR Portal ** http://netmar.nersc.no/|Public Website ** recentchanges-url|recentchanges ** http://wiki.rsg.pml.ac.uk/pywps/index.php/Main_Page|PyWPS Wiki ** helppage|help * SEARCH * TOOLBOX * LANGUAGES 47 234 2011-01-17T12:46:27Z Anthony 1 Created page with "This property describes the [[wiki:QualityAttributes|Quality Attributes]] of most relevance in analysing this scenario." This property describes the [[wiki:QualityAttributes|Quality Attributes]] of most relevance in analysing this scenario. 48 239 2011-01-24T16:01:30Z Anthony 1 Created page with "test" test 49 240 2011-01-24T16:01:47Z Anthony 1 Created page with "test" test 50 243 2011-01-26T10:40:53Z Anthony 1 Created page with "http://xmlns.com/foaf/0.1/|[http://www.foaf-project.org/ Friend Of A Friend] name|Type:String homepage|Type:URI Person|Category knows|Type:Page ..." http://xmlns.com/foaf/0.1/|[http://www.foaf-project.org/ Friend Of A Friend] name|Type:String homepage|Type:URI Person|Category knows|Type:Page ... 51 246 2011-01-26T10:43:40Z Anthony 1 Created page with "[[imported from::foaf:Person]]" [[imported from::foaf:Person]] 425 2011-02-25T12:35:49Z Anthony 1 [[imported from::foaf:Person]] [[imported from::soa:HumanActor]] 426 2011-02-25T12:38:38Z Anthony 1 [[imported from::soa:HumanActor]] 427 2011-02-25T12:40:23Z Anthony 1 [[imported from::foaf:Person]] [[imported from::soa:HumanActor]] 52 249 2011-01-26T10:52:58Z Anthony 1 Created page with "{{#sparql:PREFIX xsd:<http://www.w3.org/2001/XMLSchema#> PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#> PREFIX rdf:<http://www.w3.org/1999/02/22-rdf-syntax-ns#> PREFI..." {{#sparql:PREFIX xsd:<http://www.w3.org/2001/XMLSchema#> PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#> PREFIX rdf:<http://www.w3.org/1999/02/22-rdf-syntax-ns#> PREFIX owl:<http://www.w3.org/2002/07/owl#> PREFIX a:<http://netmar.cmrc.ie/wiki/index.php/Special:URIResolver/> PREFIX cat:<http://netmar.cmrc.ie/wiki/index.php/Special:URIResolver/Category:> PREFIX prop:<http://netmar.cmrc.ie/wiki/index.php/Special:URIResolver/Property:> PREFIX foaf:<http://xmlns.com/foaf/0.1/> select * { ?x a foaf:Person } LIMIT 5}} 53 250 2011-01-26T16:23:45Z Anthony 1 Created page with "http://netmar.cmrc.ie/atam#|[http://www.sei.cmu.edu/architecture/tools/atam/ Architecture Tradeoff Analysis Method] Scenario|Category ApproachDescription|Category fromScenario..." http://netmar.cmrc.ie/atam#|[http://www.sei.cmu.edu/architecture/tools/atam/ Architecture Tradeoff Analysis Method] Scenario|Category ApproachDescription|Category fromScenario|type:Page ... 253 2011-01-26T16:26:27Z Anthony 1 http://netmar.cmrc.ie/atam#|[http://www.sei.cmu.edu/architecture/tools/atam/ Architecture Tradeoff Analysis Method] scenario|type:String ApproachDescription|Category fromScenario|type:Page ... 256 2011-01-26T16:58:24Z Anthony 1 http://netmar.cmrc.ie/atam#|[http://www.sei.cmu.edu/architecture/tools/atam/ Architecture Tradeoff Analysis Method] scenario|type:String ApproachDescription|Category fromScenario|type:Page decision|type:Page ... 54 251 2011-01-26T16:24:17Z Anthony 1 Created page with "[[imported from::atam:fromScenario]]" [[imported from::atam:fromScenario]] 266 2011-02-02T14:58:33Z Anthony 1 Blanked the page 55 267 2011-02-07T11:26:44Z Anthony 1 Created page with "{{Decision |Scenario=Third party data provider releases data with restrictions, permissions, etc |Attribute=Licensability |Environment=NETMAR operational. Data provider has usefu..." {{Decision |Scenario=Third party data provider releases data with restrictions, permissions, etc |Attribute=Licensability |Environment=NETMAR operational. Data provider has useful data but wishes to retain certain rights on how data is used. |Stimulus=Data provider specifies data license. |Response=NETMAR output must honour all terms of license }} {{Reasoning}} 293 2011-02-09T11:31:54Z Anthony 1 {{Decision |Scenario=Third party data provider releases data with restrictions, permissions, etc |Attribute=Licensability |Environment=NETMAR operational. Data provider has useful data but wishes to retain certain rights on how data is used. |Stimulus=Data provider specifies data license. |Response=NETMAR output must honour all terms of license }} {{Reasoning |Theme=Licensing }} 410 2011-02-21T16:20:55Z Anthony 1 {{Decision |Scenario=Third party data provider releases data with restrictions, permissions, etc |Attribute=Licensability |Environment=NETMAR operational. Data provider has useful data but wishes to retain certain rights on how data is used. |Stimulus=Data provider specifies data license. |Response=NETMAR output must honour all terms of license }} {{Analysis |Decision=End user beware |Sensitivity=Service chaining complexity |Pattern=soapatterns:domain inventory }} {{Analysis |Decision=License composition |Sensitivity=Service chaining complexity |Pattern=soapatterns:rules centralization }} {{Reasoning |Reasoning=If the basic assumption of unrestricted data is not valid for certain data providers, the system may still be valid provided: * the default policy is that the end user is responsible for ensuring their own compliance with the policies of all relevant data providers/processors * the system eventually moves towards a more sophisticated set of policy composition rules which may alleviate the burden on the end user. The default situation may be viewed as the combination of two simple rules: ** if the data is unrestricted, the output is unrestricted ** if the data is restricted, the user is responsible for compliance |Theme=Licensing }} 56 268 2011-02-07T15:16:46Z Anthony 1 Created page with "{{Decision |Scenario=End user receives data from NETMAR which is a product of different data sources |Attribute=Licensability, Usefulness |Environment=NETMAR operational. User ha..." {{Decision |Scenario=End user receives data from NETMAR which is a product of different data sources |Attribute=Licensability, Usefulness |Environment=NETMAR operational. User has discovered data processed by NETMAR |Stimulus=User decides how to use the data |Response=Should be able to use the data without violating the licensing agreements of the downstream data providers }} {{Reasoning}} 294 2011-02-09T11:32:20Z Anthony 1 {{Decision |Scenario=End user receives data from NETMAR which is a product of different data sources |Attribute=Licensability, Usefulness |Environment=NETMAR operational. User has discovered data processed by NETMAR |Stimulus=User decides how to use the data |Response=Should be able to use the data without violating the licensing agreements of the downstream data providers }} {{Reasoning |Theme=Licensing }} 317 2011-02-11T14:56:03Z Anthony 1 {{Decision |Scenario=End user receives data from NETMAR which is a product of different data sources |Attribute=Licensability, Usefulness |Environment=NETMAR operational. User has discovered data processed by NETMAR |Stimulus=User decides how to use the data |Response=Should be able to use the data without violating the licensing agreements of the downstream data providers }} {{Analysis |Decision=Assume unrestricted data |Risk=Limits data providres }} {{Reasoning |Theme=Licensing }} 318 2011-02-11T14:56:33Z Anthony 1 {{Decision |Scenario=End user receives data from NETMAR which is a product of different data sources |Attribute=Licensability, Usefulness |Environment=NETMAR operational. User has discovered data processed by NETMAR |Stimulus=User decides how to use the data |Response=Should be able to use the data without violating the licensing agreements of the downstream data providers }} {{Analysis |Decision=Assume unrestricted data |Risk=Limits data providers }} {{Reasoning |Theme=Licensing }} 404 2011-02-18T17:01:31Z Anthony 1 {{Decision |Scenario=End user receives data from NETMAR which is a product of different data sources |Attribute=Licensability, Usefulness |Environment=NETMAR operational. User has discovered data processed by NETMAR |Stimulus=User decides how to use the data |Response=Should be able to use the data without violating the licensing agreements of the downstream data providers }} {{Analysis |Decision=Assume unrestricted data |Risk=Limits data providers |Pattern=soapatterns:Policy Centralization }} {{Reasoning |Theme=Licensing }} 409 2011-02-21T12:29:36Z Anthony 1 {{Decision |Scenario=End user receives data from NETMAR which is a product of different data sources |Attribute=Licensability, Usefulness |Environment=NETMAR operational. User has discovered data processed by NETMAR |Stimulus=User decides how to use the data |Response=Should be able to use the data without violating the licensing agreements of the downstream data providers }} {{Analysis |Decision=Assume unrestricted data |Risk=Limits data providers |Pattern=soapatterns:policy centralization }} {{Reasoning |Theme=Licensing }} 57 269 2011-02-07T16:53:44Z Anthony 1 Created page with "{{Decision |Scenario=Processing service provider modifies restricted data source }} {{Reasoning}}" {{Decision |Scenario=Processing service provider modifies restricted data source }} {{Reasoning}} 295 2011-02-09T11:33:00Z Anthony 1 {{Decision |Scenario=Processing service provider modifies restricted data source }} {{Reasoning |Theme=Licensing }} 58 270 2011-02-08T09:35:44Z Anthony 1 Created page with "{{Decision |Scenario=Processing service provider modifies restricted data source }} {{Reasoning}}" {{Decision |Scenario=Processing service provider modifies restricted data source }} {{Reasoning}} 289 2011-02-09T11:08:16Z Anthony 1 {{Decision |Scenario=Processing service provider modifies restricted data source }} {{Reasoning |Theme=Licensing }} 411 2011-02-21T16:38:31Z Anthony 1 {{Decision |Scenario=Processing service provider modifies restricted data source |Attribute=Licensability, |Environment=NETMAR operational. Provider wishes to add value to restricted data source. |Stimulus=Provider accesses one or more restricted data sources. |Response=No additional complexity for end-user }} {{Analysis |Decision=No new license terms |Pattern=soapatterns:policy centralization }} {{Reasoning |Reasoning=Within the context of the NETMAR domain inventory, services provided as part of the NETMAR infrastructure should avoid adding any non-standard access restrictions to their data. |Theme=Licensing }} 412 2011-02-21T16:38:44Z Anthony 1 {{Decision |Scenario=Processing service provider modifies restricted data source |Attribute=Licensability, |Environment=NETMAR operational. Provider wishes to add value to restricted data source. |Stimulus=Provider accesses one or more restricted data sources. |Response=No additional complexity for end-user }} {{Analysis |Decision=No new license terms |Pattern=soapatterns:policy centralization }} {{Reasoning |Reasoning=Within the context of the NETMAR domain inventory, services provided as part of the NETMAR infrastructure should avoid adding any non-standard access restrictions to their data. |Theme=Licensing }} 59 272 2011-02-08T15:30:51Z Anthony 1 Created page with "{{#get_web_data:url=http://semanticweb.org/wiki/Special:Ask/-5B-5BGermany-5D-5D/-3FBorders/-3FPopulation/-3FArea/format%3Dcsv/sep%3D, |format=csv with header|data=bordered co..." {{#get_web_data:url=http://semanticweb.org/wiki/Special:Ask/-5B-5BGermany-5D-5D/-3FBorders/-3FPopulation/-3FArea/format%3Dcsv/sep%3D, |format=csv with header|data=bordered countries=borders,population=population,area=area} * Germany borders the following countries and bodies of water: {{#arraymap:{{#external_value:bordered countries}}|,|x|[[Borders country::x]]}}. 273 2011-02-08T15:35:52Z Anthony 1 {{#get_web_data:url=http://semanticweb.org/wiki/Special:Ask/-5B-5BGermany-5D-5D/-3FBorders/-3FPopulation/-3FArea/format%3Dcsv/sep%3D, |format=csv with header|data=bordered countries=borders,population=population,area=area}} * Germany borders the following countries and bodies of water: {{#arraymap:{{#external_value:bordered countries}}|,|x|[[Borders country::x]]}}. {{#get_web_data:url=http://www.citeulike.org/json/group/14642/, |format=json|reftype=type,title=title}} {{#arraymap:{{#external_value:title}}|,|%%|[[Title::%%]]}}. 274 2011-02-08T15:38:20Z Anthony 1 {{#get_web_data:url=http://semanticweb.org/wiki/Special:Ask/-5B-5BGermany-5D-5D/-3FBorders/-3FPopulation/-3FArea/format%3Dcsv/sep%3D, |format=csv with header|data=bordered countries=borders,population=population,area=area}} * Germany borders the following countries and bodies of water: {{#arraymap:{{#external_value:bordered countries}}|,|x|[[Borders country::x]]}}. {{#get_web_data:url=http://www.citeulike.org/json/group/14642/, |format=json|data=reftype=type,title=title}} {{#arraymap:{{#external_value:title}}|,|%%|%%}} 275 2011-02-08T16:04:34Z Anthony 1 {{#get_web_data:url=http://semanticweb.org/wiki/Special:Ask/-5B-5BGermany-5D-5D/-3FBorders/-3FPopulation/-3FArea/format%3Dcsv/sep%3D, |format=csv with header|data=bordered countries=borders,population=population,area=area}} * Germany borders the following countries and bodies of water: {{#arraymap:{{#external_value:bordered countries}}|,|x|[[Borders country::x]]}}. {{#get_web_data:url=http://www.citeulike.org/json/group/14642/, |format=json|data=reftype=type,title=title}} {{#store_external_table:Citation For|Type={{{reftype}}}|Title={{{title}}} }} {{#ask: [[Citation For::+]] |?Title }} 276 2011-02-08T16:08:48Z Anthony 1 {{#get_web_data:url=http://www.citeulike.org/json/group/14642/ |format=json|data=reftype=type,title=title}} {{#store_external_table:Citation For|Type={{{reftype}}}|Title={{{title}}} }} {{#ask: [[Citation For::{{PAGENAME}}]] |?Title }} {{#get_web_data:url=http://discoursedb.org/wiki/Special:GetData/Fruits_data|format=CSV with header|data=name=Name,color=Color,shape=Shape}} {{#store_external_table:Is fruit in|Has name={{{name}}}|Has color={{{color}}}|Has shape={{{shape}}} }} Here are the results of a query to retrieve that data again. {{#ask:[[Is fruit in::+]]|? Has name|? Has color|? Has shape}} 277 2011-02-08T16:42:18Z Anthony 1 {{#get_web_data:url=http://discoursedb.org/wiki/Special:GetData/Fruits_data|format=CSV with header|data=name=Name,color=Color,shape=Shape}} {{#store_external_table:Is fruit in|Has name={{{name}}}|Has color={{{color}}}|Has shape={{{shape}}} }} Here are the results of a query to retrieve that data again. {{#ask:[[Is fruit in::+]]|? Has name|? Has color|? Has shape}} {{#get_web_data:url=http://www.citeulike.org/json/group/14642/ |format=json|data=reftype=type,title=title}} {{#store_external_table:Citation For|Type={{{reftype}}}|Title={{{title}}} }} {{#ask: [[Citation For::{{+}}]] |?Title }} 278 2011-02-08T16:42:53Z Anthony 1 {{#get_web_data:url=http://discoursedb.org/wiki/Special:GetData/Fruits_data|format=CSV with header|data=name=Name,color=Color,shape=Shape}} {{#store_external_table:Is fruit in|Has name={{{name}}}|Has color={{{color}}}|Has shape={{{shape}}} }} Here are the results of a query to retrieve that data again. {{#ask:[[Is fruit in::+]]|? Has name|? Has color|? Has shape}} {{#get_web_data:url=http://www.citeulike.org/json/group/14642/ |format=json|data=reftype=type,title=title}} {{#store_external_table:Citation For|Type={{{reftype}}}|Title={{{title}}} }} {{#ask: [[Citation For::+]] |?Title }} 279 2011-02-08T16:46:16Z Anthony 1 {{#get_web_data:url=http://www.citeulike.org/json/group/14642/ |format=json|data=reftype=type,title=title}} {{#store_external_table:Citation For|Cite Type={{{reftype}}}|Cite Title={{{title}}} }} {{#ask: [[Citation For::+]] [[Cite Type::THES]] |?Title }} 280 2011-02-08T16:48:27Z Anthony 1 {{#get_web_data:url=http://www.citeulike.org/json/group/14642/ |format=json|data=reftype=type,title=title,authors=authors}} {{#store_external_table:Citation For|Cite Type={{{reftype}}}|Cite Title={{{title}}}|Cite Authors={{{authors}}} }} {{#ask: [[Citation For::+]] [[Cite Type::THES]] |?Cite Title |?Authors }} 282 2011-02-08T16:50:01Z Anthony 1 {{#get_web_data:url=http://www.citeulike.org/json/group/14642/ |format=json|data=reftype=type,title=title,authors=authors}} {{#store_external_table:Citation For|Cite Type={{{reftype}}}|Cite Title={{{title}}}|Cite Authors={{{authors}}} }} {{#ask: [[Citation For::+]] [[Cite Type::THES]] |mainlabel=- |?Cite Title |?Cite Authors }} 283 2011-02-08T17:18:38Z Anthony 1 {{#get_web_data:url=http://www.citeulike.org/json/group/14642/ |format=json|data=reftype=type,title=title,authors=authors}} {{#store_external_table:Citation For|Cite Type={{{reftype}}}|Cite Title={{{title}}}|{{#arraymap:{{{authors}}}|,|%%|Cite Author=%%|,}} }} {{#ask: [[Citation For::+]] [[Cite Type::THES]] |mainlabel=- |?Cite Title |?Cite Author }} 60 281 2011-02-08T16:49:00Z Anthony 1 Created page with "[[has type::String]]" [[has type::String]] 61 291 2011-02-09T11:15:43Z Anthony 1 Created page with "{{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]=Licensing}} {{#ask: [[Category:Analysis]] [[Theme::..." {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]=Licensing}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} 296 2011-02-09T12:10:34Z Anthony 1 The EUMIS, when operational, will be responsible for taking data from many providers, combining them, adding value, and displaying the resulting data. Each of the data providers is expected to have a variety of restrictions, permissions and conditions attached to the use of its data. These may be expressed in a variety of non-standard formats. Respecting the rights of the data provider and the rights of the partners providing processing services on these data while allowing the end user access to the data in a way that meets his needs is a complex problem whose full solution is beyond the scope of the NETMAR project. However, in order to validate the NETMAR demonstration system against real-world requirements, and to suggest future paths by which we may address these issues, we will analyse the relevant forces in terms of representative scenarios from a number of stakeholders, i.e. end-user, data-provider, data-processor, and policy-maker. {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]=Licensing}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} 298 2011-02-09T14:02:26Z Anthony 1 The EUMIS, when operational, will be responsible for taking data from many providers, combining them, adding value, and displaying the resulting data. Each of the data providers is expected to have a variety of restrictions, permissions and conditions attached to the use of its data. These may be expressed in a variety of non-standard formats. Respecting the rights of the data provider and the rights of the partners providing processing services on these data while allowing the end user access to the data in a way that meets his needs is a complex problem whose full solution is beyond the scope of the NETMAR project. However, in order to validate the NETMAR demonstration system against real-world requirements, and to suggest practical future roadmaps <ref>M. Nilsson, From Interoperability to Harmonization in Metadata Standardization : Designing an Evolvable Framework for Metadata Harmonization. KTH, Media Technology and Graphic Arts, Media: KTH, 2010. [Online]. Available: http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-26057 </ref>by which we may address these issues, we will analyse the relevant forces in terms of representative scenarios from a number of stakeholders, i.e. end-user, data-provider, data-processor, and policy-maker. {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]=Licensing}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} <references/> 312 2011-02-11T13:47:19Z Anthony 1 The EUMIS, when operational, will be responsible for taking data from many providers, combining them, adding value, and displaying the resulting data. Each of the data providers is expected to have a variety of restrictions, permissions and conditions attached to the use of its data. These may be expressed in a variety of non-standard formats. Respecting the rights of the data provider and the rights of the partners providing processing services on these data while allowing the end user access to the data in a way that meets his needs is a complex problem whose full solution is beyond the scope of the NETMAR project. However, in order to validate the NETMAR demonstration system against real-world requirements, and to suggest practical future roadmaps<ref>M. Nilsson, From Interoperability to Harmonization in Metadata Standardization : Designing an Evolvable Framework for Metadata Harmonization. KTH, Media Technology and Graphic Arts, Media: KTH, 2010. [Online]. Available: http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-26057</ref> by which we may address these issues, we will analyse the relevant forces in terms of representative scenarios from a number of stakeholders, i.e. end-user, data-provider, data-processor, and policy-maker. {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]=Licensing}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} <references/> 319 2011-02-11T15:05:53Z Anthony 1 The EUMIS, when operational, will be responsible for taking data from many providers, combining them, adding value, and displaying the resulting data. Each of the data providers is expected to have a variety of restrictions, permissions and conditions attached to the use of its data. These may be expressed in a variety of non-standard formats. Respecting the rights of the data provider and the rights of the partners providing processing services on these data while allowing the end user access to the data in a way that meets his needs is a complex problem whose full solution is beyond the scope of the NETMAR project. However, in order to validate the NETMAR demonstration system against real-world requirements, and to suggest practical future roadmaps<ref>M. Nilsson, From Interoperability to Harmonization in Metadata Standardization : Designing an Evolvable Framework for Metadata Harmonization. KTH, Media Technology and Graphic Arts, Media: KTH, 2010. [Online]. Available: http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-26057</ref> by which we may address these issues, we will analyse the relevant forces in terms of representative scenarios from a number of stakeholders, i.e. end-user, data-provider, data-processor, and policy-maker. {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]=Licensing}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::Licensing]] |?Pattern |?=Decision |mainlabel=- }} <references/> 320 2011-02-11T15:09:17Z Anthony 1 /* Summaries */ The EUMIS, when operational, will be responsible for taking data from many providers, combining them, adding value, and displaying the resulting data. Each of the data providers is expected to have a variety of restrictions, permissions and conditions attached to the use of its data. These may be expressed in a variety of non-standard formats. Respecting the rights of the data provider and the rights of the partners providing processing services on these data while allowing the end user access to the data in a way that meets his needs is a complex problem whose full solution is beyond the scope of the NETMAR project. However, in order to validate the NETMAR demonstration system against real-world requirements, and to suggest practical future roadmaps<ref>M. Nilsson, From Interoperability to Harmonization in Metadata Standardization : Designing an Evolvable Framework for Metadata Harmonization. KTH, Media Technology and Graphic Arts, Media: KTH, 2010. [Online]. Available: http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-26057</ref> by which we may address these issues, we will analyse the relevant forces in terms of representative scenarios from a number of stakeholders, i.e. end-user, data-provider, data-processor, and policy-maker. {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]=Licensing}} {{#ask: [[Category:Analysis]] [[Theme::Licensing]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::Licensing]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::Licensing]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} <references/> 322 2011-02-11T15:34:23Z Anthony 1 The EUMIS, when operational, will be responsible for taking data from many providers, combining them, adding value, and displaying the resulting data. Each of the data providers is expected to have a variety of restrictions, permissions and conditions attached to the use of its data. These may be expressed in a variety of non-standard formats. Respecting the rights of the data provider and the rights of the partners providing processing services on these data while allowing the end user access to the data in a way that meets his needs is a complex problem whose full solution is beyond the scope of the NETMAR project. However, in order to validate the NETMAR demonstration system against real-world requirements, and to suggest practical future roadmaps<ref>M. Nilsson, From Interoperability to Harmonization in Metadata Standardization : Designing an Evolvable Framework for Metadata Harmonization. KTH, Media Technology and Graphic Arts, Media: KTH, 2010. [Online]. Available: http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-26057</ref> by which we may address these issues, we will analyse the relevant forces in terms of representative scenarios from a number of stakeholders, i.e. end-user, data-provider, data-processor, and policy-maker. {{Theme|Theme=Licensing}} 326 2011-02-11T16:06:53Z Anthony 1 The EUMIS, when operational, will be responsible for taking data from many providers, combining them, adding value, and displaying the resulting data. Each of the data providers is expected to have a variety of restrictions, permissions and conditions attached to the use of its data. These may be expressed in a variety of non-standard formats. Respecting the rights of the data provider and the rights of the partners providing processing services on these data while allowing the end user access to the data in a way that meets his needs is a complex problem whose full solution is beyond the scope of the NETMAR project. However, in order to validate the NETMAR demonstration system against real-world requirements, and to suggest practical future roadmaps<ref name="Nilsson2010From">M. Nilsson, From Interoperability to Harmonization in Metadata Standardization : Designing an Evolvable Framework for Metadata Harmonization. KTH, Media Technology and Graphic Arts, Media: KTH, 2010. [Online]. Available: http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-26057</ref> by which we may address these issues, we will analyse the relevant forces in terms of representative scenarios from a number of stakeholders, i.e. end-user, data-provider, data-processor, and policy-maker. {{Theme|Theme=Licensing}} 62 321 2011-02-11T15:31:51Z Anthony 1 Created page with "{{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[The..." {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {| !Decisions !Risks !Non-risks !Sensitivity points !Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} <references/> 323 2011-02-11T15:58:02Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {|padding="1em" !width="20%"|Decisions !width="20%"|Risks !width="20%"|Non-risks !width="20%"|Sensitivity points !width="20%"|Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} <references/> 324 2011-02-11T15:58:49Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {|padding="1em" border="1" !width="20%"|Decisions !width="20%"|Risks !width="20%"|Non-risks !width="20%"|Sensitivity points !width="20%"|Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} <references/> 325 2011-02-11T15:59:43Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {|cellpadding="1em" border="1" !width="20%"|Decisions !width="20%"|Risks !width="20%"|Non-risks !width="20%"|Sensitivity points !width="20%"|Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} <references/> 346 2011-02-14T16:30:01Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {|cellpadding="1em" border="1" !width="20%"|Decisions !width="20%"|Risks !width="20%"|Non-risks !width="20%"|Sensitivity points !width="20%"|Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |?Attribute |?Scenario |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 350 2011-02-14T16:40:09Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {|cellpadding="1em" border="1" !width="20%"|Decisions !width="20%"|Risks !width="20%"|Non-risks !width="20%"|Sensitivity points !width="20%"|Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} {{#ask: [[Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}]] |?Attribute |?Scenario |?From Scenario |?Decision |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 367 2011-02-17T17:24:32Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {|cellpadding="1em" border="1" !width="20%"|Decisions !width="20%"|Risks !width="20%"|Non-risks !width="20%"|Sensitivity points !width="20%"|Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} {{#ask: [[Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}]] OR [[Pattern::+]] |?Attribute |?Scenario |?From Scenario |?Decision |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 368 2011-02-17T17:26:04Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {|cellpadding="1em" border="1" !width="20%"|Decisions !width="20%"|Risks !width="20%"|Non-risks !width="20%"|Sensitivity points !width="20%"|Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} {{#ask: [[Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}]] |?Attribute |?Scenario |?From Scenario |?Decision |?Pattern |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 369 2011-02-17T17:30:24Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {|cellpadding="1em" border="1" !width="20%"|Decisions !width="20%"|Risks !width="20%"|Non-risks !width="20%"|Sensitivity points !width="20%"|Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} {{#ask: [[Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}.Decision]] |?Attribute |?Scenario |?From Scenario |?Decision |?Pattern |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 405 2011-02-18T17:02:45Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == {|cellpadding="1em" border="1" !width="20%"|Decisions !width="20%"|Risks !width="20%"|Non-risks !width="20%"|Sensitivity points !width="20%"|Tradeoffs |- |{{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|<br/>}} |{{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|<br/>}} |{{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|<br/>}} |{{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|<br/>}} |{{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|<br/>}} |} === Patterns used=== {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] [[Pattern::+]] |?Pattern |?=Decision |mainlabel=- |default=no patterns entered }} {{#ask: [[Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}]] |?Attribute |?Scenario |?From Scenario |?Decision |?Pattern |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 413 2011-02-21T16:46:06Z Anthony 1 /* Summaries */ {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == '''Decisions:''' {{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|,}} '''Risks:''' {{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|,}} '''Non-risks:''' {{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|,}} '''Sensitivity points:''' {{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|,}} '''Tradeoffs:''' {{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|,}} '''Patterns:''' {{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Pattern= }}|, |unique}} {{#ask: [[Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}]] |?Attribute |?Scenario |?From Scenario |?Decision |?Pattern |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 414 2011-02-21T16:49:06Z Anthony 1 {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == '''Decisions:''' {{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|,}} '''Risks:''' {{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|,}} '''Non-risks:''' {{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|,}} '''Sensitivity points:''' {{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|,}} '''Tradeoffs:''' {{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|,}} '''Patterns:''' {{#arraydefine:patterns| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Pattern= }}|, |unique}} {{#ask: [[Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}]] |?Attribute |?Scenario |?From Scenario |?Decision |?Pattern |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 415 2011-02-21T16:50:24Z Anthony 1 /* Summaries */ {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == '''Decisions:''' {{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|,}} '''Risks:''' {{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|,}} '''Non-risks:''' {{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|,}} '''Sensitivity points:''' {{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|,}} '''Tradeoffs:''' {{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|,}} '''Patterns:''' {{#arraydefine:patterns| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Pattern= }}|, |unique}} {{#arrayprint:patterns|,}} {{#ask: [[Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}]] |?Attribute |?Scenario |?From Scenario |?Decision |?Pattern |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 416 2011-02-21T16:50:47Z Anthony 1 /* Summaries */ {{#formlink:form=Analysis|link text=Add an Architectural Approach Description|link type=button|query string=Reasoning[Theme]={{{Theme|}}} }} {{#ask: [[Category:Analysis]] [[Theme::{{{Theme|}}}]] |mainlabel=Edit... |?Attribute=Quality Attribute |?Scenario |?Stimulus |?Response }} == Summaries == '''Decisions:''' {{#arraydefine:decisions| <!-- uses ArrayExtension to remove duplicated decisions --> {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |?Decision= |sep =,}} |, |unique}} {{#arrayprint:decisions|,}} '''Risks:''' {{#arraydefine:risks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep =, |?Risk= }}|, |unique}} {{#arrayprint:risks|,}} '''Non-risks:''' {{#arraydefine:nonrisks| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Non-risk=}}|, |unique}} {{#arrayprint:nonrisks|,}} '''Sensitivity points:''' {{#arraydefine:sensitivities| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Sensitivity= }}|, |unique}} {{#arrayprint:sensitivities|,}} '''Tradeoffs:''' {{#arraydefine:tradeoffs| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Tradeoff= }}|, |unique}} {{#arrayprint:tradeoffs|,}} '''Patterns:''' {{#arraydefine:patterns| {{#ask: [[From Scenario.Theme::{{{Theme|}}}]] |mainlabel=- |sep=, |?Pattern= }}|, |unique}} {{#arrayprint:patterns|,}} {{#ask: [[Theme::{{{Theme|}}}]] OR [[From Scenario.Theme::{{{Theme|}}}]] |?Attribute |?Scenario |?From Scenario |?Decision |?Pattern |format=graph |graphlabel=yes |graphlink=yes |graphsize=15,100 |rankdir=LR }} <references/> 63 330 2011-02-14T14:34:16Z Anthony 1 Created page with "One approach to this which is favoured by some of the partners, is to assume that the data to be used by the initial NETMAR demo is available without any restrictions which might..." One approach to this which is favoured by some of the partners, is to assume that the data to be used by the initial NETMAR demo is available without any restrictions which might cause problems for the end-user. 365 2011-02-17T17:13:47Z Anthony 1 One approach to this which is favoured by some of the partners, is to assume that the data to be used by the initial NETMAR demo is available without any restrictions which might cause problems for the end-user. This could be considered as an application of [[Pattern::soapatterns:Policy Centralization]] applied within the boundaries of the NETMAR [[soapatterns:Domain Inventory]]<ref>SOA Pattern of the Week (#7): Policy Centralization, InformIT, http://www.informit.com/articles/article.aspx?p=1356856</ref>. 366 2011-02-17T17:14:15Z Anthony 1 One approach to this which is favoured by some of the partners, is to assume that the data to be used by the initial NETMAR demo is available without any restrictions which might cause problems for the end-user. This could be considered as an application of [[Pattern::soapatterns:Policy Centralization]] applied within the boundaries of the NETMAR [[soapatterns:Domain Inventory]]<ref>SOA Pattern of the Week (#7): Policy Centralization, InformIT, http://www.informit.com/articles/article.aspx?p=1356856</ref>. <references/> 64 331 2011-02-14T14:36:34Z Anthony 1 Created page with "An obvious downside to restricting the scope of the NETMAR demo to data providers who are willing to provide data without restriction, is that there may not be many of these prov..." An obvious downside to restricting the scope of the NETMAR demo to data providers who are willing to provide data without restriction, is that there may not be many of these providers, thus limiting the usefulness of the demo. 65 360 2011-02-17T14:23:48Z Anthony 1 361 2011-02-17T14:25:42Z Anthony 1 uploaded a new version of &quot;[[File:NetmarCommunity.png]]&quot; 363 2011-02-17T14:29:48Z Anthony 1 uploaded a new version of &quot;[[File:NetmarCommunity.png]]&quot;: shrank to fit 421 2011-02-24T15:30:11Z Anthony 1 uploaded a new version of &quot;[[File:NetmarCommunity.png]]&quot; 422 2011-02-24T16:03:11Z Anthony 1 uploaded a new version of &quot;[[File:NetmarCommunity.png]]&quot; 423 2011-02-24T16:04:37Z Anthony 1 uploaded a new version of &quot;[[File:NetmarCommunity.png]]&quot; 66 371 2011-02-18T11:46:35Z Anthony 1 Created page with "{{{1}}}" {{{1}}} 373 2011-02-18T11:53:49Z Anthony 1 {{#set_internal:Uses Pattern| Usage={{{1}}}|Pattern={{{Pattern|}}} }} 375 2011-02-18T12:52:49Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{1}}}|Pattern=test} }} </includeonly> 376 2011-02-18T12:54:21Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{1}}}|Pattern=test }} </includeonly> 377 2011-02-18T13:30:27Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{1}}}|Pattern={{{2}}} }} </includeonly> 379 2011-02-18T13:38:29Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{1}}}|Pattern={{{Pattern|}}} }} </includeonly> 380 2011-02-18T13:47:08Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{1}}}|Pattern={{{Pattern|}}} }} {{{1}}} {{{2}}} {{{Pattern|}}} </includeonly> 381 2011-02-18T13:48:06Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{1}}}|Pattern={{{Pattern|}}} }} 1:{{{1}}} 2:{{{2}}} p:{{{Pattern|}}} </includeonly> 383 2011-02-18T13:51:07Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{Decision}}}|Pattern={{{Pattern|}}} }} 1:{{{1}}} 2:{{{2}}} p:{{{Pattern|}}} </includeonly> 386 2011-02-18T13:52:53Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{Decision}}}|Pattern={{{Pattern|}}} }} 1:{{1}} 2:{{2}} p:{{Pattern|}} </includeonly> 387 2011-02-18T14:10:37Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{Decision}}}|Pattern={{{Pattern|}}} }} 1:{{{1|}}} 2:{{{2|}}} p:{{{Pattern|}}} </includeonly> 388 2011-02-18T14:17:43Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{Decision}}}|Pattern={{{Pattern|}}} }} 1:{{{1|}}} 2:{{{Decision|}}} p:{{{Pattern|}}} </includeonly> 390 2011-02-18T14:24:10Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{Decision}}}|Pattern={{{Pattern|}}} }} 1:{{{1|}}} 2:{{{2|}}} p:{{{3|}}} </includeonly> 393 2011-02-18T14:39:16Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{Decision}}}|Pattern={{{Pattern|}}} }} 1:{{{Pattern|}}} 2:{{{Decision|}}} p:{{{3|}}} </includeonly> 394 2011-02-18T14:40:02Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{2}}}|Pattern={{{1}}} }} </includeonly> 395 2011-02-18T14:42:13Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{2|}}}|Pattern={{{3|}}} }} </includeonly> 397 2011-02-18T14:44:03Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{Decision}}}|Pattern={{{Pattern|}}} }} 1:{{{Pattern|}}} 2:{{{Decision|}}} p:{{{3|}}} </includeonly> 398 2011-02-18T14:44:59Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{3}}}|Pattern={{{2|}}} }} 1:{{{Pattern|}}} 2:{{{Decision|}}} p:{{{3|}}} </includeonly> 399 2011-02-18T14:45:50Z Anthony 1 <includeonly> {{#set_internal:Uses Pattern|Usage={{{3}}}|Pattern={{{2|}}} }} </includeonly> 67 424 2011-02-25T12:32:51Z Anthony 1 Created page with "http://www.semanticweb.org/ontologies/2010/01/core-soa.owl#|[http://www.opengroup.org/soa/standards/ontology.htm#_The_Open_Group_2 SOA Ontology] ..." http://www.semanticweb.org/ontologies/2010/01/core-soa.owl#|[http://www.opengroup.org/soa/standards/ontology.htm#_The_Open_Group_2 SOA Ontology] ...