SOFTWARE DESIGN DOCUMENT Software Design Document $($SDD$)$ describes design goals set by the project, subsystem decomposition $($with UML class diagrams$),$ hardware$/$software mapping $($with UML deployment diagrams$),$ data management, access control, control flow mechanisms, and boundary conditions. The SDD is used to define interfaces between teams of developers and serve as a reference when architecture$-$level decisions need to be revisited. It also describes object design trade$-$offs made by developers, guidelines they followed for subsystem interfaces, the decomposition of subsystems into packages and classes, and the class interfaces. The SDD is used to exchange interface information among teams and as a reference during testing. In some cases the content of this