Kernel 7.2.x Verification Project
Support Honeywell in the verification of the 7.2.x Version of the Deos Kernel.
Description
Honeywell as requested our assistance as described in the tasks below. Our efforts are combined with their efforts, documented on the Honeywell Kernel Project Page, in order to complete Deos Kernel 7.2.x verification.
This project requires the following expertise:
- Deos kernel and API
- Deos Verification Processes
Status
| Milestones | Due Date | Estimated Delivery | Delivered | Percentage Complete |
|---|---|---|---|---|
| [2a] Certification Candidate 2 | 16-Feb-09 | 16-Feb-09 | TBD | 38% |
| [2b] Tests complete | 03-Mar-09 | 02-Mar-09 | TBD | 4% |
| [3] Software Accomplishments Summary Release | 09-Apr-09 | 01-Apr-09 | TBD | 0% |
20090119: From John Kimball:
Re asking for volunteers: All the bodies on the HI side are already assigned to programs more or less full time, with pretty limited flexibility. So I don't expect there will be much volunteering from over here.
Re nagging folks: That would be fine. Paul has been stepping thru the list of folks with PCRs weekly at the kernel meeting, but some in-between attention from someone who has a much deeper understanding of what the PCRs involve would be useful.
[2a] Certification Candidate 2
| Task | Dependency | Assignee | Original Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|
| [2a.6] Address any problems turned up in informal run of testsuite. | None | MD, BC | 49 | 4 | 0 |
| [2a.7] Finish requirements/code PCRs | None | MD, BC | 109 | 68 | 0 |
| [2a.8] Finish requirements/code reviews | 2a.6 & 2a.7 | MD, BC | 58 | 0 | 58 |
| [2a.9] Do kernel release activities | 2a.8 | MD, BC | 35 | 0 | 35 |
| [2a.10] Complete the processor & errata analysis | 2a.8 | RR | 26 | 0 | 26 |
| Totals | 277 | 72 | 119 | ||
[2b] Tests complete
| Task | Dependency | Assignee | Original Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|
| [2b.1] Merge test changes and test reviews from Agave to mainline. | None | MD, BC | 16 | 0 | 24 |
| [2b.2] Finish test PCRs. | 2b.1 | MD, BC | 100 | 5 | 95 |
| [2b.3] Finish post-8270 test reviews. | 2b.2 | MD, BC | 20 | 0 | 20 |
| Totals | 136 | 5 | 139 | ||
[3] Software Accomplishments Summary Release
| Task | Dependency | Assignee | Original Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|
| C.0 B-Tree Analysis | 2b.3 | MD, BC | 32 | 0 | 32 |
| C.2 Portal Analysis | 2b.3 | MD, BC | 8 | 0 | 8 |
| C.4 Conformity inspection - SQA build Witness | 2b.3 | MD, BC | 8 | 0 | 8 |
C.7.2 603e Run for score, including SQA witnessing, and test results review
|
C.6 | MD, BC | 4 | 0 | 4 |
| C.8.1 PPC Structural coverage analysis | C.7.1-C.7.3 | MD, BC | 60 | 0 | 60 |
| C.8.2 X86 Structural coverage analysis | C.7.4,C.7.5, & C.8.1 | MD, BC | 40 | 0 | 40 |
| C.10 SAS, SLCECI, SCI | C.9 | MD, BC | 40 | 0 | 40 |
| C.11 Population of certification archive (PCA) | C.10 | MD, BC | 8 | 0 | 8 |
| Totals | 200 | 0 | 200 | ||
Risks
The total number of hours listed above (i.e., 613) does not match the PO amount. DDC-I will stop work once we have reach 428 hours (the amount in the PO) unless the discrepancy is resolved (e.g., DDC-I work scope decreased, Honeywell PO increased, etc.).
