Search

Global crises have forced the healthcare sector to advance the way they practise. Patient empowerment has emerged as one of the solutions to face these challenges. Nevertheless, patient empowerment is still lacking for accepted conditions, making it difficult to effectively promote within the healthcare system. This study aims to systemically map the concept of patient empowerment using principles of systems thinking with the Boardman Soft Systems Methodology that enables a graphical visualization (i.e., Systemigrams). This includes levels of patient empowerment and their relationship with other concepts such as health literacy, health providers, self‐management, patient characteristics and healthcare outcomes. This study contributes to the literature by (a) articulating a set of conditions to enable patient empowerment, (b) identifying the key concept that might influence the level of patient empowerment and (c) providing guidance and propositions for future research that can promote and further study patient empowerment. [ABSTRACT FROM AUTHOR]

Byline: Brian J. Sauser, Jose E. Ramirez-Marquez, Devanandham Henry, Donald DiMarzio In the United States (USA) National Aeronautics and Space Administration (NASA) and the USA Department of Defense (DoD) the Technology Readiness Level (TRL) scale is a measure of maturity of an individual technology, with a view towards operational use in a system context. A comprehensive set of concerns becomes relevant when this metric is abstracted from an individual technology to a system context. This paper proposes the development of a system-focused approach for managing system development and making effective and efficient decisions during a systems engineering life cycle. This paper presents a System Readiness Level (SRL) index that incorporates both the current TRL scale and an Integration Readiness Level (IRL) and provides a method for determining readiness of a system in the systems engineering life cycle. This paper concludes with a general discuss of the implication of the proposed SRL and how this may be applied to four case examples.

This paper presents the results of our research into cooperation in Government Extended Enterprises, a type of system of systems. The effort proposed and evaluated a novel theory that these decisions are the result of the interaction of four canonical forces—Sympathy, Trust, Fear, and Greed. A computational simulation involving the Stag Hunt game examined information sharing decisions in a series of key decision points in three large case studies. For the five hypotheses tested, exploratory data analysis and nonparametric statistical testing show strong support for three of the hypotheses (cooperation is positively correlated with actors’ levels of Sympathy and Trust and negatively correlated with actors’ levels of Fear) and moderate support for the fourth (cooperation is negatively correlated with actors’ levels of Greed). Indications are that the fifth hypothesis (cooperation is correlated with history of behavior) is not needed to explain observed behavior. Multiple correspondence analysis showed significant interactions both among pairs of forces and when a force is paired with decision making strategies. These results can form the basis for: 1) analysis of additional case studies; 2) development of an agent-based simulation; and 3) creation of training programs for current and future organizational leaders. [ABSTRACT FROM AUTHOR]

Access to government funding is one of the most effective ways to enhance the resilience for small- and medium-sized enterprises (SME) community after a disaster. Along these lines, a major focus of SME resiliency research has been on examining factors needed to keep an SME open after a disaster. This makes sense as SMEs are critical to community recovery. It seems logical that the severity of a disaster would indicate the impact to a community. Using a systems thinking methodology, we developed a hypothesis that this correlation of severity to impact breaks down over time, causing the community to quickly spiral into trouble. This paper presents an agent-based model to test our hypothesis. The results indicate the impact to a community becomes much more extreme after a threshold or 'tipping point' is crossed. [ABSTRACT FROM AUTHOR]

This study applies a systems thinking approach to sustainment-phase redesign planning for large-scale, complex, sustainment-dominated systems (SDSs) found in the airline, aerospace and defense, healthcare, and utilities industries. Maintaining the SDS's effectiveness throughout its long life presents a significant engineering and business challenge. This research contributes to the literature by developing an academically rigorous redesign-planning framework (RPF) through the lens of management and systems theories and the use of the grounded theory, research methodology. With the RPF, engineering managers can now simultaneously consider key issues, improvement opportunities, and risks of SDSs to develop and execute strategic, sustainment redesign plans that improve SDS performance at a lower lifecycle cost. [ABSTRACT FROM AUTHOR]

