Opened on Feb 26, 2019 at 1:12:31 PM

Last modified on Mar 4, 2019 at 6:54:54 AM

#3705 accepted task

Software Design Document (SDD) for space profile

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: 6.1
Component: doc Version: 6
Severity: normal Keywords: qualification
Cc: Blocked By: #3704, #3706, #3708
Blocking: #3701

Description

A Software Design Document (SDD) is required by ​ECSS-E-ST-40C specified by Annex F. The plan is to use Doxygen for the software

  • architecture, and
  • detailed design.

How should links to from a software component (Doxygen group) to requirements be handled?

Change History (5)

comment:1 Changed on Feb 26, 2019 at 1:23:37 PM by Sebastian Huber

Blocked By: 3706 added

comment:2 Changed on Feb 26, 2019 at 1:30:45 PM by Sebastian Huber

Status: assigned → accepted

comment:3 Changed on Feb 26, 2019 at 2:22:06 PM by Sebastian Huber

Blocked By: 3708 added

comment:4 Changed on Mar 1, 2019 at 10:01:45 AM by Sebastian Huber <sebastian.huber@…>

In e6dd36ca/rtems:

bsp/gen5200: Remove offending @mainpage

Update #3705.

comment:5 Changed on Mar 4, 2019 at 6:54:54 AM by Sebastian Huber <sebastian.huber@…>

In a6e39d4a/rtems:

Update Doxyfile to Doxygen 1.8.15

Generate Doxygen output in doc and ignore this directory in Git. Add
RTEMS logo. The Doxygen documentation is now built using the source
tree. Just invoke "doxygen" in the top-level source directory.

The Doxyfile works also with at least Doxygen 1.8.13 and Doxygen 1.8.14.

Update #3705.

Note: See TracTickets for help on using tickets.