Time-PRL Jupiter
Time-prl verification for ARM, PPC and X86 using multicore.
Component has been Deprecated -- See Time_Jupiter
A DAL A project.
This page tracks development and verification activities and progress.
Useful Links
- Query of all outstanding PCRs
- Query of open Rqts/Code PCRs (PCRs with requirements/code work assigned).
- Query of open test PCRs (PCRs with test work assigned).
- mainline review status
Scope
Time-prl is a new component which is supporting the time component as a process resource library gaining access to Deos system time via the target board's PAL. All the qemus' PALs support this, and also many newer boards,
The time-prl component requires the calling process to be privileged to modify the time-prl information, and this is done with xml-additions for the calling process.
Activities
Outstanding Requirement Tasks
- None. Requirements document for time-prl has been created.
Status file for Requirements, Code and Test have been created.
Outstanding Code Tasks
- None. Code completed
Outstanding Test Tasks
- The creation of test cases and following the test procedures.
4 ad hoc test programs exist which can be used as basis for the to-be-developed test cases/procedures.
| Requirements Development | TBR | Done |
| Standards Change Analysis | TBD | No |
| Initialize Status Files | TBR | Done |
| Requirements review | MAS | Done |
| Code Development, i.e. trace tag insertion and additional test points as determined via test development. | TBR | Done |
| Code review | MAS | In Work |
| Test Case Development | MAS | In Work |
| Test Procedure Development | DED | No |
| Test Reviews | DED/MAS | No |
| Software life cycle audits | SQA | No |
| ABC SCAT Qual | TBR | No |
| Before the following can be done the above activities must be complete | ||
|---|---|---|
| Integration Review | TBR/JEC | No |
| Before the following can be done the Requirements Coverage analysis' traceability needs to be confirmed and SCAT Qual need to be completed | ||
| Formal build (including Conformity inspection) | TBR/JEC | No |
| Before the following can be done the Formal build needs to be completed. Each executable object code analysis has an analysis and review task. | ||
| Executable Object Code Analysis (Testing vs Release variant equivalence) | ||
| Executable Object Code Analysis Review (Testing vs Release variant equivalence) | ||
| Requirements Coverage Analysis | TBR | No |
| Before the following can be completed all of the above analysis need to be completed. The RFS was completed with the expectation the analysis above will be successful. | ||
| Run For Score | TBR | No |
| Test Results Review | ? | No |
| Before the following can be done the Run For Score needs to be completed | ||
| Structural coverage analysis | TBR | No |
| Verification audit | JEC | No |
| Before the following can be completed all of the above tasks need to be completed | ||
| Report Documents | ||
| - SLCECI | JON? | Not Started |
| - SLCECI review | TBD | Not Started |
| - SCI | JON? | Not Started |
| - SCI review | TBD | Not Started |
| - Open Problem Reports List | JON? | Not Started |
| - SAS | JON? | Not Started |
| - SAS review | TBD | Not Started |
| Populate the cert archive | JON? | Not Started |
| Software conformity audit | JEC | Not Started |