At the 2006 IEEE International Conference on Systems of Systems Engineering, Boardman and Sauser presented a set of characteristics based on an integrative review of the literature. These characteristics are the foundation of the Boardman–Sauser system of systems (SoS) theory. We accept this theory as the basis of collaborative SoS and desire a means to validate this assertion. While numerous simulations have been published, the target SoS is usually a specific implementation. These specialized simulations produce results applicable primarily to the system under study but not necessarily SoS in general. Simulating the mathematical model of the Boardman–Sauser SoS theory in the form of an agent-based model produces results that can be compared with chemical reactions. This paper contends that the formation of molecules from atoms is an analog of systems forming any collaborative SoS, which we call our molecule organization model. The result is a supported logical argument that validates the Boardman–Sauser SoS theory as definitive of a generic SoS with behavior applicable to collaborative SoS. This paper seeks to provide a unique contribution to the SoS body of knowledge by increasing our understanding of collaboration in an SoS, so we may better understand their health, maintenance, replication, and evolution. [ABSTRACT FROM PUBLISHER]

This publication contains reprint articles for which IEEE does not hold copyright. Full text is not available on IEEE Xplore for these articles. [ABSTRACT FROM PUBLISHER]

A fundamental challenge for system engineers is to capture a problem with an effective model or framework and then facilitate transferring the information of that captured problem to practical systems engineering tools and methods. The early problem definition phase requires an application of systems thinking with adequate modeling tools and methods. Then, the later problem definition phase and early system architecting phase requires transferring the captured problem to systems engineering tools and methods through emerging techniques such as model-based systems engineering (MBSE) using SysML (MBSE is the practice of using a modeling tools to capture systems engineering diagrams). This paper presents a method for capturing a problem through systemigrams and the Boardman soft systems methodology and then directly translating the systemigrams into SysML diagrams. With MBSE increasing in usage, this method could provide a time savings opportunity during model development along with the possibility of lowering information distortion or loss that can occur during transformation of systems thinking to systems engineering activities. This paper includes a case study which demonstrates how the proposed approach was applied on a problem being considered by the U.S. Army—Contingency Basing for Small Combat Units. Finally, this paper will provide the conclusion on the development of the method and describe future research directions that can allow systems thinking and MBSE to function in a congruent methodology. [ABSTRACT FROM AUTHOR]

In order to understand how we may engineer system of systems (SoS), we will have to rely significantly on our abilities in modeling and simulation. While there are some models of non-specific SoS, few attempts have been made to demonstrate these models with simulation. Simulations of SoS are usually specific cases. Likewise, in the description of a SoS, most of the approaches have focused on their characterization, yet this characterization has not been greatly utilized as an underlying feature in the modeling and simulation of SoS. We review different modeling techniques and use two converse techniques, i.e. agent-based and event-based modeling, to run a simulation of hypothetical systems collaborating into a SoS. The results of the empirical comparison indicate an agent-based modeling approach would achieve a characterization model better with validation achieved through an event-based approach. [ABSTRACT FROM AUTHOR]

ABSTRACT The Schelling segregation model is a well-established representation of social issues in a neighbourhood. On the basis of the systems approach, a model of system of systems (SoS) that is validated through comparison with the Schelling model and applies to more neighbourhoods is proposed. The systems model of an SoS empirically demonstrates the potential for conflict to arise as the autonomy of systems within a geographically distributed SoS increases. The results may contribute to future international policy as well as ecological management. Copyright © 2012 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

The designation System of Systems (SoS) applies to many types of system structures. We consider a collaborative SoS, which forms through the apparent voluntary decisions of its component systems. However, many collaborative SoS do not possess the intellectual capacity to make human-like decisions. To understand the formation of SoS better, properties are modeled mathematically. An agent-based model (ABM) simulation validates the model via a mock chemical reaction of atoms forming molecules. In the engineering and management of these systems, this information allows better decisions that support or deny SoS formation. [ABSTRACT FROM PUBLISHER]

As part of this, we identified some of the possible constituents of the systemic risk of SoS. It is valuable to note that the constituents could vary from case-to-case and are also time-dependent due to the dynamic nature of SoS and the environment in which it operates. Furthermore, the authors pointed out the importance of the application of systemic risk in the SoS domain and thus understanding the interconnectedness between the various constituents. [ABSTRACT FROM PUBLISHER]

New product development is complex. Companies often underestimate this complexity and do not invest in efforts to fully understand their new product development system and the ramifications of running that system without control. New product development involves dedicated resources, from multiple disciplines, often for long periods of time. These resources are precious and decisions about how they are utilized should be informed. This work pursues a simulation model of a full new product development pipeline, incorporating the common organizational pathology of taking on too many projects, consistent with the literature and the researchers' experience. This project considers the fact that queues may not occur in all areas of new product development and that resources can be allocated at levels greater than 100%. The phenomenon of decreased efficiencies, when capacity of any discipline is exceeded, has been incorporated to show how the pipeline slows down and unplanned costs increase. [ABSTRACT FROM AUTHOR]

