EU
Quality related consulting and supporting: Process improvement
- Comprehensive evaluation of process documents
- Reporting of all findings along with a final report, conclusions, options
- Proposing a mitigation workflow
- Reviews of the Design Development
EASA conform UAS training A2, STS (Specific)
Automotive Cyber Security training (ISO 21434, TARA)
· SUP.7 - Quality related analysis and correction of documentation. Creation of JIRA tickets to cover review workflows of documentation. Creation of an internal documentation rule set and instructions. Investigating and supporting the process of selecting and evaluating a CCMS system based on Confluence. Development of a pilot plan to identify the feasibility of that CCMS system.
· PIM.3 ? Jira process analysis and improvement, proposing specific workflow redesigns and organisation.
· RM ? Analysing requirements after quality criteria. Creating stakeholder requirements for a RADAR power management module, after specification documents provided by the US design team and the customer. Supporting the organization of requirements among involved teams. Gap analysis of common attributes of requirements among different projects.
· Communicating and coordinating numerous topics among people and teams.
· Supporting diverse objectives, roles, and activities.
· Tracking and reporting defect tickets, internal and customer tickets.
· Creating and rewriting PRM process documentation, creating trend reports, RM and PRM role descriptions, fulfilling ASPICE demands, solving process tickets.
· Communicating and coordinating numerous topics among people and teams.
· Supporting diverse objectives and activities of the PM, performing as substitute of the PM, conducting team meetings, serving requests of the customer.
· Process analysis and improvement, JIRA defect ticket workflow redesign, evaluating and commenting documents of requirements management.
· Working on work packages of ASPICE related demands of the QA department. Creating, and extending QA content according to ASPICE level 2.
· Cyber Security requirements analysis and interpretation regarding intelligibility and effort estimation.
· Coordinating Cyber Security topics among other team leads, and according to planning of, and along with the Cyber Security Manager, as a task force serving the project.
Tools: DOORS, JIRA, Confluence, ASPICE, MS Office, MindManager
· Analysis, investigation, coordination of activities, deliverables, and information necessary to plan and achieve the goals of next steps.
· Supporting the planning of diverse quality related activities like requirements management, change management, issue tracking, management of customer, stakeholder, and supplier documents.
· Defining JIRA tracking workflows while adapting those to the project structure.
· Introducing JIRA to the project team, planning of the JIRA configuration.
· Supporting the process of Requirements Elicitation.
Tools: SharePoint, Polarion, JIRA, Confluence, Agile SCRUM, XMind
Three separate roles:
Requirements Management (RM: DOORS, SP, JIRA, Confluence)
o Managing baselines of DOORS and SP modules of delivery sets.
o Producing documentation of baseline workflows in Confluence.
o Transfer of DOORS modules between Bosch and Daimler.
o Adding and maintaining requirements objects on demand.
o Supporting team members on technical issues incl. issues with DOORS.
Change Management (CM CRM: SUP.10, DOORS, SP, JIRA, Confluence)
o Conducting the CCB and ECB weekly round tables.
o Conducting other regular meetings for different teams incl. the customer.
o Regular import of MAP data and managing the versioning.
o Producing documentation of CRM activities in Confluence and PPT slides.
Problem Resolution Management [tickets/defects] (PRM: SUP.9 JIRA)
o Regular sync of tickets between the customer system and Bosch.
o Fixing diverse issues of tickets involving the customer.
o Supporting the update of PRM process documentation.
Tools: DOORS, SharePoint, JIRA, Confluence, Agile SCRUM, MindManager
During the first half of 2020 I managed to ?secure? three long-term contracts (to run during 2020 and longer) with agreed starting dates, however, due to the COVID-19 situation, none of these contracts started.
· Performing the integration of specific audio work products as part of a complex overall integration process and testing the model behavior against requirements each time.
· For the testing activities I initially used some of the existing test benches of the testing team. However, since our team required a dedicated test bench for the audio processing modules, I was appointed to assemble a new test bench and put this into operation.
· Creating the documentation of all required procedures (workflows) with all those numerous details required, including alternative routes, and variants of the required ways of integration and testing.
Tools: Perforce, git, Agile, Python, Confluence, Linux systems for build, XMind
· Analysis and improvement of requirements related processing.
· Analysis and improvement of stakeholder requirement documents, creating new and improving existing SW requirements of Radar development.
· Supporting the improvement of processing regarding ASPICE quality demands along with the migration of the environment related to ASPICE processing.
· Developing Python and LaTeX code for the Automation Team and improving the integration process to automate the creation of SW release notes.
Tools: PTC Integrity, ASPICE-3, E.Architect, Python, Agile SCRUM, XMind
· Analysis and improvement of requirements related processing.
· Incorporating customer requirements from various document formats.
· Creating new and improving existing requirements in DOORS modules.
· Improvement of existing, and creation of new DOORS modules regarding ASPICE quality demands.
· Investigating into EU regulations and international standards concerning lighting related requirements.
· Supporting the migration of the DOORS environment and participating in the development and migration of the ASPICE related processing.
· Python scripting for the filtering and analysis of requirements data.
Tools: DOORS, ISO 26262, ASPICE-3, E.Architect, Python, Agile SCRUM, XMind
· Analysis and improvement of customer requirements data, and requirements related processing.
· Investigation of document related issues and proposing solutions.
· The use of DOORS was limited to module exchange and updates, while the requirement's related activities were carried out using Polarion.
· Python scripts were created for complex filtering of a large amount of data.
Tools: DOORS, Polarion, Python, Subversion SVN, SharePoint, XMind
· Analysis and improvement of Active Safety user requirements specifications (URS) in terms of content and quality regarding Radar (front and rear) and Camera (front).
· Responsible for performing DXL scripts during a weekly exchange process of DOORS modules with the Client including numerous manual steps required.
· Responsible for the quality of the English versions of those DOORS requirements specification modules and diagramming specifications.
· Managing external language translations (German to English) carried out via a translation office based in India.
· Numerous PPT documentations were produced to document existing workflow, processing, and planned structures, some of those for the documentation set of the PMP Project Management Plan.
Tools: DOORS, translation tools, graphics tools, SharePoint, XMind
· In-house project to identify general pre-requirements of Active Safety topics by conducting meetings with the relevant teams (international).
· Finalising the findings into high level use cases using UML, in order to provide the Project Management with additional assets for making further decisions in this area.
Tools: Google Office Docs, OmniGraffle (UML diagramming), XMind
· Static Testing, Analysis of requirements, use cases, and HMI source code (manual analysis), static code approval (Klocwork: tool-based code analysis).
· Creation of problem reports, reviews and improvement of involved tools and documents, and creation of Python scripts for the purpose of source code analysis.
· Evaluating HMI use cases against requirements, C++ source codes and other existing design specifications.
Tools: DOORS, Klocwork, Synergy, Tree mapping, VMware virtualisation, Lotus Notes, Python, HMI, Connectivity, Embedded SW, Qt, QML, Linux, E.Architect, XMind
· Analysis of structures, linkage and consistency of test cases and system requirements (SRS).
· Identifying, verifying, and classifying technical content due for clarification, those were to be communicated to the respective functional owners.
· Documenting existing branches and inter-relationships of functional areas among Garmin's and the customer's project- and platform structures (Connecting the relevant features in lists of tree structures).
Tools: DOORS, Polarion, Confluence, E.Architect, MindManager
· Responsible for managing the Testing cycles while synchronising with the Software Development cycles of the Software Team working on embedded software of ECUs controlling comfort functionality.
· In order to achieve this, I worked closely with the SW Team Leader, reported to the Project Manager, kept communicating with the Requirements- and the Quality Manager, the Architects, and all members of the Testing Team.
· Analysis of DOORS requirements and diverse data related to Testing activities, managing and organising Testing related events, teams, results, resources, and involvement in planning.
· Tracking of issues of Testing results, dispatching those to responsible Team members, documenting Testing procedures used at different stages.
· Produced two different types of cyclic Testing reports for Management levels.
Tools: MS Office, MKS, DOORS, CANoe, XMind
· Analysing and adapting existing HMI requirements and specifications of the Car infotainment, HMI system, developed at JCI.
· I worked on EB Guide models delivered by the client. In particular, I frequently used EB Guide to process and adapt the delivered models to conform to the JCI internal procedures and processing.
· Improving, establishing and documenting the complex procedure of adapting the EB Guide models to the JCI process.
Tools: DOORS, UML, EB Guide, CANoe, some proprietary JCI internal tools, XMind
Aug 2010 to June 2011
Bosch Automotive
Position: IT Analyst, Requirements Manager, Systems Engineer (Steering)
· Analysing and producing SW requirements specifications of steering systems.
· I investigated into relevant ISO standards and compiled a large documented tree of ISO standards, related to the corresponding car brands, projects, and time frames. That tree was supposed to be used among diverse projects (car brand neutral).
· The diversity of URS documents (User Requirements Specification) got analysed and adapted, integrated into Bosch's own SRS (System Requirements Specification), required to communicate with and understand the needs of customer teams based in the USA, India, Italy, and Japan.
· This included language translation and interpretation for each improvement cycle.
· I produced diverse requirements specifications (SRS) plus other documents.
Tools: DOORS, ISO 26262, Translation tools, MindManager
· Analysis of diverse specifications, mainly the analysis of the existing and production of new HMI/MMI User Interface (UX) specifications of the Japanese part of the BMW HMI system. That involved creating new SRS in DOORS.
· I modelled an analysis tree map including linkage to existing documents of the project, which provided a complete overview of that part of the HMI. This way it was possible to identify missing or redundant parts, which were otherwise hard to spot since the BMW HMI system at that time was extraordinary complex.
· I was involved in HMI UX related meetings with Japanese team members of BMW Japan.
Tools: DOORS, MS Office, OmniGraffle, Visio, MindManager
BOSCH Automotive (Two projects, same site)
IT Analyst, Requirements- Systems Engineer (HMI, IC)
Harman/Becker Automotive
Software Architect, Developer, Integrator, IT Analyst (HMI, IC), C++ Developer
Sybase Brussels Mobile
UX Interaction Designer, GUI / Mobile App Designer, C#, C++ Developer
ACCESS Europe Mobile
FAE, Pre-Sales Engineer for Mobile Platform Solutions
Infineon Technologies Mobile
GUI Designer, GUI Developer, Analyst for Windows Mobile, C++ Developer
EPC Dublin Mobile
GUI Designer, GUI Developer, IT Analyst, Integrator, C# Developer
PDA Consulting Mobile
GUI Designer, Software Architect, IT Analyst mobile platforms, C Developer
FORCE Computers Linux/UNIX
Software Architect, Linux / Kernel / GUI Developer, IT Analyst, C Developer
NSE Java
Software Architect, GUI Designer, IT Analyst, Java Developer
EUROCURA Web/Internet, Java
Software Architect, GUI Designer, IT Analyst, Web, Java Developer
Rohde&Schwarz Linux/UNIX
Software Architect, Linux / GUI Developer, IT Analyst, C Developer
China King Enterprise Web/Internet
IT Analyst, Linux Expert, GUI Designer, Web Developer
Selbach&Partner Web/Internet
Position: IT Analyst, Linux Expert, Web Developer
EPoX Web/Internet, Linux/UNIX
Position: Software Architect, IT Analyst, Linux Expert, Web Developer
(Details on request)
BA: Besides development, I've got involved as IT Analyst for:
User interface issues, usability, analysis, proposals, design, prototyping, facing clients, traveling, trouble shooting, tool chain, configuration management, project management, requirement specifications, documentation, serving clients, support.
SW: Software development mainly included:
- Embedded projects (C, Forth, Assembler, Electronics, Micro controller)
- PC based software applications (C, C++, Forth applications on DOS, and Windows GUI applications)
Education / Training:
1982 M.S. in Computer Science, Information
1995 Certified Suggestopaedia
2013 BCS/ISTQB training of ISEB Software Testing
2024 Cyber Security training (ISO 21434, TARA)
2024 EASA conform UAS training A2, STS (Specific)
Max Schmidt - IT Consulting - Company registration No: 027 866 01503
Sr Systems Engineer, Automotive Consultant, UAS Consultant (EU, EASA, Specific)
Activities, Roles
? Requirements Engineer, Requirements Analyst
? Analysis, Investigation, Coordination, Reporting
? ASPICE SUP.9 Defect Management (PRM)
? ASPICE SUP.10 Change Management (CM)
? ASPICE SUP.7 Documentation Management
? ASPICE PIM.3 Process Improvement
More
? DOORS [9 years], JIRA [3 years], Confluence, Polarion, Python
? 19 years of support of projects in the Automotive Supply Business
Summary
At the forefront of automotive quality and process enhancement, my roles at Indiesemi, NSEU, AGC, and Bosch have been pivotal in driving quality related activities and workflow optimisation. Our dedication to process improvement has resulted in streamlined operations and enhanced workflows, thanks to the adept use of tools like JIRA and Confluence.
My hands-on experience in requirements processing, defect management and process analysis not only supports fulfilling industry standards like ASPICE but also contributes to a culture of continuous improvement. Our collaborative efforts have fortified the relationship between quality assurance and project management, ensuring excellence in every facet of automotive processes.
Interests
Drone test operations, photography, bicycling.
Multicultural awareness
Places of working and living in the past: Belgium, Germany, Ireland, Taiwan, UK.
[Name auf Anfrage / Name on request]
Senior Systems Engineer, Automotive
Activities
· RM Requirements Management - Traceability, Reviews, ASPICE
· RM Requirements Analysis - Quality related analysis
· RE Requirements Engineering - Supporting the RE process
· PRM Defect ticket Management - ASPICE SUP.9
· CM Change Management - ASPICE SUP.10
· PIM Process Improvement - ASPICE PIM.3
Areas
· ADAS, Radar, LiDAR, Camera, HMI, Infotainment, Connectivity, MAP, HUD
Tools
· DOORS [9 years], Polarion, JIRA, Confluence, Python, DXL
Time
? 17 years Automotive industry (2005 till present)
? 20 years System and SW development (1982 till 2005)
EU
Quality related consulting and supporting: Process improvement
- Comprehensive evaluation of process documents
- Reporting of all findings along with a final report, conclusions, options
- Proposing a mitigation workflow
- Reviews of the Design Development
EASA conform UAS training A2, STS (Specific)
Automotive Cyber Security training (ISO 21434, TARA)
· SUP.7 - Quality related analysis and correction of documentation. Creation of JIRA tickets to cover review workflows of documentation. Creation of an internal documentation rule set and instructions. Investigating and supporting the process of selecting and evaluating a CCMS system based on Confluence. Development of a pilot plan to identify the feasibility of that CCMS system.
· PIM.3 ? Jira process analysis and improvement, proposing specific workflow redesigns and organisation.
· RM ? Analysing requirements after quality criteria. Creating stakeholder requirements for a RADAR power management module, after specification documents provided by the US design team and the customer. Supporting the organization of requirements among involved teams. Gap analysis of common attributes of requirements among different projects.
· Communicating and coordinating numerous topics among people and teams.
· Supporting diverse objectives, roles, and activities.
· Tracking and reporting defect tickets, internal and customer tickets.
· Creating and rewriting PRM process documentation, creating trend reports, RM and PRM role descriptions, fulfilling ASPICE demands, solving process tickets.
· Communicating and coordinating numerous topics among people and teams.
· Supporting diverse objectives and activities of the PM, performing as substitute of the PM, conducting team meetings, serving requests of the customer.
· Process analysis and improvement, JIRA defect ticket workflow redesign, evaluating and commenting documents of requirements management.
· Working on work packages of ASPICE related demands of the QA department. Creating, and extending QA content according to ASPICE level 2.
· Cyber Security requirements analysis and interpretation regarding intelligibility and effort estimation.
· Coordinating Cyber Security topics among other team leads, and according to planning of, and along with the Cyber Security Manager, as a task force serving the project.
Tools: DOORS, JIRA, Confluence, ASPICE, MS Office, MindManager
· Analysis, investigation, coordination of activities, deliverables, and information necessary to plan and achieve the goals of next steps.
· Supporting the planning of diverse quality related activities like requirements management, change management, issue tracking, management of customer, stakeholder, and supplier documents.
· Defining JIRA tracking workflows while adapting those to the project structure.
· Introducing JIRA to the project team, planning of the JIRA configuration.
· Supporting the process of Requirements Elicitation.
Tools: SharePoint, Polarion, JIRA, Confluence, Agile SCRUM, XMind
Three separate roles:
Requirements Management (RM: DOORS, SP, JIRA, Confluence)
o Managing baselines of DOORS and SP modules of delivery sets.
o Producing documentation of baseline workflows in Confluence.
o Transfer of DOORS modules between Bosch and Daimler.
o Adding and maintaining requirements objects on demand.
o Supporting team members on technical issues incl. issues with DOORS.
Change Management (CM CRM: SUP.10, DOORS, SP, JIRA, Confluence)
o Conducting the CCB and ECB weekly round tables.
o Conducting other regular meetings for different teams incl. the customer.
o Regular import of MAP data and managing the versioning.
o Producing documentation of CRM activities in Confluence and PPT slides.
Problem Resolution Management [tickets/defects] (PRM: SUP.9 JIRA)
o Regular sync of tickets between the customer system and Bosch.
o Fixing diverse issues of tickets involving the customer.
o Supporting the update of PRM process documentation.
Tools: DOORS, SharePoint, JIRA, Confluence, Agile SCRUM, MindManager
During the first half of 2020 I managed to ?secure? three long-term contracts (to run during 2020 and longer) with agreed starting dates, however, due to the COVID-19 situation, none of these contracts started.
· Performing the integration of specific audio work products as part of a complex overall integration process and testing the model behavior against requirements each time.
· For the testing activities I initially used some of the existing test benches of the testing team. However, since our team required a dedicated test bench for the audio processing modules, I was appointed to assemble a new test bench and put this into operation.
· Creating the documentation of all required procedures (workflows) with all those numerous details required, including alternative routes, and variants of the required ways of integration and testing.
Tools: Perforce, git, Agile, Python, Confluence, Linux systems for build, XMind
· Analysis and improvement of requirements related processing.
· Analysis and improvement of stakeholder requirement documents, creating new and improving existing SW requirements of Radar development.
· Supporting the improvement of processing regarding ASPICE quality demands along with the migration of the environment related to ASPICE processing.
· Developing Python and LaTeX code for the Automation Team and improving the integration process to automate the creation of SW release notes.
Tools: PTC Integrity, ASPICE-3, E.Architect, Python, Agile SCRUM, XMind
· Analysis and improvement of requirements related processing.
· Incorporating customer requirements from various document formats.
· Creating new and improving existing requirements in DOORS modules.
· Improvement of existing, and creation of new DOORS modules regarding ASPICE quality demands.
· Investigating into EU regulations and international standards concerning lighting related requirements.
· Supporting the migration of the DOORS environment and participating in the development and migration of the ASPICE related processing.
· Python scripting for the filtering and analysis of requirements data.
Tools: DOORS, ISO 26262, ASPICE-3, E.Architect, Python, Agile SCRUM, XMind
· Analysis and improvement of customer requirements data, and requirements related processing.
· Investigation of document related issues and proposing solutions.
· The use of DOORS was limited to module exchange and updates, while the requirement's related activities were carried out using Polarion.
· Python scripts were created for complex filtering of a large amount of data.
Tools: DOORS, Polarion, Python, Subversion SVN, SharePoint, XMind
· Analysis and improvement of Active Safety user requirements specifications (URS) in terms of content and quality regarding Radar (front and rear) and Camera (front).
· Responsible for performing DXL scripts during a weekly exchange process of DOORS modules with the Client including numerous manual steps required.
· Responsible for the quality of the English versions of those DOORS requirements specification modules and diagramming specifications.
· Managing external language translations (German to English) carried out via a translation office based in India.
· Numerous PPT documentations were produced to document existing workflow, processing, and planned structures, some of those for the documentation set of the PMP Project Management Plan.
Tools: DOORS, translation tools, graphics tools, SharePoint, XMind
· In-house project to identify general pre-requirements of Active Safety topics by conducting meetings with the relevant teams (international).
· Finalising the findings into high level use cases using UML, in order to provide the Project Management with additional assets for making further decisions in this area.
Tools: Google Office Docs, OmniGraffle (UML diagramming), XMind
· Static Testing, Analysis of requirements, use cases, and HMI source code (manual analysis), static code approval (Klocwork: tool-based code analysis).
· Creation of problem reports, reviews and improvement of involved tools and documents, and creation of Python scripts for the purpose of source code analysis.
· Evaluating HMI use cases against requirements, C++ source codes and other existing design specifications.
Tools: DOORS, Klocwork, Synergy, Tree mapping, VMware virtualisation, Lotus Notes, Python, HMI, Connectivity, Embedded SW, Qt, QML, Linux, E.Architect, XMind
· Analysis of structures, linkage and consistency of test cases and system requirements (SRS).
· Identifying, verifying, and classifying technical content due for clarification, those were to be communicated to the respective functional owners.
· Documenting existing branches and inter-relationships of functional areas among Garmin's and the customer's project- and platform structures (Connecting the relevant features in lists of tree structures).
Tools: DOORS, Polarion, Confluence, E.Architect, MindManager
· Responsible for managing the Testing cycles while synchronising with the Software Development cycles of the Software Team working on embedded software of ECUs controlling comfort functionality.
· In order to achieve this, I worked closely with the SW Team Leader, reported to the Project Manager, kept communicating with the Requirements- and the Quality Manager, the Architects, and all members of the Testing Team.
· Analysis of DOORS requirements and diverse data related to Testing activities, managing and organising Testing related events, teams, results, resources, and involvement in planning.
· Tracking of issues of Testing results, dispatching those to responsible Team members, documenting Testing procedures used at different stages.
· Produced two different types of cyclic Testing reports for Management levels.
Tools: MS Office, MKS, DOORS, CANoe, XMind
· Analysing and adapting existing HMI requirements and specifications of the Car infotainment, HMI system, developed at JCI.
· I worked on EB Guide models delivered by the client. In particular, I frequently used EB Guide to process and adapt the delivered models to conform to the JCI internal procedures and processing.
· Improving, establishing and documenting the complex procedure of adapting the EB Guide models to the JCI process.
Tools: DOORS, UML, EB Guide, CANoe, some proprietary JCI internal tools, XMind
Aug 2010 to June 2011
Bosch Automotive
Position: IT Analyst, Requirements Manager, Systems Engineer (Steering)
· Analysing and producing SW requirements specifications of steering systems.
· I investigated into relevant ISO standards and compiled a large documented tree of ISO standards, related to the corresponding car brands, projects, and time frames. That tree was supposed to be used among diverse projects (car brand neutral).
· The diversity of URS documents (User Requirements Specification) got analysed and adapted, integrated into Bosch's own SRS (System Requirements Specification), required to communicate with and understand the needs of customer teams based in the USA, India, Italy, and Japan.
· This included language translation and interpretation for each improvement cycle.
· I produced diverse requirements specifications (SRS) plus other documents.
Tools: DOORS, ISO 26262, Translation tools, MindManager
· Analysis of diverse specifications, mainly the analysis of the existing and production of new HMI/MMI User Interface (UX) specifications of the Japanese part of the BMW HMI system. That involved creating new SRS in DOORS.
· I modelled an analysis tree map including linkage to existing documents of the project, which provided a complete overview of that part of the HMI. This way it was possible to identify missing or redundant parts, which were otherwise hard to spot since the BMW HMI system at that time was extraordinary complex.
· I was involved in HMI UX related meetings with Japanese team members of BMW Japan.
Tools: DOORS, MS Office, OmniGraffle, Visio, MindManager
BOSCH Automotive (Two projects, same site)
IT Analyst, Requirements- Systems Engineer (HMI, IC)
Harman/Becker Automotive
Software Architect, Developer, Integrator, IT Analyst (HMI, IC), C++ Developer
Sybase Brussels Mobile
UX Interaction Designer, GUI / Mobile App Designer, C#, C++ Developer
ACCESS Europe Mobile
FAE, Pre-Sales Engineer for Mobile Platform Solutions
Infineon Technologies Mobile
GUI Designer, GUI Developer, Analyst for Windows Mobile, C++ Developer
EPC Dublin Mobile
GUI Designer, GUI Developer, IT Analyst, Integrator, C# Developer
PDA Consulting Mobile
GUI Designer, Software Architect, IT Analyst mobile platforms, C Developer
FORCE Computers Linux/UNIX
Software Architect, Linux / Kernel / GUI Developer, IT Analyst, C Developer
NSE Java
Software Architect, GUI Designer, IT Analyst, Java Developer
EUROCURA Web/Internet, Java
Software Architect, GUI Designer, IT Analyst, Web, Java Developer
Rohde&Schwarz Linux/UNIX
Software Architect, Linux / GUI Developer, IT Analyst, C Developer
China King Enterprise Web/Internet
IT Analyst, Linux Expert, GUI Designer, Web Developer
Selbach&Partner Web/Internet
Position: IT Analyst, Linux Expert, Web Developer
EPoX Web/Internet, Linux/UNIX
Position: Software Architect, IT Analyst, Linux Expert, Web Developer
(Details on request)
BA: Besides development, I've got involved as IT Analyst for:
User interface issues, usability, analysis, proposals, design, prototyping, facing clients, traveling, trouble shooting, tool chain, configuration management, project management, requirement specifications, documentation, serving clients, support.
SW: Software development mainly included:
- Embedded projects (C, Forth, Assembler, Electronics, Micro controller)
- PC based software applications (C, C++, Forth applications on DOS, and Windows GUI applications)
Education / Training:
1982 M.S. in Computer Science, Information
1995 Certified Suggestopaedia
2013 BCS/ISTQB training of ISEB Software Testing
2024 Cyber Security training (ISO 21434, TARA)
2024 EASA conform UAS training A2, STS (Specific)
Max Schmidt - IT Consulting - Company registration No: 027 866 01503
Sr Systems Engineer, Automotive Consultant, UAS Consultant (EU, EASA, Specific)
Activities, Roles
? Requirements Engineer, Requirements Analyst
? Analysis, Investigation, Coordination, Reporting
? ASPICE SUP.9 Defect Management (PRM)
? ASPICE SUP.10 Change Management (CM)
? ASPICE SUP.7 Documentation Management
? ASPICE PIM.3 Process Improvement
More
? DOORS [9 years], JIRA [3 years], Confluence, Polarion, Python
? 19 years of support of projects in the Automotive Supply Business
Summary
At the forefront of automotive quality and process enhancement, my roles at Indiesemi, NSEU, AGC, and Bosch have been pivotal in driving quality related activities and workflow optimisation. Our dedication to process improvement has resulted in streamlined operations and enhanced workflows, thanks to the adept use of tools like JIRA and Confluence.
My hands-on experience in requirements processing, defect management and process analysis not only supports fulfilling industry standards like ASPICE but also contributes to a culture of continuous improvement. Our collaborative efforts have fortified the relationship between quality assurance and project management, ensuring excellence in every facet of automotive processes.
Interests
Drone test operations, photography, bicycling.
Multicultural awareness
Places of working and living in the past: Belgium, Germany, Ireland, Taiwan, UK.
[Name auf Anfrage / Name on request]
Senior Systems Engineer, Automotive
Activities
· RM Requirements Management - Traceability, Reviews, ASPICE
· RM Requirements Analysis - Quality related analysis
· RE Requirements Engineering - Supporting the RE process
· PRM Defect ticket Management - ASPICE SUP.9
· CM Change Management - ASPICE SUP.10
· PIM Process Improvement - ASPICE PIM.3
Areas
· ADAS, Radar, LiDAR, Camera, HMI, Infotainment, Connectivity, MAP, HUD
Tools
· DOORS [9 years], Polarion, JIRA, Confluence, Python, DXL
Time
? 17 years Automotive industry (2005 till present)
? 20 years System and SW development (1982 till 2005)