Record:   Prev Next
作者 Le Put, Alain
書名 Systems Product Line Engineering Handbook
出版項 TOULOUSE : Cepadues Editions, 2015
©2016
國際標準書號 9782364934993 (electronic bk.)
book jacket
說明 1 online resource (250 pages)
text txt rdacontent
computer c rdamedia
online resource cr rdacarrier
附註 Systems Product Line Engineering Handbook -- 1 Product Line Scoping -- 1.1 Scope -- 1.2 Potential benefits -- 1.2.1 Goals -- 1.2.2 Viewpoints -- 1.3 Product Line Needs Analysis -- 1.3.1 Market Survey -- 1.3.2 Other Needs Analysis -- 1.3.3 Product Line Scope Document -- 1.4 Product Line Specification -- 1.4.1 Lessons Learned from Experience -- 1.4.2 Main Concepts -- 1.4.3 Solution Viability -- 1.4.4 The Software Experience -- 1.4.5 Product Line Specification Document -- 1.5 Strategic Plan -- 1.5.1 Setting up a Product Line and Investment -- 1.5.2 Choosing a Product Line Organization -- 1.5.3 Product Line Change Strategy -- 1.5.4 Investment -- 1.5.5 Break-Even Point -- 1.5.6 Strategic Plan -- 1.6 Working in a Product Line Organization and Recurrent Costs -- 1.6.1 Working in a Product Line Organization -- 1.6.2 Recurrent Costs -- 1.6.3 Management -- 2 Product Description and Management -- 2.1 Scope -- 2.2 Product Description -- 2.2.1 Common features (or common artifacts) -- 2.2.2 Variability and Variation Points -- 2.2.3 Variants -- 2.2.4 Variability Constraints -- 2.2.5 Specific features -- 2.3 Product Organization -- 2.3.1 Initial Variability Breakdown Structure -- 2.3.2 Product Openness and Robustness -- 2.3.3 Evolving and enriching the Generic System -- 2.3.4 Product Configuration -- 2.4 Reuse and Capitalization -- 2.4.1 Reusing the Generic Product -- 2.4.2 Capitalization in the Generic Product -- 2.4.2.1 A posteriori Product Capitalization -- 2.4.2.2 A priori Product Capitalization -- 2.4.3 Simplifying the Generic Product -- 2.5 Managing the Generic Product -- 2.5.1 Responsibilities -- 2.5.2 Domain CCB and Application CCB -- 2.5.3 CCB Organization -- 3 Enterprise Organization and Process Management -- 3.1 Scope -- 3.2 Systems Engineering Organization -- 3.2.1 Organization -- 3.2.2 Tailoring the Systems Engineering Process
3.3 Reuse and Capitalization Processes -- 3.3.1 Opportunistic Reuse -- 3.3.1.1 Opportunistic Reuse without links -- 3.3.1.2 Opportunistic Reuse with links -- 3.3.1.3 Opportunistic Reuse and Capitalization -- 3.3.2 Integrated Reuse and Capitalization -- 3.3.2.1 Application Systems Engineering -- 3.3.2.2 Domain Systems Engineering -- 3.3.3 Anticipated Reuse and Capitalization -- 3.4 Systems Engineering Process -- 3.5 Systems Engineering Team Organization -- 3.6 Process Management -- 3.6.1 Setting up Management -- 3.6.2 Product Line Maturity -- 3.6.2.1 Opportunistic Reuse -- 3.6.2.2 Integrated Reuse -- 3.6.2.3 Managed Reuse -- 3.6.2.4 Anticipated Reuse -- 3.6.3 Product Line Change Strategy -- 3.6.4 Lessons Learned from Experience -- 3.6.4.1 Thales Alenia Space Satellite Product Line -- 3.6.4.2 Interacting Product Lines -- 3.7 Product Lines and Process Improvement -- 3.7.1 Setting Up a Product Line and the CMMI -- 3.7.2 Maturity -- 3.7.2.1 Process Maturity -- 3.7.2.2 Product Maturity -- 3.7.2.3 Organization Maturity -- 3.7.3 Enterprise Culture -- 4 Profit and Investment Management -- 4.1 Scope -- 4.2 Return on Investment (ROI) -- 4.2.1 Definition -- 4.2.2 Example -- 4.3 Using the ROI Tool -- 4.3.1 Taking into account all the parameters -- 4.3.2 Example -- 4.3.3 Decision Analysis and Resolution -- 4.4 Planning the ROI -- 4.5 Product Line Management -- 4.5.1 Setting Up Management -- 4.5.2 Product Line Change Strategy -- 4.5.3 Product Line Life Cycle -- 4.5.4 Responsibilities -- 4.5.5 Role of the Enterprise Management -- 4.6 Lessons Learned from Experience -- 4.6.1 Reuse rate estimation -- 4.6.2 Real Example -- 5 Requirements Engineering -- 5.1 Scope -- 5.2 Types of Requirement Concerned -- 5.3 Stakeholder Needs and Requirements Definition -- 5.3.1 Process (Reminder) -- 5.3.2 Eliciting needs -- 5.3.3 Capitalizing Needs -- 5.3.4 Product Portfolio
5.3.5 Meeting Needs -- 5.4 System Requirements Specification -- 5.4.1 Process Reminder -- 5.4.2 Requirements Breakdown Structure -- 5.4.3 Generic Requirements -- 5.4.4 Reusing requirements -- 5.4.5 Defining Requirements -- 5.4.6 Requirements Analysis -- 5.4.6.1 Process Reminder -- 5.4.6.2 "Classical" Needs Definition -- 5.4.6.3 Needs Definition when using the Product Line Portfolio -- 5.4.7 Technical Specification -- 5.5 Allocating Requirements to System Components -- 5.5.1 Process Reminder -- 5.5.2 Allocated Requirements and Interface Requirements -- 5.6 Requirements Management -- 5.6.1 Process Reminder -- 5.6.2 Managing Requirements in a Product Line -- 5.6.3 Working Space -- 5.7 Product Line Change Strategy -- 6 Architectural Design -- 6.1 Scope -- 6.2 Architectural Design -- 6.2.1 Architectural Design Methods Reminder -- 6.2.2 Selecting an Architectural Design Reminder -- 6.2.3 Drawing Convention -- 6.2.4 Architectural Design Example -- 6.3 Robust Architectural Design -- 6.3.1 Reusing Architectural Design with small change -- 6.3.2 Reusing Architectural Design with big change -- 6.3.3 Architectural Design Rigidity -- 6.3.4 Examples of Architectural Design Rigidity -- 6.4 Reusable Architectural Design -- 6.4.1 Reusability Criteria -- 6.4.2 Example of Reusing a Rigid Architectural Design -- 6.5 Architectural Design driven by Reusability -- 6.5.1 Architectural Design Variability -- 6.5.2 Examples of Architectural Design Variability -- 6.5.2.1 Example of Variability in Software Interface -- 6.5.2.2 Example of Variability in mechanical Interface -- 6.5.2.3 Example of Variability in electrical Interface -- 6.5.2.4 Example of Variability in thermal Interface -- 6.6 Product Line Change Strategy -- 7 System Building and System Tests2F -- 7.1 Scope -- 7.1.1 Problem scope -- 7.1.2 Processes Reminder -- 7.1.3 The "Testing" Concept -- 7.2 Tests
7.2.1 Test Strategy -- 7.2.2 Testing the Generic Product -- 7.2.3 Testing Applications -- 7.2.4 Opportunistic Tests and Test Results Capitalization -- 7.2.4.1 Opportunistic Tests -- 7.2.4.2 Capitalization of Test Results for Opportunistic Tests -- 7.2.5 Test Facilities (enabling) -- 7.3 System Integration and Integration Tests -- 7.3.1 Process Reminder -- 7.3.2 Testing the System Components -- 7.3.3 Integration Strategy -- 7.3.4 Integration Procedure and Integration Means -- 7.3.5 Integration Tests and Integration Means -- 7.4 System Verification and Verification Tests -- 7.4.1 Process Reminder -- 7.4.2 System Verification and Verification Tests -- 7.4.3 Optimizing System Verification Tests -- 7.5 System Transition and Transition Tests -- 7.5.1 Process Reminder -- 7.5.2 System Transition and Transition means -- 7.5.3 Example of System Transition -- 7.6 System Validation and Validation Tests -- 7.6.1 Process Reminder -- 7.6.2 System Validation and Validation Tests -- 7.7 Other System Building Processes (QCA) -- 7.7.1 IVTV vs IVVQCA -- 7.7.2 QCA -- 7.7.3 Configuration Audits -- 7.7.3.1 Reminder -- 7.7.3.2 Product Line Qualification -- 7.7.3.3 Product Line Audits and Qualification -- 7.8 Product Line Change Strategy -- 7.8.1 System Definition Processes and System Building Processes -- 7.8.2 Product Maturity -- 8 System Life Cycle Processes -- 8.1 Scope -- 8.2 Concept -- 8.2.1 Concept Phase Reminder -- 8.2.2 Concept Phase and Product Line -- 8.3 Production -- 8.4 Operation -- 8.5 Maintenance (Support) -- 8.6 Disposal (Withdrawal) -- 9 Model Based Product Line Systems Engineering -- 9.1 Scope -- 9.1.1 System Product Line -- 9.1.2 Model Based Systems Engineering (MBSE) -- 9.1.3 Model Based Product Line Systems Engineering -- 9.2 Product Line Modeling -- 9.2.1 Definition -- 9.2.3 Variability Model Quality Criteria -- 9.2.4 Benefits of Modeling
9.2.5 Formalism -- 9.2.6 Selecting a Formalism -- 9.3 Model Based Product Line Systems Engineering -- 9.3.1 Systems Engineering Artifacts -- 9.3.2 Systems Engineering Artifact Variability -- 9.3.3 Relationships between the Systems Engineering Artifacts -- 9.3.4 Relationships between the Variability Models for Systems Engineering Artifacts -- 9.3.5 Relationships between Variation Points inherited from the Traceability of Systems Engineering Artifacts -- 9.3.6 Relationships between Variation Points not inherited from the Traceability of Systems Engineering Artifacts -- 9.3.7 Relationships between Variability Constraints inherited from the Traceability of Systems Engineering Artifacts -- 9.3.8 Other Relationships between Variation Points -- 9.3.9 Model Based Product Line Systems Engineering -- 9.3.10 Variability Model Quality Criteria for Model Based Product Line Systems Engineering -- 9.4 Model Based Product Line Systems Engineering Mockup -- 9.4.1 Goals -- 9.4.2 First Mockup -- 9.4.3 Second Mockup -- 9.4.4 Conclusions -- 10 Conclusions -- 10.1 Product Line Definition -- 10.1.1 Dimensions of Product Lines -- 10.1.2 Product Line Meta Model -- 10.2 Systems product line engineering -- 10.3 PRODUCT LINE CHANGE STRATEGY -- 10.3.1 Pieces of Product Line Change Strategy -- 10.3.2 Goals -- 10.3.3 Dependencies -- 10.3.4 Product Line Maturity -- 10.3.5 Product Line Thinking -- 10.3.6 Enterprise Management Involvement -- 10.3.7 Global Product Line Change Strategy -- 10.4 State of Art -- 10.4.1 Lessons Learned from Experience -- 10.4.2 Model-Based Product Line Systems Engineering State of Art -- 10.4.2.1 Standardization -- 10.4.2.2 Research -- 10.4.3 Tools -- 10.5 So now what… -- Page vierge
Description based on publisher supplied metadata and other sources
Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2020. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries
鏈接 Print version: Le Put, Alain Systems Product Line Engineering Handbook TOULOUSE : Cepadues Editions,c2015
主題 Software engineering-Handbooks, manuals, etc.
Software product line engineering-Handbooks, manuals, etc
Electronic books
Alt Author AFIS, Collectif
Record:   Prev Next