Assessment 2 — Battery Swap Rack Concept Pitch

1. Overview of Assessment

Assessment 2 is a group presentation worth 30% of the course grade.

Building on the individual insights from Assessment 1, teams will converge on a concept for the single-site battery swap rack in Ho Chi Minh City. The presentation simulates a design review with stakeholders, (Department of Transport, Department of Industry and Trade, site landlord or retail host, neighbourhood representatives) and representatives from Project Saffron (the client’s electric-mobility program).

It aligns with Weeks 5–10 content within the Systems Engineering V Lifecycle process, emphasising fully automated rider operations.

2. Assessment Task

Form teams of 3 to 4 students. Nominate a Systems Engineer (team leader) to coordinate your efforts. At your first meeting, exchange the Assessment 1 handover packs, identify differences in requirements, and agree on a shared baseline (stakeholder needs, priority requirements, assumptions, and unresolved issues) before allocating tasks. Prepare for an 8-minute presentation plus 2 minutes of Q&A following the structure below.

Segment	Key content	Indicative time
Problem statement & stakeholder explanation	Shared baseline from handover packs, key stakeholder needs, and success measures (≈500 swaps/day with S-Series packs).	2 min
Concept of Operations narrative	Storyboard/sequence diagram for the rider journey and supporting automation, highlighting safety and customer experience.	2 min
Requirements & architecture	Consolidated user/system requirements, showing traceability and one preferred rack concept with brief trade-off explanation.	2.5 min
Roadmap & team reflection	Planning milestones, risk register, and an explanation of how you have collaborated to make progress	1.5 min

Use speaker notes to provide details that cannot fit on slides.

Slide Checklist

Use the following checklist to create your 8-minute presentation:

Slide 1: Team introduction and a summary of the agreed stakeholder needs, key requirements, any assumptions, and and any unresolved issues from Assessment 1 handover packs (consolidated).
Slide 2: Stakeholder/problem framing (key needs, risks, and success criteria).
Slide 3: Concept of Operations sequence diagram.
Slide 4: Consolidated requirements (table or matrix) and details of the planned test for each system requirement.
Slide 5: An explanation of your chosen concept shown using functional hierarchy and functional flow.
Slide 6: Risk register, and a brief explanation of how your team collaborated.
Backup: Additional evidence (e.g., alternative concept, data tables) for Q&A.

Feel free to adapt the layout, but ensure every item above is covered during the presentation.

Approach Checklist

Baseline alignment (Week 6): review individual handover packs, agree on the consolidated stakeholder needs and user and system requirements (merge overlapping user/system requirements).
Storyboard drafting (Week 7): sketch the user journey and interactions using Week 3 Concept of Operations patterns, gathering supporting evidence.
Requirements consolidation (Week 7–8): Evaluate traceability from user requirements through system requirements and functional hierarchy. Document your verification plan.
Concept comparison (Week 8): evaluate at least one alternative rack concept, documenting decision criteria and selecting a preferred option.
Presentation build (Week 9): follow the slide checklist and allocate speaking roles.
Rehearsal & refinement (Week 10/11): run timed rehearsals and refine transitions between speakers.

3. Timeline

Align team progress with the Week 6–11 teaching:

Week 6 – Form: confirm team membership and team leader, review Assessment 1 handover packs together, agree on concept scope and success criteria.
Week 7 – Shape: draft stakeholder/concept of operations slides, collect illustrations and diagrams, and update requirements traceability as MBSE content is covered in class.
Week 8 – Evaluate: complete architecture comparison, capture verification approach, and prepare early user journey/interaction.
Week 9 – Refine: finalise roadmap, rehearsal script, risk summary and practice presentation timing.
Week 10/11 – Deliver: final refinement of presentation and upload deliverables before presenting.

4. Submission Instructions and Presentation Logistics

Submit a single ZIP or folder containing the slide deck (PDF or PPTX) and optional supporting appendix (max 5 pages).
Use the filename convention GroupID_Assessment2_ConceptPitch.* (matching appendix names).
Upload via Canvas Assessment 2 by the scheduled deadline (presentations are delivered in Weeks 10–11).
All team members should present (note individual contributions in the notes).
Verbal feedback will be provided after the presentation with further feedback available through Canvas.

5. Assessment Criteria

Component	Criteria	Weight	CLO Alignment
Problem framing and stakeholder needs	Stakeholder needs analysis and thorough analysis of risk.	20%	CLO1, CLO3, CLO7
Concept of operations	Quality of workflow narrative for system context, inclusion of supporting diagrams, and scenario coverage.	20%	CLO1, CLO3
Requirements traceability	Depth/justification of consolidated requirements, traceability, and verification/validation approach.	20%	CLO2, CLO4
Architecture justification	Depth of comparison, decision criteria, and subsystem/interface clarity.	20%	CLO1, CLO2, CLO3
Professional communication and teamwork reflection	Presentation delivery, critical analysis, reflective insight, and presentation timing.	20%	CLO1, CLO4, CLO7

6. Academic Integrity and Teamwork

This is a group assessment. Collaboration within the team is required, but sharing across different teams is not permitted. Maintain a design notebook recording decisions, meeting notes, and contributions; the teaching team may request it for moderation. Cite all data, images, standards, and external references used in the presentation. Declare any use of generative AI or automation tools in accordance with university policy.