ANSI Library Project
From Deos
Jump to navigationJump to search
Description
The ANSI Library needs some improvements to make it easier for our customers to use, maximize its reuse potential, and to improve the performance of our customer's applications that use this library. This update is occuring in the context of the SLS_Program.
Required Changes
The following updates will be made as part of this effort:
- Convert from Microsoft Portable Executable format to the Electronic Library Format. This will result in a library containing position-independent code, thus reducing customer software integration costs.
- Add the API specification file that is required for the user to easily generate an import library via the makelib utility that is included with the DESK distribution.
- Improve the performance of the memcpy() function. See PCR:4025.
Optional Changes
One or more of the following updates may also be made if time and resources allow:
- Clarify the requirements for the strnicmp() function. See PCR:4060.
- Improve the sprintf() function by eliminating its use of a global variable. See PCR:596.
- Include variable argument macros via stdarg.h for x86. See PCR:595.
- Address review comments from previous certification. See PCR:557.
- Remove unused constants from stdlib.h. See PCR:450.
- Create a user guide. See PCR:416.
- Create a thread-safe strtok() function. See PCR:333.
- Remove leading underscore from the strtold() function. See PCR:234.
- Enhance the CRC routine. See PCR:85.
- Add the snprintf() function. See PCR:3663.
Status
- The library has been converted to ELF format for x86. See PCR:4777.
- The API specification file for the makelib utility has been added to the distribution.
- The snprintf function has been removed. See PCR:4848.
- The performance of the memcpy and memset functions has been improved. See PCR:4025.
Consultants From ALT Software
- Farrukh Qurashi 416 203 8508 x1408
- Liviu Solomon 416 203 8508 x1422
- Kenneth Wenger 416 203 8508 x1453
Tasks
Initial Budget: $47,752
TTD: $68,052
Current ETC: $0
Current EAC: $68,052
| Delivery | Due Date | Estimated Delivery | Delivered | Percentage Complete |
|---|---|---|---|---|
| [1] Certification Candidate Release | 12-Dec-2007 | 31-MAR-2008 | 3-APR-2008 | 100% |
| [2] Software Accomplishment Summary Release | 01-Mar-2008 | 30-APR-2008 | 11-Jun-2008 | 100% |
Delivery [1] Certification Candidate Release
- Feature Description: Sufficient verification steps complete to achieve high confidence executables will not need further changes. This estimate is for required changes only.
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 1.1 Requirements development | N/A | JBR | There is no development here, as all the new features are deferred. The new plan is to convert the existing work DOC file into RTF to be compatible with our trace tag tooling. This will result in a manual comparison of the DOC and RTF versions | 32 | 3 | 3 | 0 |
| 1.2 Code development | N/A | JBR | Resource availability | 32 | 9 | 11 | 0 |
| 1.3 Software life cycle audit #1 | 1.1, 1.2 | Kelly Leonard | None | 16 | 6 | 6 | 0 |
| 1.4 Test case development | [none as there is no content change to the requirements] | Kenneth Wenger | The requirement content is not intended change, so the test cases should not have to change. However, they are in DOC form and need to be converted to HTM, so each one will need to be read by a human to ensure the content is unchanged. Ref PCR:4856 | 32 | 12 | 12 | 0 |
| 1.5 Test procedure development. This task includes getting all the test procedures to build and execute on the reference platforms, and to achieve the expected structural coverage. | 1.1 | JBR, Kenneth Wenger, Gary | Deploying the new test system. | 64 | 173 | 173 | 0 |
| 1.6 Requirements review | 1.1 | Farrukh | 16 | 16 | 16 | 0 | |
| 1.7 Code review | 1.2 | Liviu, Kenneth Wenger | 16 | 34 | 42 | 0 | |
| 1.8 Test case review | 1.5 | Liviu | Resource availability | 16 | 40 | 36 | 0 |
| 1.9 Test procedure review | 1.5 | Liviu Solomon | Resource availability | 67 | 80 | 84 | 0 |
| 1.10 Software life cycle audit #2 | 1.7 | Kelly Leonard | None | 16 | 10 | 10 | 0 |
| 1.11 Train the staff | None | 0 | 80 | 89 | 0 | ||
| 1.12 Build updates | JBR | None | 0 | 32 | 32 | 0 | |
| 1.13 Trace tools and file format conversion | JBR | None | 0 | 37 | 37 | 0 | |
| Totals | 307 | 521 | 500 | 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 | ALT1 | Resource availability | 16 | 16 | 16 | 0 |
| 2.2 Conformity inspection - SQA build Witness | 2.1 | Kelly Leonard | None | 8 | 4 | 4 | 0 |
| 2.3 SCAT/ABC qualification | 1.8, 1.9 | ALT1 | Resource availability | 8 | 8 | 8 | 0 |
| 2.4 Integration review | 2.2, 2.3 | Kelly Leonard | None | 16 | 16 | 16 | 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 | ALT1 | Resource availability | 32 | 32 | 32 | 0 |
| 2.7 Verification audit | 2.6 | Kelly Leonard | None | 8 | 6 | 6 | 0 |
| 2.8 Certification documents: SAS, SLCECI, SCI | 2.6 | ALT2 | Resource availability | 24 | 24 | 24 | 0 |
| 2.9 Population of certification archive (PCA) | 2.8 | ALT2 | Resource availability | 8 | 8 | 8 | 0 |
| 2.10 Software conformity audit | 2.9 | Kelly Leonard | None | 8 | 6 | 6 | 0 |
| 2.11 Additional Audits due to PCRs 5037 and 5059 | 2.9 | Kelly Leonard | None | 0 | 8 | 8 | 0 |
| Totals | 136 | 136 | 136 | 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.
