Index: doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.pdf =================================================================== diff -u -r171 -r178 Binary files differ Index: doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tex =================================================================== diff -u -r171 -r178 --- doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tex (.../D-Soil Model - Test Report.tex) (revision 171) +++ doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tex (.../D-Soil Model - Test Report.tex) (revision 178) @@ -59,9 +59,9 @@ \keywords{WTI2017, hydraulic structures, structural failure, calculation kernel, wave pressure, linear load calculation, quadratic load calculation} -\references{\bibliography{../../Work/WTI_references/wti_references}} +\references{Refer to \autoref{chp:References}.} -\summary{This document contains the test report for \ProgramName \VersionNumber. +\summary{This document contains the test report for \ProgramName \VersionNumber, released with the following Delta Shell Light libraries: DSL--Core 16.1.1.574, DSL--FormsGeo 16.1.0.582, DSL--FormsMap 16.1.0.582, DSL--FormsStandard 16.1.0.581, DSL--Geo 16.1.1.578, DSL--Geographic 16.1.0.362, DSL--GeotechnicsIO 16.1.0.538 and DSL--Probabilistic 16.1.0.364. All the unit 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\%. Not all the features of \ProgramName were tested during the user interface testing (using test scripts). The functioning of \ProgramName as described in the Functional Design is therefore not ensured. \textbf{\footnotesize{Samenvatting}} \newline Dit document bevat het test rapport voor \ProgramName \VersionNumber.} @@ -81,12 +81,14 @@ \section{Purpose and scope of this document} \label{sec:1.1} -This document contains the Test Report for the standalone program \ProgramName that computes the erosion of a grass revetment in the wave runup zone and in the wave impact zone. This program is part of the WTI 2017 program. +This document contains the Test Report for \ProgramName. -The document will not give any background on the context of the WTI project and on the derivation or motivation of the supported physical models. For this purpose the reader is referred to the VTV2017 and to its supporting technical reports and their background reports underneath. +The document will not give any background on the context of the WTI project. For this purpose the reader is referred to the WTI2017 and to its supporting technical reports and their background reports underneath (\autoref{sec:1.3}). -This Test Report describes the results of the tests that must take place before the program can be released. The tests must ensure that all the requirements are fulfilled with and that the quality of the program is sufficient. This document reports the success of the relevant tests. +This document will not describe how the requirements of the functional design are implemented in the program. +This document describes the results of the tests that must take place before the program can be released. The tests must ensure that all the requirements are fulfilled with and that the quality of the program is sufficient. This document reports the success of the relevant tests. + \section{Other system documents} \label{sec:1.2} The full documentation on the program comprises the following documents. @@ -108,9 +110,78 @@ \section{Requirements} \label{sec:1.3} + + + 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{13mm}p{\textwidth-13mm-24pt}} -?? +\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 +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: +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 +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 +REQ 6.4 & Definition of the location of the 1D profile for Piping and DFlowSlide. 2D profiles exist for piping and flow slide analyses. The current kernels can only handle 1D schematizations. The D-Soil Model user must be able to define the location of the 1D profile per 2D profile per mechanism. & \\ \hline +REQ 6.5 & The application must support profile properties. Profile properties are information which is related and can be allocated to a soil profile. Thus far, the yield stress (Pre-consolidation stress) is the only profile property being used. & \\ \hline +REQ 6.6 & The application must support layer properties. Layer properties are information which is related and can be allocated to a soil layer. Thus far, the "is aquifer" property is the only available layer property. In future, leak agelength sor dampingfactors may also be transferred to layer properties. & \\ \hline +REQ 7 & Stochastic schematization of subsoil. All the parameters of above described schematization can consist of stochastic variables or "as is" value (characteristic value or design value). All stochastic variables can be stored as a mean value with distribution parameters and the distribution type. Per mechanisms the partial factor is stored in Ringtoets such that a stochastic variable can be turned into a semiprobabilistic design value & \\ \hline +REQ 7.1 & Stochastic subsoil modelling consists of soil segments (either lines or areas), each with soilprofiles with a probability of appearance. Per failure mechanism the segments are defined. This stochastic subsoil modelling is presented in D-Soil Model. & \\ \hline +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 +REQ 8.5 & Automatically project boreholes and CPT onto a cross section. Borehole and CPT can be allocated automatically to one or more soil profiles if it lies within a certain (user defined) distance of this cross section. If the location in RD is known the borehole or CPT is plotted perpendicular to the 20 profile if the borehole or CPT is within a user defined distance. This distance is set per cross section and is default 100 meter. The CPT/boring and the soilprofile are plotted on the same vertical referencelevel (e.g. NAP) and scale & 6) \\ \hline +REQ 8.6 & Segments have an ID that the user can relate to. This ID must be presented in mapview & \\ \hline +REQ 8.7 & Show all soil investigation with labels in mapview The name of the boring or CTP must be visible to the user in mapview & \\ \hline +REQ 8.8 & Visualize the surface lines with their characteristic points. A user must be able to view surface lines and characteristic points on top of a 10 and/ or 20 cross section. & \\ \hline +REQ 8.9 & Select boreholes and CPT's onto a cross section. If automatic plotting (RE08.5) is not possible, the borehole or CPT can be dragged by the user to the right location in the 20 profile. The height reference of a borehole or CPT is assumed to be the same as in the soil profile and plotted in the height reference of the 20 profile & \\ \hline +REQ 8.10 & 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 maintains open. This scenarios view is not yet required in this version of the application if an overview of the scenarios per soil area or segments is provided in another manner (see also REO 5.1). En zie plaatje in Functional design document. & \\ \hline +REQ 8.11 & View files in file-related software. a. CPT's and borings in GEF format can be shown in an external program like GefPlotTool by doubleclicking the names in D-Soil Model. b. Open *.sti in DGeoStability by doubleclicking the name in D-Soil Model. & \\ \hline +REQ 8.12 & In map view, relevant background information must be shown. Standard relevant information is AHN information and information from a (later to be specified) WMS server. & \\ \hline +REQ 7.2 & Allocation of CPT's and boreholes on a map and to a segment Imported CPT's and borings are shown on a map and can be matched to a segment. This Match can be pre-defined via a GIS-file.The application must support the allocation of soil profile scenarios to a soil area or segments. A soil profile scenario consists of a collection of 1D or 2D soil profiles with a probability of appearance. & \\ \hline +REQ 8.14 & Draw SOS profiles in one segment on the same height for comparison. When plotting SOS profiles next to one another, they must be plotted relative to a same reference level (e.g. NAP) and scale for simple comparison. The minimum and maximum value of the layers must also be shown. & \\ \hline +REQ 8.15 & Show ground investigation simultaneously to REO 8.14 at the same reference level. When plotting soil investigations (CPT's and borings) on a reference line next to one another, they must be plotted relative to a same reference level (e.g. NAP) for simple comparison. & \\ \hline +REQ 8.16 & Synchronization between different views. The user can switch between different kind of views of the data by clicking on the name. E.g. clicking on segment A in the table window, also selects this segment on the map and the properties of this segment are shown on the map. Applicable for names of: Soilsegments, soilprofiles, material, layer, CPT, boring, surfacelines & \\ \hline +REQ 8.17 & Visibility of yield stress Yield stresses are plotted in the 2D profile as points with optional labels (label =Spanningswaarde). & \\ \hline +REQ 9 & Edit and generate the building blocks of the subsoil schematization The user is able to edit all the building blocks. The user is responsible for the edits, D-Soil Model gives validations messages when applicable (e.g. minimum and maximum values). The user is supported by the application with tools. & 7) \\ \hline +REQ 9.1 & The soil materials can be named or renamed and the material properties can be created and modified in table view. Modification of the soil materials automatically updates the soil materials in the regarding soil layers. The material properties can be filtered on failure mechanism and calculationmodel if applicable. & \\ \hline +REQ 9.2 & The probably of appearance of one SOS scenario can be changed. The user is responsible for letting these scenarios add up to 100 percent. The interface should be such that the user can check this easily. & \\ \hline +REQ 9.3 & An existing 1D profile can be changed into a 2D profile so that the user can make changes in the cross section. A reference surface line needs to be drawn in this profile. Default width 100m. & \\ \hline +REQ 9.4 & A user can make changes in a cross section is a similar way he can do in DGeoStability. & 8) \\ \hline +REQ 9.5 & Have reference points to draw surface lines on 2D profiles. Surface lines and characteristic points must be plotted onto a 2D profile.As a referencepoint, the x-value of the outer crest line will be used. This means that, for each 2D profile, the location of the initial outer crest characteristic point must be stored. The user can move the reference point lf no width of the cross section is known, the default is set to 100 meters. Other mapping methods are in consideration for more reliable mapping. & \\ \hline +REQ 9.7 & The application must support the user to draw two dimensional soil layering. & \\ \hline +REQ 9.8 & The application must support the allocation of a soil material to a soil layer in one or more soil profiles. & \\ \hline + REQ 9.9 & Define layer as aquifer or aquitard. A soil layer in a soil profile can be defined in profile view as an aquifer. All other layers are considered to be an aquitard..This is a layer property. & \\ \hline +REQ 9.10 & Enter yield stresses for macrostability. The pre-consolidation pressure can be entered as a profile property and as soil material property. If the pre-consolidation pressure is a profile property it can be entered as point in profileview. The yield stresses must be shown to the user in a visual manner. & \\ \hline +REQ 8.13 & Show SOS scenario's in 20 profiles. All relevant SOS scenario's (the ones from the same segment) must be visible in a 20 profile at the same reference level. The user will use this additional information to make sure the 20 subsoil schematization fits the SOS segments. & \\ \hline +REQ 9.12 & Modify the location of de borehole or CPT in the 2D profile. A CPT or borehole can be dragged to another location in the profile view. This will never alter the depth of the CPT or borehole, nor will it affect the "real" world position of the CPT or borehole. & \\ \hline +REQ 9.14 & Minimal validity check on the data. Minimal validation for the right values within given boundaries & \\ \hline +REQ 9.15 & Extensive validity check on the data for Ringtoets. Complete validation for a Ringtoets analyses where the user can ask if the data is complete to perform the analysis (as a WTI add-on).Validation is possible per failure mechanism. & 9) \\ \hline +REQ 9.16 & Define n and gamma per material parameter for determination of stochastic or design values. Parameters to define the nature of the soil tests regarding one material need to be stored to be able to calculate stochastic values. & 10) \\ \hline +REQ 9.18 & Add another 1D profile to an existing 2D profile. The user must be able to build a 2D schematization based on multiple 1D profiles. A newly selected 1D profile is then valid in a predefined range. Different material properties underneath and next to an embankment can be selected. The surface line and dike material (including the internal geometry of the dike) can also be edited. & \\ \hline +REQ 9.19 & Draw a new subsoil configuration. The user must be able to configure a new subsoil schematization from scratch. & \\ \hline +REQ 9.20 & Incorporate settlements underneath an embankment. The user must be able to define settlements (input cm settlement as input) underneath the embankment. & \\ \hline +REQ 9.21 & On a longitudinal cross section, the user is to be able to Visualize minimum and maximum of layer boundaries from the SOS data. For each 1D SOS scenario, the user must see the expected value of each layer boundary, together with the minimum and maximum value of the layer boundary. & \\ \hline +REQ 9.23 & On a longitudinal cross section, the user is to be able to Import soil areas and segments. The application can import soil areas (as a nice to have) and segments (must have) as shapefiles (polygons or polylines). & \\ \hline +REQ 9.24 & On a longitudinal cross section, the user is to be able to Table import/export. All the tables in D-Soil Model (tables in table window, yield stresses, Sigmatau curves etc.) must have an export as well as an import functionality (for table or column(s)). & \\ \hline \end{longtable} @@ -330,14 +401,34 @@ \chapter{Test Document \ProgramName \VersionNumber} \label{app:TestDocument} -\includepdf[pages=1, offset=-72 -70]{../Work/Testdocument_Grastoets_16-1-0-1825_paraaf.pdf} -\includepdf[pages=2, offset=72 -70]{../Work/Testdocument_Grastoets_16-1-0-1825_paraaf.pdf} -\includepdf[pages=3, offset=-72 -70]{../Work/Testdocument_Grastoets_16-1-0-1825_paraaf.pdf} -\includepdf[pages=4, offset=72 -70]{../Work/Testdocument_Grastoets_16-1-0-1825_paraaf.pdf} -\includepdf[pages=5, offset=-72 -70]{../Work/Testdocument_Grastoets_16-1-0-1825_paraaf.pdf} +\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} - - \end{appendices} Index: doc/Work/DSoilModel - Test documenten/Test Document DSoilModel 15.1.1.2.docx =================================================================== diff -u -r153 -r178 Binary files differ Index: doc/Work/DSoilModel - Test documenten/Test Document DSoilModel 15.1.1.1.docx =================================================================== diff -u -r153 -r178 Binary files differ Fisheye: Tag 178 refers to a dead (removed) revision in file `doc/Work/DSoilModel - Test documenten/Test Document DSoilModel 15.2.1.1.pdf'. Fisheye: No comparison available. Pass `N' to diff? Index: doc/Work/DSoilModel - Test documenten/DSoilmodel testdocument 16.1.1.1.xlsx =================================================================== diff -u -r153 -r178 Binary files differ Index: doc/Work/DSoilModel - Test documenten/Test Document DSoilModel 14.1.1.2.docx =================================================================== diff -u -r153 -r178 Binary files differ Index: doc/Work/DSoilModel - Test documenten/Testdocument_DSoilModel_16_1_0_135.pdf =================================================================== diff -u -r177 -r178 Binary files differ