SAFe approach to Systems Engineering disciplines
When we review the Systems Engineering disciplines, we can see that most of the different disciplines are addressed in SAFe using different wordings and concepts:
1.????Requirement Management
Since SAFe has its roots in the book “Agile Software Requirements” [1], this discipline is fully embraced by SAFe. To name a few obvious mapping:
In addition, SE requirement management defines further artifacts, where the mapping is defined in more detail in “[7] 01 Achieving Regulatory and Industry Standards Compliance with SAFe 5.0”:
2.????Integration, Verification and Validation (IVV)
Vehicles underlie compliance regulations e.g. regarding functional safety (ISO 26262), software process reference and assessment models (Automotive SPICE), cyber security and software update management (UNECE WP.29) and CO2 emissions (WLTP, RDE). These regulations impose requirements on the development process or the product itself. Regulations that affect the development process can be implemented with processes, methods, tools, and organizational measures. Regulations that address the product must be fed into the development process as requirements and systematically implemented, verified, and validated in order to obtain certifications / type approvals [18]. Traceability between the artifacts must be maintained over the product life cycle so that evidence for meeting the regulations can be presented e.g. during an assessment or audit.
SAFe provides concepts and processes that continuously foster verification and validation, while making the V&V activities part of a regular flow:
●??????Iterations verification using automated story testing
●??????Iteration validation using bi-weekly system demos
●??????PI validation using quarterly PI system and solution demos
●??????Release validations
?
Compliance Example:
Within the UNECE, the CSMS (CyberSecurity Management System) and the SUMS (Software Update Management System) are two important regulations the automotive industry must fulfill. The aim is to specify a structured process for the CSMS/SUMS at car manufacturers and for cybersecurity and software update in the vehicle, which reduces the success rate of hacker attacks and establishes a standard against cyber threats in the automotive industry. Using the SAFe V&V activities, those regulations can be implemented [18].?The PEDCO Applied SAFe Platform [9] is a process model on the standard process platform stages that maps difference compliance frameworks like ASPICE, or Safety to the SAFe Framework. OEMs can extend Applied SAFe with their own process models and therefore prove the process conformity. This reduces the implementation time of SAFe processes models.
领英推荐
3. Configuration Management?
The SAFe Concept to implement versioning, baselining, delta analysis, etc. is the “solution Intent”, which contains all artifacts (specifications, code, tests, etc.) that are subject of configuration management. The “solution intent” also contains hardware and physical models, and a list of experiments by registering rooms and locations. To show the complexity an OEM might implement the “solution intent” using an IT landscape with over 100 of applications.
When integrating the system continuously, configuration management may become a bottleneck, because the system will be continuously changed. Automation and Tooling of the Configuration Management is key.
4. Release Management (not part of ISO 15288)
One major Systems Engineering discipline when building a vehicle or other safety relevant products is Release Management. Who takes the responsibility for releasing products? In the SAFe “Agile Product Delivery” Competency, the concept “Develop on Cadence and Release on Demand” differentiates between a technical release and a business/contractual release:
a. Technical Release Management
The complete solution train (450 people) especially the teams with their Build-In Quality core value are responsible to check the technical compliance by building automated compliance checks. The technical “release” happens on the sprint and PI cadence, where development increments are continuously being developed and accepted by PO, PM and SM with the support of DoD and test results.
b. Business Release Management
For an Automotive Solution you have one or more business owners who take the responsibility to sign and give fast feedback to the teams. This release management function has the authority, knowledge, and capacity to foster and approve releases.
5.????Function and System Architecture Creation
In SAFe Architecture descriptions, Functional Architecture, Logical Architecture, and Physical Architecture are created using the “Agile Architecture” approach. This approach is not part of Systems Engineering.
Agile Architecture is a set of values, practices, and collaborations that support the active, evolutionary design and architecture of a system. It is a collaboration and balance between intentional architecture driven by the system/solution architects and emergent design developed by the teams. It is important that architecture will be developed iteratively. Architecture evolves supported by MBSE where models evolve more easily than documents.
6.????Quality Management
For applying system quality in cyber physical systems the Built-In Quality core value in SAFe ensure that each solution element, at every increment, meets the appropriate quality standards throughout implementation:
7.????Project Management
Most of the projects where the Systems Engineering approach is used, manage the product lifecycle time using a phase gate approach, which is based on the traditional waterfall project management approach. SAFe has transformed this approach into a scaled, lean-agile, value stream and team based framework for long-lived products. Project Management becomes Product and Solution Management as described in [20].
Business Operations Optimization, Standards Integration, Board Advisor, Mentor, Investor
2 年Nice summary. I would also say that ASPICE and SAFe applied with a System Engineering approach are great together.