Volume Two demonstrates Data Driven System Engineering through one complete industrial example: Automatic Emergency Braking (AEB). The example begins with vehicle usage, physical locations, the operational boundary, system components, and required output behavior. It then carries the same authoritative Data objects and relationships through every development step so that the reader can see exactly how an output-first method works in practice. The AEB development proceeds from behavior definition and SOC construction to Data Contracts, architecture, allocation, verification, functional safety, cybersecurity, implementation, and lessons learned. Required signals such as detections, object tracks, vehicle motion, driver inputs, brake requests, actuator responses, availability, diagnostics, and timestamps are treated explicitly through Data Value and Data Timing. Middle Data is justified by the relationships that need it; architecture realizes the SOC; implementation preserves contract meaning; and verification applies independent Value and Timing oracles to the production-representative system. The final chapters distinguish established DDSE from derived knowledge organization and future research. They show how authoritative DDSE objects can support engineering knowledge frameworks, repositories, knowledge graphs, governed services, and human-led AI assistance without allowing AI to become the source of engineering truth. Appendices provide the operational reference material needed to apply the method: a glossary, Master Data Contract template, SOC template, verification checklist, Data Value and Data Timing reference, standards mapping, and notation summary. Volume Two is intended for readers who want a detailed end-to-end application, reviewers who need auditable evidence continuity, and engineering organizations preparing to make development knowledge explicit, reusable, and machine-understandable.