\chapter{Overall design}
\label{chapter_overall_design}

\section{System overview}
TCCRMS enables the organization to better serve their customers
through the introduction of reliable process and procedures of
interacting with those customers.\\
The system will support or automate the tasks in the insurance
proposal and/or an insurance policy making process. It provides
detailed information about the client, claims and payments, to
employees. Employees will also use this system to track and manage
there own careers and those of other employees.\\
The system will be build from scratch, because this isn't an update
of an earlier system.


\section{Stakeholders}
The system has a couple of stakeholder groups.

The first group consists of the users of the system. This group
contains the sales representatives, clients (via website),
administrative personnel and the business department. The main
purpose of this document for this group is to show that every
requirement is adequately provided by the system. The sequence
diagrams are the views for this particular group.

The second group are the people who will maintain the system. The
main purpose of this document for this group is to show how the
system is build and deployed, so it can be understood and
maintained. The logical view shows how the system is divided into
classes and describes the functionality of the the system. The
deployment view shows where each component or layer will be
installed.

The third group are the developers who will implement the system.
The main purpose of this document for this group is to show what has
to be implemented. The logical view shows the functionality that
should be implemented.

The last group consist of the managers who will divide the work,
assign development teams and must calculate project metrics. The
main purpose of this document for this group is to show how the
system can be divided into smaller subsystems. The development view
shows how the system can be divided.



\section{View template}
This is a description of the template of used to describe all of the views.

\subsection{Primary presentation}
The primary view shows the elements and the relationships among them that populate the view. It contains information which we want to convey about the system, in the vocabulary of the view. It includes the primary elements and relations of the view.

\subsection{Element catalog}
The element catalog details the elements and relations depicted in the primary presentation. Any elements or relations which where relevant to the view that were omitted from the primary presentation, are introduced and explained. The behavior and interfaces of an element are also described here.

\subsection{Context diagram}
The context diagram shows how the system depicted in the view relates to its environment in the vocabulary of the view.

\subsection{Variability guide}
The variability guide shows how to exercise any variation points that are a part of the architectural shown in this view.

\subsection{Architectural background}
The architectural background explains why the design reflected in the view came to be.
\subsubsection{Rationale}
The rationale part will explain why the decisions reflected in the view were made and why alternatives were rejected.
\subsubsection{Assumptions}
The assumptions part will describe any assumptions reflected in the design.


\section{Chosen views}
See \textit{stakeholders} section for explanation of chosen views.


\section{Mapping between views}
There is a clear mapping between the logical view and the development view. The classes described in
the logical view are divided into layers in the development view. 

The sequence diagrams are derived from the operations of the classes in the logical view.