000 05705cam a2200601Ii 4500
001 ocn922528510
003 OCoLC
005 20190328114812.0
006 m o d
007 cr cnu|||unuuu
008 150929s2016 mau o 001 0 eng d
010 _a 2017275025
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
019 _a926044925
_a929521679
_a938427407
_a966385725
_a993532652
_a999589770
_a1002909004
_a1008844354
_a1008948774
_a1066566973
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
050 4 _aTA168
072 7 _aTEC
_x009000
_2bisacsh
072 7 _aTEC
_x035000
_2bisacsh
082 0 4 _a620.001/171
_223
100 1 _aDouglass, Bruce Powel,
_eauthor.
245 1 0 _aAgile systems engineering /
_h[electronic resource]
_cBruce Powel Douglass, Ph.D.
264 4 _c�2016
264 1 _aWaltham, MA :
_bMorgan Kaufmann,
_c2016.
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 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 4 _aElectronic books.
655 0 _aElectronic books.
776 0 8 _iPrint version:
_aDouglass, Bruce Powel
_tAgile Systems Engineering
_d: Elsevier Science,c2015
856 4 0 _3ScienceDirect
_uhttp://www.sciencedirect.com/science/book/9780128021200
999 _c247176
_d247176