Prescriptive metrics have been widely accepted and used in engineering management to assess the progress and success of engineering efforts. However, these types of metrics have two major challenges: human subjectivity and confidence in data estimates. In this paper we use a system-focused prescriptive metric entitled System Readiness Level (SRL) [a function of Technology and Integration Readiness Levels (TRL/IRL)], to propose a probabilistic approach to estimating the development maturity of a system of interest. In order to reduce the subjective impact, we propose a probabilistic method by assigning probability distributions to the estimated TRLs and IRLs to reflect the reality of evaluators' subjective estimates. Based on these probability distributions of TRLs and IRLs, a Monte-Carlo simulation methodology is used to assess the maturity status of the whole system and its components. An illustrative example is examined to show the proposed methodology and to investigate its implication to engineering management. The paper concludes with a discussion of the added value of this new methodology, its limitation, and future work. [ABSTRACT FROM AUTHOR]

Recently, a system maturity scale, i.e., system readiness level (SRL), was proposed to measure the maturity that a system achieves during development. However, this SRL assesses maturity for systems from only a single function and capability perspective, and is unable to assess maturity for multifunction multicapability (MFMC) systems. With ever increasing systems that provide multiple functions and capabilities, it is challenging for managers to properly allocate resources to ensure the achievement of critical capabilities and functions. In order to prioritize the allocation of resources for component development, it is common to perform importance analysis during system development and maintenance. Therefore, this paper first enhances the original SRL definition for maturity assessment at the capability, function, and system levels, and then, proposes the use of component importance analysis for the identification of the most important components for system development. This paper approaches component importance by introducing three important measures with respects to three main factors: technology readiness level/integration readiness level, developing cost, and developing effort. The paper uses an illustrative example of a MFMC system to show the proposed methodology and enhanced definitions and concludes with a discussion of the added value and future work. [ABSTRACT FROM PUBLISHER]

Enterprises exist in webs of alliances, partnerships, and cooperatives and must necessarily reflect their strategic intent at the level of these networks. This network level strategic intent is fundamental to developing security strategies and operational policies that consider emergent, decentralized behavior of the enterprise as a positive contribution to ensuring resilience in enterprise service. Recent strategies of the Department of Homeland Security (DHS) have articulated that our homeland security solutions will only be found in the national enterprise via a collective and shared responsibility that stretches from national to local to community involvement. This paper presents our results from using the Boardman Soft Systems Methodology (BSSM) and supporting graphical systemic diagramming technique, i.e., systemigrams, to better understand and identify the significant elements and their relationships within the small vessel security enterprise as articulated by the DHS Small Vessel Security Strategy. BSSM and systemigrams allow us to help identify organizational and communication bottlenecks, provide stakeholders with the knowledge about the architectural structure of the extended network of activities in their environment, and equip system analysts with relevant information on understanding systemic issues with consideration of resilience factors. We conclude by identifying what we believe to be key observations in the realization of this strategy between maritime security partners and the small vessel community via maritime governance that should be embraced and not mitigated. [ABSTRACT FROM AUTHOR]

The concept of resilience has been used among a diversity of fields with a myriad of definitions. A systems approach to discovering the essence of resilience could aid in understanding its concept and provide opportunities to distinguish its systemic characteristics that can be identified, planned, or analyzed regardless of the field in which it is considered. In order to begin executing such an approach, a comprehensive study of the literature on the topic and circumstances in which resilience has been used or referred to in several fields of studies is necessary. In this paper, the conceptual common denominator of resilience is identified based on the results of a literature survey and according to the way it has been used in different contexts. This basis leads to the objective of this effort, and that is to recognize the systemic characteristics of resilience and demonstrate the defining of a universally accepted definition. Using a soft systems methodology and a supporting systemic diagramming technique entitled Systemigrams, we present the formulation of defining resilience in maritime homeland security. In this effort, many stakeholders contributed their thoughts and concerns on the meaning and operational use of resilience through a repetitive process to formulate a definition of the term. The result of this methodic approach is a general definition of resilience that has been refined in a collaborative environment via the application the Boardman Soft Systems Methodology. [ABSTRACT FROM AUTHOR]

