This document, within the context of methods and tools for architecture design for software and systems product lines:<\/p>\n
defines processes and their subprocesses performed during domain and application architecture design. Those processes are described in terms of purpose, inputs, tasks and outcomes;<\/p>\n<\/li>\n
defines method capabilities to support the defined tasks of each process;<\/p>\n<\/li>\n
defines tool capabilities to automate\/semi-automate tasks or defined method capabilities.<\/p>\n<\/li>\n<\/ul>\n
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.<\/p>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | National foreword <\/td>\n<\/tr>\n | ||||||
| 8<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
| 9<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 1 Scope 2 Normative references 3 Terms and Definitions <\/td>\n<\/tr>\n | ||||||
| 12<\/td>\n | 4 Reference model for product line architecture design 4.1 Overview <\/td>\n<\/tr>\n | ||||||
| 13<\/td>\n | 4.2 Architecture management 4.3 Domain design <\/td>\n<\/tr>\n | ||||||
| 14<\/td>\n | 4.4 Asset management 4.5 Variability management in design <\/td>\n<\/tr>\n | ||||||
| 15<\/td>\n | 4.6 Application design <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 5 Architecture management 5.1 General <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 5.2 Architecture design planning 5.2.1 Principal constituents 5.2.2 Establish architecture design goals <\/td>\n<\/tr>\n | ||||||
| 18<\/td>\n | 5.2.3 Define key procedures for architecture design 5.2.4 Define schedules and required resources for architecture design <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 5.2.5 Specify how to monitor, measure and control the effectiveness of architecture design 5.2.6 Document the architecture design plan <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 5.3 Architecture design enabling 5.3.1 Principal constituents 5.3.2 Prepare for the architecture enablement <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 5.3.3 Develop and establish enabling capabilities and resources 5.3.4 Deploy capabilities and resources for architecture enablement <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 5.3.5 Improve architecture enablement capabilities and resources 5.4 Architecture design managing 5.4.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 5.4.2 Prepare for architecture management execution <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 5.4.3 Implement the architecture management plans 5.4.4 Close and prepare for the architecture management plan change 6 Domain design 6.1 General <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 6.2 Conceptual architecture design 6.2.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 6.2.2 Analyse problem space of the domain architecture 6.2.3 Synthesize potential solution alternatives <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 6.2.4 Formulate potential domain architecture(s) 6.2.5 Capture domain architecture concepts and properties <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 6.2.6 Hand off conceptualized domain architecture to users and other stakeholders 6.3 Domain architectural structure design 6.3.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 6.3.2 Develop architecture viewpoints for the product line 6.3.3 Develop models and views of the domain architecture <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 6.3.4 Relate the domain architecture to requirements 6.3.5 Relate the domain architecture to detailed design <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 6.4 Architectural texture design 6.4.1 Principal constituents 6.4.2 Analyse common rules guiding realization <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 6.4.3 Define common ways to deal with variability at domain realization 6.4.4 Define common ways to deal with variability at application design and realization <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 6.4.5 Formulate architectural texture 6.5 Domain architecture documentation 6.5.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 6.5.2 Assess the domain architecture documentation for structure and texture 6.5.3 Hand off architecture documentation to downstream users <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 6.6 Domain architecture evaluation 6.6.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 6.6.2 Determine evaluation criteria for domain architecture 6.6.3 Establish measurement techniques for domain architecture <\/td>\n<\/tr>\n | ||||||
| 37<\/td>\n | 6.6.4 Review evaluation-related information for domain architecture 6.6.5 Analyse domain architecture and assess stakeholder satisfaction <\/td>\n<\/tr>\n | ||||||
| 38<\/td>\n | 6.6.6 Formulate findings and recommendations for domain architecture 6.6.7 Communicate evaluation results 7 Variability management in design 7.1 General <\/td>\n<\/tr>\n | ||||||
| 39<\/td>\n | 7.2 Internal variability in domain architecture 7.2.1 Principal constituents 7.2.2 Identify newly added internal variability <\/td>\n<\/tr>\n | ||||||
| 40<\/td>\n | 7.2.3 Refine external variability into internal variability 7.2.4 Relate internal variability with variability in requirements <\/td>\n<\/tr>\n | ||||||
| 41<\/td>\n | 7.3 Variability model in architecture 7.3.1 Principal constituents 7.3.2 Model variability in views of architecture(s) <\/td>\n<\/tr>\n | ||||||
| 42<\/td>\n | 7.3.3 Maintain variability model in architecture 7.3.4 Document variability in architecture <\/td>\n<\/tr>\n | ||||||
| 43<\/td>\n | 7.4 Variability mechanism in architecture 7.4.1 Principal constituents 7.4.2 Identify variability mechanisms in architecture by category <\/td>\n<\/tr>\n | ||||||
| 44<\/td>\n | 7.4.3 Guide the use of variability mechanism category in architecture 7.4.4 Trace the usage status of variability mechanism category in architecture <\/td>\n<\/tr>\n | ||||||
| 45<\/td>\n | 7.4.5 Update variability mechanism category in architecture 7.5 Variability traceability in architecture 7.5.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 46<\/td>\n | 7.5.2 Define trace links among variability in different architectural artefacts 7.5.3 Define trace links between architectural artefacts and variability model 8 Asset management in design 8.1 General <\/td>\n<\/tr>\n | ||||||
| 47<\/td>\n | 8.2 Managing domain design artefacts as domain assets 8.2.1 Principal constituents 8.2.2 Identify architectural artefacts managed as domain assets <\/td>\n<\/tr>\n | ||||||
| 48<\/td>\n | 8.2.3 Define configuration and annotation for domain architecture assets 8.3 Managing application design artefacts as application assets 8.3.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 49<\/td>\n | 8.3.2 Identify architectural artefacts managed as application assets 8.3.3 Define configuration and annotation for application architecture assets <\/td>\n<\/tr>\n | ||||||
| 50<\/td>\n | 9 Application design 9.1 General 9.2 Binding in architecture 9.2.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 51<\/td>\n | 9.2.2 Decide values of variabilities in architecture 9.2.3 Conduct bindings in architecture <\/td>\n<\/tr>\n | ||||||
| 52<\/td>\n | 9.2.4 Validate consistencies with bindings in requirements 9.2.5 Validate whether binding decisions adhere to the architectural texture 9.3 Application specific architectural structure design 9.3.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 53<\/td>\n | 9.3.2 Develop models of the application specific architecture <\/td>\n<\/tr>\n | ||||||
| 54<\/td>\n | 9.3.3 Validate whether the application specific architecture adheres to the architectural texture 9.3.4 Relate the application specific architecture to requirements 9.3.5 Relate the application specific architecture to detailed design <\/td>\n<\/tr>\n | ||||||
| 55<\/td>\n | 9.4 Application architecture documentation 9.4.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 56<\/td>\n | 9.4.2 Assess the application specific architecture documentation 9.4.3 Hand off application specific architecture documentation to downstream users <\/td>\n<\/tr>\n | ||||||
| 57<\/td>\n | 9.5 Application architecture evaluation 9.5.1 Principal constituents <\/td>\n<\/tr>\n | ||||||
| 58<\/td>\n | 9.5.2 Determine application specific evaluation criteria 9.5.3 Establish application specific measurement techniques 9.5.4 Review evaluation-related information for application architecture <\/td>\n<\/tr>\n | ||||||
| 59<\/td>\n | 9.5.5 Analyse application architecture and assess stakeholder satisfaction 9.5.6 Formulate findings and recommendations for application architecture <\/td>\n<\/tr>\n | ||||||
| 60<\/td>\n | 9.5.7 Communicate evaluation results with application specific stakeholders <\/td>\n<\/tr>\n | ||||||
| 61<\/td>\n | Annex A (informative) Cross-reference with ISO\/IEC\/IEEE 42020, ISO\/IEC\/IEEE 42010 and ISO\/IEC\/IEEE 15288 <\/td>\n<\/tr>\n | ||||||
| 68<\/td>\n | Annex B (informative) Variability specification elements in ADL <\/td>\n<\/tr>\n | ||||||
| 69<\/td>\n | Annex C (informative) Architecture structure and texture example <\/td>\n<\/tr>\n | ||||||
| 70<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Software and systems engineering. Tools and methods for product line architecture design<\/b><\/p>\n |