MARC Record from marc_columbia

LEADER: 06434cam a2200697Ii 4500
001 13725804
005 20220703224339.0
006 m o d
007 cr cnu|||unuuu
008 150929s2016 mau o 001 0 eng d
010 $a 2017275025
035 $a(OCoLC)ocn922528510
035 $a(NNC)13725804
040 $aN$T$beng$erda$epn$cN$T$dN$T$dIDEBK$dYDXCP$dUIU$dUMI$dCDX$dOCLCF$dCOO$dEBLCP$dKNOVL$dTEFOD$dDEBSZ$dK6U$dVT2$dVGM$dOTZ$dLIV$dOCLCQ$dD6H$dVVB$dU3W$dCEF$dTXM$dWYU$dMERER$dOCLCQ$dAU@$dLQU$dOCLCQ$dINARC$dOCLCO
019 $a926044925$a929521679$a938427407$a966385725$a993532652$a999589770$a1002909004$a1008844354$a1008948774$a1066566973$a1103274473$a1105187332$a1105566023$a1129337740$a1152998681$a1192335686$a1235829483$a1240536117$a1262678875
020 $a9780128023495$qelectronic bk.
020 $a012802349X$qelectronic bk.
020 $z0128021209
020 $z9780128021200
035 $a(OCoLC)922528510$z(OCoLC)926044925$z(OCoLC)929521679$z(OCoLC)938427407$z(OCoLC)966385725$z(OCoLC)993532652$z(OCoLC)999589770$z(OCoLC)1002909004$z(OCoLC)1008844354$z(OCoLC)1008948774$z(OCoLC)1066566973$z(OCoLC)1103274473$z(OCoLC)1105187332$z(OCoLC)1105566023$z(OCoLC)1129337740$z(OCoLC)1152998681$z(OCoLC)1192335686$z(OCoLC)1235829483$z(OCoLC)1240536117$z(OCoLC)1262678875
037 $aCL0500000660$bSafari Books Online
037 $a4EBDAC14-7AE9-4446-9BC6-EF306C034DB1$bOverDrive, Inc.$nhttp://www.overdrive.com
050 4 $aTA168
072 7 $aTEC$x009000$2bisacsh
072 7 $aTEC$x035000$2bisacsh
082 04 $a620.001/171$223
049 $aZCUA
100 1 $aDouglass, Bruce Powel,$eauthor.
245 10 $aAgile systems engineering /$cBruce Powel Douglass, Ph.D.
264 4 $c©2016
264 1 $aWaltham, MA :$bMorgan Kaufmann,$c[2016]
300 $a1 online resource
336 $atext$btxt$2rdacontent
337 $acomputer$bc$2rdamedia
338 $aonline resource$bcr$2rdacarrier
500 $aIncludes index.
588 0 $aVendor-supplied metadata.
505 0 $aFront Cover; Agile Systems Engineering; Copyright Page; Dedication; Contents; About the Author; Preface; Audience; Goals; Tooling; Where to Go After the Book; Acknowledgments; 1 What Is Model-Based Systems Engineering?; 1.1 Key Systems Engineering Activities; 1.1.1 Identifying Customer Needs; 1.1.2 Specifying System Requirements; 1.1.3 Assess Dependability; 1.1.4 Evaluating Alternative Architectures and Technologies; 1.1.5 Selecting Specific Architectures and Technologies; 1.1.6 Allocating Requirements and Interfaces to Architectures; 1.1.7 Hand Off to Downstream Engineering
505 8 $a1.1.8 Integrate Discipline-Specific Designs into System Composite1.1.9 Verify System as a Whole; 1.1.9.1 Syntactic verification; Audits; Syntactic reviews; 1.1.9.2 Semantic verification; Semantic review; Testing; Formal methods; 1.1.9.3 System verification; 1.1.10 System Validation; 1.2 Systems Engineering Data; 1.2.1 System Development Plan; 1.2.2 Stakeholder Requirements; 1.2.3 System Requirements; 1.2.4 Certification Plan; 1.2.5 Subsystem Requirements; 1.2.6 Discipline-Specific Requirements; 1.2.7 Safety Analysis; 1.2.8 Reliability Analysis; 1.2.9 Security Analysis
505 8 $a1.2.10 System Architecture1.2.10.1 Subsystems; 1.2.10.2 Deployment architecture; 1.2.10.3 Dependability architecture; 1.2.10.4 Distribution architecture; 1.2.11 Integration Test Plan; 1.2.12 Integration Tests; 1.2.13 Verification Plan; 1.2.14 Verification Tests; 1.2.15 Validation Plan; 1.2.16 Trace Matrix; 1.2.17 Integration Test Results; 1.2.18 Verification Results; 1.2.19 Validation Results; 1.3 Lifecycles of the Systems Engineer; 1.3.1 V-Model Lifecycle; 1.3.2 Incremental; 1.3.3 Hybrid; 1.4 Model-Based Systems Engineering (MBSE); 1.4.1 The Modeling Advantage
505 8 $a1.4.1.1 Precision of engineering data1.4.1.2 Data consistency across work products and engineering activities; 1.4.1.3 A common source of engineering truth; 1.4.1.4 Improved visualization and comprehension of engineering data; 1.4.1.5 Ease of integration of disparate engineering data; 1.4.1.6 Improved management and maintenance of engineering data; 1.4.1.7 Early verification of the correctness of engineering data; 1.4.2 High-Precision Modeling with UML and SysML; 1.4.2.1 The fundamental truth of modeling: drawing≠modeling; 1.4.3 Modeling Is Essential for Agile Systems Engineering
505 8 $a1.4.3.1 The fundamental truth of agile systems engineering: verifiable models are required for agile systems engineering1.4.4 Adopting Modeling in Your Organization or Project; 1.4.4.1 Antipatterns of adopting MBSE; 1.4.4.2 Recommend approaches for adopting MBSE; Assessment; Planning for adoption; Pilot; Deployment; 1.4.5 The Rules (of Modeling); 1.5 Summary; References; 2 What Are Agile Methods and Why Should I Care?; 2.1 The Agile Manifesto; 2.2 Benefits of Agile Methods; Improved Quality of Engineering Data; Improved Engineering Efficiency; Early Return on Investment (ROI)
504 $aIncludes bibliographical references.
520 $aPresenting a vision of systems engineering where precise specification of requirements, structure, and behavior meet larger concerns as such as safety, security, reliability, and performance in an agile engineering context, this book discusses the lifecycle of systems development, including requirements, analysis, design, and the handoff to specific engineering disciplines. --$cEdited summary from book.
650 0 $aSystems engineering.
650 0 $aAgile software development.
650 0 $aSysML (Computer science)
650 6 $aIngénierie des systèmes.
650 6 $aMéthodes agiles (Développement de logiciels)
650 6 $aSysML (Informatique)
650 7 $asystems engineering.$2aat
650 7 $aTECHNOLOGY & ENGINEERING / Engineering (General)$2bisacsh
650 7 $aTECHNOLOGY & ENGINEERING / Reference$2bisacsh
650 7 $aAgile software development.$2fast$0(OCoLC)fst01743753
650 7 $aSysML (Computer science)$2fast$0(OCoLC)fst01744325
650 7 $aSystems engineering.$2fast$0(OCoLC)fst01141455
655 0 $aElectronic books.
655 4 $aElectronic books.
776 08 $iPrint version:$aDouglass, Bruce Powel$tAgile Systems Engineering$d: Elsevier Science,c2015
856 40 $uhttp://www.columbia.edu/cgi-bin/cul/resolve?clio13725804$zACADEMIC - General Engineering & Project Administration
852 8 $blweb$hEBOOKS