| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 11<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 4 Reference model for product line requirements engineering <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 5 Product Line Scoping 5.1 Product scoping <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 5.1.1 Structure information to be used for scoping 5.1.2 Identify products <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 5.1.3 Analyze common and variable features 5.1.4 Define a product portfolio <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 5.2 Domain scoping 5.2.1 Identify functional domains 5.2.2 Map features to functional domains <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 5.2.3 Define domain scope 5.3 Asset scoping <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 5.3.1 Gather historical data from existing single products 5.3.2 Estimate additional effort required to adapt potential assets <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 5.3.3 Estimate expected development effort for new products in the product portfolio definition 5.3.4 Estimate economic benefits from reusing proposed assets 5.3.5 Derive asset proposals from economic evaluation results <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 6 Domain Requirements Engineering 6.1 Domain requirements elicitation <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 6.1.1 Draw a context diagram 6.1.2 Gather domain information <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 6.1.3 Identify initial domain requirements 6.1.4 Review the elicited initial domain requirements <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 6.2 Domain requirements analysis 6.2.1 Classify and balance initial domain requirements <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 6.2.2 Analyze commonalities and variabilities 6.2.3 Model domain requirements <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 6.2.4 Create prototypes and analyze feasibility 6.2.5 Develop conceptual test cases and scenarios for acceptance testing 6.2.6 Review the analyzed domain requirements <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 6.3 Domain requirements specification 6.3.1 Identify sources of domain requirements <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 6.3.2 Establish traceability 6.3.3 Document domain requirements <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 6.3.4 Review the domain requirements specification 6.4 Domain requirements verification and validation <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 6.4.1 Verify domain requirements 6.4.2 Validate domain requirements 6.4.3 Validate conceptual test cases and scenarios for acceptance testing <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 6.4.4 Baseline domain requirements 6.4.5 Initiate change management process 6.5 Domain requirements management <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 6.5.1 Manage domain requirements change <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 6.5.2 Manage traceability 6.5.3 Manage versions of domain requirements 6.5.4 Record and report status <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 6.5.5 Manage process improvement 6.5.6 Manage feedback 7 Variability Management in Requirements Engineering <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 7.1 Variability in textual requirements 7.1.1 Define requirements variability in textual requirements 7.1.2 Document requirements variability in textual requirements <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 7.2 Variability in requirements models 7.2.1 Define requirements variability in model <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 7.2.2 Document requirements variability in requirements model 7.3 Traceability between requirements variability and variability model 7.3.1 Define explicit links between requirements variability and variability model <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 8 Asset Management in Requirements Engineering 8.1 Domain requirements artifacts as domain assets <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 8.1.1 Identify domain requirements artifacts managed as domain assets 8.1.2 Define configuration and annotation 8.2 Application requirements artifacts as application assets <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 8.2.1 Identify application requirements artifacts managed as application assets 8.2.2 Define configuration and annotation for application requirements assets <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 9 Application Requirements Engineering 9.1 Application requirements elicitation <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 9.1.1 Draw a context diagram for an application 9.1.2 Identify the requirements gaps between domain and application requirements <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 9.1.3 Bind the best matching variants 9.1.4 Select domain assets 9.1.5 Review the elicited application requirements <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 9.2 Application requirements analysis <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | 9.2.1 Classify and balance application specific initial requirements 9.2.2 Analyze commonalities and variabilities 9.2.3 Model application specific requirements <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 9.2.4 Create prototypes and analyze feasibility 9.2.5 Develop conceptual test cases and scenarios for acceptance testing <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 9.2.6 Review the analyzed application requirements 9.3 Application requirements specification <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 9.3.1 Identify sources of application specific requirements 9.3.2 Establish traceabilities for application specific requirements 9.3.3 Document application specific requirements <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 9.3.4 Document the rationale for variability decision 9.3.5 Review the application requirements specification 9.4 Application requirements verification and validation <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 9.4.1 Verify application specific requirements 9.4.2 Validate application specific requirements 9.4.3 Validate conceptual test cases and scenarios for acceptance testing <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 9.4.4 Baseline application specific requirements 9.4.5 Initiate application change management process 9.5 Application requirements management <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 9.5.1 Manage application specific requirements change <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | 9.5.2 Manage application specific traceability 9.5.3 Manage versions of application specific requirements artifacts 9.5.4 Record and report status of application requirements management <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | 9.5.5 Manage application specific process improvement <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Software and systems engineering. Tools and methods for product line requirements engineering<\/b><\/p>\n |