Barry Boehm – författare
Visar alla böcker från författaren Barry Boehm. Handla med fri frakt och snabb leverans.
17 produkter
17 produkter
Häftad, Engelska, 2003
346 kr
Skickas inom 7-10 vardagar
Nowadays, there are many methodologies you can introduce your to students. On the one hand, there are the more agile methods that focus on individual projects, and how to get them done fast—the camp represented by Beck and Cockburn. On the other hand, there are the more disciplined methods, focused on setting up organizational processes for getting projects done with predictable high quality—the camp best represented by the SEI, the CMMI, and Humphrey. Although these methods are often presented as mutually exclusive, they actually lie on a continuum. The authors of Balancing Agility and Discipline have worked out clear guidelines for determining where on that continuum a particular software development project is located—and therefore, how agile or disciplined a chosen methodology can or has to be.
Inbunden, Engelska, 2020
451 kr
Skickas inom 10-15 vardagar
From the beginning of software time, people have wondered why it isn’t possible to accelerate software projects by simply adding staff. This is sometimes known as the “nine women can’t make a baby in one month” problem. The most famous treatise declaring this to be impossible is Fred Brooks’ 1975 book The Mythical Man-Month, in which he declares that “adding more programmers to a late software project makes it later,” and indeed this has proven largely true over the decades. Aided by a domain-driven code generator that quickly creates database and API code, Parallel Agile (PA) achieves significant schedule compression using parallelism: as many developers as necessary can independently and concurrently develop the scenarios from initial prototype through production code. Projects can scale by elastic staffing, rather than by stretching schedules for larger development efforts. Schedule compression with a large team of developersworking in parallel is analogous to hardware acceleration of compute problems using parallel CPUs.PA has some similarities with and differences from other Agile approaches. Like most Agile methods, PA "gets to code early" and uses feedback from executable software to drive requirements and design. PA uses technical prototyping as a risk-mitigation strategy, to help sanity-check requirements for feasibility, and to evaluate different technical architectures and technologies.Unlike many Agile methods, PA does not support "design by refactoring," and it doesn't drive designs from unit tests. Instead, PA uses a minimalist UML-based design approach (Agile/ICONIX) that starts out with a domain model to facilitate communication across the development team, and partitions the system along use case boundaries, which enables parallel development. Parallel Agile is fully compatible with the Incremental Commitment Spiral Model (ICSM), which involves concurrent effort of a systems engineering team, a development team, and a test team working alongside the developers. The authors have been researching and refining the PA process for several years on multiple test projects that have involved over 200 developers. The book’s example project details the design of one of these test projects, a crowdsourced traffic safety system.
E-bok
Engelska, 2020571 kr
Läs direkt efter köp
From the beginning of software time, people have wondered why it isn’t possible to accelerate software projects by simply adding staff. This is sometimes known as the “nine women can’t make a baby in one month” problem. The most famous treatise declaring this to be impossible is Fred Brooks’ 1975 book The Mythical Man-Month, in which he declares that “adding more programmers to a late software project makes it later,” and indeed this has proven largely true over the decades.
Aided by a domain-driven code generator that quickly creates database and API code, Parallel Agile (PA) achieves significant schedule compression using parallelism: as many developers as necessary can independently and concurrently develop the scenarios from initial prototype through production code. Projects can scale by elastic staffing, rather than by stretching schedules for larger development efforts. Schedule compression with a large team of developersworking in parallel is analogous to hardware acceleration of compute problems using parallel CPUs.
PA has some similarities with and differences from other Agile approaches. Like most Agile methods, PA "gets to code early" and uses feedback from executable software to drive requirements and design. PA uses technical prototyping as a risk-mitigation strategy, to help sanity-check requirements for feasibility, and to evaluate different technical architectures and technologies.
Unlike many Agile methods, PA does not support "design by refactoring," and it doesn''t drive designs from unit tests. Instead, PA uses a minimalist UML-based design approach (Agile/ICONIX) that starts out with a domain model to facilitate communication across the development team, and partitions the system along use case boundaries, which enables parallel development. Parallel Agile is fully compatible with the Incremental Commitment Spiral Model (ICSM), which involves concurrent effort of a systems engineering team, a development team, and a test team working alongside the developers.
The authors have been researching and refining the PA process for several years on multiple test projects that have involved over 200 developers. The book’s example project details the design of one of these test projects, a crowdsourced traffic safety system.
Häftad, Engelska, 2021
451 kr
Skickas inom 10-15 vardagar
From the beginning of software time, people have wondered why it isn’t possible to accelerate software projects by simply adding staff. This is sometimes known as the “nine women can’t make a baby in one month” problem. The most famous treatise declaring this to be impossible is Fred Brooks’ 1975 book The Mythical Man-Month, in which he declares that “adding more programmers to a late software project makes it later,” and indeed this has proven largely true over the decades. Aided by a domain-driven code generator that quickly creates database and API code, Parallel Agile (PA) achieves significant schedule compression using parallelism: as many developers as necessary can independently and concurrently develop the scenarios from initial prototype through production code. Projects can scale by elastic staffing, rather than by stretching schedules for larger development efforts. Schedule compression with a large team of developersworking in parallel is analogous to hardware acceleration of compute problems using parallel CPUs.PA has some similarities with and differences from other Agile approaches. Like most Agile methods, PA "gets to code early" and uses feedback from executable software to drive requirements and design. PA uses technical prototyping as a risk-mitigation strategy, to help sanity-check requirements for feasibility, and to evaluate different technical architectures and technologies.Unlike many Agile methods, PA does not support "design by refactoring," and it doesn't drive designs from unit tests. Instead, PA uses a minimalist UML-based design approach (Agile/ICONIX) that starts out with a domain model to facilitate communication across the development team, and partitions the system along use case boundaries, which enables parallel development. Parallel Agile is fully compatible with the Incremental Commitment Spiral Model (ICSM), which involves concurrent effort of a systems engineering team, a development team, and a test team working alongside the developers. The authors have been researching and refining the PA process for several years on multiple test projects that have involved over 200 developers. The book’s example project details the design of one of these test projects, a crowdsourced traffic safety system.
Inbunden, Engelska, 2022
2 377 kr
Skickas inom 10-15 vardagar
This volume comprises papers from the 18th Conference on Systems Engineering Research (CSER). The theme of this volume, “Recent Trends and Advances in Model-Based Systems Engineering,” reflects the fact that systems engineering is undergoing a transformation motivated by mission and system complexity and enabled by technological advances such as model-based systems engineering, digital engineering, and the convergence of systems engineering with other disciplines. This conference is focused on exploring recent trends and advances in model-based systems engineering (MBSE) and the synergy of MBSE with simulation technology and digital engineering. Contributors have submitted papers on MBSE methods, modeling approaches, integration of digital engineering with MBSE, standards, modeling languages, ontologies and metamodels, and economics analysis of MBSE to respond to the challenges posed by 21st century systems. What distinguishes this volume are the latest advances in MBSE research, the convergence of MBSE with digital engineering, and recent advances in applied research in MBSE, including growing convergence with systems science and decision science. This volume is appropriate as a reference text in graduate engineering courses in Model-Based Systems Engineering.
E-bok
Engelska, 20223 157 kr
Läs direkt efter köp
This volume comprises papers from the 18th Conference on Systems Engineering Research (CSER). The theme of this volume, “Recent Trends and Advances in Model-Based Systems Engineering,” reflects the fact that systems engineering is undergoing a transformation motivated by mission and system complexity and enabled by technological advances such as model-based systems engineering, digital engineering, and the convergence of systems engineering with other disciplines. This conference is focused on exploring recent trends and advances in model-based systems engineering (MBSE) and the synergy of MBSE with simulation technology and digital engineering. Contributors have submitted papers on MBSE methods, modeling approaches, integration of digital engineering with MBSE, standards, modeling languages, ontologies and metamodels, and economics analysis of MBSE to respond to the challenges posed by 21st century systems. What distinguishes this volume are the latest advances in MBSE research, the convergence of MBSE with digital engineering, and recent advances in applied research in MBSE, including growing convergence with systems science and decision science. This volume is appropriate as a reference text in graduate engineering courses in Model-Based Systems Engineering.
Häftad, Engelska, 2023
2 377 kr
Skickas inom 10-15 vardagar
This volume comprises papers from the 18th Conference on Systems Engineering Research (CSER). The theme of this volume, “Recent Trends and Advances in Model-Based Systems Engineering,” reflects the fact that systems engineering is undergoing a transformation motivated by mission and system complexity and enabled by technological advances such as model-based systems engineering, digital engineering, and the convergence of systems engineering with other disciplines. This conference is focused on exploring recent trends and advances in model-based systems engineering (MBSE) and the synergy of MBSE with simulation technology and digital engineering. Contributors have submitted papers on MBSE methods, modeling approaches, integration of digital engineering with MBSE, standards, modeling languages, ontologies and metamodels, and economics analysis of MBSE to respond to the challenges posed by 21st century systems. What distinguishes this volume are the latest advances in MBSE research, the convergence of MBSE with digital engineering, and recent advances in applied research in MBSE, including growing convergence with systems science and decision science. This volume is appropriate as a reference text in graduate engineering courses in Model-Based Systems Engineering.
Inbunden, Engelska, 2017
3 238 kr
Skickas inom 10-15 vardagar
The theme of this volume on systems engineering research is disciplinary convergence: bringing together concepts, thinking, approaches, and technologies from diverse disciplines to solve complex problems. Papers presented at the Conference on Systems Engineering Research (CSER), March 23-25, 2017 at Redondo Beach, CA, are included in this volume. This collection provides researchers in academia, industry, and government forward-looking research from across the globe, written by renowned academic, industry and government researchers.
E-bok
Engelska, 20173 948 kr
Läs direkt efter köp
The theme of this volume on systems engineering research is disciplinary convergence: bringing together concepts, thinking, approaches, and technologies from diverse disciplines to solve complex problems. Papers presented at the Conference on Systems Engineering Research (CSER), March 23-25, 2017 at Redondo Beach, CA, are included in this volume. This collection provides researchers in academia, industry, and government forward-looking research from across the globe, written by renowned academic, industry and government researchers.
Häftad, Engelska, 2020
3 238 kr
Skickas inom 10-15 vardagar
The theme of this volume on systems engineering research is disciplinary convergence: bringing together concepts, thinking, approaches, and technologies from diverse disciplines to solve complex problems. Papers presented at the Conference on Systems Engineering Research (CSER), March 23-25, 2017 at Redondo Beach, CA, are included in this volume. This collection provides researchers in academia, industry, and government forward-looking research from across the globe, written by renowned academic, industry and government researchers.
Inbunden, Engelska, 2005
1 893 kr
Skickas inom 10-15 vardagar
Although software engineering can trace its beginnings to a NATO conf- ence in 1968, it cannot be said to have become an empirical science until the 1970s with the advent of the work of Prof. Victor Robert Basili of the University of Maryland. In addition to the need to engineer software was the need to understand software. Much like other sciences, such as physics, chemistry, and biology, software engineering needed a discipline of obs- vation, theory formation, experimentation, and feedback. By applying the scientific method to the software engineering domain, Basili developed concepts like the Goal-Question-Metric method, the Quality-Improvement- Paradigm, and the Experience Factory to help bring a sense of order to the ad hoc developments so prevalent in the software engineering field. On the occasion of Basili’s 65th birthday, we present this book c- taining reprints of 20 papers that defined much of his work. We divided the 20 papers into 6 sections, each describing a different facet of his work, and asked several individuals to write an introduction to each section. Instead of describing the scope of this book in this preface, we decided to let one of his papers, the keynote paper he gave at the International C- ference on Software Engineering in 1996 in Berlin, Germany to lead off this book. He, better than we, can best describe his views on what is - perimental software engineering.
Inbunden, Engelska, 2005
1 671 kr
Skickas inom 10-15 vardagar
The IT community has always struggled with questions concerning the value of an organization’s investment in software and hardware. It is the goal of value-based software engineering (VBSE) to develop models and measures of value which are of use for managers, developers and users as they make tradeoff decisions between, for example, quality and cost or functionality and schedule – such decisions must be economically feasible and comprehensible to the stakeholders with differing value perspectives. VBSE has its roots in work on software engineering economics, pioneered by Barry Boehm in the early 1980s. However, the emergence of a wider scope that defines VBSE is more recent. VBSE extends the merely technical ISO software engineering definition with elements not only from economics, but also from cognitive science, finance, management science, behavioral sciences, and decision sciences, giving rise to a truly multi-disciplinary framework.Biffl and his co-editors invited leading researchers and structured their contributions into three parts, following an introduction into the area by Boehm himself. They first detail the foundations of VBSE, followed by a presentation of state-of-the-art methods and techniques. The third part demonstrates the benefits of VBSE through concrete examples and case studies.This book deviates from the more anecdotal style of many management-oriented software engineering books and so appeals particularly to all readers who are interested in solid foundations for high-level aspects of software engineering decision making, i.e., to product or project managers driven by economics and to software engineering researchers and students.
E-bok
PDF, Engelska, 20062 110 kr
Läs direkt efter köp
The IT community has always struggled with questions concerning the value of an organization’s investment in software and hardware. It is the goal of value-based software engineering (VBSE) to develop models and measures of value which are of use for managers, developers and users as they make tradeoff decisions between, for example, quality and cost or functionality and schedule – such decisions must be economically feasible and comprehensible to the stakeholders with differing value perspectives. VBSE has its roots in work on software engineering economics, pioneered by Barry Boehm in the early 1980s. However, the emergence of a wider scope that defines VBSE is more recent. VBSE extends the merely technical ISO software engineering definition with elements not only from economics, but also from cognitive science, finance, management science, behavioral sciences, and decision sciences, giving rise to a truly multi-disciplinary framework.Biffl and his co-editors invited leading researchers and structured their contributions into three parts, following an introduction into the area by Boehm himself. They first detail the foundations of VBSE, followed by a presentation of state-of-the-art methods and techniques. The third part demonstrates the benefits of VBSE through concrete examples and case studies.This book deviates from the more anecdotal style of many management-oriented software engineering books and so appeals particularly to all readers who are interested in solid foundations for high-level aspects of software engineering decision making, i.e., to product or project managers driven by economics and to software engineering researchers and students.
Häftad, Engelska, 2006
562 kr
Skickas inom 10-15 vardagar
This volume contains papers presented at SPW 2005, the Software Process Workshop held in Beijing, P. R. China, on May 25-27, 2005, and prepared for final publication. The theme of SPW2005 was “Unifying the Software Process Spectrum. ” Software process encompasses all the activities that aim at developing or evolving software products. The expanding role of software and information systems in the world has focused increasing attention on the need for assurances that software systems can be developed at acceptable speed and cost, on a predictable schedule, and in such a way that resulting systems are of acceptably high quality and can be evolved surely and rapidly as usage contexts change. This sharpened focus is creating new challenges and opportunities for software process technology. The increasing pace of software s- tem change requires more lightweight and adaptive processes, while the increasing mission criticality of software systems requires more process predictability and c- trol as well as more explicit attention to business or mission values. Emergent app- cation requirements create a need for ambiguity tolerance. Systems of systems and global development create needs for scalability and multi-collaborator, multi-culture concurrent coordination. COTS products provide powerful capabilities, but their v- dor-determined evolution places significant constraints on software definition, dev- opment, and evolution processes. The recognition of these needs has spawned a considerable amount of software process research across a broad spectrum.
E-bok
PDF, Engelska, 2005734 kr
Läs direkt efter köp
This volume contains papers presented at SPW 2005, the Software Process Workshop held in Beijing, P. R. China, on May 25-27, 2005, and prepared for final publication. The theme of SPW2005 was “Unifying the Software Process Spectrum. ” Software process encompasses all the activities that aim at developing or evolving software products. The expanding role of software and information systems in the world has focused increasing attention on the need for assurances that software systems can be developed at acceptable speed and cost, on a predictable schedule, and in such a way that resulting systems are of acceptably high quality and can be evolved surely and rapidly as usage contexts change. This sharpened focus is creating new challenges and opportunities for software process technology. The increasing pace of software s- tem change requires more lightweight and adaptive processes, while the increasing mission criticality of software systems requires more process predictability and c- trol as well as more explicit attention to business or mission values. Emergent app- cation requirements create a need for ambiguity tolerance. Systems of systems and global development create needs for scalability and multi-collaborator, multi-culture concurrent coordination. COTS products provide powerful capabilities, but their v- dor-determined evolution places significant constraints on software definition, dev- opment, and evolution processes. The recognition of these needs has spawned a considerable amount of software process research across a broad spectrum.
Häftad, Engelska, 2010
1 338 kr
Skickas inom 10-15 vardagar
Although software engineering can trace its beginnings to a NATO conf- ence in 1968, it cannot be said to have become an empirical science until the 1970s with the advent of the work of Prof. Victor Robert Basili of the University of Maryland. In addition to the need to engineer software was the need to understand software. Much like other sciences, such as physics, chemistry, and biology, software engineering needed a discipline of obs- vation, theory formation, experimentation, and feedback. By applying the scientific method to the software engineering domain, Basili developed concepts like the Goal-Question-Metric method, the Quality-Improvement- Paradigm, and the Experience Factory to help bring a sense of order to the ad hoc developments so prevalent in the software engineering field. On the occasion of Basili’s 65th birthday, we present this book c- taining reprints of 20 papers that defined much of his work. We divided the 20 papers into 6 sections, each describing a different facet of his work, and asked several individuals to write an introduction to each section. Instead of describing the scope of this book in this preface, we decided to let one of his papers, the keynote paper he gave at the International C- ference on Software Engineering in 1996 in Berlin, Germany to lead off this book. He, better than we, can best describe his views on what is - perimental software engineering.
Häftad, Engelska, 2010
1 671 kr
Skickas inom 10-15 vardagar
The IT community has always struggled with questions concerning the value of an organization’s investment in software and hardware. It is the goal of value-based software engineering (VBSE) to develop models and measures of value which are of use for managers, developers and users as they make tradeoff decisions between, for example, quality and cost or functionality and schedule – such decisions must be economically feasible and comprehensible to the stakeholders with differing value perspectives. VBSE has its roots in work on software engineering economics, pioneered by Barry Boehm in the early 1980s. However, the emergence of a wider scope that defines VBSE is more recent. VBSE extends the merely technical ISO software engineering definition with elements not only from economics, but also from cognitive science, finance, management science, behavioral sciences, and decision sciences, giving rise to a truly multi-disciplinary framework.Biffl and his co-editors invited leading researchers and structured their contributions into three parts, following an introduction into the area by Boehm himself. They first detail the foundations of VBSE, followed by a presentation of state-of-the-art methods and techniques. The third part demonstrates the benefits of VBSE through concrete examples and case studies.This book deviates from the more anecdotal style of many management-oriented software engineering books and so appeals particularly to all readers who are interested in solid foundations for high-level aspects of software engineering decision making, i.e., to product or project managers driven by economics and to software engineering researchers and students.