CMU MK II Boot Project
From Deos
Jump to navigationJump to search
Provide a fully functional and verified Boot as a means to support the CMU_MK_II_Program.
Description
Develop a DO-178B level A Boot for the MPC8270 prcessor on the CMU MKII platform.
Boot is a free standing component required in a system which utilizes Deos™. The purpose of Boot is to initialize the platform hardware, interact with the Deos™, and (optionally) respond to loss of power. In a desktop computing environment, this kind of software is referred to as the Basic Input/Output System (BIOS). In effect Boot is a BIOS for running Deos™.
The effort tracked on this page is covered in/by the following:
Meeting Minutes: CMU Boot Project Meeting Minutes
Status
| Milestones | Due Date | Estimated Delivery | Delivered | Percentage Complete |
|---|---|---|---|---|
| [1] Full Functionality Release | 15-Dec-08 | 15-Dec-08 | 15-Dec-08 | 100% |
| [1a] Reset Button Release | 23-Jan-09 | 22-Jan-09 | 22-Jan-09 | 100% |
| [1b] Bad Image Release | 27-Feb-09 | 27-Feb-09 | 27-Feb-09 | 100% |
| [1c] Power Interrupt Release | 30-Mar-09 | 26-Mar-09 | 26-Mar-09 | 100% |
| [2] Certification Candidate Release | 08-Jun-09 | 08-Jun-09 | 08-Jun-09 | 100% |
| [3] Verified Release | 29-Jun-09 | 29-Jun-09 | 29-Jun-09 | 100% |
Tasks for Milestone [1] Full Functionality Release
| Task | Dependency | Assignee | Risk | Original Estimate | Elapsed | Remaining | Est. End Date |
|---|---|---|---|---|---|---|---|
| 1.0 Program Kick-off (e.g., euipment set-up, etc.) | None | Eli,Bill,Rob | None | 60 | 75 | 0 | 26-Nov-08 |
| 1.1 PODRC & PODRD Initialization | None | Eli | None | 8 | 8 | 0 | 14-Nov-08 |
| 1.2 Machine Check Interrupt Functionality | None | Eli | None | 28 | 34 | 0 | 12-Dec-08 |
| 1.3 Store RTC &TP02J During Power-Down | None | Eli | None | 8 | 31 | 0 | 12-Dec-08 |
| 1.4 Handling of OOOI State | None | Rob | None | 28 | 37 | 0 | 04-Dec-08 |
| 1.5 Complete Requirements Development | None | Rob,Eli | None | 16 | 18 | 0 | 15-Dec-08 |
| 1.6 Ensure Warm-start, WDT & Full Functionality | 1.1 - 1.5 | Rob,Eli | None | 32 | 84 | 0 | 12-Dec-08 |
| 1.7 Full Functionality Release | 1.6 | Rob | None | 8 | 23 | 0 | 15-Dec-08 |
| Totals | 188 | 307 | 0 | 15-Dec-08 | |||
Tasks for Milestone [1a] Reset Button Release
| Task | Dependency | Assignee | Risk | Original Estimate | Elapsed | Remaining | Est. End Date |
|---|---|---|---|---|---|---|---|
| 1a.1 Reset Button Logic | None | Rob | None | 16 | 7 | 0 | 19-Jan-09 |
| 1a.2 Complete Requirements Development | None | Rob | None | 8 | 7 | 0 | 20-Jan-09 |
| 1a.3 Ensure 1a.1 Functionality | 1a.1 | Eli,Rob | None | 12 | 12 | 0 | 20-Jan-09 |
| 1a.4 Integration Testing w/PAL | 1a.3 | Eli,Rob | None | 16 | 8 | 0 | 21-Jan-09 |
| 1a.5 Reset Button Release | 1a.4 | Rob | None | 8 | 8 | 0 | 22-Jan-09 |
| Totals | 60 | 41 | 0 | 22-Jan-09 | |||
Tasks for Milestone [1b] Bad Image Release
| Task | Dependency | Assignee | Risk | Original Estimate | Elapsed | Remaining | Est. End Date |
|---|---|---|---|---|---|---|---|
| 1b.1 Complete Documentation Updates | None | Rob | None | 14 | 16 | 0 | 25-Feb-09 |
| 1b.2 Bad Image & Warmstart Updates | None | Rob | None | 14 | 7 | 0 | 26-Feb-09 |
| 1b.3 Ensure 1b.2 Functionality | 1b.1 | Eli,Rob | None | 12 | 5 | 0 | 27-Feb-09 |
| 1b.4 Integration Testing w/PAL | 1b.3 | Eli,Rob | None | 16 | 0 | 0 | N/A |
| 1b.5 Bad Image Release | 1b.4 | Eli,Rob | None | 10 | 4 | 0 | 27-Feb-09 |
| Totals | 66 | 31 | 0 | 27-Feb-09 | |||
Tasks for Milestone [1c] Power Interrupt Release
| Task | Dependency | Assignee | Risk | Original Estimate | Elapsed | Remaining | Est. End Date |
|---|---|---|---|---|---|---|---|
| 1c.1 Power Interrupt Release | None | Rob | None | 0 | 9 | 0 | 26-Mar-09 |
| Totals | 0 | 9 | 0 | 26-Mar-09 | |||
Tasks for Milestone [2] Certification Candidate Release
| Task | Dependency | Assignee | Risk | Original Estimate | Elapsed | Remaining | Est. End Date |
|---|---|---|---|---|---|---|---|
| 2.0 Add Resource | None | Eli,Rob,Shannon | None | 32 | 32 | 0 | 19-Jan-09 |
| 2.1a Requirements Development | None | Gary | None | 52 | 47 | 0 | 20-Mar-09 |
| 2.1 Requirements review | 1.5 | Bill | None | 140 | 163 | 0 | 22-May-09 |
| 2.2a Code Development | None | Gary | None | 12 | 4 | 0 | 20-May-09 |
| 2.2 Code review | 2.1 | Bill | None | 185 | 181 | 0 | 22-May-09 |
| 2.3 Test Case Development | 1.5 | Bill | None | 190 | 87 | 0 | 01-Jun-09 |
| 2.4 Test Case Review | 2.1,2.3 | Gary | None | 118 | 79 | 0 | 01-Jun-09 |
| 2.5 Test Procedure Development | 1.5 | Gary, Bill | None | 460 | 971 | 0 | 07-Jun-09 |
| 2.6 Software life cycle audit #2 | 2.4 | Kelly | None | 24 | 10 | 0 | 18-May-09 |
| 2.7 Test Procedure Review | 2.4,2.5 | Gary,Bill,Matt | None | 220 | 262 | 0 | 08-Jun-09 |
| 2.8 Certification Candidate Release | 2.7 | Bill | None | 8 | 5 | 0 | 08-Jun-09 |
| Totals | 1441 | 1839 | 0 | 08-Jun-09 | |||
Tasks for Milestone [3] Verified Release
| Task | Dependency | Assignee | Risk | Original Estimate | Elapsed | Remaining | Est. End Date |
|---|---|---|---|---|---|---|---|
| 3.1 Software life cycle audit #3 | 2.8 | Kelly | None | 24 | 8 | 0 | 14-Jun-09 |
| 3.2 Requirements coverage analysis | 2.4 | Gary | None | 10 | 5 | 0 | 12-Jun-09 |
| 3.3 Document Update Analysis | None | Gary | See Below | 26 | 1 | 0 | 15-Jun-09 |
| 3.4 Conformity inspection - SQA build Witness | 2.8, 3.2 | Gary, Kelly | None | 12 | 4 | 0 | 16-Jun-09 |
| 3.5 SCAT/ABC qualification | 3.4 | Gary | None | 10 | 5 | 0 | 17-Jun-09 |
| 3.6 Integration review | 3.4 | Gary, Kelly | None | 10 | 5 | 0 | 18-Jun-09 |
| 3.7 Run for score, including SQA witnessing, and test results review | 3.6 | Gary, Kelly | None | 10 | 14 | 0 | 19-Jun-09 |
| 3.8 Structural coverage analysis | 3.7 | Bill | None | 10 | 30 | 0 | 20-Jun-09 |
| 3.9 Verification audit | 3.8 | Kelly | None | 10 | 7 | 0 | 23-Jun-09 |
| 3.10 SAS, SLCECI, SCI | 3.8 | Matt | None | 44 | 34 | 0 | 26-Jun-09 |
| 3.11 Population of certification archive (PCA) | 3.10 | Matt | None | 10 | 4 | 0 | 27-Jun-09 |
| 3.12 Software conformity audit | 3.11 | Kelly | None | 10 | 4 | 0 | 29-Jun-09 |
| Totals | 186 | 121 | 0 | 29-Jun-09 | |||
Risks
Need Final Documentation
Reviews of the Boot artifacts are procedding at risk. Typically, the HRD would be in its final release form before reviews. This task will assess deltas between the documentation uised during review and the final HRD. The schedule above assumes no impact from such an analysis.
Resolved
Documents used (and their revisions) are in CM and referenced by material under review and/or review packets themselves.
