Systems Engineering with SysML The Path to the Future?

Feature‐driven systems engineering procedure for standardized product‐line development

“…These methods combine four viewpoints respec-tively abstraction levels with different granularity layers respectively decomposition levels. 4,37 Analogous to OOSEM, the four viewpoints are divided into consideration of all relevant requirements (requirements viewpoint), description of functions assigned to the system or system elements (functional viewpoint), definition of logical architectures (logical viewpoint) as well as of the technical system realization (technical viewpoint). 4,37 The logical system view is not emphasized by SMArDT and MTSF, but the "realization" is defined as the fourth system view.…”

“…4 The trend of increasing system complexity, caused by increasing networking (e.g., in the fields of Advanced Driver Assistance Systems, Automotive Connectivity, 5 or Internet of Things, 6 ) or increasing degrees of automation, and at the same time shortening development cycles, additionally increase the cost pressure for manufacturers and require high specification quality to avoid delays in the development process. [3][4][5][6][7][8] One core strategy for solving the conflicts between time-to-market, cost reduction, and emerging quality problems is the frontloading of development activities. 4,9 This requires increased effort in early development stages, such as requirement specification and architectural design.…”

“…9,10 One possible type of frontloading is model-based systems engineering, which focuses on the system-based consideration of products and associated processes in all phases of the product life cycle. 4,8,11 A special meaning is assigned to the systembased development of architectures and requirements on basis of continuously extended models. 3,[12][13][14] Model-based systems engineering requires high coordination efforts between all relevant stakeholders in the early phases of the development, but allows a complete consideration of relevant system interdependencies and technical and subject-specific aspects, which leads to an increased quality of requirements.…”

“…3,[12][13][14] Model-based systems engineering requires high coordination efforts between all relevant stakeholders in the early phases of the development, but allows a complete consideration of relevant system interdependencies and technical and subject-specific aspects, which leads to an increased quality of requirements. 3,4 In contrast to classical mechanical engineering, system-based product development is widely established in the area of software, taking into account solution-neutral and product-specific views. Methods for the suitable reuse of system elements and for the realization of variant management have become indispensable in the field of software product line development, but are only rarely used in the design of hardware-based systems.…”

“…7 Model-based specification can contribute to improve communication in interdisciplinary development teams, to the avoidance of inconsistencies between requirements as well as errors and failures that would otherwise only be perceived at later verification levels. 4,8 A transfer of these methods for the design of hardware-oriented products or embedded systems represents a large optimization potential in mechanical engineering dominated industries.…”