Software and systems engineering — Tools and methods for product line architecture design

This document, within the context of methods and tools for architecture design for software and systems product lines: — defines processes and their subprocesses performed during domain and application architecture design. 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 document does not concern processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.

Ingénierie du logiciel et des systèmes — Outils et méthodes pour la conception architecturale des gammes de produits

General Information

Status
Published
Publication Date
15-May-2019
Current Stage
9060 - Close of review
Start Date
02-Dec-2029
Ref Project

Buy Standard

Standard
ISO/IEC 26552:2019 - Software and systems engineering — Tools and methods for product line architecture design Released:5/16/2019
English language
61 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO/IEC 26552:2019 - Software and systems engineering -- Tools and methods for product line architecture design
English language
61 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO/IEC
STANDARD 26552
First edition
2019-05
Software and systems engineering —
Tools and methods for product line
architecture design
Ingénierie du logiciel et des systèmes — Outils et méthodes pour la
conception architecturale des gammes de produits
Reference number
©
ISO/IEC 2019
© ISO/IEC 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – All rights reserved

Contents Page
Foreword .vi
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 Terms and Definitions . 1
4 Reference model for product line architecture design . 2
4.1 Overview . 2
4.2 Architecture management . 3
4.3 Domain design . 3
4.4 Asset management . 4
4.5 Variability management in design. 4
4.6 Application design . 5
5 Architecture management . 6
5.1 General . 6
5.2 Architecture design planning . 7
5.2.1 Principal constituents . 7
5.2.2 Establish architecture design goals . 7
5.2.3 Define key procedures for architecture design . 8
5.2.4 Define schedules and required resources for architecture design . 8
5.2.5 Specify how to monitor, measure and control the effectiveness of
architecture design . 9
5.2.6 Document the architecture design plan . 9
5.3 Architecture design enabling .10
5.3.1 Principal constituents .10
5.3.2 Prepare for the architecture enablement .10
5.3.3 Develop and establish enabling capabilities and resources .11
5.3.4 Deploy capabilities and resources for architecture enablement .11
5.3.5 Improve architecture enablement capabilities and resources .12
5.4 Architecture design managing .12
5.4.1 Principal constituents .12
5.4.2 Prepare for architecture management execution .13
5.4.3 Implement the architecture management plans .14
5.4.4 Close and prepare for the architecture management plan change .14
6 Domain design .14
6.1 General .14
6.2 Conceptual architecture design .15
6.2.1 Principal constituents .15
6.2.2 Analyse problem space of the domain architecture .16
6.2.3 Synthesize potential solution alternatives .16
6.2.4 Formulate potential domain architecture(s) .17
6.2.5 Capture domain architecture concepts and properties .17
6.2.6 Hand off conceptualized domain architecture to users and other stakeholders .18
6.3 Domain architectural structure design .18
6.3.1 Principal constituents .18
6.3.2 Develop architecture viewpoints for the product line .19
6.3.3 Develop models and views of the domain architecture .19
6.3.4 Relate the domain architecture to requirements .20
6.3.5 Relate the domain architecture to detailed design .20
6.4 Architectural texture design .21
6.4.1 Principal constituents .21
6.4.2 Analyse common rules guiding realization .21
6.4.3 Define common ways to deal with variability at domain realization .22
© ISO/IEC 2019 – All rights reserved iii

6.4.4 Define common ways to deal with variability at application design and
realization .22
6.4.5 Formulate architectural texture .23
6.5 Domain architecture documentation .23
6.5.1 Principal constituents .23
6.5.2 Assess the domain architecture documentation for structure and texture .24
6.5.3 Hand off architecture documentation to downstream users .24
6.6 Domain architecture evaluation.25
6.6.1 Principal constituents .25
6.6.2 Determine evaluation criteria for domain architecture .26
6.6.3 Establish measurement techniques for domain architecture .26
6.6.4 Review evaluation-related information for domain architecture .27
6.6.5 Analyse domain architecture and assess stakeholder satisfaction .27
6.6.6 Formulate findings and recommendations for domain architecture .28
6.6.7 Communicate evaluation results.28
7 Variability management in design .28
7.1 General .28
7.2 Internal variability in domain architecture .29
7.2.1 Principal constituents .29
7.2.2 Identify newly added internal variability .29
7.2.3 Refine external variability into internal variability .30
7.2.4 Relate internal variability with variability in requirements .30
7.3 Variability model in architecture .31
7.3.1 Principal constituents .31
7.3.2 Model variability in views of architecture(s) .31
7.3.3 Maintain variability model in architecture .32
7.3.4 Document variability in architecture .32
7.4 Variability mechanism in architecture .33
7.4.1 Principal constituents .33
7.4.2 Identify variability mechanisms in architecture by category .33
7.4.3 Guide the use of variability mechanism category in architecture .34
7.4.4 Trace the usage status of variability mechanism category in architecture .34
7.4.5 Update variability mechanism category in architecture .35
7.5 Variability traceability in architecture .35
7.5.1 Principal constituents .35
7.5.2 Define trace links among variability
...


