1. 14 Data Analysis Document Status for LISA Pathfinder N. Tateo 20/02/2007

2. 14 1 Current status The current status of document writing is consistent with the LTP Science Implementation Plan (SIP):

3. 14 2 Time planning The time planning is similarly consistent:

4. 14 3 DA Requirement Document The DA Requirement Document has been delivered (Iss.1.0). Latest evolvement in DA, including consequences of previous meetings, can be implemented in a revised issue.

5. 14 4 DA Design Document The DA Design Document, not issued yet, is ready and contains the S/W architecture as stated in the LTP SIP. It’s a review of the DA topics discussed so far, plus the definition of science data channels to be analyzed.

6. 14 5 Da Design Document While it contains a preliminary definition of the Quick-Look Analysis tool (QLA) and the definition of the GUI to be implemented, it’s still lacking the summary elements description, i.e. the concise and defined examination of algorithms and functions to be enclosed into each package. This part is now intended to be included in the “Software Requirement Document”.

7. 14 6 How many documents? In the latest meetings and following communications different documents were mentioned: User Requirement Document (URD). Software Requirement Document (SRD). Implementation Plan (IP). Architecture Document (AD). Given that the DA Architecture is already covered by the DA Design Document, remains to be clarified the content of the AD.

8. 14 7 User Requirement Document About the URD, the LISA Pathfinder Science Implementation Plan (LPF SIP) states: Is there another URD?

9. 14 8 Software Requirement Document It’s also stated that the Operations Scientist (ESA) will support the writing of Software Requirement Document:

10. 14 9 Software Requirement Document Supporting who? The definition of the necessary tools to be developed, now intended to converge in the SRD, according to the LPF SIP should be issued by the Project Scientist: What kind of “inputs from the LTP PI Team”?

11. 14 10 Software Requirement Document In the LPF SIP there is also: What exactly are the “STOC Work Packages”?

12. 14 11 Implementation Plan The Implementation Plan (IP) should describe “how, by whom and when this S/W development is going to take place”. Who’s responsible for its writing, and by when it’s intended to be delivered?

13. 14 12 Documents summary ContentIntendedProposedStatus DA RequirementsDA Requirement Document Issued QL RequirementsQL Requirement Document DA S/W ArchitectureArchitecture Document ? DA Design DocumentDraft Data definitionDA Design Document Quick-Look AnalysisQL Design Document ImplementationImplementation Plan DA Summary Elements Description DA Design Document Software Requirement Document To be written QL Summary Elements Description QL Design Document

14. 14 13 Questions to be solved 1.What kind of document, and which contents must precisely have the Software Requirement Document? 2.Who’s going to write the summary analysis elements description, i.e. the precise definition of sub-functions and algorithms to be included in each package? 3.If the SRD is responsibility of ESA “with inputs from LTP PI Team”, which kind of inputs? 4.By when is intended to be delivered the SRD?

15. 14 Questions to be solved 5.The Implementation Plan must be a standalone document, or can be incorporated into the DA Design Document? And the Architecture Document? 6.By when are to be delivered the IP and the AD? 7.How to distribute the future work, among actual analysis functions programming and document writing? 8.The last mail (Texier, 09/02/2007) noted that “the URD is already in good shape”, against what stated by the LPF SIP (“no URD will be written”).