DC3Schedule: notes-LSST-DC3-updated-08.26.txt

File notes-LSST-DC3-updated-08.26.txt, 9.9 KB (added by cbeldica, 11 years ago)
Line 
1
2
3Greg:
4======
5108. "identify data types to be transmitted"   from    0% to 50% .
6We have implemented a general  scheme for the sharing of Clipboard data,  whereby
71) a  application programmer can mark data as shareable and post it to the Clipboard, after which
82) the data will be transferred prior to the next stage as a (serialized) DataProperty with Boost MPI.
9Thus we can accommodate which ever  data types the developer posts.  The code for the marking/posting
10and the retrieval has been written.  The final code for transmission has not been written as that requires Boost MPI
11and the rest of the new software stack.  Thus, this stands at 50% .
12
13Bill:
14=====
1543 - install and configure initial testing system -- 95% complete; having some connectivity problems with our build server
16208 - Security Document -- 75% complete; basic content is all present; much editing remains
17
18
19Serge:
20=====
21I've been on vacation and have no progress to report.
22
23
24
25Ray:
26====
27DC3 Tasks:
28Task 32:  update software dist. server
29   Status:  underway, behind schedule; completion 85%
30   Activity:  David and I have the package server working with the new
31       DC3 software organization delivering most of the LSST packages.
32       Friendly users are now downloading the stack on CentOS/Red Hat
33       platforms, both 32-bit and 64-bit.
34   Time to Complete: I estimate I need 1 more day to merge eups changes to
35       trunk and readying a review by Robert.
36
37Task 35:  enable support for 64-bit Linux
38   Status:  complete
39   Activity:  64-bit CentOS/Red Hat build routinely.  We have one package
40       that has problems (ip/diffim), but we are passing this problem back
41       to the developers.
42
43Task 85:  policy/data property integration
44   Status:  not started
45   Notes:  recent discussion regarding metadata may have an impact on this
46       task; discussion is underway in various WG telecons.
47
48Task 115:  fault tolerance plan
49   Status:  completed
50Task 116:  fault tolerance plan editing
51   Status:  transfered to KT
52
53Task 120, 121: Orchestration Layer
54   Status:  not started
55
56Other non-DC3 activity:
57   o  worked with B. Baker on reviewing and editing the Security Plan
58        Document.
59   o  worked with C. Cribbs and C. Beldica on update to Infrastructure
60        costing.  We submitted an estimate of floorspace, power, and
61        cooling for the Base Site for Jeff Barr who is working with
62        NOAO in planning for the Base Site building.
63   o  assisted B. Baker with testing platform issues.
64   o  moderated middleware telecons
65
66
67
68DC3 Milestones for Roberta Allsman  25 August 2008
69===================================================
70I updated the completion dates. They are remarkably undefined for the tasks
71which are required by PDR as opposed to those required by DC3. 
72
73The one DC3 task (#15) dependant on a PDR task can be started any time
74since the PDR tasks (#6-14) have progressed to a state where the DC3
75derivative can occur. I'm not saying I'm getting to that task yet since
76I'm personally oversubscribed.
77
78The PDF files of the project plan do not show the continuation pages. Is there
79a way to get those included also?  Or, do you have a simple list of project
80tasks,their start/stop dates and who is assigned to them.
81
82I think it's time to enter the milestones into the trac milestone report. 
83There is NO way (that I've seen) of altering the start- & end- date
84specified so you want to be reasonably comfortable with the plan.  Have the
85Applications Group entered their more comprehensive project data? 
86
87Thanks, Robyn
88
89
90
91PDR & DC3 Milestones for Roberta Allsman  25 August 2008
92===================================================
93
946   SW Quality Assurance
95______________________________________________________________
967   .. Software Quality Assurance: Planning
97______________________________________________________________
988   .... Develop Framework of LSST DM Software Development Process
99______________________________________________________________
1009   ...... Software Quality Assurance (SQA) Plan
101           Draft: Framework is 90% complete
102           Draft: Content is 30% complete
103           Review and Rewrite:
104           PL and CCB Approval:
105           % Complete: 30%
106           New finish date: PDR
107______________________________________________________________
10810  ...... Verification and Validation (V&V) Plan
109                                    (Excludes APP & MW Unit Test Plans)
110           Draft: Plan framework is 90% complete
111           Draft: Content is 30% complete 
112           Review and Rewrite:
113           PL and CCB Approval:
114           % Complete:30%
115           New finish date: PDR
116______________________________________________________________
11711  ...... Configuration Management  (CM) Plan
118           Draft: Plan framework is 90% complete
119           Draft: Content is 60% complete
120           Review then Rewrite:
121           PL and CCB Approval:
122           % Complete: 60%
123           New finish date: PDR
124______________________________________________________________
12512  .... V&V: Tracking Requirements to Tested Product Release
126______________________________________________________________
12713  ...... Std: develop standard labelling scheme for products and their
128           provenance
129           Draft: Policy is 90% complete
130           Review and Rewrite:
131           PL and CCB approval:
132           % Complete: 90%
133           New finish date: PDR
134______________________________________________________________
13514  ...... V&V: define procedure whereby the initial requirements are traced
136           to the validated product
137           Draft: 10%
138           Review and Rewrite:
139           PL and CCB approval:
140           % Complete: 10%
141           New finish date: PDR
142______________________________________________________________
14315  .... Develop DC3 specialization of SQA plans
144           DC3 SQA Draft: 0%
145           DC3 V&V Draft: 0%      depends on completion of Robustness diagrams
146                                        and MW & App Unit Test Plans
147           DC3 CM Draft: 0%
148           % Complete: 0% 
149           New finish date: 2 months before DC3 benchmark testing
150______________________________________________________________
15116  .... Evaluation of commercial or open-source testing tools
152           DELETE THIS ENTRY  it's covered by 19.1 and 20.1
153______________________________________________________________
15417  .... Decision on testing tool
155           DELETE THIS ENTRY  it's covered by 19.2 and 20.2
156______________________________________________________________
15718  .. V&V: Acquire SQA support tools
158______________________________________________________________
15919  .... Configurable tool to perform Lsst software standards checking
160           C++ LSST benchmark test suite packaged (done)
161______________________________________________________________
16219.1  ...... benchmark  ***  being done by Russ Laher IPAC ***
163           C++: Programming Research benchmarked using industry standard RuleSet
164           C++: Abraxis preparing for benchmark: LSST RuleSet being implemented
165           C++: Parasoft solicted for benchmarking
166           python: no options identified
167           % Complete: 30% C++, 0% python
168           New finish date:   This is on a slow track
169______________________________________________________________
17019.2  ...... acquire for widespread use
171           % Complete: 0%
172           New finish date: #19.1 + 30 days
173______________________________________________________________
17420  .... coverage analysis tool
175______________________________________________________________
17620.1  ...... benchmark
177           C++: gcov (open source) 
178           C++: ggcov (open source)
179           python: no option identified
180           % Complete: 0%   
181           New Start date:  after #19.1 completed
182           New finish date:  no one available to integrate into build system
183______________________________________________________________
18420.2  ...... acquire for widespread use
185           % Complete: 0%
186           New finish date: instantaneous after #20.1 (they are pd tools)
187______________________________________________________________
18821  .. V&V: Increased Validation Testing for DC3
189______________________________________________________________
19022  .... Std: specify testing requirements for each phase of Prod development
191______________________________________________________________
19224  ...... unit test: black box, white box, performance tests
193           % Complete: 10%
194           New finish date: 1 month before DC3 benchmark testing
195______________________________________________________________
19625  ...... integration tests: black box, performance, regression
197           % Complete: 10%
198           New finish date: 1 month before DC3 benchmark testing
199_____________________________________________________________
20026  ...... system tests: function, performance, interface, resource, security,
201           portability, reliability, maintainability, safety
202           % Complete: 10%
203           New finish date: 1 month before DC4 completion (not doing DC3)
204______________________________________________________________
20527  ...... acceptance tests: capability and constraint tests
206           % Complete: 10%
207           New finish date: 1 month before DC4 completion (not doing DC3)
208______________________________________________________________
20928  .... Std: specify the pass/fail metrics for each test type
210         (eg compliance levels)
211           % Complete: 0%
212           New finish date: 1 month before DC3 benchmark testing
213______________________________________________________________
21429  .... V&V: Refine workflow process to incorporate additional V & V testing.
215
216           Enhanced Ticket Workflow installed but not yet being appropriately
217           used by developers. Remaining task--writeup corrent Ticket Workflow
218           Process.
219           % Complete: 98%
220           New finish date:  Sept 8
221