🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS ISO/IEC 26551:2012:2013 Edition

BS ISO/IEC 26551:2012:2013 Edition

$198.66

Software and systems engineering. Tools and methods for product line requirements engineering

Published By Publication Date Number of Pages
BSI 2013 66
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

PDF Catalog

PDF Pages PDF Title
11 1 Scope
2 Normative references
3 Terms and definitions
13 4 Reference model for product line requirements engineering
17 5 Product Line Scoping
5.1 Product scoping
18 5.1.1 Structure information to be used for scoping
5.1.2 Identify products
19 5.1.3 Analyze common and variable features
5.1.4 Define a product portfolio
20 5.2 Domain scoping
5.2.1 Identify functional domains
5.2.2 Map features to functional domains
21 5.2.3 Define domain scope
5.3 Asset scoping
22 5.3.1 Gather historical data from existing single products
5.3.2 Estimate additional effort required to adapt potential assets
23 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
24 6 Domain Requirements Engineering
6.1 Domain requirements elicitation
25 6.1.1 Draw a context diagram
6.1.2 Gather domain information
26 6.1.3 Identify initial domain requirements
6.1.4 Review the elicited initial domain requirements
27 6.2 Domain requirements analysis
6.2.1 Classify and balance initial domain requirements
28 6.2.2 Analyze commonalities and variabilities
6.2.3 Model domain requirements
29 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
30 6.3 Domain requirements specification
6.3.1 Identify sources of domain requirements
31 6.3.2 Establish traceability
6.3.3 Document domain requirements
32 6.3.4 Review the domain requirements specification
6.4 Domain requirements verification and validation
33 6.4.1 Verify domain requirements
6.4.2 Validate domain requirements
6.4.3 Validate conceptual test cases and scenarios for acceptance testing
34 6.4.4 Baseline domain requirements
6.4.5 Initiate change management process
6.5 Domain requirements management
35 6.5.1 Manage domain requirements change
36 6.5.2 Manage traceability
6.5.3 Manage versions of domain requirements
6.5.4 Record and report status
37 6.5.5 Manage process improvement
6.5.6 Manage feedback
7 Variability Management in Requirements Engineering
38 7.1 Variability in textual requirements
7.1.1 Define requirements variability in textual requirements
7.1.2 Document requirements variability in textual requirements
39 7.2 Variability in requirements models
7.2.1 Define requirements variability in model
40 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
41 8 Asset Management in Requirements Engineering
8.1 Domain requirements artifacts as domain assets
42 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
43 8.2.1 Identify application requirements artifacts managed as application assets
8.2.2 Define configuration and annotation for application requirements assets
44 9 Application Requirements Engineering
9.1 Application requirements elicitation
45 9.1.1 Draw a context diagram for an application
9.1.2 Identify the requirements gaps between domain and application requirements
46 9.1.3 Bind the best matching variants
9.1.4 Select domain assets
9.1.5 Review the elicited application requirements
47 9.2 Application requirements analysis
48 9.2.1 Classify and balance application specific initial requirements
9.2.2 Analyze commonalities and variabilities
9.2.3 Model application specific requirements
49 9.2.4 Create prototypes and analyze feasibility
9.2.5 Develop conceptual test cases and scenarios for acceptance testing
50 9.2.6 Review the analyzed application requirements
9.3 Application requirements specification
51 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
52 9.3.4 Document the rationale for variability decision
9.3.5 Review the application requirements specification
9.4 Application requirements verification and validation
53 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
54 9.4.4 Baseline application specific requirements
9.4.5 Initiate application change management process
9.5 Application requirements management
55 9.5.1 Manage application specific requirements change
56 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
57 9.5.5 Manage application specific process improvement

Related products

BS ISO/IEC 26551:2012
$198.66