The purpose of this paper is to describe a methodology that enables systems engineers or program managers to formulate a system-wide optimal development plan in order to facilitate monitoring and evaluation of the development process in terms of the actual readiness of the system. It proposes the use of the System Readiness Level (SRL) scale to measure the maturity of a system composed of technological elements, which are being developed based on cost-driven strategies (as opposed to time-to-market-driven strategies). A constrained optimization model is used to identify which critical technology elements and integration links can be matured to which levels at a particular time such that the development costs are minimized while a targeted SRL value is attained on schedule. While the algorithm does not necessarily reduce the total cost of development, it is able to find the minimal amount of expenditures which will achieve the desired maturity level during the earlier part of the development process. Essentially, it shifts the rest of the expenditures towards the latter part of the development during which model-based integration and testing procedures which have been suggested by others can be applied to reduce costs and time further. This can be a useful option to have when there is substantial uncertainty with the system due to its high novelty and technological content. As a value added approach, the model gives the systems engineer the information needed to understand what a delay may mean to development, so a more informed decision can be made. The paper concludes by discussing the possible use of the optimal development plan to monitor and control the progress of systems under development. © 2009 Wiley Periodicals, Inc. Syst Eng [ABSTRACT FROM AUTHOR]

The strategic objective of a test and evaluation (T&E) organization is to detect defects, which must be fixed prior to system deployment in order to meet the operational needs and achieve customer satisfaction. Numerous process improvement models have been developed and applied to address the issue of preventing “critical” defects getting to the field. However, the escalating costs of system deployment (especially in government programs), due to critical defects found in the field, continues to be a major quality issue affecting customer satisfaction. The failure of programs to meet quality and performance objectives has been shown to be related to inadequate planning and an ineffective program management strategy. Thus, for a T&E organization, the program management strategy can greatly influence overall performance goals. While current literature on T&E quality improvement focuses primarily on T&E technical tools, equipment, and processes, little to no attention has been paid to integrating program management into the T&E organization's strategy. We intend to demonstrate in this paper that taking a holistic view of both T&E and program management (PM) activities using the tools of systems thinking can provide new insights to understand and create a more effective T&E execution strategy. Using Boardman's Soft Systems Methodology and Systemigrams (systemic diagrams), we evaluate the unification of a Federal Aviation Administration's T&E program management into its T&E strategy. The resultant Systemigram model represents the alignment of T&E with program management. We conclude with recommendations on how other organizations may modify their T&E execution strategy to achieve better customer satisfaction. © 2009 Wiley Periodicals, Inc. Syst Eng [ABSTRACT FROM AUTHOR]

This paper demonstrates a method that can be used to analyze the degree to which an organization's systems engineering capabilities meet government-industry defined systems engineering needs. To demonstrate this process, using universities as the case study, we summarize secondary research completed for nine institutions from various countries that offer systems engineering graduate level programs in the space domain. Next, we select a Masters degree program from three universities, one from each country, and map their space-based systems engineering courses to the 37 systems engineering capabilities within the 10 systems engineering competencies. These capabilities represent the knowledge, skills, and behaviors that systems engineers are expected to possess and perform as a part of their job. We then review a process for a more detailed mapping of the curriculum to one of four levels of proficiency within each capability, using the Stevens Institute of Technology as the example. The result is a systems engineering competency-based approach that can be used by universities or companies to compare the “as is” state of their systems engineering capabilities development against a government-industry defined set of needs to identify and address gaps or opportunities in the curriculum, training, or experience of their students and/or employees. © 2009 Wiley Periodicals, Inc. Syst Eng [ABSTRACT FROM AUTHOR]

This paper will propose to do as von Bertalanffy once did, and that is to draw on the biological sciences, now hugely advanced beyond that ever imagined by von Bertalanffy and his peers, and use its findings, architectures, and emergent behaviors to argue for a biology of system of systems (SoS). We seek a science and approach that we believe will provide richer insight into SoS failure, "health"maintenance, repair, replication, growth, and mutation--all those features of the evolution of systems which constantly challenge us and which, thus far, we have only been able to explain via macrolevel models and tools. We propose to go deeper into the structure of these systems and to discover their "DNA" (building blocks), thus establishing a foundation to understand their behavior using biological analogies, which we believe will turn out to be more than metaphors. We assert that these systems have microstructures which will explain their individual life cycle and their communal ecology. [ABSTRACT FROM AUTHOR]

In order to optimize the process of complex system integration, it is necessary to first improve the management of the process. This can be accomplished through the use of a generally understood metric. One such metric is Technology Readiness Level (TRL), which is used to determine technology maturity, but does not address integration maturity. Integration Maturity Metric (IMM) requirements are developed through review of aerospace and defense related literature. These requirements are applied to currently existing integration maturity metrics, and the proposed Integration Readiness Level (IRL). IRL is then refined to fully meet these requirements, and applied to three aerospace case studies, along with the other identified metrics, to compare and contrast the results obtained. [ABSTRACT FROM AUTHOR]

