summaryrefslogtreecommitdiffstats
path: root/ADD/chapter1.tex
diff options
context:
space:
mode:
Diffstat (limited to 'ADD/chapter1.tex')
-rw-r--r--ADD/chapter1.tex15
1 files changed, 8 insertions, 7 deletions
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