INTERNATIONAL ISO/IEC
STANDARD 26552
First edition
2019-05
Software and systems engineering —
Tools and methods for product line
architecture design
Ingénierie du logiciel et des systèmes — Outils et méthodes pour la
conception architecturale des gammes de produits
Reference number
©
ISO/IEC 2019
© ISO/IEC 2019
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO/IEC 2019 – All rights reserved

Contents Page
Foreword .vi
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 Terms and Definitions . 1
4 Reference model for product line architecture design . 2
4.1 Overview . 2
4.2 Architecture management . 3
4.3 Domain design . 3
4.4 Asset management . 4
4.5 Variability management in design. 4
4.6 Application design . 5
5 Architecture management . 6
5.1 General . 6
5.2 Architecture design planning . 7
5.2.1 Principal constituents . 7
5.2.2 Establish architecture design goals . 7
5.2.3 Define key procedures for architecture design . 8
5.2.4 Define schedules and required resources for architecture design . 8
5.2.5 Specify how to monitor, measure and control the effectiveness of
architecture design . 9
5.2.6 Document the architecture design plan . 9
5.3 Architecture design enabling .10
5.3.1 Principal constituents .10
5.3.2 Prepare for the architecture enablement .10
5.3.3 Develop and establish enabling capabilities and resources .11
5.3.4 Deploy capabilities and resources for architecture enablement .11
5.3.5 Improve architecture enablement capabilities and resources .12
5.4 Architecture design managing .12
5.4.1 Principal constituents .12
5.4.2 Prepare for architecture management execution .13
5.4.3 Implement the architecture management plans .14
5.4.4 Close and prepare for the architecture management plan change .14
6 Domain design .14
6.1 General .14
6.2 Conceptual architecture design .15
6.2.1 Principal constituents .15
6.2.2 Analyse problem space of the domain architecture .16
6.2.3 Synthesize potential solution alternatives .16
6.2.4 Formulate potential domain architecture(s) .17
6.2.5 Capture domain architecture concepts and properties .17
6.2.6 Hand off conceptualized domain architecture to users and other stakeholders .18
6.3 Domain architectural structure design .18
6.3.1 Principal constituents .18
6.3.2 Develop architecture viewpoints for the product line .19
6.3.3 Develop models and views of the domain architecture .19
6.3.4 Relate the domain architecture to requirements .20
6.3.5 Relate the domain architecture to detailed design .20
6.4 Architectural texture design .21
6.4.1 Principal constituents .21
6.4.2 Analyse common rules guiding realization .21
6.4.3 Define common ways to deal with variability at domain realization .22
© ISO/IEC 2019 – All rights reserved iii

6.4.4 Define common ways to deal with variability at application design and
realization .22
6.4.5 Formulate architectural texture .23
6.5 Domain architecture documentation .23
6.5.1 Principal constituents .23
6.5.2 Assess the domain architecture documentation for structure and texture .24
6.5.3 Hand off architecture documentation to downstream users .24
6.6 Domain architecture evaluation.25
6.6.1 Principal constituents .25
6.6.2 Determine evaluation criteria for domain architecture .26
6.6.3 Establish measurement techniques for domain architecture .26
6.6.4 Review evaluation-related information for domain architecture .27
6.6.5 Analyse domain architecture and assess stakeholder satisfaction .27
6.6.6 Formulate findings and recommendations for domain architecture .28
6.6.7 Communicate evaluation results.28
7 Variability management in design .28
7.1 General .28
7.2 Internal variability in domain architecture .29
7.2.1 Principal constituents .29
7.2.2 Identify newly added internal variability .29
7.2.3 Refine external variability into internal variability .30
7.2.4 Relate internal variability with variability in requirements .30
7.3 Variability model in architecture .31
7.3.1 Principal constituents .31
7.3.2 Model variability in views of architecture(s) .31
7.3.3 Maintain variability model in architecture .32
7.3.4 Document variability in architecture .32
7.4 Variability mechanism in architecture .33
7.4.1 Principal constituents .33
7.4.2 Identify variability mechanisms in architecture by category .33
7.4.3 Guide the use of variability mechanism category in architecture .34
7.4.4 Trace the usage status of variability mechanism category in architecture .34
7.4.5 Update variability mechanism category in architecture .35
7.5 Variability traceability in architecture .35
7.5.1 Principal constituents .35
7.5.2 Define trace links among variability
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.