This is an old revision of the document!


Guideline for the book

General Chapter Structure

Each chapter should follow a consistent structure and be linked to the book’s central V-model and verification and validation framework.

1. Introduction (1 page exactly)

At the beginning of each chapter, briefly explain:

  • what the chapter covers and why the topic is important for autonomous systems;
  • domain specifics and general aspects;
  • what the main V&V challenges are;
  • general schematic or architectural figure at the beginning of the chapter.

2. Technical Content (approx. 50%)

Present the technical content as fluent text, not as a collection of bullet points. Use lists and tables only when they make the information clearer.

3. V&V of [chapter title] (approx. 50%)

Each chapter should include a clearly identifiable V&V section titled:

V&V of [chapter title]

This section should describe how the chapter topic is verified and validated, including relevant methods, limitations and risks.

4. Summary (1 page exactly)

Each chapter should end with a short summary that highlights:

* the main conclusions; * the key V&V challenges; * the transition to the next chapter.

Every chapter will be 15–25 pages in PDF format.

en/safeav/rules.1780484625.txt.gz · Last modified: by raivo.sell
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0