\chapter{Introduction}

\section{Purpose}
The purpose of the Architectural Design Document (ADD) is to describe the basic system design for the software to be made in this project. Furthermore the ADD defines a decomposition of the software system into components and the distribution of these components over the hardware. It also defines the external interfaces of the system.

\section{Scope}
The system being developed will be called TCCRMS. TCCRMS enables organizations to beter serve their customers through the introduction of reliable process and procedures of interacting with those customers. This CRMS in specific will improve the company's strategic position.

\section{List of definitions}


% THE DEFINITIONS OF ALL USED TERMS, ACRONYMS AND ABBREVIATIONS.

\begin{tabular}{|l|l|}
\hline

\textbf{ADD} & Architectural Design Document\\

\textbf{CRMS} & Customer Relationship Management System\\

\textbf{UR} & User Requirements\\

\textbf{URD} & User Requirements Document\\

\textbf{SR} & Software Requirements\\

\textbf{TCCRMS} & TOTAL COVER CRMS\\


\hline

\end{tabular}

\bibliographystyle{plain}

\bibliography{add}

\section{Overview}
This chapter contains the general information about the document and the project.

Chapter 2 describes the overall design. It contains a system overview and describes the different stakeholders.
A view template is described, which is used in chapter 3, 4 and 5.

Chapter 3 describes the logical view. It contains a description of the class diagram.

Chapter 4 describes the development view. It contains a description of the layer diagram.

Chapter 5 describes the deployment view. It contains a description of the deployment diagram.

Chapter 6 contains a use case diagram and models each use case as a separate sequence diagram.

Chapter 7 shows a traceability matrix. The matrix is used to connect each requirement to the 
operations and attributes, which will implement the requirement.

Appendix A shows some larger versions of diagrams used in the chapters.
\newpage
