* Maturity can only be measured on existing software * For source selection this means COTS, GOTS... more * Maturity can only be measured on existing software * For source selection this means COTS, GOTS, NDI, prototype, experimental * Initial set of software product maturity characteristics defined * Maturity evaluation complex - dependent on context and related factors * Agile approaches may make it easier to determine software product maturity.
Product Focused Software Process Improvement, 2002
... I believe some of the findings of the USC workshop are debatable, and represent mispercepti... more ... I believe some of the findings of the USC workshop are debatable, and represent misperceptions on the part of ... Agile processes evolve, but they generally do so via their own experience, generally within a team or a project. ... Agile Meets CMMI: Culture Clash or Common Cause ...
There is an increasing emphasis on rapid development of products and services to meet immediate, ... more There is an increasing emphasis on rapid development of products and services to meet immediate, mission-critical needs. In order to reduce the development cycle, "agile" approaches are needed. There are methods, proc-esses, and tools (MPTs) already in existence, and gaps where new solutions are needed that work within specific contexts. For a context where developers with unstable requirements must react quickly to stakeholder needs to build new capabilities that rely on existing systems in a wide range of operational environments, applicable MPTs were investigated using an online survey on approaches to requirements, stakeholders, sustainment and integration. Participants provided information on their experience and development environment, allowing responses to be evaluated within the context of interest. Scrum, Rapid Prototyping, and Continuous Integration emerged as promis-ing MPTs. Further investigation included follow-up interviews with survey participants in simila...
The current state of the art of aircraft systems integration is similar to the traditional serial... more The current state of the art of aircraft systems integration is similar to the traditional serial software engineering waterfall method. Agile methods transformed software engineering with a focus on incremental iterative value added design. This paper reviews selected non software agile case studies for lessons that are applicable to implementing agile methods to transform the aircraft systems integration process. (C) 2013 The Authors. Published by Elsevier B. V. and/or peer-review under responsibility of Georgia Institute of Technology
The systems engineering research center university affiliated research center (SERC-UARC) at Stev... more The systems engineering research center university affiliated research center (SERC-UARC) at Stevens Institute has been tasked to evaluate the effectiveness of the systems and software engineering processes, methods and tools (MPTs) used in US department of defense acquisition and development programs. This paper presents the selection and evaluation process, describes its evolution based on changing sponsor needs, and presents additional
There is good evidence from experience reports and other literature that the lean flow concepts o... more There is good evidence from experience reports and other literature that the lean flow concepts of on-demand, value-based scheduling and limited work-in-progress are highly effective in many instances of software development. The question remains, however, if they are equally applicable to the systems and enterprise engineering found in large or complex system environments. This paper builds on previous conceptual work to describe specific applications of the concepts to support coordination of systems engineering activities within large-scale system acquisition, development and evolution. Using a surrogate environment derived from the complex interactions of IT, embedded systems, and human activities in a large multifacility hospital system, we provide examples of how integrated kanban-like constructs can be created at each systems engineering level from an individual project through the complete capabilities portfolio.
2005 International Symposium on Empirical Software Engineering, 2005., 2005
... This prototype will evolve into a set of requirements that will be implemented in an operatio... more ... This prototype will evolve into a set of requirements that will be implemented in an operational system according to DoD specifications and fielded within the Defense Acquisition University's (DAU) Advanced Knowledge Management Systems (AKSS). ...
This paper is based on a workshop held at the University of Southern California Center for Softwa... more This paper is based on a workshop held at the University of Southern California Center for Software Engineering in March, 2002. The components of the Capability Maturity Model Integration SM (CMMI SM ) Systems Engineering/ Software Engineering/Integrated Product and Process Model 1 are evaluated for their support of agile methods. We also present a set of dualistic concepts differentiating the approaches. The results help to identify and reduce the level of mythology and establishes common ground for further discussion. SM -SE/SW/IPPD) model [5, 6] with agile concepts. Additional characterizations of the two approaches, beyond oil and water, were also developed and a survey of the level of agreement performed.
2012 IEEE International Systems Conference SysCon 2012, 2012
Effective application of systems engineering in rapid response environments has been difficult, p... more Effective application of systems engineering in rapid response environments has been difficult, particularly those where large, complex brownfield systems or systems of systems exist and are constantly being updated with both short and long term software enhancements. This paper proposes a general case for solving this problem by combining a services approach to systems engineering with a kanban-based scheduling system. It provides the basis for validating the approach with agent-based simulations.
2012 International Conference on Software and System Process (ICSSP), 2012
ABSTRACT Systems engineering processes using pull scheduling methods (kanban) are being evaluated... more ABSTRACT Systems engineering processes using pull scheduling methods (kanban) are being evaluated with hybrid modeling and simulation. We are assessing integrated systems and software engineering at the enterprise level, where rapid response software development projects incrementally evolve capabilities of existing systems and/or systems of systems. A kanban-based scheduling system was defined and implemented with connected discrete, continuous and agent-based models. We are simulating the process performance vs. traditional methods of sharing systems engineering services across projects, and whether the overall value of the systems of systems over time is increased.
2012 International Conference on Software and System Process (ICSSP), 2012
Systems engineering is often ineffective in development environments where large, complex, brownf... more Systems engineering is often ineffective in development environments where large, complex, brownfield systems of systems are evolved through parallel development of new capabilities in response to external, time-sensitive requirements. This paper defines a conceptual framework to improve that effectiveness and better integrate the systems engineering and software engineering processes. The framework is based on a services approach to systems engineering and the use of kanban techniques to schedule scarce enterprise systems engineering resources across multiple related systems and software development projects. The framework also addresses the differing value of work items to multiple stakeholders in the scheduling and coordination processes. Models and simulations are being used to capture, refine and validate the framework prior to in vivo experimentation.
2008 21st Conference on Software Engineering Education and Training, 2008
A broad coalition of professionals from academia, industry, and government, under sponsorship of ... more A broad coalition of professionals from academia, industry, and government, under sponsorship of the US Department of Defense, is building a new model curriculum for a Masters Degree in Software Engineering (SwE). Before beginning to create such a model, a study of 28 programs was completed to determine the current state of SwE masters-level education in the US and abroad.
ABSTRACT The software engineering institute published the last reference curriculum for a master&... more ABSTRACT The software engineering institute published the last reference curriculum for a master's in software engineering in 1991. In 2007, a coalition from academia, industry, and government began creating a new reference curriculum. An early step was to establish a baseline of graduate education by surveying 28 master's programs in software engineering. The survey was largely limited to US schools. Key findings showed that the universities viewed software engineering largely as a specialization of computer science, that faculty size is generally small with few dedicated professors, and that new master's programs continue to start despite the decrease in computer science majors over the past few years. We used the IEEE Computer Society's Software Engineering Body of Knowledge (SWEBOK) to structure our analysis of the 28 curricula, focusing primarily on courses and topics required or semirequired of all students. (A course is semirequired if there is at least a 50 percent chance a student must take it.) Major findings show wide variation in the depth and breadth of SWEBOK coverage in required and semirequired courses, less than 40 percent of all programs requiring an introductory course on software engineering, and many universities having required and semirequired courses that are peripheral to SWEBOK.
I wish I could remember the name of the author of a book I read several years ago on SEI processe... more I wish I could remember the name of the author of a book I read several years ago on SEI processes, which provided excellent guidelines for projects. The author was very explicit and provided examples. He also stated in the Foreword that, though the book contained a ...
Abstract: Software engineering, both as a discipline and as a profession, is at a pivotal point i... more Abstract: Software engineering, both as a discipline and as a profession, is at a pivotal point in its evolution. Although software has become critical in the development of most new human created systems, the concepts, principles, and methods for engineering software are still neither well defined nor uniformly agreed upon. The lack of consensus regarding software engineering practice and the requisite competencies creates confusion and has serious consequences for the evaluation, acquisition, and application of software ...
From the Book:Why We Wrote This BookTrue believers represent software development alternativesIn ... more From the Book:Why We Wrote This BookTrue believers represent software development alternativesIn the last few years, two ostensibly conflicting approaches to software development have competed for hegemony. Agile method supporters released a manifesto that shifts the focus from traditional plan-driven, process-based methods to lighter, more adaptive paradigms. Traditional methods have reasserted the need for strong process discipline and rigorous practices. True believers on both sides have raised strident, often antagonistic, voices. This book is for the rest of us We wrote this book for the rest of us—those caught in the middle of the method wars simply trying to get our projects completed and accepted within too-tight schedules and budgets. We hope to clarify the perplexity about the roles of discipline, agility, and process in software development. We objectively compare and contrast the traditional, plan-driven approaches to the newer, agile approaches and present an overview o...
Systems are becoming increasingly reliant on software due to needs for rapid fielding of -70%‖ ca... more Systems are becoming increasingly reliant on software due to needs for rapid fielding of -70%‖ capabilities, interoperability, net-centricity, and rapid adaptation to change. The latter need has led to increased interest in agile methods of software development, in which teams rely on shared tacit interpersonal knowledge rather than explicit documented knowledge. However, such capabilities often need to be scaled up to higher level of performance and assurance, requiring stronger architectural support. Several organizations have recently transformed themselves by developing successful combinations of agility and architecture that scale up to projects of up to 100 personnel. This paper identifies a set of key principles for such architected agile solutions for software-reliant systems, and illustrates them with several case studies.
Many of today's problems are in search of new, innovative solutions. However, the development of ... more Many of today's problems are in search of new, innovative solutions. However, the development of new and innovative solutions has been elusive to many, resulting in considerable effort and dollars and no solution or a mediocre solution late to the marketplace or customer. This paper describes the results of research conducted to identify the critical success factors employed by several successful, high-performance organizations in the development of innovative systems. These critical success factors span technical, managerial, people, and cultural aspects of the innovative environment.
ABSTRACT 1. Abstract In these days of rapid change, many organizations find that their current ba... more ABSTRACT 1. Abstract In these days of rapid change, many organizations find that their current balance between using agile and disciplined methods is not what it should be. (We realize that "disciplined" is not the opposite of "agile," but it is our working label here for methods relying more on explicit documented knowledge than on tacit interpersonal knowledge). In a forthcoming book (Boehm-Turner, 2003), we have analyzed many organizations' experiences with agile and disciplined methods, and have elaborated our previous characterization (Boehm, 2002) of the "home grounds" in which agile and disciplined methods have been most successful. This analysis has enabled us to determine five critical decision factors that organizations and projects can use to determine whether they are in either the agile or disciplined home grounds, or somewhere in between. These five decision factors are size, criticality, personnel, dynamism, and culture. In this paper, we set the context by characterizing the agile and disciplined home grounds. We then define the five decision factors and their rating scales; provide a stepwise approach for assessing your organization's or project's location in the decision space and developing a strategy for rebalancing its agility and discipline; and illustrate its use with a representative organizational example.
* Maturity can only be measured on existing software * For source selection this means COTS, GOTS... more * Maturity can only be measured on existing software * For source selection this means COTS, GOTS, NDI, prototype, experimental * Initial set of software product maturity characteristics defined * Maturity evaluation complex - dependent on context and related factors * Agile approaches may make it easier to determine software product maturity.
Product Focused Software Process Improvement, 2002
... I believe some of the findings of the USC workshop are debatable, and represent mispercepti... more ... I believe some of the findings of the USC workshop are debatable, and represent misperceptions on the part of ... Agile processes evolve, but they generally do so via their own experience, generally within a team or a project. ... Agile Meets CMMI: Culture Clash or Common Cause ...
There is an increasing emphasis on rapid development of products and services to meet immediate, ... more There is an increasing emphasis on rapid development of products and services to meet immediate, mission-critical needs. In order to reduce the development cycle, "agile" approaches are needed. There are methods, proc-esses, and tools (MPTs) already in existence, and gaps where new solutions are needed that work within specific contexts. For a context where developers with unstable requirements must react quickly to stakeholder needs to build new capabilities that rely on existing systems in a wide range of operational environments, applicable MPTs were investigated using an online survey on approaches to requirements, stakeholders, sustainment and integration. Participants provided information on their experience and development environment, allowing responses to be evaluated within the context of interest. Scrum, Rapid Prototyping, and Continuous Integration emerged as promis-ing MPTs. Further investigation included follow-up interviews with survey participants in simila...
The current state of the art of aircraft systems integration is similar to the traditional serial... more The current state of the art of aircraft systems integration is similar to the traditional serial software engineering waterfall method. Agile methods transformed software engineering with a focus on incremental iterative value added design. This paper reviews selected non software agile case studies for lessons that are applicable to implementing agile methods to transform the aircraft systems integration process. (C) 2013 The Authors. Published by Elsevier B. V. and/or peer-review under responsibility of Georgia Institute of Technology
The systems engineering research center university affiliated research center (SERC-UARC) at Stev... more The systems engineering research center university affiliated research center (SERC-UARC) at Stevens Institute has been tasked to evaluate the effectiveness of the systems and software engineering processes, methods and tools (MPTs) used in US department of defense acquisition and development programs. This paper presents the selection and evaluation process, describes its evolution based on changing sponsor needs, and presents additional
There is good evidence from experience reports and other literature that the lean flow concepts o... more There is good evidence from experience reports and other literature that the lean flow concepts of on-demand, value-based scheduling and limited work-in-progress are highly effective in many instances of software development. The question remains, however, if they are equally applicable to the systems and enterprise engineering found in large or complex system environments. This paper builds on previous conceptual work to describe specific applications of the concepts to support coordination of systems engineering activities within large-scale system acquisition, development and evolution. Using a surrogate environment derived from the complex interactions of IT, embedded systems, and human activities in a large multifacility hospital system, we provide examples of how integrated kanban-like constructs can be created at each systems engineering level from an individual project through the complete capabilities portfolio.
2005 International Symposium on Empirical Software Engineering, 2005., 2005
... This prototype will evolve into a set of requirements that will be implemented in an operatio... more ... This prototype will evolve into a set of requirements that will be implemented in an operational system according to DoD specifications and fielded within the Defense Acquisition University's (DAU) Advanced Knowledge Management Systems (AKSS). ...
This paper is based on a workshop held at the University of Southern California Center for Softwa... more This paper is based on a workshop held at the University of Southern California Center for Software Engineering in March, 2002. The components of the Capability Maturity Model Integration SM (CMMI SM ) Systems Engineering/ Software Engineering/Integrated Product and Process Model 1 are evaluated for their support of agile methods. We also present a set of dualistic concepts differentiating the approaches. The results help to identify and reduce the level of mythology and establishes common ground for further discussion. SM -SE/SW/IPPD) model [5, 6] with agile concepts. Additional characterizations of the two approaches, beyond oil and water, were also developed and a survey of the level of agreement performed.
2012 IEEE International Systems Conference SysCon 2012, 2012
Effective application of systems engineering in rapid response environments has been difficult, p... more Effective application of systems engineering in rapid response environments has been difficult, particularly those where large, complex brownfield systems or systems of systems exist and are constantly being updated with both short and long term software enhancements. This paper proposes a general case for solving this problem by combining a services approach to systems engineering with a kanban-based scheduling system. It provides the basis for validating the approach with agent-based simulations.
2012 International Conference on Software and System Process (ICSSP), 2012
ABSTRACT Systems engineering processes using pull scheduling methods (kanban) are being evaluated... more ABSTRACT Systems engineering processes using pull scheduling methods (kanban) are being evaluated with hybrid modeling and simulation. We are assessing integrated systems and software engineering at the enterprise level, where rapid response software development projects incrementally evolve capabilities of existing systems and/or systems of systems. A kanban-based scheduling system was defined and implemented with connected discrete, continuous and agent-based models. We are simulating the process performance vs. traditional methods of sharing systems engineering services across projects, and whether the overall value of the systems of systems over time is increased.
2012 International Conference on Software and System Process (ICSSP), 2012
Systems engineering is often ineffective in development environments where large, complex, brownf... more Systems engineering is often ineffective in development environments where large, complex, brownfield systems of systems are evolved through parallel development of new capabilities in response to external, time-sensitive requirements. This paper defines a conceptual framework to improve that effectiveness and better integrate the systems engineering and software engineering processes. The framework is based on a services approach to systems engineering and the use of kanban techniques to schedule scarce enterprise systems engineering resources across multiple related systems and software development projects. The framework also addresses the differing value of work items to multiple stakeholders in the scheduling and coordination processes. Models and simulations are being used to capture, refine and validate the framework prior to in vivo experimentation.
2008 21st Conference on Software Engineering Education and Training, 2008
A broad coalition of professionals from academia, industry, and government, under sponsorship of ... more A broad coalition of professionals from academia, industry, and government, under sponsorship of the US Department of Defense, is building a new model curriculum for a Masters Degree in Software Engineering (SwE). Before beginning to create such a model, a study of 28 programs was completed to determine the current state of SwE masters-level education in the US and abroad.
ABSTRACT The software engineering institute published the last reference curriculum for a master&... more ABSTRACT The software engineering institute published the last reference curriculum for a master's in software engineering in 1991. In 2007, a coalition from academia, industry, and government began creating a new reference curriculum. An early step was to establish a baseline of graduate education by surveying 28 master's programs in software engineering. The survey was largely limited to US schools. Key findings showed that the universities viewed software engineering largely as a specialization of computer science, that faculty size is generally small with few dedicated professors, and that new master's programs continue to start despite the decrease in computer science majors over the past few years. We used the IEEE Computer Society's Software Engineering Body of Knowledge (SWEBOK) to structure our analysis of the 28 curricula, focusing primarily on courses and topics required or semirequired of all students. (A course is semirequired if there is at least a 50 percent chance a student must take it.) Major findings show wide variation in the depth and breadth of SWEBOK coverage in required and semirequired courses, less than 40 percent of all programs requiring an introductory course on software engineering, and many universities having required and semirequired courses that are peripheral to SWEBOK.
I wish I could remember the name of the author of a book I read several years ago on SEI processe... more I wish I could remember the name of the author of a book I read several years ago on SEI processes, which provided excellent guidelines for projects. The author was very explicit and provided examples. He also stated in the Foreword that, though the book contained a ...
Abstract: Software engineering, both as a discipline and as a profession, is at a pivotal point i... more Abstract: Software engineering, both as a discipline and as a profession, is at a pivotal point in its evolution. Although software has become critical in the development of most new human created systems, the concepts, principles, and methods for engineering software are still neither well defined nor uniformly agreed upon. The lack of consensus regarding software engineering practice and the requisite competencies creates confusion and has serious consequences for the evaluation, acquisition, and application of software ...
From the Book:Why We Wrote This BookTrue believers represent software development alternativesIn ... more From the Book:Why We Wrote This BookTrue believers represent software development alternativesIn the last few years, two ostensibly conflicting approaches to software development have competed for hegemony. Agile method supporters released a manifesto that shifts the focus from traditional plan-driven, process-based methods to lighter, more adaptive paradigms. Traditional methods have reasserted the need for strong process discipline and rigorous practices. True believers on both sides have raised strident, often antagonistic, voices. This book is for the rest of us We wrote this book for the rest of us—those caught in the middle of the method wars simply trying to get our projects completed and accepted within too-tight schedules and budgets. We hope to clarify the perplexity about the roles of discipline, agility, and process in software development. We objectively compare and contrast the traditional, plan-driven approaches to the newer, agile approaches and present an overview o...
Systems are becoming increasingly reliant on software due to needs for rapid fielding of -70%‖ ca... more Systems are becoming increasingly reliant on software due to needs for rapid fielding of -70%‖ capabilities, interoperability, net-centricity, and rapid adaptation to change. The latter need has led to increased interest in agile methods of software development, in which teams rely on shared tacit interpersonal knowledge rather than explicit documented knowledge. However, such capabilities often need to be scaled up to higher level of performance and assurance, requiring stronger architectural support. Several organizations have recently transformed themselves by developing successful combinations of agility and architecture that scale up to projects of up to 100 personnel. This paper identifies a set of key principles for such architected agile solutions for software-reliant systems, and illustrates them with several case studies.
Many of today's problems are in search of new, innovative solutions. However, the development of ... more Many of today's problems are in search of new, innovative solutions. However, the development of new and innovative solutions has been elusive to many, resulting in considerable effort and dollars and no solution or a mediocre solution late to the marketplace or customer. This paper describes the results of research conducted to identify the critical success factors employed by several successful, high-performance organizations in the development of innovative systems. These critical success factors span technical, managerial, people, and cultural aspects of the innovative environment.
ABSTRACT 1. Abstract In these days of rapid change, many organizations find that their current ba... more ABSTRACT 1. Abstract In these days of rapid change, many organizations find that their current balance between using agile and disciplined methods is not what it should be. (We realize that "disciplined" is not the opposite of "agile," but it is our working label here for methods relying more on explicit documented knowledge than on tacit interpersonal knowledge). In a forthcoming book (Boehm-Turner, 2003), we have analyzed many organizations' experiences with agile and disciplined methods, and have elaborated our previous characterization (Boehm, 2002) of the "home grounds" in which agile and disciplined methods have been most successful. This analysis has enabled us to determine five critical decision factors that organizations and projects can use to determine whether they are in either the agile or disciplined home grounds, or somewhere in between. These five decision factors are size, criticality, personnel, dynamism, and culture. In this paper, we set the context by characterizing the agile and disciplined home grounds. We then define the five decision factors and their rating scales; provide a stepwise approach for assessing your organization's or project's location in the decision space and developing a strategy for rebalancing its agility and discipline; and illustrate its use with a representative organizational example.
Uploads
Papers by Richard Turner