Information systems, software engineering, and systems thinking: challenges and opportunities

This article traces past research on the application of the systems approach to information systems development within the disciplines of information systems and software engineering. Their origins historically are related to a number of areas, including general systems theory. While potential improvement of software development practices is linked by some leading experts to the application of more systemic methods, the current state of the practice in software engineering and information systems development shows this is some way from being achieved. The authors propose possible directions for future research and practical work on bringing together both fields with systems thinking

Empirical Studies of Evolving Systems

This paper describes the results of the working group investigating the issues of empirical studies for evolving systems. The groups found that there were many issues that were central to successful evolution and this concluded that this is a very important area within software engineering. Finally nine main areas were selected for consideration. For each of these areas the central issues were identified as well as success factors. In some cases success stories were also described and the critical factors accounting for the success analysed. In some cases it was later found that a number of areas were so tightly coupled that it was important to discuss them together

A Model for Educating Systems Engineers

The full SEBoK 0.5 outline is provided online at: http://sebokwiki.org/index.php/SEBoK_0.5_Outline.This paper discusses a model for developing a master’s degree curriculum for systems engineering professionals. The model provides guidelines and recommendations that can be used for developing a new program or for modifying an existing program. The model was developed as part of the BKCASE (Body of Knowledge and Curriculum to Advance Systems Engineering) project to develop a guide to the Systems Engineering Body of Knowledge (SEBoK) and a Graduate Reference Curriculum for Systems Engineering (GRCSE). This paper describes the content of the SEBoK used to drive the core body of knowledge in a systems engineering program, and discusses the GRCSE purpose, organization, content, development process, and implementation.The BKCASE team is grateful for the involvement of U.S. Office of the Secretary of Defense and for their leadership and financial support for the BKCASE effor

Defense Acquisition System Simulation Studies

A systems engineering process model for the acquisition of large, complex systems for the U.S. Department of Defense (DoD) is being adapted for ongoing experiments in acquisition process policies. The discrete‐event simulation model of the larger “enterprise of acquisition” for weapon systems has a broad scope from program beginning through development. It reveals some of the challenges and risks in weapon system acquisition. Initially the model was used to evaluate potential policies as interventions and/or system changes in an Air Force context. The simulation results showed varying degrees of influence on program outcomes and suggested no single antidote exists for solving acquisition problems. Many of the negative outcomes reflected through cost and schedule overruns are due to the behavior of the acquisition system itself. A collaboration between the Air Force Institute of Technology (AFIT), the Naval Postgraduate School (NPS), and The Aerospace Corporation is underway to translate the model and adapt it for new considerations. Shortly we will propagate new model versions and results to the public, and use it for additional Air Force and Navy programs of concern