Math Library Project
From Deos
Jump to navigationJump to search
Description
Traces examined during SOI 2 revealed several defects through Math Library software life cycle data that must be addressed. While this update is occuring in the context of the SLS_Program, re-use funds will be used to cover the work.
Required Changes
- Examine Math Library software life cycle data to determine the scope of the effort. Estimate below assumes same realative size as the ANSI Library Project.
- Fix call fegetenv() or fesetenv() in x86 GNUC - See PCR:4695.
Optional Changes
- Any of the open PCRs
Tasks
Initial Budget: $49,784
TTD: $96,674
Current ETC: $14,552
Current EAC: $111,226
| Delivery | Due Date | Estimated Delivery | Delivered | Percentage Complete |
|---|---|---|---|---|
| [1] Certification Candidate Release | 01-Mar-08 | 06-Jun-08 | 09-JUN-08 | 100% |
| [2] Software Accomplishment Summary Release | 01-Mar-08 | 23-JUN-08 | 02-JUL-08 | 100% |
Delivery [1] Certification Candidate Release
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 1.1 [1] Requirements development. The task here is to convert the existing word DOC into RTF format so that it can be parsed by our tracing tools. x86 PCR is PCR:4952 | N/A | Kenneth Wenger | Resource availability | 32 | 32 | 8 | 0 |
| 1.1a As described at the top of this wiki, this component has failed a tracability audit. There is specifically no additional data so as to not mislead the effort. What needs to get is...for each requirement, search the code for traces to the requirement and ensure the associated code is logical. Then search the test case documents to ensure the description for how the requirement is to be tested is logical. Then compare the test procedure code against the test case to ensure the test procedure implements the test case objectives. Several problems are known to exist, so this activity must yield some changes. | 1.1 | Andrei Davidov Yong Zhang, Kenneth Wenger | 0 | 162 | 174 | 0 | |
| 1.2 Code development | N/A | Kenneth Wenger, Yong Zhang | Resource availability | 32 | 58.5 | 335.5 | 0 |
| 1.4 Test case development | 1.1 | Kenneth Wenger Yong Zhang | Resource availability | 32 | 32 | 32 | 0 |
| 1.5 Test procedure development | 1.1 | Kenneth Wenger, JBR, Gary, Andrei Davidov, Yong Zhang | Resource availability | 64 | 130 | 174 | 0 |
| 1.6 Requirements review | 1.1 | Liviu Solomon | Resource availability | 16 | 16 | 5 | 0 |
| 1.7 Code review | 1.2 | Liviu Solomon, Kenneth Wenger | Resource availability | 16 | 40 | 80 | 0 |
| 1.8 Test case review | 1.4, 1.6 | Liviu Solomon | Resource availability | 8 | 64 | 64 | 0 |
| 1.9 Test procedure review | 1.5 | Liviu Solomon | Resource availability | 8 | 25 | 83 | 0 |
| 1.10 Software life cycle audit | 1.7 | Kelly Leonard | None | 16 | 16 | 16 | 0 |
| Totals | 240 | 555.5 | 887.5 | 0 | |||
Delivery [2] Software Accomplishment Summary Release
- Feature Description: Indicates all verification steps complete.
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 2.1 Requirements coverage analysis | 1.6, 1.7, 1.8, 1.9 | gary kindorf | 16 | 16 | 8 | 0 | |
| 2.2 Conformity inspection - SQA build Witness | 2.1 | Kelly Leonard | None | 8 | 8 | 8 | 0 |
| 2.3 SCAT/ABC qualification (v4.2.0 is PPC only) | 1.8, 1.9 | kindorf | 8 | 8 | 8 | 0 | |
| 2.4 Integration review | 2.2, 2.3 | kindorf | None | 16 | 16 | 9.5 | 0 |
| 2.5 Run for score, including SQA witnessing, and test results review | 2.4 | Kelly Leonard | Resource availability | 8 | 8 | 8 | 0 |
| 2.6 Structural coverage analysis | 2.5 | kindorf | 32 | 32 | 20 | 0 | |
| 2.7 Verification audit | 2.6 | Kelly Leonard | None | 8 | 8 | 4 | 0 |
| 2.8 Certification documents: SAS, SLCECI, SCI | 2.6 | kindorf | Resource availability | 24 | 24 | 14 | 0 |
| 2.9 Population of certification archive (PCA) | 2.8 | kindorf | Resource availability | 8 | 8 | 8 | 0 |
| 2.10 Software conformity audit | 2.9 | Kelly Leonard | None | 8 | 8 | 4 | 0 |
| Totals | 136 | 136 | 99.5 | 0 | |||
Standards
All SQA activities will be performed in compliance with: Plan for Software Aspects of Certification for Deos, DEOSDOC1 as well as all documents it references.
Organizational Responsibilities
Honeywell Responsibilities
Provide project coordination within Honeywell between departments and between Honeywell and ALT Software.
Software Configuration Management
- Maintain Configuration Management.
- Maintain and Archive software requirements documents, and other associated SLCD.
- The Honeywell Technical Lead will be responsible for this activity.
Honeywell Quality Assurance
- The SQA Focal will perform the required audits as per the Software Quality Assurance Plan for Deos, DEOSDOC4.
- The deliverables will consist of the aforementioned SLCD.
Honeywell Program Management Responsibilities
The work responsibilities of Honeywell Program Management are as follows:
- Facilitate the authorization of statements of work and quotes
- Facilitate changes to statements of work
- Provide purchase orders and payment authorization
ALT Software Responsibilities
- ALT Software will provide status to Honeywell upon request.
- Progress report should be submitted to Honeywell Technical Lead at a rate to be determined by said lead.
Note: above progress should be measured against incremental, achievable tasks rather than percentage complete. Progress reports will consist of the statement that we completed a given task, didn't complete a given task (and what we will do to mitigate), or the task has changed.
