Bertrandt | Automotive Best Practice: How to Design, Review, Approve, and Efficiently Deploy Project Templates across the Enterprise with codeBeamer ALM
1 like376 views
The document outlines the configuration process for the design, review, approval, and deployment of codebeamer templates at Bertlandt. It includes specifications, requirements management, testing, and deployment strategies, focusing on a feature-based development approach and compliance with automotive standards. Key trends and goals are presented, emphasizing innovation in technology for the automotive and aerospace industries.
Bertrandt | Automotive Best Practice: How to Design, Review, Approve, and Efficiently Deploy Project Templates across the Enterprise with codeBeamer ALM
- 1. Configuration-Process of codeBeamer Templates Design, Review, Approve, and Efficiently Deploy Project Templates 22.10.2020, Alexandros Velikis
- 2. 01 Short introduction Bertrandt 02 Specification and Design of cB-Templates 03 Testing and Deployment of cB-Templates 04 Configuration Process Agenda
- 3. Bertrandt Key Facts Intland User Conference | 22.10.2020 | Alexandros Velikis experience in engineering-solutions for the international automotive and aerospace industries 45 Years 50 Locations in Europe, China and USA in close proximity to our customers. The main customers include the automotive OEM and numerous system suppliers. accompany our customers with their extensive know-how and future-oriented project solutions from the idea to series production throughout the entire product development process. 13.600 Employees
- 4. Four major trends dominate our strategy and efforts Intland User Conference | 22.10.2020 | Alexandros Velikis
- 5. Autonomous Driving Human Machine Interface eMobility Distributed Development TECHNOLOGY FIELDS OF THE INNOVATION PROJECT B.FORWARD Goals of the innovation project Moving the company in a technological way one step ahead Different results could be incorporated into various projects for customers in the following areas: User studies Software Architecture Validation Data analysis HV Battery Trajectory Planing Domain-Architecture Vehicle Assembly Navigation Development Process HV Battery Connected Car User Interface Mobile App On-Board Charger Charging Station UX-Simulator Intland User Conference | 22.10.2020 | Alexandros Velikis
- 6. Our innovation platform HARRI Digital Autonomous Connected Electrified Intland User Conference | 22.10.2020 | Alexandros Velikis
- 7. 01 Short introduction Bertrandt 02 Specification and Design of cB-Templates 03 Testing and Deployment of cB-Templates 04 Configuration Process Agenda
- 8. Intland User Conference | 22.10.2020 | Alexandros Velikis Specification and design of cB-templates feature based development process System- architektur
- 9. Intland User Conference | 22.10.2020 | Alexandros Velikis Specification and design of cB-templates Automotive SPICE: traceability and consistency model Source: Automotive SPICE
- 10. Intland User Conference | 22.10.2020 | Alexandros Velikis Specification and design of cB-templates Concept of the template architecture
- 11. Specification and design of cB-templates Derivation of configuration requirements from ASPICE Intland User Conference | 22.10.2020 | Alexandros Velikis Field/Permission Workflow Field FieldsReference- Fields Each xx-yy inherits everything from its xx-00
- 12. Specification and design of cB-templates Derivation of configuration requirements from ASPICE Tracker „WP A“ Tracker „WP B“ Tracker „WP C“ Tracker „WP n“ Top-Level-Items REQ: fields REQ: workflow REQ: permissions REQ: content Which fields/attributes and references are needed? How does the workflow look like? Which role has which permission in the tracker? How shall the content of the tracker be structured? Requirements on the Trackers Intland User Conference | 22.10.2020 | Alexandros Velikis The specification of the tracker-configuration can be derived from the workproduct-description in ASPICE The configuration-requirements can be managed in a codeBeamer „configuration“-project With the requirements in codeBeamer we can start useing codeBeamer-features (reviews, releases, testing etc.)
- 13. Intland User Conference | 22.10.2020 | Alexandros Velikis Specification and design of cB-templates Management of configuration requirements in codeBeamer Requirements regarding the tracker attributes/fields can be managed in different ways: Requirements: fields Requirements: workflow Workflow-Requirements can be linked from the codeBeamer document-management-system A: One item for each Tracker C: One item for each field B: linked office-files from document section
- 14. Intland User Conference | 22.10.2020 | Alexandros Velikis Specification and design of cB-templates Management of configuration requirements in codeBeamer Requirements regarding permissions can be configured on three different levels A generic RASCI-Matrix is recommended Requirements: permissions Requirements: structure Requirements regarding the structure of the tracker-content can be inherited from trackers or imported from office. The fulfillment of the requirements can be reviewed vie review hub A: permissions on project level C: permissions on tracker level C: permissions on field/workflow level
- 15. 01 Short introduction Bertrandt 02 Specification and Design of cB-Templates 03 Testing and Deployment of cB-Templates 04 Configuration Process Agenda
- 16. Intland User Conference | 22.10.2020 | Alexandros Velikis Testing and deployment of cB-templates Derivation of test cases from configuration-requirements tracker „WP A“ tracker „WP B“ tracker „WP C“ tracker „WP n“ config-items REQ: fields REQ: workflow REQ: permissions REQ: content requirements TC: fields TC: workflow TC: permissions TC: content test cases test set: tracker A test sets Test run: racker A test runs The codeBeamer-testing-functions (Test-Cases / Testsets / Testruns) can be used for the testing of the tracker-configurations Testcases can be derived from the tracker-configuration-requirements Testcases can be created automatically via java-script or import from an excel-macro
- 17. Intland User Conference | 22.10.2020 | Alexandros Velikis Testing and deployment of cB-templates Testing of the configuration All manual-testing functions from codeBeamer can be used for testing the tracker-configuration Test cases: tracker-fields Test cases: tracker-workflow There is a test step for each status. Test steps can also be (re-)used for role-based testing. field requirements field test specification workflow workflow test specification
- 18. Intland User Conference | 22.10.2020 | Alexandros Velikis Testing and deployment of cB-templates Deployment of cB-templates Implementation configuration sprint A Testing & Bugfixing DEVINTPROD V1.0 V2.0 V2.1 V2.2 V3.0 Testing & Bugfixing Time Export Export Export Export Export Implementation configuration sprint B
- 19. 01 Short introduction Bertrandt 02 Specification and Design of cB-Templates 03 Testing and Deployment of cB-Templates 04 Configuration Process Agenda
- 20. configuration process summary of the entire configuration process ASPICE: - Workproduct A - Workproduct B - Workproduct n Tracker WP A Tracker WP B Tracker n REQ: fields REQ: workflow REQ: permissions TC: fields TC: workflow TC: permission test set: Tracker A test run: Tracker A TASK: configuration tracker A conifig. items requirements tasks testcases testsets testruns BUG: Feld A 2020 Jan. Febr. Mar Apr 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 Configuration sprint 1 Tätigkeit Configuration sprint 2 Configuration sprint 3 Task A Testrun A Task B BACKLOG REQ: structure Intland User Conference | 22.10.2020 | Alexandros Velikis TC: structure
- 21. Alexandros Velikis Lead Engineer Bertrandt Group Bertrandt Group, Birkensee 1, 71139 Ehningen Mobil: +49 151 167 688 14 Alexandros.Velikis@de.bertrandt.com www.bertrandt.com Intland User Conference | 22.10.2020 | Alexandros Velikis