Philosophers have studied paradoxes for millennia. The term paradox is appearing increasingly outside of philosophy, and researchers seek to understand them in common situations. By understanding these phenomena, systems engineers may develop better strategies to deal with them when encountered in business or projects. However, what is meant by the term systems paradox and are there different types? Towards this goal, this paper will present definitions of systems from systems science and paradox from philosophy in a quest to define systems paradox. A paradox that impacts some objective of a system is designated a systems paradox. Then a typology of systems paradoxes will be proposed and described using set theory. Various examples provide a demonstration of the typology. [ABSTRACT FROM AUTHOR]

The operating environment for test and evaluation (T&E) is changing with advancements in technology affecting users' needs and systems development approaches. These changes demand new strategies for conducting T&E to keep pace with the changing environment. However, collecting and managing appropriate data could pose serious challenges to T&E programs that do not have established processes. To address this issue, the authors conducted a systemic analysis of previous operational T&E programs within a government T&E organization to determine the extent to which integration of project management with technical processes contribute to making T&E execution easier. The research analysis demonstrates that the application of project management practices contributes to achieving success in executing T&E programs within the Federal Aviation Administration. This research contributes to the field by identifying the critical dimensions of project management that contribute to achieving operational T&E program success. [ABSTRACT FROM AUTHOR]

Based on preliminary research of the experience of groups like the policy community, we believe that engineers, especially those developing systems of systems, may benefit from an appreciation of paradox. For example, the policy community embraces and leverages paradox to address problems that might otherwise prove intractable. We believe that policy makers will also benefit from systems thinking. We briefly review the definition of paradox, introduce its potential to generate "breakthrough" thinking for innovative solutions, and illustrate some contemporary engineering problems that contain paradoxes. We then recount several historical examples of successfully applied paradoxical thinking, illustrate the paradoxes inherent in two fundamental systems thinking constructs, and postulate a three-step approach to leveraging paradox in problem solving situations. We close by posing some key follow-on questions and a research program designed to support the development of paradox-related training in both systems engineering and policy development. [ABSTRACT FROM AUTHOR]

A critical role of a test and evaluation (T&E) organization is to detect defects and remove them from systems prior to deployment to meet operational needs and achieve customer satisfaction. However, the escalating cost of systems deployment (especially in government programs) due to critical defects found in the field continues to be a major quality issue affecting customer satisfaction. This inability of programs to meet quality and program performance objectives has been linked to inadequate coordination of T&E programs. While current literature on T&E quality imp movement focuses primarily on T&E technical tools, equipment, and processes, little to no attention has been paid to integrating program management with T&E. This article contributes to the state of practice by adopting a holistic approach that uses a Systemigram to analyze the current state of practice and to propose a modified model to improve the T&E program management strategy. [ABSTRACT FROM AUTHOR]

The requirements of various stakeholders associated with System of Systems (SOS) are constantly changing. Consequently, the shareholders priorities of return and risk continuously shift. However, their expectations of gaining value from the SoS are enhancing. One way of enhancing value from the SoS is by having the tight amount of flexibility associated with it. Flexibility can be defined as the ability of a system to be able to adapt and cope with the changing environment. SoS flexibility means creating options at various levels, developing ways and means of change across the range of options. One possible way of creating enterprise flexibility is by outsourcing certain functions which would help affect the flexibility of an organization. The outsourcing done might also have an effect on each of the building blocks of SoS Flexibility. In this paper, we will look at how outsourcing could affect each of the building blocks of SoS flexibility as well as show whether it is beneficial or not for an organization to outsource depending on how it affects their flexibility. We also come up with a matrix to show the effects of insufficient as well as excessive outsourcing on the overall functioning of the SoS. [ABSTRACT FROM AUTHOR]

