Format:
Online-Ressource (376 p)
Edition:
Online-Ausg. 2013 Electronic reproduction; Available via World Wide Web
ISBN:
9780124077683
,
1299591981
,
9781299591981
Content:
According to reports based on IT case studies, more than half of all software projects either fail outright or run woefully over budget and behind schedule. Software engineering education is not "standardized." Many institutions focus on implementation rather than design as it impacts product architecture. Many graduates join the workforce with incomplete skills and may not be prepared to perform the duties required during their initial careers. In 2004, the IEEE proposed the Software Engineering Body of Knowledge (SWEBOK) standard, which offers a reference for key skills, but not the training path to ensure mastery. Software Engineering: Architecture-driven Software Development is the first comprehensive guide to the underlying skills embodied in the SWEBOK, covering the majority of the standard. Standards expert Richard Schmidt explains the traditional software engineering practices recognized for developing projects for government or corporate systems. Additionally, many software engineers lack an understanding of system engineering and architecture--the hardware and peripherals their programs will run on--leading to inefficient coding or changes in project requirements. This issue will only grow in importance as more programs leverage parallel computing, requiring an understanding of the parallel capabilities of processors and hardware. Therefore, this book will give both software developers and system engineers key insights into how their two skillsets can support and complement each other. The book maintains focus on these key knowledge areas and offers a set of "best practices" that can be applied to any industry or domain involved in developing software products. A comprehensive, integrated compilation on the engineering of software products, addressing the majority of the standard knowledge areas and topics Offers best practices focused on those key skills common to many industries and domains that develop software Learn how software engineering relates to systems engineering, to facilitate better communication and understanding with other engineering professionals within a project environment
Content:
According to reports based on IT case studies, more than half of all software projects either fail outright or run woefully over budget and behind schedule. Software engineering education is not ""standardized."" Many institutions focus on implementation rather than design as it impacts product architecture. Many graduates join the workforce with incomplete skills and may not be prepared to perform the duties required during their initial careers. In 2004, the IEEE proposed the Software Engineering Body of Knowledge (SWEBOK) standard, which offers a reference for key skills, but not the tra
Note:
Description based upon print version of record
,
Front Cover; Software Engineering; Copyright Page; Contents; A Note from the Author; Preface; Book outline and subject matter; 1 Software Engineering Fundamentals; Systems engineering principles and practices; Summary; 1 Introduction to Software Engineering; 1.1 Specifying software requirements; 1.2 Software architecture; 1.3 Integrated product and process development; 1.4 Integrated product teams; 1.5 Work breakdown structure; 1.6 Software breakdown structure; 1.7 Specification and documentation trees; 1.8 Integrated master plan and schedule; 1.9 Reviews and audits
,
1.10 Configuration management and change control1.11 Trade-off analysis; 1.12 Risk management; 1.13 Modeling and simulation; 2 Generic Software Development Framework; 2.1 Software breakdown structure; 2.2 Software development process; 2.2.1 Requirements definition stage; 2.2.1.1 Product requirements review; 2.2.1.2 Software requirements review; 2.2.2 Preliminary architecture definition stage; 2.2.2.1 Preliminary architecture review; 2.2.2.2 Deployment strategy review; 2.2.2.3 Training strategy review; 2.2.2.4 Sustainment strategy review; 2.2.2.5 Preliminary design review
,
2.2.3 Critical architecture definition stage2.2.3.1 Detailed architecture review; 2.2.3.2 Deployment design review; 2.2.3.3 Training design review; 2.2.3.4 Sustainment design review; 2.2.3.5 Critical design review; 2.2.4 Software unit code and testing stage; 2.2.4.1 Unit design review (peer evaluation); 2.2.4.2 Unit qualification review (peer evaluation); 2.2.5 Software component integration and testing stage; 2.2.5.1 Integration readiness review (peer evaluation); 2.2.5.2 Product testing readiness review; 2.2.6 Product testing stage; 2.2.6.1 Acceptance testing readiness review
,
2.2.6.2 Testing readiness review2.2.7 Acceptance testing stage; 2.2.7.1 Functional configuration audit; 2.2.7.2 Physical configuration audit; 2.2.7.3 Deployment qualification review; 2.2.7.4 Training qualification review; 2.2.7.5 Sustainment qualification review; 2.2.7.6 Deployment readiness review; 2.3 Summary; 3 Software Architecture; 3.1 Stakeholder needs relationships and dependencies; 3.2 Software requirements baseline relationships and dependencies; 3.3 Computing environment relationships and dependencies; 3.4 Test and evaluation relationships and dependencies
,
3.5 Functional architecture relationships and dependencies3.6 Physical architecture relationships and dependencies; 3.7 Post-development process relationships and dependencies; 3.8 Motivation for the software architecture; 4 Understanding the Software Project Environment; 4.1 Integrated product teams; 4.2 Software architecture; 4.3 Complexity control mechanisms; 4.3.1 Work breakdown structure; 4.3.2 Product breakdown structure; 4.3.3 Specification tree; 4.3.4 Documentation tree; 4.3.5 Software product baselines; 4.3.6 Requirements traceability guidelines; 4.3.7 Trade-off analysis
,
4.3.8 Software complexity measures
,
Front Cover; Software Engineering; Copyright Page; Contents; A Note from the Author; Preface; Book outline and subject matter; 1 Software Engineering Fundamentals; Systems engineering principles and practices; Summary; 1 Introduction to Software Engineering; 1.1 Specifying software requirements; 1.2 Software architecture; 1.3 Integrated product and process development; 1.4 Integrated product teams; 1.5 Work breakdown structure; 1.6 Software breakdown structure; 1.7 Specification and documentation trees; 1.8 Integrated master plan and schedule; 1.9 Reviews and audits
,
1.10 Configuration management and change control1.11 Trade-off analysis; 1.12 Risk management; 1.13 Modeling and simulation; 2 Generic Software Development Framework; 2.1 Software breakdown structure; 2.2 Software development process; 2.2.1 Requirements definition stage; 2.2.1.1 Product requirements review; 2.2.1.2 Software requirements review; 2.2.2 Preliminary architecture definition stage; 2.2.2.1 Preliminary architecture review; 2.2.2.2 Deployment strategy review; 2.2.2.3 Training strategy review; 2.2.2.4 Sustainment strategy review; 2.2.2.5 Preliminary design review
,
2.2.3 Critical architecture definition stage2.2.3.1 Detailed architecture review; 2.2.3.2 Deployment design review; 2.2.3.3 Training design review; 2.2.3.4 Sustainment design review; 2.2.3.5 Critical design review; 2.2.4 Software unit code and testing stage; 2.2.4.1 Unit design review (peer evaluation); 2.2.4.2 Unit qualification review (peer evaluation); 2.2.5 Software component integration and testing stage; 2.2.5.1 Integration readiness review (peer evaluation); 2.2.5.2 Product testing readiness review; 2.2.6 Product testing stage; 2.2.6.1 Acceptance testing readiness review
,
2.2.6.2 Testing readiness review2.2.7 Acceptance testing stage; 2.2.7.1 Functional configuration audit; 2.2.7.2 Physical configuration audit; 2.2.7.3 Deployment qualification review; 2.2.7.4 Training qualification review; 2.2.7.5 Sustainment qualification review; 2.2.7.6 Deployment readiness review; 2.3 Summary; 3 Software Architecture; 3.1 Stakeholder needs relationships and dependencies; 3.2 Software requirements baseline relationships and dependencies; 3.3 Computing environment relationships and dependencies; 3.4 Test and evaluation relationships and dependencies
,
3.5 Functional architecture relationships and dependencies3.6 Physical architecture relationships and dependencies; 3.7 Post-development process relationships and dependencies; 3.8 Motivation for the software architecture; 4 Understanding the Software Project Environment; 4.1 Integrated product teams; 4.2 Software architecture; 4.3 Complexity control mechanisms; 4.3.1 Work breakdown structure; 4.3.2 Product breakdown structure; 4.3.3 Specification tree; 4.3.4 Documentation tree; 4.3.5 Software product baselines; 4.3.6 Requirements traceability guidelines; 4.3.7 Trade-off analysis
,
4.3.8 Software complexity measures
,
Electronic reproduction; Available via World Wide Web
Additional Edition:
ISBN 9780124078789
Additional Edition:
Erscheint auch als Druck-Ausgabe Schmidt, Richard F., 1956 - Software engineering Amsterdam [u.a.] : Elsevier/MK, Morgan Kaufmann, 2013 ISBN 0124077684
Additional Edition:
ISBN 9780124077683
Language:
English
Subjects:
Computer Science
Keywords:
Softwarearchitektur
;
Software Engineering
;
Electronic books
Bookmarklink
