Work in process: A Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE&amp;#x2122;)

Squires, Alice; Hutchison, Nicole; Pyster, Art; Olwell, David H.; Enck, Stephanie; Ferris, Timothy L.J.; Gelosh, Don

doi:10.1109/syscon.2011.5929066

Cited by 4 publications

(1 citation statement)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Also, in [36][37][38][39], stakeholders use BOK to develop academic programs where parameters can be synthetized to describe knowledge. Finally, BOKs such as the ones presented in [40][41][42][43][44][45][46][47][48][49][50][51], show further structures and guidelines to describe knowledge.…”

Section: Related Workmentioning

confidence: 99%

Open BOK on Software Engineering Educational Context: A Systematic Literature Review

et al. 2020

View full text Add to dashboard Cite

In this review, a Systematic Literature Review (SLR) on Open Body of Knowledge (BOK) is presented. Moreover, the theoretical base to build a model for knowledge description was created, and it was found that there is a lack of guidelines to describe knowledge description because of the dramatically increasing number of requirements to produce an Open BOK, the difficulty of comparing related BOK contents, and the fact that reusing knowledge description is a very laborious task. In this sense, this review can be considered as a first step in building a model that can be used for describing knowledge description in Open BOK. Finally, in order to improve the educational context, a comparison among BOK, structure, and evolution is conducted.

show abstract

Section: Related Workmentioning

confidence: 99%

Open BOK on Software Engineering Educational Context: A Systematic Literature Review

et al. 2020

View full text Add to dashboard Cite

show abstract

Gaps in the Body of Knowledge of Systems Engineering

Squires

Olwell

Roedler

et al. 2012

INCOSE International Symp

View full text Add to dashboard Cite

Abstract. The boundaries of systems engineering are evolving as system related needs evolve. These 'fuzzy' boundaries result in gaps between what users in the systems engineering community need and what the body of knowledge of systems engineering provides. This paper covers various use cases of the body of knowledge of systems engineering and explores gaps in the existing knowledge base in two areas: 1) related disciplines, and 2) emerging systems engineering topics.

show abstract