Gaps in the body of knowledge of systems engineering
Ekstrom, Joseph J.
MetadataShow full item record
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.
Showing items related by title, author, creator and subject.
Pyster, A.; Ardis, M.; Frailey, D.; Olwell, D.; Squires, A. (2010);Two projects now underway have the potential to signi - cantly improve the worldwide software engineering workforce. The Integrated Software and Systems Engineering Curricu- lum Project (ISSEC) recently published Graduate ...
Nissen, Mark E. (Monterey, California. Naval Postgraduate School, 2001); NPS-GSBPP-01-003Knowledge is power. As the U.S. Navy is working to revise its strategy and tactics through knowledge-centric warfare, it is apparent that knowledge flow is key. However, our current state of understanding does not address ...
Kasser, Joseph; Hitchins, Derek; Huynh, Thomas V. (2009);This paper documents (1) the early phases of using systems engineering to develop a conceptual system – the system being developed is a systems engineering body of knowledge (SEBoK) and (2) the findings and opportunities ...