Difference between revisions of "Case Studies"

Revision as of 16:13, 9 May 2012

All Forsys participants are requested to submit one or more case studies to the wiki. June - Dec 2012 the Case Study Technical Committee will solicit and follow up on potential cases, answer any questions, provide feedback on drafts.

Purpose

The purpose of thes case studies is to identify 'lessons learned' which will contribute to the overall Forsys objective of providing guidelines on DSS development and use.

Sources

Two sources of cases are envisioned:

1. Unpublished cases contributed by Forsys members and STSMs: We ask that each Forsys participant try to identify one or more case from their personal knowledge and enter some basic information on it in the wiki (including lessons). We are in the proces of designing a semantic wiki form for members to enter this information.
2. Cases from the literature: We also ask that Forsys participants identify existing cases in the literature and extract lessons learned. We are in the process of reviewing possible databases to enter and store this information, such as Citeulike and Mendeley

Example

Similar to the DSS descriptions, we have identified certain types of information we would like to collect about each case. Please see this example case.

Case Study Template

You can use this Case Study Template to create your own case on the wiki.

The focus of each case should be on 'lessons learned', so please pay special attention to linking the case description supports the lessons list at the end of the case.

The Case Study Technical Committee is also working on a semantic wiki form for case entry, and we will send out the request to all Forsys members when the forms for entering case studies are ready.

More Information

For more details on the Forsys case studies, please see the case studies category page at the link below: