Fisheye: Tag 179 refers to a dead (removed) revision in file `doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tps'. Fisheye: No comparison available. Pass `N' to diff? Index: doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tex =================================================================== diff -u -r178 -r179 --- doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tex (.../D-Soil Model - Test Report.tex) (revision 178) +++ doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tex (.../D-Soil Model - Test Report.tex) (revision 179) @@ -110,29 +110,41 @@ \section{Requirements} \label{sec:1.3} +\subsection{Non-functional requirements} +\begin{longtable}{p{10mm}p{\textwidth-10mm-24pt}} +NFR2 & The regular conventions, standards, tools and libraries for Deltares Systems software will be used. (must have). \\ +NFR & Data definitions will follow existing and emerging standards such as IRIS as much as possible. (must have). +Where possible emerging standards will be followed. For geometry a format has been used since the start of the development of Ringtoets which remained unchanged. \\ +NFR12 & The user-interface may not cause crashes during regular usage. (must have) \\ +NFR14 & Consistency between the input data and the output data must be guaranteed. (must have) \\ +NFR15 & ``e generieke code coverage wordt gesteld op 80\%, met uitzondering van de Delta Shell Light componenten, waarvoor een code coverage van 60\% zal worden gehanteerd.'' \\ +\end{longtable} -In the Functional Design of the \textit{User Interface} \cite{DSoilModel_FunctionalDesign}, the following requirements are defined and must be therefore tested: -\begin{longtable}{p{10mm}p{\textwidth-20mm-36pt}p{10mm}} -REQ 3 & Format of import data. The required import files are: geo-file, sti file, dsx file and mdb file from D-GeoStability; for subsoil schematizations (20 profiles) and strength parameters. • csv files; description of the segments and 1Dsoil profiles. shape files; location of segments, 20 profiles, CPT's, borings. & \\ \hline +\subsection{Functional requirements} + + +In the Functional Design of \ProgramName \citep{DSoilModel_FunctionalDesign}, the following requirements are defined and must be therefore tested: + +\begin{longtable}{|p{15mm}|p{\textwidth-20mm-36pt}|p{5mm}|} \hline +REQ 3 & Format of import data. The required import files are: geo-file, sti file, dsx file and mdb file from D-GeoStability; for subsoil schematizations (20 profiles) and strength parameters. csv files; description of the segments and 1Dsoil profiles. shape files; location of segments, 20 profiles, CPT's, borings. & \\ \hline REQ 3.2 & REQ 3.2 Import and view all SOS data. The user must be able to get an overview of all available SOS subsoil schematizations. A user must be able to import all SOS segments and browse through them. The user must get a good visual overview of all available scenarios of soil profiles. & \\ \hline REQ 3.3 & Select relevant SOS information for project. Only the relevant part of the SOS database needs to be read. The user defines the relevant area, a reference line, or the user specifies the segments from a list. Only the SOS data relevant data is imported into the O-Soil Model project. & \\ \hline REQ 4.1 & All existing M-SoilBase functionality must be present in D-Soil Model & 1) \\ \hline -REQ 5 & The application gathers the (stochastic) subsoil schematizations input and parameters for the following kernels: • WTI macro stability kernel, WTI piping kernel, WTI flow slide kernel. D-Soil Model can save this output into one file. & \\ \hline -"REQ 5.1 & In order to supply the kernels with the right input, the application supports the schematisation, storage and management of the subsoil schematisation for the failure mechanism macrostability. A subsoil schematisationf or a macrostability mechanism consists of: +REQ 5 & The application gathers the (stochastic) subsoil schematizations input and parameters for the following kernels: WTI macro stability kernel, WTI piping kernel, WTI flow slide kernel. D-Soil Model can save this output into one file. & \\ \hline REQ 5.1 & In order to supply the kernels with the right input, the application supports the schematisation, storage and management of the subsoil schematisation for the failure mechanism macrostability. A subsoil schematisationf or a macrostability mechanism consists of: One or more soil areas (polygons)or soil segments (polylines). Per soil area or segment per mechanism one (stochastic)soil profile schematisation. Per (stochastic) soil profile schematisation one or more 1D and/or 2D soil profiles scenarios with a probability of appearance and profile properties (e.g. preconsolidationpressure) if applicable. Per 1D or 2D soil profile scenario one or more soil layers with layer properties (e.g. aquifer yes/no) if applicable. • Per soil layer one soil material with soil material properties. • Surface line profiles related to the soil area or segment, if applicable . -All inputs are defined in the technical design document of the macrosstability kernel. [5]. Within a segment, Ringtoets must be able to combine the surface lines with all (relevant) available stochastic subsoil scenarios and other schematization parameters to form all inputs for the analysis of a failure mechanism. - & \\ \hline " -REQ 5.2 & Supply the subsoil schematization and –parameters for the WTI piping kernel. A subsoil schematization for piping consists of the same type of dataset as the data for the macro stability kernel. Within a segment, each surface line must be combined with all available stochastic subsoil scenarios to form all piping input scenarios. All piping inputs are defined in the technical design document of the piping kernel. [6]. & \\ \hline -REQ 5.3 & Supply the subsoil schematization and -parameters for the WTI flow slide kernel. A subsoil schematization for flow slide consists of the same type of dataset as the data for the macro stability kernel. Within a segment, each surface line must be combined with all available stochastic subsoil scenarios to form all flow slide input scenarios. All flow slide inputs are defined in the technical design document of the flow slide kernel. [7]. & 2) \\ \hline -REQ 5.4 & Each kernel has a list of variables defined in its own technical design [5, 6 and 7]. Each of these variables that have to do with subsoil information must be provided by D-Soil Model. In addition of these mechanism related variables, all general soil related properties need to be stored as well [8]. & \\ \hline +All inputs are defined in the technical design document of the macrosstability kernel. Within a segment, Ringtoets must be able to combine the surface lines with all (relevant) available stochastic subsoil scenarios and other schematization parameters to form all inputs for the analysis of a failure mechanism. + & \\ \hline +REQ 5.2 & Supply the subsoil schematization and –parameters for the WTI piping kernel. A subsoil schematization for piping consists of the same type of dataset as the data for the macro stability kernel. Within a segment, each surface line must be combined with all available stochastic subsoil scenarios to form all piping input scenarios. All piping inputs are defined in the technical design document of the piping kernel. & \\ \hline +REQ 5.3 & Supply the subsoil schematization and -parameters for the WTI flow slide kernel. A subsoil schematization for flow slide consists of the same type of dataset as the data for the macro stability kernel. Within a segment, each surface line must be combined with all available stochastic subsoil scenarios to form all flow slide input scenarios. All flow slide inputs are defined in the technical design document of the flow slide kernel. & 2) \\ \hline +REQ 5.4 & Each kernel has a list of variables defined in its own technical design. Each of these variables that have to do with subsoil information must be provided by D-Soil Model. In addition of these mechanism related variables, all general soil related properties need to be stored as well. & \\ \hline REQ 6 & For each failure mechanism the subsoil is described in soil seqrnents" consisting of one of more scenario(s) of a soil profile" with a probability of appearance. These soil profiles are described in either 10 or 20 layer schematization. A soil segment can have a combination of 10 and 20 soil profiles. Each layer is described with at least all the parameters needed for the relevant failure mechanism. This output is gathered in one file, which can be directly imported in Ringtoets. & \\ \hline REQ 6.1 & Stochastic characterization of the variables. A stochastic variable has a distribution. All stochastic variables can be stored as a mean value with a distribution . Per mechanisms the partial factor is stored in Ringtoets such that a stochastic variable can be turned into a semi- probabilistic designvalue. Ringtoets needs to work either with stochastic parameters or design values. The design values can be derived from the stochastic parameters. & 3) \\ \hline REQ 6.3 & Separate segments for each failure mechanism. The SOS segment boundaries can be different, depending upon the failure mechanism. Each mechanism has its own segment boundaries. & \\ \hline @@ -144,7 +156,6 @@ REQ 3.4 & Import relevant reference data. Also data which is not passed through to Ringtoets should be showed in order to make good subsoil schematizations. The following items need to be shown in a relevant window: Surface lines, Characteristic points, Outside water level, PL lines, Polder water level. Note: A surface line with characteristic points and the actual polder water level can be imported and placed above a relevant 20 cross section. Surface lines will be combined with all possible subsoil scenarios in Ringtoets. They will not be available as a separate object in O-Soil Model. Also, the outer water level and other PL lines can be viewed for reference in the cross sections of the 20 profile. & 4) \\ \hline REQ 7.3 & Overview of all available borings and CPT's in a segment/crosssection. All available ground investigation information in a section can be scrolled through and preferably dragged/dropped into a SOS scenario for viewing purposes. & \\ \hline REQ 7.4 & Overview of all available SOS scenario's in a segment. All available SOS scenarios per segment per mechanism must be presented. Preferably, available CPT's and borings can be matched with one SOS scenario. & \\ \hline -REQ 8 & & \\ \hline REQ 8.1 & A reference line can be imported form a GIS. This reference line can, for example, be used for the projection of soil investigation in longitudinal direction or to import SOS data in a relevant section. & 5) \\ \hline REQ 8.2 & Table view for soil parameters The application must support the several views to show (parts of) the subsoil schematisation. Table view to show all the information in a tabular format. The soil materials properties will only be shown in table view (not in graphical views). Property view to show details (information)of the selected object and if applicable the relation with other information(objects). & \\ \hline REQ 8.4 & Profile view to modify soil profiles .The application must support in profile view the drawing and modification of 10 and 20 soil profiles. 10 and 20 soil profile can be viewed in map view in case the location of the soil profile is available in RD (point or line). Modification of the location must be able in future development of the application. The application must support in profile view the drawing and modification of 10 and 20 soil profiles. Visualize the surface lines with their characteristic points. The application must give an overview in scenarios view of the soil profile scenarios for a soil area or segment. Since this might mean a major change in the software architecture an overview of the soil profile scenarios in another way than a scenarios view is acceptable if future development towards scenarios view maintain open. & \\ \hline @@ -283,70 +294,87 @@ %------------------------------------------------------------------------------ \chapter{System testing (Test Scripts)} \label{chapter3} -The tests on this level are to provide proof of the fact that the program meets its acceptation criteria: -\begin{itemize} - \item all main functions must provide the correct answers; - \item all possible errors must be handled and reported properly; - \item the functionalities of the \textit{User Interface} listed in the requirements (\Sref{sec:1.3}) must be present and work properly. -\end{itemize} +The tests on this level are to provide proof of the fact that the functionalities of the \textit{User Interface} listed in the requirements (\Sref{sec:1.3}) are present and work properly. - - -\section{Test of the \textit{User Interface}} \label{sec:4.3} - The test of the \textit{User Interface} has been executed by a tester using \textit{Test Script(s)}. All the \textit{Test Scripts} are part of the \textit{Test Document}, joined in appendix \autoref{app:TestDocument} at the end of this Test Report. -The test scripts testing the units and the default value of the input parameters are based on the Functional Design of \ProgramName. It appears that this document contains some typing errors or is incomplete. +Most of the test scripts pass. However, many test scripts are missing, as shown in \autoref{tab:OverviewTests}. This table gives an overview of which requirments are tested. Refer to \autoref{sec:1.3} for a complete description of the requirements. -Most of the test scripts pass; however, few errors were found on different levels and reported in the Deltares issue tracker tool called JIRA: -\begin{itemize} - \item \textbf{\textit{Errors in User Interface of \ProgramName :}} - \begin{itemize} - \item \href{https://issuetracker.deltares.nl/browse/GEOUI-60}{\textbf{GEOUI-60}}: When opening the Help-Over window a second time, the button ``Annuleren'' became ``NL-Annuleren''; - \item \href{https://issuetracker.deltares.nl/browse/GEOUI-68}{\textbf{GEOUI-68}}: In Run-up results, the unit of outputs ``Overbelasting per tijdsinterval'' and ``Overbelasting totaal'' must be [m$^{\text{2}}$/s$^{\text{2}}$] instead of [-]; - \item \href{https://issuetracker.deltares.nl/browse/GEOUI-74}{\textbf{GEOUI-74}}: Hints are missing for some parameters; - \item \href{https://issuetracker.deltares.nl/browse/GEOUI-71}{\textbf{GEOUI-71}}: The default value of Cu (constant in relation between Runup level and max front velocity) should be 1.1 instead of None; - \item \href{https://issuetracker.deltares.nl/browse/GEOUI-81}{\textbf{GEOUI-81}}: In tab Oploop-Geometrie, the unit of parameters ``Zbegin'' and ``Zend'' is [m] but should be [m NAP]; - \end{itemize} - - \item \textbf{\textit{Errors in the documentation of \ProgramName :}} - \begin{itemize} - \item \href{https://issuetracker.deltares.nl/browse/GEOUI-73}{\textbf{GEOUI-73}}: Some units given in Annex A of the Functional Design of \ProgramName are not correct; - \item \href{https://issuetracker.deltares.nl/browse/GEOUI-79}{\textbf{GEOUI-79}}: In the Functional Design of \ProgramName, add the default value and the number of decimals of all input parameters; - \end{itemize} -\end{itemize} +\begin{longtable}{|p{17mm}|p{\textwidth-17mm-24pt}|} +\caption{Overview of the tested requirements} \hline +REQ nr. & Test script in Test Document (\autoref{app:TestDocument}) \\ \hline +REQ 3.2 & Tested in script ``D-Soil model - Bestand'' and in ``D-Soil model - View'' \\ \hline +REQ 3.3 & Not tested \\ \hline +REQ 4.1 & Not relevant \\ \hline +REQ 5.1 & Not tested \\ \hline +REQ 5.2 & Not tested \\ \hline +REQ 5.3 & Not tested \\ \hline +REQ 5.4 & Not tested \\ \hline +REQ 6.1 & Not tested \\ \hline +REQ 6.3 & Not tested \\ \hline +REQ 6.4 & Not tested \\ \hline +REQ 6.5 & Not tested \\ \hline +REQ 6.6 & Tested in script ``D-Soil model - Tabellen - 1D Profielen'' but not tested for 2D profiles \\ \hline +REQ 7.1 & Not tested \\ \hline +REQ 7.2 & Not relevant \\ \hline +REQ 7.3 & Tested in script ``D-Soil model - Tabellen - Sonderingen'' and ``D-Soil model - Tabellen - Boringen'' but not completely \\ \hline +REQ 7.4 & Not tested \\ \hline +REQ 8.1 & Not relevant\\ \hline +REQ 8.2 & Tested in script ``D-Soil model - Tabellen -Materialen'' \\ \hline +REQ 8.4 & Not tested \\ \hline +REQ 8.5 & Not tested \\ \hline +REQ 8.6 & Not tested \\ \hline +REQ 8.7 & Not tested \\ \hline +REQ 8.8 & Not tested \\ \hline +REQ 8.9 & Tested in test script ``D-Soilmodel - Tabellen - Segmenten'' \\ \hline +REQ 8.10 & Not tested \\ \hline +REQ 8.11 & Not tested \\ \hline +REQ 8.12 & Not tested \\ \hline +REQ 8.13 & Not tested \\ \hline +REQ 8.14 & Not tested \\ \hline +REQ 8.15 & Not tested \\ \hline +REQ 8.16 & Not tested \\ \hline +REQ 8.17 & Not tested \\ \hline +REQ 9.1 & Tested in script ``D-Soil model - Tabellen -Materialen'' \\ \hline +REQ 9.2 & Not tested \\ \hline +REQ 9.3 & Not tested \\ \hline +REQ 9.4 & Not tested \\ \hline +REQ 9.5 & Not tested \\ \hline +REQ 9.7 & Not tested \\ \hline +REQ 9.8 & Not tested \\ \hline +REQ 9.9 & Tested in script ``D-Soil model - Tabellen - 1D Profielen'' but not tested for 2D profiles \\ \hline +REQ 9.10 & Not tested \\ \hline +REQ 9.11 & Not tested \\ \hline +REQ 9.12 & Not tested \\ \hline +REQ 9.14 & Not tested \\ \hline +REQ 9.15 & Not tested \\ \hline +REQ 9.16 & Not tested \\ \hline +REQ 9.18 & Not tested \\ \hline +REQ 9.19 & Not tested \\ \hline +REQ 9.20 & Not tested \\ \hline +REQ 9.21 & Not tested \\ \hline +REQ 9.23 & Not tested \\ \hline +REQ 9.24 & Not tested \\ \hline +\label{tab:OverviewTests} +\end{longtable} -After solving the issues on the documentation, the Test Document self will need to be updated. This is reported in JIRA as task number \href{https://issuetracker.deltares.nl/browse/GEOUI-80}{\textbf{GEOUI-80}}. +A special attention must be paid to improved the number of test scripts in the Test Document, so that all the requirements listed in the Functional Design are tested. This is reported as task \href{https://issuetracker.deltares.nl/browse/DSB-479}{\textbf{DSB-479}} in the Deltares issue tracker tool called JIRA. -The error(s)/warning(s) generated by an input outside its limits (and performed in the kernel self) were also tested by means of test scripts. Two errors were found: -\begin{itemize} - \item \textbf{\textit{Validation errors in Grass Run-up kernel:}} - \begin{itemize} - \item \href{https://issuetracker.deltares.nl/browse/GEORU-29}{\textbf{GEORU-29}}: For parameter $\Delta$T, the Functional Design of the Run-up kernel \citep{GrassWaveRunupKernel_FunctionalDesign} gives a likely interval of [0.2. 2.0] but the kernel uses [0.08333, 0.5]; - \end{itemize} - - \item \textbf{\textit{Validation errors in Grass Wave Impact kernel:}} - \begin{itemize} - \item \href{https://issuetracker.deltares.nl/browse/GEOWI-26}{\textbf{GEOWI-26}}: No warning is displayed if coefficient C is outside its likely interval [0..0.5]; - \end{itemize} -\end{itemize} -The errors listed above are absolutely not blocking for the use of \ProgramName within WTI 2017. \ProgramName can therefore be handed over to the client. \\ -All those issues should be fixed in the next release of the program. - %------------------------------------------------------------------------------ \chapter{Conclusion} All the unit and integration tests performed for the validation of \ProgramName pass but cover only 19.8\% of the code, so largely less than the minimum required code coverage of 60\% prescribed in \cite{OverallTestPlanWTI}. \\ A special attention should be therefore paid to increase the code coverage of \ProgramName. -A complete test of the User Interface has been performed by means of test scripts (see appendix \autoref{app:TestDocument}). Some test scripts failed with respect to the valid and likely intervals of input parameter, the unit or the presence of hint. +A complete test of the User Interface has been performed by means of test scripts (see appendix \autoref{app:TestDocument}). + -To conclude, all the requirements of the Functional Design of \ProgramName (listed in \Sref{sec:1.3}) are implemented. The correct functioning of \ProgramName \VersionNumber is ensured with respect to the calculated output, however the User Interface needs some minor improvements. +To conclude, this test report does not allow to conclude that all the requirements of the Functional Design of \ProgramName (listed in \Sref{sec:1.3}) are implemented. The correct functioning of \ProgramName \VersionNumber is there not ensured with respect to the calculated output, however the User Interface needs some minor improvements. @@ -401,34 +429,35 @@ \chapter{Test Document \ProgramName \VersionNumber} \label{app:TestDocument} -\includepdf[pages=1, offset=-72 -70]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=2, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=3, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=4, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=5, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=6, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=7, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=8, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=9, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=10, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=11, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=12, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=13, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=14, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=15, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=16, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=17, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=18, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=19, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=20, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=21, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=22, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=23, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=24, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=25, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=26, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} -\includepdf[pages=27, offset=-72 -70]{../DSoilModel - Test documenten/Testdocument_DSoilModel_16-1-0-135.pdf} +\includepdf[pages=1, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=2, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=3, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=4, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=5, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=6, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=7, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=8, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=9, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=10, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=11, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=12, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=13, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=14, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=15, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=16, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=17, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=18, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=19, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=20, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=21, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=22, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=23, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=24, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=25, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=26, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} +\includepdf[pages=27, fitpaper,rotateoversize]{../DSoilModel-TestDocumenten/Testdocument_DSoilModel_16_1_0_135.pdf} + \end{appendices} @@ -439,7 +468,7 @@ \pagestyle{empty} \cleardoublepage \mbox{} -\includepdf[pages=2, offset=-72 -70]{pictures/D-SoilModel-TestDocument.pdf} % links-rechts past precies +\includepdf[pages=2, fitpaper,rotateoversize]{pictures/D-SoilModel-TestDocument.pdf} % links-rechts past precies \end{document} Index: doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.pdf =================================================================== diff -u -r178 -r179 Binary files differ