Today's fast-paced and competitive business environment requires a shift from a disintegrated and closed enterprise structure to a more dynamic and flexible enterprise structure. Enterprise flexibility is the ability of an enterprise to adapt to changing business and stakeholder requirements more efficiently, easily and rapidly. This paper proposes a model to create enterprise flexibility using service oriented architecture approach. This model is based on two key enablers of enterprise flexibility. First enabler is the capability of an enterprise to connect people, processes, and information in a way that allows enterprise to become more flexible and responsive to the dynamics of its environment, stakeholders, and competitors. This requires integration within the enterprise and across the partners, suppliers, and customers of the enterprise. Second enabler is alignment of information technology and business goals. This requires simplification of the underlying technology infrastructure and creation of a consolidated view of and access to, all available resources in the enterprise. This can be achieved with well-defined enterprise architecture. Based on these two key enablers, we outline our theoretical model explaining the relationship between the attributes of Service Oriented Architecture and enterprise flexibility as a function of agility, efficiency, and adaptability. This paper further discusses the possible expansion of this theoretical model to develop an enterprise architecture framework based on service oriented architecture at the enterprise level. [ABSTRACT FROM AUTHOR]

Based on preliminary research of the experience of groups like the policy community, we believe that engineers, especially those developing systems of systems, may benefit from an appreciation of paradox. For example, the policy community embraces and leverages paradox to address problems that might otherwise prove intractable. We believe that policy makers will also benefit from systems thinking. We briefly review the definition of paradox, introduce its potential to generate "breakthrough" thinking for innovative solutions, and illustrate some contemporary engineering problems that contain paradoxes. We then recount several historical examples of successfully applied paradoxical thinking, illustrate the paradoxes inherent in two fundamental systems thinking constructs, and postulate a three-step approach to leveraging paradox in problem solving situations. We close by posing some key follow-on questions and a research program designed to support the development of paradox-related training in both systems engineering and policy development. [ABSTRACT FROM AUTHOR]

Knowledge for managing projects, for the development of systems, has not kept pace with the increasing complexity and integration of the projects themselves. This increased complexity has permitted some to reason distinctions between systems projects and propose a form of system called a "system of system" (SoS). Faced with this situation, we argue that a single point solution cannot be the answer to how to manage these systems. We suggest the remedy is a form of project management predicated on four principles that underline SoS thinking: problem demystification, legacy assessment, state-space solutioning, and integration framework. Using these principles as a foundation, we provide a set of characteristics (i.e. autonomy, belonging, connectivity, diversity, and emergence) that can be applied as fundamental building blocks to actualize the management of an SoS, or any system. More importantly, we present an architecture predicated on the paradoxes that exist in realizing and formalizing these characteristics. [ABSTRACT FROM AUTHOR]

In order to remain competitive, organizations have to make themselves accessible to a diversity of alternatives, which could be a direct influence on their flexibility; however, flexibility introduces a new context by which these organizations manage the systems they realize. In this paper, we present a theoretical perspective on the management of flexibility of a type of system called a System of Systems (SOS). We first define flexibility as it has been described with respect to the management of a system, how this may relate to SoS and establish that there is a deficiency for understanding how the SoS should be managed near the optimization region of flexibility. We then propose a theoretical model for managing flexibility in a SoS that begins to address this optimization region of flexibility. We demonstrate our model with an empirical case study of the New York City Yellow Cab SoS and conclude with potential implications this research has on flexible systems management. [ABSTRACT FROM AUTHOR]

In today's dynamic competitive business environment, project reviews are fundamental for most organizations ability to complete their projects successfully; however, it is important to know how to execute project reviews effectively. One important quality of an effective project review is the independence of its reviewers-the central focus of this article. Through four case studies chosen from different scenarios, we have shown that, despite independence being an important quality of project reviews, most organizations choose reviewers who are within their own social network. This issue can partially be resolved by the use of knowledge network theory and analysis (KNA), which will help us characterize relationships which can significantly influence the effective execution of project reviews. [ABSTRACT FROM AUTHOR]

This paper proposes the use of a new Systems Readiness Level (SRL) scale for managing system development and for making effective and efficient decisions during the defense acquisition process. This scale incorporates both the current Technology Readiness Level (TRL) of the Department of Defense (DoD) and the concept of an Integration Readiness Level (IRL) developed by Stevens Institute of Technology. The paper describes the foundations for the SRL and how it is formulated; it also demonstrates the SRL's application within the defense acquisition process using a sample case with notional readiness values. [ABSTRACT FROM AUTHOR]

In some costly failures of projects within the National Aeronautics and Space Administration (NASA), NASA has been criticized for their improper use or lack of independent reviews in projects. To begin to understand some prospective success characteristics of project reviews within NASA and potentially across engineering management, a qualitative case study methodology was used with four NASA projects to identify key attributes of independent project reviews. These attributes were identified in relation to categories of reviewer, reviewee, and the review type. Within each of these categories, attributes were identified and characterized as size, competence, independence, authority, culture, and formality. [ABSTRACT FROM AUTHOR]