First version

abstract.tex

@@ -1,10 +1,12 @@
 
 \begin{abstract}
-The Vera C. Rubin Observatory Data Management (DM), in the context of the Legacy Survey of Space and Time (LSST), is responsible for creating the software, services, and systems that will be used to produce science-ready data products.
+The Data Management (DM) subsystem of the Vera C. Rubin Observatory Legacy Survey of Space and Time (LSST) is responsible for creating the software, services, and systems that will be used to produce science-ready data products.
 The software, currently under development is heterogeneous, comprising both C++ and Python components, and is designed to facilitate both the processing of the observatory images and to enable value-added contributions from the broader scientific community.
 Verification and validation of these software products, services, and systems is an essential yet time-consuming task.
 
-In this paper, we present the tooling and procedures used in the preparation of the LSST, for a systematic verification and validation documentation approach. 
+% Come back to this ensure the production of the documentation for V&V in a systematic way.
+In this paper, we present the tooling and procedures used in the preparation of  documentation, for a systematic verification and validation documentation approach.
+
 By adopting a systematic approach, we guarantee full traceability to system requirements, integration with the project’s System Engineering model, and substantially reduce the time required for the whole process.
 \end{abstract}
 

body.tex

@@ -21,7 +21,7 @@ \section{Introduction}
 produce verification and validation documentation, and its integration with the project's System Engineering model, 
 see \cite{10.1117/12.2310125} , ensures full traceability to system requirements.
 
-
+% Should this be moved to after?
 \section{The Documentation Process}
 
 In the scope of Verification and Validation, documents are written using \LaTeX and considered as source code.
@@ -31,7 +31,24 @@ \section{The Documentation Process}
 Using the GitHub \textbf{Pull Request}, it is easy to drive formal reviews, keeping the right contributors informed,
 and ensuring that changes are agreed.
 
+% This is what wraps the information from Jira and puts it in a document 
+% Add the link to the github repo and 
+Docsteady has been developed in-house by LSST DM to address this problem. Expand on this and explain why 
+we developed this. 
+
+
+% Moving this here because this is part of the problem to be solved. The documentation process is part of the solution
+% make this secion smaller and explain the problem andcontext 
+
+% Describe a here a general V&V approach, explain our requirements documents and how they are flowed down from the SRD. DM is responsible to verify requirements that are re
+
+% Leanne to add the graphics from talks and LDM-XXX on the document flowdown. (maybe just the high one) 
+% DM verifies require,ents in DMSR 
+% maybe have a flow down to lower documents
+
+% How do we systematically document the verufication of all the reqirements in this picture in an automated way. 
 
+% GCM to draft a schematic of the approach 
 \section{The Verification and Validation}
 
 The verification and validation approach as illustrated in \cite{10.1117/12.2310125} , has been implemented.
@@ -184,7 +201,7 @@ \subsubsection{Verification Elements Baseline}
 Approved versions are uploaded in Docushare and used as a reference in other test documents.
 
 
-\section{Information Summary and Control Document}
+\section{Information Summary and the Verification Control Document}
 
 As it has been described in the above section, all Rubin Observatory test information is managed in Jira. 
 This permits to extract very easily the Verification Control Document (VCD), that shows the level of coverage for each requirement.