🔥🔥 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:2016

BS ISO/IEC 26551:2016

$215.11

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

Published By Publication Date Number of Pages
BSI 2016 78
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]

This International Standard, within the context of tools and methods of requirements engineering for software and systems product lines :

  • provides the terms and definitions specific to requirements engineering for software and systems product lines and associated member products;

  • defines process groups and their processes performed during product line requirements engineering (those processes are described in terms of purpose, inputs, tasks, and outcomes);

  • defines method capabilities to support the defined tasks of each process;

  • defines tool capabilities to automate/semi-automate tasks or defined method capabilities.

This International Standard concerns processes and capabilities of requirements tools and methods for a family of products, not for a single system.

This International Standard is not applicable to physical artefacts. Instead, system-level artefacts and software lifecycle artefacts such as requirements documents, architectural data, validation plans, behavioural models, etc. are produced using methods and tools in this International Standard. In the case of the software components of a system, this International Standard can apply twice: once to handle the system elements of the product line and a second time to handle the software elements of the product line, if any. The product line processes are recursive within the different levels of products.

NOTE

The requirements in this International Standard apply to the family of systems, software or services.

PDF Catalog

PDF Pages PDF Title
8 Foreword
9 Introduction
11 1 Scope
2 Normative references
3 Terms and definitions
13 4 Reference model for product line requirements engineering
17 5 Product line scoping
18 5.1 Product scoping
5.1.1 Purpose of product scoping
19 5.1.2 Structure information to be used for scoping
5.1.3 Identify products
20 5.1.4 Analyse common and variable features
5.1.5 Define a product portfolio
5.2 Domain scoping
5.2.1 Purpose of domain scoping
21 5.2.2 Identify functional domains
5.2.3 Map features to functional domains
22 5.2.4 Define domain scope
5.3 Asset scoping
5.3.1 Purpose of asset scoping
23 5.3.2 Gather historical data from existing single products
24 5.3.3 Estimate additional effort required to adapt potential assets
5.3.4 Estimate expected development effort for new products in the product portfolio definition
5.3.5 Estimate economic benefits from reusing proposed assets
25 5.3.6 Derive asset proposals from economic evaluation results
6 Domain requirements engineering
26 6.1 Domain requirements elicitation
6.1.1 Purpose of the domain requirements elicitation
27 6.1.2 Draw a context diagram
6.1.3 Gather domain information
28 6.1.4 Identify initial domain requirements
6.1.5 Review the elicited initial domain requirements
29 6.2 Domain requirements analysis
6.2.1 Purpose of the domain requirements analysis
30 6.2.2 Classify and balance initial domain requirements
6.2.3 Analyse commonalities and variabilities
31 6.2.4 Model domain requirements
6.2.5 Create prototypes and analyse feasibility
32 6.2.6 Develop conceptual test cases and scenarios for acceptance testing
6.2.7 Review the analysed domain requirements
33 6.3 Domain requirements specification
6.3.1 Purpose of the domain requirements specification
6.3.2 Identify sources of domain requirements
34 6.3.3 Establish traceability
6.3.4 Document domain requirements
35 6.3.5 Review the domain requirements specification
6.4 Domain requirements verification and validation
6.4.1 Purpose of the domain requirements verification and validation
36 6.4.2 Verify domain requirements
6.4.3 Validate domain requirements
37 6.4.4 Validate conceptual test cases and scenarios for acceptance testing
6.4.5 Baseline domain requirements
38 6.4.6 Initiate change management process
6.5 Domain requirements management
6.5.1 Purpose of the domain requirements management
39 6.5.2 Manage domain requirements change
40 6.5.3 Manage traceability
6.5.4 Manage versions of domain requirements
6.5.5 Record and report status
41 6.5.6 Manage process improvement
6.5.7 Manage feedback
42 7 Variability management in requirements engineering
7.1 Variability in textual requirements
7.1.1 Purpose of variability in textual requirements
43 7.1.2 Define requirements variability in textual requirements
7.1.3 Document requirements variability in textual requirements
7.2 Variability in requirements models
7.2.1 Purpose of variability in requirements models
44 7.2.2 Define requirements variability in model
7.2.3 Document requirements variability in requirements model
45 7.3 Variability mechanisms in requirements
7.3.1 Purpose of variability mechanisms in requirements
7.3.2 Identify variability mechanisms in requirements
46 7.3.3 Guide the use of variability mechanisms in requirements
7.3.4 Verify the usage of variability mechanisms in requirements
47 7.3.5 Improve variability mechanisms in requirements
7.4 Traceability between requirements variability and variability model
7.4.1 Purpose of traceability between requirements variability and variability model
7.4.2 Define explicit links between requirements variability and variability model
48 8 Asset management in requirements engineering
8.1 Domain requirements artefacts as domain assets
8.1.1 Purpose of domain requirements artefacts as domain assets
49 8.1.2 Identify domain requirements artefacts managed as domain assets
8.1.3 Define configuration and annotation
50 8.2 Application requirements artefacts as application assets
8.2.1 Purpose of application requirements artefacts as application assets
8.2.2 Identify application requirements artefacts managed as application assets
8.2.3 Define configuration and annotation for application requirements assets
51 9 Application requirements engineering
52 9.1 Application requirements elicitation
9.1.1 Purpose of the application requirements elicitation
9.1.2 Draw a context diagram for an application
53 9.1.3 Identify the requirements gaps between domain and application requirements
9.1.4 Bind the best matching variants
54 9.1.5 Select domain assets
9.1.6 Review the elicited application requirements
55 9.2 Application requirements analysis
9.2.1 Purpose of the application requirements analysis
56 9.2.2 Classify and balance application specific initial requirements
9.2.3 Analyse commonalities and variabilities
57 9.2.4 Model application specific requirements
9.2.5 Create prototypes and analyse feasibility
58 9.2.6 Develop conceptual test cases and scenarios for acceptance testing
9.2.7 Review the analysed application requirements
59 9.3 Application requirements specification
9.3.1 Purpose of the application requirements specification
60 9.3.2 Identify sources of application specific requirements
9.3.3 Establish traceabilities for application specific requirements
9.3.4 Document application specific requirements
61 9.3.5 Document the rationale for variability decision
9.3.6 Review the application requirements specification
9.4 Application requirements verification and validation
9.4.1 Purpose of the application requirements verification and validation
62 9.4.2 Verify application specific requirements
9.4.3 Validate application specific requirements
63 9.4.4 Validate conceptual test cases and scenarios for acceptance testing
9.4.5 Baseline application specific requirements
64 9.4.6 Initiate application change management process
9.5 Application requirements management
9.5.1 Purpose of the application requirements management
65 9.5.2 Manage application specific requirements change
9.5.3 Manage application specific traceability
66 9.5.4 Manage versions of application specific requirements artefacts
9.5.5 Record and report status of application requirements management
9.5.6 Manage application specific process improvement
68 Annex A (informative) Comparison of requirements engineering tasks between single product and product line
70 Annex B (informative) Process mapping with ISO/IEC 12207, ISO/IEC/IEEE 15288, and ISO/IEC/IEEE 29148
73 Annex C (informative) A construct for process, method, tool, and aspect
74 Bibliography

Related products

BS ISO/IEC 26551:2016
$215.11