instruction stringlengths 60 310 | input stringclasses 1
value | output stringlengths 129 3.62k |
|---|---|---|
Draft configuration management (SUP [SUP adj 26].1) for the program [SUP adj 26]. (BMS scenario v7) [SUP adj 26]. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Coordinate work product management (MAN.2) across teams. (BMS scenario v2). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop documentation (SUP.7) style guide for the program. (Chassis scenario v2). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create supply (SPL.1) for an embedded gateway delivery. (Infotainment scenario v5). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish project acquisition requirements (ACQ.13) for infotainment head unit sourcing. (Chassis scenario v1). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Verify software (SWE.6) per acceptance criteria. (Infotainment scenario v2). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design Provide and maintain infrastructure services (INF.2). (Gateway scenario v2). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare verification strategy (SUP.2) for the platform. (Charging scenario v1). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Plan reusable asset management (REU.1). (Chassis scenario v5). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design potential suppliers (ACQ.15) for OTA backend platform. (Chassis scenario v6). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design project acquisition requirements (ACQ.13) for infotainment head unit sourcing. (ADAS scenario v4). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop project acquisition requirements (ACQ.13) for infotainment head unit sourcing. (ADAS scenario v2). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop system architectural design (SYS [SYS adj 297].3) for a zonal E/E platform [SYS adj 297]. (Telematics scenario v3) [SYS adj 297]. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft an ACQ vX122.4 supplier monitoring dashboard for an ADAS camera supplier vX122. (BMS scenario v5) vX122. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop bid management process (MAN.1) for multi-supplier program. (Charging scenario v7). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design supply (SPL.3) for prototype batch. (Body scenario v4). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish supply (SPL.3) for prototype batch. (ADAS scenario v2). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft software units (SWE.4) for RetryQueue. (Powertrain scenario v1). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design project plan (MAN.3) for a powertrain SW release. (ADAS scenario v6) — balanced variant 1024. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish configuration management (SUP.1) for the program. (Body scenario v6). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design technical acquisition requirements (ACQ.11) for a battery management system (BMS). (Powertrain scenario v7). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create audit plan (SUP.1/SUP.8 context) for configuration and quality. (Telematics scenario v6). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish engineering infrastructure (INF.1) for CI/CD. (ADAS scenario v4). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare validation (SUP [SUP adj 287].3) for customer acceptance tests [SUP adj 287]. (ADAS scenario v2) [SUP adj 287]. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare documentation (SUP.7) style guide for the program. (Infotainment scenario v3). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Conduct a joint review (SUP [SUP adj 343].4) of system requirements [SUP adj 343]. (Powertrain scenario v2) [SUP adj 343]. | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design Plan and perform system integration (SYS [SYS adj 380].4) [SYS adj 380]. (ADAS scenario v2) [SYS adj 380]. | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create supply (SPL.3) for prototype batch. (Gateway scenario v1). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare supply (SPL.1) for an embedded gateway delivery. (Body scenario v6) — balanced variant 6577. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Define process management (MAN.4) responsibilities and audits. (ADAS scenario v6). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish verification strategy (SUP [SUP adj 178].2) for the platform [SUP adj 178]. (Telematics scenario v5) [SUP adj 178]. | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare system architectural design (SYS.3) for a zonal E/E platform. (ADAS scenario v6). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish software units (SWE.4) for RetryQueue. (Powertrain scenario v4). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare a Request for Proposals (ACQ.14) package for a gateway ECU. (Body scenario v1). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop audit plan (SUP.1/SUP.8 context) for configuration and quality. (ADAS scenario v7). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create system architectural design (SYS.3) for a zonal E/E platform. (Telematics scenario v2). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop changes (SUP.10) for system interface specification. (Gateway scenario v5). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Plan process assessment (PIM.1) and objectives. (Chassis scenario v4). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop software architectural design (SWE.2) for network stack. (BMS scenario v2). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish software requirements (SWE.1) for diagnostics over IP. (Chassis scenario v2) — balanced variant 2925. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft detailed software design (SWE.3) for a retry queue. (Gateway scenario v3). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create software units (SWE.4) for RetryQueue. (Telematics scenario v1). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare software requirements (SWE.1) for diagnostics over IP. (Body scenario v2). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop configuration management (SUP.1) for the program. (Gateway scenario v6) — balanced variant 8229. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Conduct a joint review (SUP.4) of system requirements. (ADAS scenario v1). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design Establish risk management (MAN [MAN adj 254].5) and corrective action linkage [MAN adj 254]. (Telematics scenario v2) [MAN adj 254]. | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Plan reusable asset management (REU.1). (Powertrain scenario v2). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft Summarize system qualification testing (SYS.5). (BMS scenario v1). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Plan process assessment (PIM.1) and objectives. (Infotainment scenario v1). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Create stakeholder requirement intake and baseline policy (SYS.1). (Infotainment scenario v1). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create software units (SWE.4) for RetryQueue. (Infotainment scenario v2). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft engineering infrastructure (INF.1) for CI/CD. (Powertrain scenario v7). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop problem resolution (SUP [SUP adj 467].9) for defects found in HIL [SUP adj 467]. (Gateway scenario v7) [SUP adj 467]. | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish technical acquisition requirements (ACQ.11) for a battery management system (BMS). (Chassis scenario v2). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish verification strategy (SUP.2) for the platform. (Telematics scenario v1). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Transform stakeholder needs into system requirements (SYS.2). (Charging scenario v6). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design validation (SUP [SUP adj 210].3) for customer acceptance tests [SUP adj 210]. (Charging scenario v2) [SUP adj 210]. | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft Establish risk management (MAN [MAN adj 287].5) and corrective action linkage [MAN adj 287]. (Chassis scenario v7) [MAN adj 287]. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft Manage reuse (REU.3) consumption and feedback. (Charging scenario v3). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop detailed software design (SWE.3) for a retry queue. (Body scenario v3). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create system architectural design (SYS vX972.3) for a zonal E/E platform vX972. (Chassis scenario v6) vX972. | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Verify software (SWE.6) per acceptance criteria. (Infotainment scenario v1). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish for reuse (REU.2) a logging component. (Body scenario v1). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare a Request for Proposals (ACQ.14) package for a gateway ECU. (Charging scenario v7). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create Run process improvement (PIM.2) action program. (BMS scenario v2). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design software requirements (SWE.1) for diagnostics over IP. (BMS scenario v7). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft configuration management (SUP.1) for the program. (Infotainment scenario v6). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design changes (SUP.10) for system interface specification. (Powertrain scenario v7). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop verification strategy (SUP [SUP adj 143].2) for the platform [SUP adj 143]. (Powertrain scenario v5) [SUP adj 143]. | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop changes (SUP.10) for system interface specification. (Telematics scenario v7). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish project plan (MAN.3) for a powertrain SW release. (BMS scenario v2) — balanced variant 7287. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft changes (SUP.10) for system interface specification. (Infotainment scenario v6). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare validation (SUP [SUP adj 290].3) for customer acceptance tests [SUP adj 290]. (Chassis scenario v5) [SUP adj 290]. | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Plan reusable asset management (REU.1). (BMS scenario v2) — balanced variant 2072. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft software requirements (SWE.1) for diagnostics over IP. (ADAS scenario v1). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare project plan (MAN.3) for a powertrain SW release. (Gateway scenario v6) — balanced variant 6630. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish a Contract Agreement conforming to ACQ.3 for a vehicle telematics program. (Body scenario v1). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop audit plan (SUP.1/SUP.8 context) for configuration and quality. (Telematics scenario v6). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop Conduct a joint review (SUP.4) of system requirements. (ADAS scenario v6). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create software architectural design (SWE.2) for network stack. (Charging scenario v7). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft for reuse (REU.2) a logging component. (Infotainment scenario v2). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare system architectural design (SYS.3) for a zonal E/E platform. (Chassis scenario v6) — balanced variant 6095. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Transform stakeholder needs into system requirements (SYS vX888.2) vX888. (BMS scenario v6) vX888. | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare project acquisition requirements (ACQ.13) for infotainment head unit sourcing. (ADAS scenario v3). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design software requirements (SWE.1) for diagnostics over IP. (Telematics scenario v5). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare supply management (SPL.2) for HIL rigs. (Body scenario v7). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Conduct a joint review (SUP.4) of system requirements. (Telematics scenario v6). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare project plan (MAN.3) for a powertrain SW release. (BMS scenario v4) — balanced variant 2141. | <pm_cot></pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design technical acquisition requirements (ACQ.11) for a battery management system (BMS). (Gateway scenario v5). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft project plan (MAN.3) for a powertrain SW release. (Charging scenario v5). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare changes (SUP.10) for system interface specification. (Charging scenario v5). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design for reuse (REU.2) a logging component. (BMS scenario v4). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish Plan process assessment (PIM.1) and objectives. (Charging scenario v2). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Establish a Contract Agreement conforming to ACQ vX1.3 for a vehicle telematics program vX1. (Chassis scenario v3) vX1. | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create configuration management (SUP.1) for the program. (Infotainment scenario v3). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Draft software units (SWE.4) for RetryQueue. (Chassis scenario v2). | <pm_cot>Aligning with ASPICE base practices on planning, monitoring, and objective evidence. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Create bid management process (MAN.1) for multi-supplier program. (Chassis scenario v4). | <pm_cot>Ensuring independence of verification and auditable records in line with ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Design Integrate software (SWE.5) into the gateway stack. (Charging scenario v3). | <pm_cot>Focusing on risk-driven decision making and measurable acceptance criteria. Risk thresholds trigger escalation paths and corrective actions.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Develop supply (SPL.3) for prototype batch. (Gateway scenario v7). | <pm_cot>Applying lessons-learned feedback loops and governance for sustained quality. Governance cadence ensures continuous visibility and agreement.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> | |
Prepare Establish reuse documentation and library (SUP.6/SUP.7 linkage). (Infotainment scenario v6). | <pm_cot>Emphasizing traceability, stakeholder agreement, and controlled change per ASPICE. Evidence links requirements to tests and controlled changes.</pm_cot>
<pm_final>
{"plan": "", "commands": [], "risks": [], "acceptance_criteria": [], "next_actions": []}
</pm_final> |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.