@phdthesis{Dannemann2015,
  author    = {Dannemann, Frank},
  title     = {Unified Monitoring of Spacecrafts},
  url       = {http://nbn-resolving.de/urn:nbn:de:bvb:20-opus-115934},
  school      = {Universit{\"a}t W{\"u}rzburg},
  year      = {2015},
  abstract  = {Within this thesis a new philosophy in monitoring spacecrafts is presented: the unification of the various kinds of monitoring techniques used during the different lifecylce phases of a spacecraft. The challenging requirements being set for this monitoring framework are: - "separation of concerns" as a design principle (dividing the steps of logging from registered sources, sending to connected sinks and displaying of information), - usage during all mission phases, - usage by all actors (EGSE engineers, groundstation operators, etc.), - configurable at runtime, especially regarding the level of detail of logging information, and - very low resource consumption. First a prototype of the monitoring framework was developed as a support library for the real-time operating system RODOS. This prototype was tested on dedicated hardware platforms relevant for space, and also on a satellite demonstrator used for educational purposes. As a second step, the results and lessons learned from the development and usage of this prototype were transfered to a real space mission: the first satellite of the DLR compact satellite series - a space based platform for DLR's own research activities. Within this project, the software of the avionic subsystem was supplemented by a powerful logging component, which enhances the traditional housekeeping capabilities and offers extensive filtering and debugging techniques for monitoring and FDIR needs. This logging component is the major part of the flight version of the monitoring framework. It is completed by counterparts running on the development computers and as well as the EGSE hardware in the integration room, making it most valuable already in the earliest stages of traditional spacecraft development. Future plans in terms of adding support from the groundstation as well will lead to a seamless integration of the monitoring framework not only into to the spacecraft itself, but into the whole space system.},
  subject      = {Raumfahrzeug},
  language  = {en}
}
@article{MontenegroDannemann2011,
  author    = {Montenegro, Sergio and Dannemann, Frank},
  title     = {Experiences and Best Practice Requirements Engineering for Small Satellites},
  series = {Computing Science and Technology International Journal},
  volume    = {1},
  journal   = {Computing Science and Technology International Journal},
  number    = {2},
  url       = {http://nbn-resolving.de/urn:nbn:de:bvb:20-opus-153307},
  year      = {2011},
  abstract  = {The design and implementation of a satellite mission is divided into several different phases. Parallel to these phases an evolution of requirements will take place. Because so many people in different locations and from different background have to work in different subsystems concurrently the ideas and concepts of different subsystems and different locations will diverge. We have to bring them together again. To do this we introduce synchronization points. We bring representatives from all subsystems and all location in a Concurrent Engineering Facility (CEF) room together. Between CEF sessions the different subsystems will diverge again, but each time the diversion will be smaller. Our subjective experience from test projects says this CEF sessions are most effective in the first phases of the development, from Requirements engineering until first coarse design. After Design and the concepts are fix, the developers are going to implementation and the concept divergences will be much smaller, therefore the CEF sessions are not a very big help any more.},
  language  = {en}
}