From c82efcda9802588de324ec80e2c31b534981ba66 Mon Sep 17 00:00:00 2001
From: Oliver Schinagl <oliver@schinagl.nl>
Date: Wed, 12 Oct 2005 09:03:50 +0000
Subject:

---
 ADD/ADD.tex      |  1 +
 ADD/chapter1.tex |  5 +----
 ADD/chapter2.tex | 28 ++++++++++++++++++++++++----
 ADD/chapter3.tex |  1 +
 ADD/chapter4.tex |  3 ++-
 ADD/chapter6.tex |  1 +
 6 files changed, 30 insertions(+), 9 deletions(-)

diff --git a/ADD/ADD.tex b/ADD/ADD.tex
index 81853f3..8e8d7cf 100644
--- a/ADD/ADD.tex
+++ b/ADD/ADD.tex
@@ -32,5 +32,6 @@
 \include{chapter5}
 \include{chapter6}
 \include{chapter7}
+\include{chapter8}
 \appendix
 \end{document}
diff --git a/ADD/chapter1.tex b/ADD/chapter1.tex
index d5cb092..b67dfa5 100644
--- a/ADD/chapter1.tex
+++ b/ADD/chapter1.tex
@@ -1,8 +1,7 @@
 \chapter{Introduction}
-%INSERT TEXT HERE
 
 \section{Purpose}
-The purpose of this URD is to specify the requirements for the final product of all different end users.
+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.
@@ -19,8 +18,6 @@ The system being developed will be called TCCRMS. TCCRMS enables organizations t
 
 \textbf{CRMS} & Customer Relationship Management System\\
 
-\textbf{ESA} & European Space Agency\\
-
 \textbf{UR} & User Requirements\\
 
 \textbf{URD} & User Requirements Document\\
diff --git a/ADD/chapter2.tex b/ADD/chapter2.tex
index c08fe6d..82abeb1 100644
--- a/ADD/chapter2.tex
+++ b/ADD/chapter2.tex
@@ -1,20 +1,40 @@
 \chapter{Overall design}
 \section{System overview}
+\textit{Short description of what the systems's function is and any important background or constraints}.
+TCCRMS enables the organization to beter serve their customers through the introduction of reliable process and procedures of interacting with those customers. 
+The following functions are It shows customer details to the employee when the customer is calling.
+
 
 \section{Stakeholders}
+\textit{Who the users of the system are and maybe their concerns or relevant views}.
 
 \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}
-\subsection{Other information}
-The standard template by which each view is described.
+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}
-Rationale about the chosen views.
+\textit{Rationale about the chosen views}.
+
 
 \section{Mapping between views}
+\textit{relationships among the views}
 
-\section{}
diff --git a/ADD/chapter3.tex b/ADD/chapter3.tex
index d7998a0..5dc7ee8 100644
--- a/ADD/chapter3.tex
+++ b/ADD/chapter3.tex
@@ -1,4 +1,5 @@
 \chapter{Logical view}
+\textit{UML class diagram}
 \section{Primary presentation}
 
 \section{Element catalog}
diff --git a/ADD/chapter4.tex b/ADD/chapter4.tex
index b9d489e..f79240c 100644
--- a/ADD/chapter4.tex
+++ b/ADD/chapter4.tex
@@ -1,4 +1,5 @@
-\chapter{Physical view}
+\chapter{Process view}
+\textit{UML Activity or state diagram}
 \section{Primary presentation}
 
 \section{Element catalog}
diff --git a/ADD/chapter6.tex b/ADD/chapter6.tex
index 8e544d1..95e7689 100644
--- a/ADD/chapter6.tex
+++ b/ADD/chapter6.tex
@@ -1,4 +1,5 @@
 \chapter{Deployment view}
+textit{UML deployment diagram}
 
 \section{Primary presentation}
 
-- 
cgit v0.12

