What diagrams and views would you suggest for showing/capturing the
SW Architecture of an existing embedded system that is not OO? It is
primarily an interrupt driven system that interacts with other systems
and sub-systems. Some of the diagrams could be outside the UML, if
deemed necessary. This system is slated to be re-engineered.

  Any papers available (practical not theoretical)?

 thanks

On May 11, 10:30 pm, mark...@yahoo.com wrote:
> What diagrams and views would you suggest for showing/capturing the
> SW Architecture of an existing embedded system that is not OO? It is
> primarily an interrupt driven system that interacts with other systems
> and sub-systems. Some of the diagrams could be outside the UML, if
> deemed necessary. This system is slated to be re-engineered.
A good resource for embedded systems is "Applied Software
Architecture" by Hofmeister, Nord and Soni.

Although the authors are researchers, their view set is a distillation
of what the software architects at Siemens do in order to document
their embedded systems.

Eoin.
--
Eoin Woods, Hemel Hempstead, UK
www.eoinwoods.info

marktxx@yahoo.com wrote:
>    What diagrams and views would you suggest for showing/capturing the
> SW Architecture of an existing embedded system that is not OO? It is
> primarily an interrupt driven system that interacts with other systems
> and sub-systems. Some of the diagrams could be outside the UML, if
> deemed necessary. This system is slated to be re-engineered.

A structure chart showing which routines call which other routines is 
good for the procedure organization.  You can add state transition 
diagrams, decision tables, significant data structures, and other 
diagrams that show the logic or data structure.

-- 
Thad

On May 11, 5:30 pm, mark...@yahoo.com wrote:
>    What diagrams and views would you suggest for showing/capturing the
> SW Architecture of an existing embedded system that is not OO? It is
> primarily an interrupt driven system that interacts with other systems
> and sub-systems. Some of the diagrams could be outside the UML, if
> deemed necessary. This system is slated to be re-engineered.
>
>   Any papers available (practical not theoretical)?
>
>  thanks

Consider drawing sequence diagrams (message sequence charts) for the
major scenarios in your system. The sequence diagrams should document
the interactions between major components in the system.

--
EventStudio 4.0 - http://www.EventHelix.com/EventStudio
Sequence Diagram based System Modeling Tool