BS ISO IEC 26555 pdf download

BS ISO IEC 26555 pdf download.Software and systems engineering — Tools and methods for product line technical management
1 Scope
This International Standard deals with the tools and methods of technical management for software products, software services, software-intensive systems (including System Architecture and excluding hardware) within a product line. The scope of this International Standard is as follows: — Enable the users of this standard to holistically understand, adopt, and enact the processes, tools, and methods for product line technical management. In addition, this International Standard helps the users evaluate and select relevant tools and methods based on business and user-related criteria. — Help product line engineers, developers, and tool vendors become informed about capabilities of tools and methods that are required for supporting product line implementation from technical aspects. — Provideproductline-specificprocessesandcapabilitiesoftoolsandmethodsintechnicalmanagement. This International Standard does not concern processes and capabilities of tools and methods for technical management for a one-of-a-kind system but rather deals with those belonging to a family of systems. NOTE System Architecture is a set of logical and physical principles used to achieve a mission within a given environment. From System Architecture are derived components that can be subsystems, software products, human-based products like crew or operators or hardware product like mechanical structures, electronic boards, chemicals, etc. The scope of the International Standard spans from the system, to sub-systems, and software products. Other types of components and especially those related to human beings and to hardware parts are not within the scope of this International Standard.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply. 3.1 application engineering process processes for developing a member product in a product line 3.2 attached process process definitions how each asset will be used in application Note 1 to entry: The set of attached processes are those for orchestrating the assets together into a coherent whole application. 3.3 binding time moment of variability resolution 3.4 external variability variability that is visible to customers 3.5 domain engineering process processes for domain asset development 3.6 internal variability variability defined from an engineer’s perspective and is not visible to customers 3.7 variability binding act of determining the variant of the variation point defined in the variability model 3.8 variability documentation detailed description of variability models for being used across the member products within a product line 3.9 variability in space variation that occurs at the same time with different shape 3.10 variability in time variation that occurs at different times 3.11 variability mechanism variability implementation methods in a product line for supporting assembly of domain assets 3.12 variability traceability trace links established for a variability model both with domain assets and with application assets where variants are bound.
4 Reference model for product line technical management
The technical management provides processes for addressing technical issues that arise during implementation of a product line, deployment of processes, and development of assets and products within a product line in balance with accomplishing the objectives of a product line, the given costs, schedule, and so forth. Technical management process group deals with variability management, asset management, process management, support management process for managing technical capabilities, resources, issues, and skills that are required for successful implementation of product lines. Tools and methods in technical management support the systematic development of product lines. Because of profound complexity of product lines, proper tool support for domain engineering lifecycle, application engineering lifecycle, technical management, and organizational management should be provided so that a product line organization can control the technical complexities. The reference model for technical management in Figure 1 is structured into four processes: process management, variability management, asset management, and support management. Each process is divided into subprocesses and each subprocess is described in terms of the following attributes: — the title of the subprocess; — the purpose of the subprocess; — the inputs to produce the outcomes;