Repository logo

Browsing by Author "Marzolf, Gregory, committee member"

Now showing 1 - 2 of 2
  • Thumbnail Image
    ItemOpen Access
    Avoiding technical bankruptcy in system development: a process to reduce the risk of accumulating technical debt
    (Colorado State University. Libraries, 2023) Kleinwaks, Howard, author; Bradley, Thomas, advisor; Batchelor, Ann, advisor; Marzolf, Gregory, committee member; Wise, Daniel, committee member; Turner, John F., committee member
    The decisions made early in system development can have profound impacts on later capabilities of the system. In iterative systems development, decisions made in each iteration produce impacts on every future iteration. Decisions that have benefits in the short-term may damage the long-term health of the system. This phenomenon is known as technical debt. If not carefully managed, the buildup of technical debt within a system can lead to technical bankruptcy: the state where the system development can no longer proceed with its lifecycle without first paying back some of the technical debt. Within the schedule constrained development paradigm of iteratively and incrementally developed systems, it is especially important to proactively manage technical debt and to understand the potential long-term implications of decisions made to achieve short-term delivery goals. To enable proactive management of technical debt within systems engineering, it is first necessary to understand the state of the art with respect to the application of technical debt methods and terminology within the field. While the technical debt metaphor is well-known within the software engineering community, it is not as well known within the systems engineering community. Therefore, this research first characterizes the state of technical debt research within systems engineering through a literature review. Next, the prevalence of the technical debt metaphor among practicing systems engineers is established through an empirical survey. Finally, a common ontology for technical debt within systems engineering is proposed to enable clear and concise communication about the common problems faced in different systems engineering development programs. Using the research on technical debt in systems engineering and the ontology, this research develops a proactive approach to managing technical debt in iterative systems development by creating a decision support system called List, Evaluate, Achieve, Procure (LEAP). The LEAP process, when used in conjunction with release planning methods, can identify the potential for technical debt accumulation and eventually technical bankruptcy. The LEAP process is developed in two phases: a qualitative approach to provide initial assessments of the state of the system and a quantitative approach that models the effects of technical debt on system development schedules and the potential for technical bankruptcy based on release planning schedules. Example applications of the LEAP process are provided, consisting of the development of a conceptual problem and real applications of the process at the Space Development Agency. The LEAP process provides a novel and mathematical linkage of the temporal and functional dependencies of system development with the stakeholder needs, enabling proactive assessments of the ability of the system to satisfy those stakeholder needs. These assessments enable early identification of potential technical debt, reducing the risk of negative long-term impacts on the system health.
  • Thumbnail Image
    ItemOpen Access
    Leveraging operational use data to inform the systems engineering process of fielded aerospace defense systems
    (Colorado State University. Libraries, 2023) Eddy, Amy, author; Daily, Jeremy, advisor; Marzolf, Gregory, committee member; Miller, Erika, committee member; Wise, Daniel, committee member
    Inefficiencies in Department of Defense (DoD) Acquisition processes have been pervasive nearly as long as the DoD has existed. Stakeholder communication issues, funding concerns, large and overly complex organizational structures all play a role in adding challenges to those tasked with fielding, operating, and sustaining a complex aerospace defense system. As legacy defense systems begin to age, logistics and other supportability element requirements may change over time. While research literature supports the evidence that many stakeholders and senior leaders are aware of the issues and the DoD faces the impact those issues cause to mission performance, most research and attempts to improve the performance issues have been focused on high level restructuring of organizations or policy, processes, and procedures. There has been little research dedicated to identifying ways for working level logisticians and systems engineers to improve performance by leveraging operational use data. This study proposes a practical approach for working level logisticians and engineers to identify relationships between operational use data and supply performance data. This research focuses on linking negative aircraft events (discrepancies) to the supply events (requisitions) that result in downtime. This approach utilizes standard statistical methods to analyze operations, maintenance, and supply data collected during the Operations and Sustainment (O&S) phase of the life cycle. Further, this research identifies methods consistent with industry systems engineering practices to create new feedback loops to better inform the systems engineering life cycle management process, update requirements, and iterate the design of the enterprise system as a holistic entity that includes the physical product and its supportability elements such as logistics, maintenance, facilities, etc. The method identifies specific recommendations and actions for working level logisticians and systems engineers to prevent future downtime. The method is practical for the existing DoD organizational structure, and uses current DoD processes, all without increasing manpower or other resource needs.