Overview – Provides an overview of the case study including system type, application domain and/or area
Domain Background – Provides a background on the associated industry, including unique terminology, pertinent history of the event or case, progression of the field or system development or capability, other applicable areas
Analysis of Case Study – Provides information about the completeness, consistency, value, development process, and rigor
Case Study Description – This is the location for the main content of the description. As the content is described, references to the SEBoK and sections of the case study are included.
Summary – Any sort of ‘wrap up’ comments and insights or perhaps lessons learned
References – Will need these to map appropriate references for this article in the wiki, includes a link to the actual case study (if applicable)
Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ (title). Please do not include version numbers in the links.
All additional references should be listed in alphabetical order.