{"id":347158,"date":"2024-10-20T00:24:49","date_gmt":"2024-10-20T00:24:49","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-iec-265512016\/"},"modified":"2024-10-25T23:54:11","modified_gmt":"2024-10-25T23:54:11","slug":"bs-iso-iec-265512016","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-iec-265512016\/","title":{"rendered":"BS ISO\/IEC 26551:2016"},"content":{"rendered":"<p>This International Standard, within the context of tools and methods of requirements engineering for software and systems product lines <b>:<\/b><\/p>\n<ul>\n<li>\n<p>provides the terms and definitions specific to requirements engineering for software and systems product lines and associated member products;<\/p>\n<\/li>\n<li>\n<p>defines process groups and their processes performed during product line requirements engineering (those processes are described in terms of purpose, inputs, tasks, and outcomes);<\/p>\n<\/li>\n<li>\n<p>defines method capabilities to support the defined tasks of each process;<\/p>\n<\/li>\n<li>\n<p>defines tool capabilities to automate\/semi-automate tasks or defined method capabilities.<\/p>\n<\/li>\n<\/ul>\n<p>This International Standard concerns processes and capabilities of requirements tools and methods for a family of products, not for a single system.<\/p>\n<p>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.<\/p>\n<div class=\"non-normative-note\">\n<div class=\"note-label\">\n  NOTE\n <\/div>\n<p>The requirements in this International Standard apply to the family of systems, software or services.<\/p>\n<\/div>\n<h4>PDF Catalog<\/h4>\n<table border=\"1px\" class=\"des-table\">\n<tr>\n<th>PDF Pages<\/th>\n<th>PDF Title<\/th>\n<\/tr>\n<tr>\n<td><b>8<b><\/td>\n<td>Foreword  <\/td>\n<\/tr>\n<tr>\n<td><b>9<b><\/td>\n<td>Introduction  <\/td>\n<\/tr>\n<tr>\n<td><b>11<b><\/td>\n<td>1 Scope <br \/> 2 Normative references <br \/> 3 Terms and definitions  <\/td>\n<\/tr>\n<tr>\n<td><b>13<b><\/td>\n<td>4 Reference model for product line requirements engineering  <\/td>\n<\/tr>\n<tr>\n<td><b>17<b><\/td>\n<td>5 Product line scoping  <\/td>\n<\/tr>\n<tr>\n<td><b>18<b><\/td>\n<td>5.1 Product scoping <br \/> 5.1.1 Purpose of product scoping  <\/td>\n<\/tr>\n<tr>\n<td><b>19<b><\/td>\n<td>5.1.2 Structure information to be used for scoping <br \/> 5.1.3 Identify products  <\/td>\n<\/tr>\n<tr>\n<td><b>20<b><\/td>\n<td>5.1.4 Analyse common and variable features <br \/> 5.1.5 Define a product portfolio <br \/> 5.2 Domain scoping <br \/> 5.2.1 Purpose of domain scoping  <\/td>\n<\/tr>\n<tr>\n<td><b>21<b><\/td>\n<td>5.2.2 Identify functional domains <br \/> 5.2.3 Map features to functional domains  <\/td>\n<\/tr>\n<tr>\n<td><b>22<b><\/td>\n<td>5.2.4 Define domain scope <br \/> 5.3 Asset scoping <br \/> 5.3.1 Purpose of asset scoping  <\/td>\n<\/tr>\n<tr>\n<td><b>23<b><\/td>\n<td>5.3.2 Gather historical data from existing single products  <\/td>\n<\/tr>\n<tr>\n<td><b>24<b><\/td>\n<td>5.3.3 Estimate additional effort required to adapt potential assets <br \/> 5.3.4 Estimate expected development effort for new products in the product portfolio definition <br \/> 5.3.5 Estimate economic benefits from reusing proposed assets  <\/td>\n<\/tr>\n<tr>\n<td><b>25<b><\/td>\n<td>5.3.6 Derive asset proposals from economic evaluation results <br \/> 6 Domain requirements engineering  <\/td>\n<\/tr>\n<tr>\n<td><b>26<b><\/td>\n<td>6.1 Domain requirements elicitation <br \/> 6.1.1 Purpose of the domain requirements elicitation  <\/td>\n<\/tr>\n<tr>\n<td><b>27<b><\/td>\n<td>6.1.2 Draw a context diagram <br \/> 6.1.3 Gather domain information  <\/td>\n<\/tr>\n<tr>\n<td><b>28<b><\/td>\n<td>6.1.4 Identify initial domain requirements <br \/> 6.1.5 Review the elicited initial domain requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>29<b><\/td>\n<td>6.2 Domain requirements analysis <br \/> 6.2.1 Purpose of the domain requirements analysis  <\/td>\n<\/tr>\n<tr>\n<td><b>30<b><\/td>\n<td>6.2.2 Classify and balance initial domain requirements <br \/> 6.2.3 Analyse commonalities and variabilities  <\/td>\n<\/tr>\n<tr>\n<td><b>31<b><\/td>\n<td>6.2.4 Model domain requirements <br \/> 6.2.5 Create prototypes and analyse feasibility  <\/td>\n<\/tr>\n<tr>\n<td><b>32<b><\/td>\n<td>6.2.6 Develop conceptual test cases and scenarios for acceptance testing <br \/> 6.2.7 Review the analysed domain requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>33<b><\/td>\n<td>6.3 Domain requirements specification <br \/> 6.3.1 Purpose of the domain requirements specification <br \/> 6.3.2 Identify sources of domain requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>34<b><\/td>\n<td>6.3.3 Establish traceability <br \/> 6.3.4 Document domain requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>35<b><\/td>\n<td>6.3.5 Review the domain requirements specification <br \/> 6.4 Domain requirements verification and validation <br \/> 6.4.1 Purpose of the domain requirements verification and validation  <\/td>\n<\/tr>\n<tr>\n<td><b>36<b><\/td>\n<td>6.4.2 Verify domain requirements <br \/> 6.4.3 Validate domain requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>37<b><\/td>\n<td>6.4.4 Validate conceptual test cases and scenarios for acceptance testing <br \/> 6.4.5 Baseline domain requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>38<b><\/td>\n<td>6.4.6 Initiate change management process <br \/> 6.5 Domain requirements management <br \/> 6.5.1 Purpose of the domain requirements management  <\/td>\n<\/tr>\n<tr>\n<td><b>39<b><\/td>\n<td>6.5.2 Manage domain requirements change  <\/td>\n<\/tr>\n<tr>\n<td><b>40<b><\/td>\n<td>6.5.3 Manage traceability <br \/> 6.5.4 Manage versions of domain requirements <br \/> 6.5.5 Record and report status  <\/td>\n<\/tr>\n<tr>\n<td><b>41<b><\/td>\n<td>6.5.6 Manage process improvement <br \/> 6.5.7 Manage feedback  <\/td>\n<\/tr>\n<tr>\n<td><b>42<b><\/td>\n<td>7 Variability management in requirements engineering <br \/> 7.1 Variability in textual requirements <br \/> 7.1.1 Purpose of variability in textual requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>43<b><\/td>\n<td>7.1.2 Define requirements variability in textual requirements <br \/> 7.1.3 Document requirements variability in textual requirements <br \/> 7.2 Variability in requirements models <br \/> 7.2.1 Purpose of variability in requirements models  <\/td>\n<\/tr>\n<tr>\n<td><b>44<b><\/td>\n<td>7.2.2 Define requirements variability in model <br \/> 7.2.3 Document requirements variability in requirements model  <\/td>\n<\/tr>\n<tr>\n<td><b>45<b><\/td>\n<td>7.3 Variability mechanisms in requirements <br \/> 7.3.1 Purpose of variability mechanisms in requirements <br \/> 7.3.2 Identify variability mechanisms in requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>46<b><\/td>\n<td>7.3.3 Guide the use of variability mechanisms in requirements <br \/> 7.3.4 Verify the usage of variability mechanisms in requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>47<b><\/td>\n<td>7.3.5 Improve variability mechanisms in requirements <br \/> 7.4 Traceability between requirements variability and variability model <br \/> 7.4.1 Purpose of traceability between requirements variability and variability model <br \/> 7.4.2 Define explicit links between requirements variability and variability model  <\/td>\n<\/tr>\n<tr>\n<td><b>48<b><\/td>\n<td>8 Asset management in requirements engineering <br \/> 8.1 Domain requirements artefacts as domain assets <br \/> 8.1.1 Purpose of domain requirements artefacts as domain assets  <\/td>\n<\/tr>\n<tr>\n<td><b>49<b><\/td>\n<td>8.1.2 Identify domain requirements artefacts managed as domain assets <br \/> 8.1.3 Define configuration and annotation  <\/td>\n<\/tr>\n<tr>\n<td><b>50<b><\/td>\n<td>8.2 Application requirements artefacts as application assets <br \/> 8.2.1 Purpose of application requirements artefacts as application assets <br \/> 8.2.2 Identify application requirements artefacts managed as application assets <br \/> 8.2.3 Define configuration and annotation for application requirements assets  <\/td>\n<\/tr>\n<tr>\n<td><b>51<b><\/td>\n<td>9 Application requirements engineering  <\/td>\n<\/tr>\n<tr>\n<td><b>52<b><\/td>\n<td>9.1 Application requirements elicitation <br \/> 9.1.1 Purpose of the application requirements elicitation <br \/> 9.1.2 Draw a context diagram for an application  <\/td>\n<\/tr>\n<tr>\n<td><b>53<b><\/td>\n<td>9.1.3 Identify the requirements gaps between domain and application requirements <br \/> 9.1.4 Bind the best matching variants  <\/td>\n<\/tr>\n<tr>\n<td><b>54<b><\/td>\n<td>9.1.5 Select domain assets <br \/> 9.1.6 Review the elicited application requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>55<b><\/td>\n<td>9.2 Application requirements analysis <br \/> 9.2.1 Purpose of the application requirements analysis  <\/td>\n<\/tr>\n<tr>\n<td><b>56<b><\/td>\n<td>9.2.2 Classify and balance application specific initial requirements <br \/> 9.2.3 Analyse commonalities and variabilities  <\/td>\n<\/tr>\n<tr>\n<td><b>57<b><\/td>\n<td>9.2.4 Model application specific requirements <br \/> 9.2.5 Create prototypes and analyse feasibility  <\/td>\n<\/tr>\n<tr>\n<td><b>58<b><\/td>\n<td>9.2.6 Develop conceptual test cases and scenarios for acceptance testing <br \/> 9.2.7 Review the analysed application requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>59<b><\/td>\n<td>9.3 Application requirements specification <br \/> 9.3.1 Purpose of the application requirements specification  <\/td>\n<\/tr>\n<tr>\n<td><b>60<b><\/td>\n<td>9.3.2 Identify sources of application specific requirements <br \/> 9.3.3 Establish traceabilities for application specific requirements <br \/> 9.3.4 Document application specific requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>61<b><\/td>\n<td>9.3.5 Document the rationale for variability decision <br \/> 9.3.6 Review the application requirements specification <br \/> 9.4 Application requirements verification and validation <br \/> 9.4.1 Purpose of the application requirements verification and validation  <\/td>\n<\/tr>\n<tr>\n<td><b>62<b><\/td>\n<td>9.4.2 Verify application specific requirements <br \/> 9.4.3 Validate application specific requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>63<b><\/td>\n<td>9.4.4 Validate conceptual test cases and scenarios for acceptance testing <br \/> 9.4.5 Baseline application specific requirements  <\/td>\n<\/tr>\n<tr>\n<td><b>64<b><\/td>\n<td>9.4.6 Initiate application change management process <br \/> 9.5 Application requirements management <br \/> 9.5.1 Purpose of the application requirements management  <\/td>\n<\/tr>\n<tr>\n<td><b>65<b><\/td>\n<td>9.5.2 Manage application specific requirements change <br \/> 9.5.3 Manage application specific traceability  <\/td>\n<\/tr>\n<tr>\n<td><b>66<b><\/td>\n<td>9.5.4 Manage versions of application specific requirements artefacts <br \/> 9.5.5 Record and report status of application requirements management <br \/> 9.5.6 Manage application specific process improvement  <\/td>\n<\/tr>\n<tr>\n<td><b>68<b><\/td>\n<td>Annex\u00a0A (informative)  Comparison of requirements engineering tasks between single product and product line  <\/td>\n<\/tr>\n<tr>\n<td><b>70<b><\/td>\n<td>Annex\u00a0B (informative)  Process mapping with ISO\/IEC\u00a012207, ISO\/IEC\/IEEE\u00a015288, and ISO\/IEC\/IEEE\u00a029148  <\/td>\n<\/tr>\n<tr>\n<td><b>73<b><\/td>\n<td>Annex\u00a0C (informative)  A construct for process, method, tool, and aspect  <\/td>\n<\/tr>\n<tr>\n<td><b>74<b><\/td>\n<td>Bibliography  <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p><b>Software and systems engineering. Tools and methods for product line requirements engineering<\/b><\/p>\n<table class=\"shortdes-table\" style=\"width: 100%\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr>\n<td>Published By<\/td>\n<td>Publication Date<\/td>\n<td>Number of Pages<\/td>\n<\/tr>\n<tr>\n<td><a href=\"https:\/\/pdfstandards.shop\/product-category\/publishers\/bsi\/\"><b>BSI<\/b><\/a><\/td>\n<td>2016<\/td>\n<td>78<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":347161,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[2641],"product_tag":[],"class_list":{"0":"post-347158","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-bsi","8":"first","9":"instock","10":"sold-individually","11":"shipping-taxable","12":"purchasable","13":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/347158","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/347161"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=347158"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=347158"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=347158"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}