Difference between revisions of "Plan the system architecture based on a broad view of future possibilities"
From COST Action FP0804: FORSYS
SeanGordon (Talk | contribs) (Undo revision 10382 by SeanGordon (talk)) |
SeanGordon (Talk | contribs) (Forsys_add_wg_subthemes.py) |
||
Line 1: | Line 1: | ||
{{Lesson | {{Lesson | ||
+ | |ID=13 | ||
|Has statement=Plan the system architecture based on a broad view of future possibilities rather than the ad hoc needs of particular funded projects | |Has statement=Plan the system architecture based on a broad view of future possibilities rather than the ad hoc needs of particular funded projects | ||
|Has evidence=The design process was rather ad-hoc and sequential, as a result of step-wise funding becoming available. Therefore, no overall scoping exercise was carried out at the start of the project and the general architecture of the system is inefficient and unstructured. | |Has evidence=The design process was rather ad-hoc and sequential, as a result of step-wise funding becoming available. Therefore, no overall scoping exercise was carried out at the start of the project and the general architecture of the system is inefficient and unstructured. | ||
− | |Has domain=Project management | + | |Has domain=Project management, Architecture |
|Has temporal scale=Medium term (tactical) | |Has temporal scale=Medium term (tactical) | ||
|Has spatial context=Spatial with no neighbourhood interrelations | |Has spatial context=Spatial with no neighbourhood interrelations | ||
Line 18: | Line 19: | ||
|Has actor perspective=Developer/Architect, Researcher | |Has actor perspective=Developer/Architect, Researcher | ||
}} | }} | ||
+ | [[Wg1::Architecture]] |
Latest revision as of 07:59, 9 September 2013
Lesson
ID | 13 |
---|---|
Has statement | Plan the system architecture based on a broad view of future possibilities rather than the ad hoc needs of particular funded projects |
Has evidence | The design process was rather ad-hoc and sequential, as a result of step-wise funding becoming available. Therefore, no overall scoping exercise was carried out at the start of the project and the general architecture of the system is inefficient and unstructured. |
Has consequences | |
Has recommendation for action | |
Has domain | Project management, Architecture |
Has DSS development stage | |
Has decision stage | |
Has temporal scale | Medium term (tactical) |
Has spatial context | Spatial with no neighbourhood interrelations |
Has spatial scale | Forest level, Stand level |
Has objectives dimension | Multiple objectives |
Has goods and services dimension | Market non-wood products, Market services, Market wood products, Non-market services |
Has decision making dimension | Single decision maker |
Has country | Ireland |
Has reference | |
Has related DSS | |
Has related case | Ireland-PractiSFM multi-resource inventory and decision support for private forest owners |
Has related lesson | |
Has other relevant information | |
Has working group theme | Dss development process |
Has DSS development | The design process was rather ad-hoc and sequential, as a result of step-wise funding becoming.Description of DSS development |
Has decision support techniques | The design process was rather ad-hoc and sequential, as a result of step-wise funding becoming.Decision support techniques |
Has knowledge management processes | The design process was rather ad-hoc and sequential, as a result of step-wise funding becoming.Knowledge management process |
Has support for social participation | The design process was rather ad-hoc and sequential, as a result of step-wise funding becoming.Support of social participation |
Has actor perspective | Developer/Architect, Researcher |
Has researcher role | |
Has user role | |
Has developer role |