From 3e63cebfc44befcb3a8d7f9634f5b1b95ec9dd8b Mon Sep 17 00:00:00 2001 From: Oliver Schinagl Date: Tue, 25 Oct 2005 18:13:18 +0000 Subject: wat references toegevoegd en final compile gedaan --- ADD/ADD.pdf | Bin 289863 -> 289862 bytes ADD/appendixa.tex | 2 +- ADD/chapter1.tex | 15 ++++++++------- ADD/chapter2.tex | 2 ++ ADD/chapter3.tex | 3 ++- ADD/chapter4.tex | 1 + ADD/chapter5.tex | 1 + ADD/chapter6.tex | 2 ++ ADD/chapter7.tex | 2 ++ 9 files changed, 19 insertions(+), 9 deletions(-) diff --git a/ADD/ADD.pdf b/ADD/ADD.pdf index c846f79..ea15c09 100644 Binary files a/ADD/ADD.pdf and b/ADD/ADD.pdf differ diff --git a/ADD/appendixa.tex b/ADD/appendixa.tex index 20d9d33..0177d3c 100644 --- a/ADD/appendixa.tex +++ b/ADD/appendixa.tex @@ -1,7 +1,7 @@ \chapter{Diagrams} \begin{figure}[t] \appendix{Class Diagram Large} - \label{appendixa} + \label{appendix_diagrams} \begin{center} \includegraphics*[angle=0, height=20cm, keepaspectratio]{Images/ClassDiagram.eps} \caption{Class Diagram} diff --git a/ADD/chapter1.tex b/ADD/chapter1.tex index a58293c..26f16ad 100644 --- a/ADD/chapter1.tex +++ b/ADD/chapter1.tex @@ -1,4 +1,5 @@ \chapter{Introduction} +\label{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. @@ -38,19 +39,19 @@ The system being developed will be called TCCRMS. TCCRMS enables organizations t \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. +Chapter \ref{chapter_overall_design} 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 \ref{chapter_logical_view} 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 \ref{chapter_development_view} 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 \ref{chapter_deployment_view} 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 \ref{chapter_user_scenarios} 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 +Chapter \ref{chapter_traceability_matrix} 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. +Appendix \ref{appendix_diagrams} shows some larger versions of diagrams used in the chapters. \newpage diff --git a/ADD/chapter2.tex b/ADD/chapter2.tex index 2564ff0..bedf950 100644 --- a/ADD/chapter2.tex +++ b/ADD/chapter2.tex @@ -1,4 +1,6 @@ \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 diff --git a/ADD/chapter3.tex b/ADD/chapter3.tex index 8167699..b93406d 100644 --- a/ADD/chapter3.tex +++ b/ADD/chapter3.tex @@ -1,4 +1,5 @@ \chapter{Logical view} +\label{chapter_logical_view} \section{Primary presentation} \begin{figure}[h] @@ -7,7 +8,7 @@ \caption{Class Diagram} \end{center} \end{figure} -A larger image can be found in appendix \ref{appendixa}, Class Diagram Large. +A larger image can be found in appendix \ref{appendix_diagrams}, Class Diagram Large. \section{Element catalog} This section describes all of the classes in the class diagram as diff --git a/ADD/chapter4.tex b/ADD/chapter4.tex index 7fcb073..8b27805 100644 --- a/ADD/chapter4.tex +++ b/ADD/chapter4.tex @@ -1,4 +1,5 @@ \chapter{Development view} +\label{chapter_development_view} \section{Primary presentation} \begin{figure}[h] diff --git a/ADD/chapter5.tex b/ADD/chapter5.tex index 8d3b8d4..59fa795 100644 --- a/ADD/chapter5.tex +++ b/ADD/chapter5.tex @@ -1,4 +1,5 @@ \chapter{Deployment view} +\label{chapter_deployment_view} \section{Primary presentation} \begin{figure}[h] diff --git a/ADD/chapter6.tex b/ADD/chapter6.tex index 8ac2df0..30182f7 100644 --- a/ADD/chapter6.tex +++ b/ADD/chapter6.tex @@ -1,4 +1,6 @@ \chapter{User Scenarios} +\label{chapter_user_scenarios} + This chapter will illustrate all the use cases derived from the requirements. Each requirement is modeled in the use case diagram as a single use case. The use case diagram is shown below. diff --git a/ADD/chapter7.tex b/ADD/chapter7.tex index b3c4dc3..a1f6054 100644 --- a/ADD/chapter7.tex +++ b/ADD/chapter7.tex @@ -1,4 +1,6 @@ \chapter{Traceability matrix} +\label{chapter_traceability_matrix} + This traceability matrix links the requirements to the attributes and properties that will implement them. \begin{longtable}{|p{30mm}|p{60mm}|} \hline -- cgit v0.12