Socket Library Project
This effort is in support of the SLS_Program.
Description
The Socket API Library needs some updates to make it easier for our customers to use, maximize its reuse potential, and reduce the risk of improper use that could lead to rework and schedule delays.
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.
- Link against libansi.so and libmtl.so.
- Fix the limitation associated with the FD_CLR macro (used with the select() function) that is documented in the Software Accomplishment Summary. This has been resolved under PCR 4407
- Add an example application to demonstrate the use of the Socket API Library with the Mailbox Transport Library (MTL), and to provide a working MTL configuration file and process template that our customers can use as a starting point in developing their applications.
- 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.
- Update header files to support C language compilation. See PCR 4370.
- Add a document number to the user guide. See PCR 2467.
- Update the library to be network stack-independent.
Optional Changes (i.e., Not part of any estimates -- no time to make things better!)
One or more of the following updates may also be made if time and resources allow:
- Documentation improvements. See PCR 4021.
- Resolve structural coverage deficiencies from previous certification. See PCR 1973.
- Test improvements. See PCR 692.
- Add videostream output to the debug version.
- Convert the documentation to the new XML/Docbook scheme.
Consultants From ALT Software
- Andrei Davidov 416 203 8508 x1432
- Liviu Solomon 416 203 8508 x1422
Tasks
Initial Budget: $38,608
TTD: $40,018
Current ETC: $0
Current EAC: $40,018
| Delivery | Due Date | Estimated Delivery | Delivered | Percentage Complete |
|---|---|---|---|---|
| [1] Certification Candidate Release | 21-Dec-2007 | 19-MAY-2008 | 20-MAY-2008 | 100% |
| [2] Software Accomplishment Summary Release | 01-Mar-2008 | 09-JUN-2008 | 30-May-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.
Note: The estimates below assume the use of an experienced developer that is fully cognizant of the problem domain and processes. Using any other type of resource will likely result in an estimate 2x to 3x higher.
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 1.1 Requirements development (XML'ify, add doc number) | JBR | 24 | 24 | 17 | 0 | ||
| 1.2 Code development Address structural coverage holes from previous cert PCR:1973 | JBR, kindorf | 48 | 41 | 57 | 0 | ||
| 1.3 Software life cycle audit #1 | 1.1, 1.2 | Kelly Leonard | None | 8 | 8 | 8 | 0 |
| 1.4 Test case development. Although there are no new requirements (and therefore no new test cases), analysis should be done to evaluate the need for more tests | 1.1 | Resource availability | 16 | 16 | 16 | 0 | |
| 1.5 Test procedure development. 1.4 may cause work on this step. The remainder of the task is for resurrecting the test harness. | 1.1 | Andrei, Gary | 32 | 163 | 172 | 0 | |
| 1.6 Requirements review | 1.1 | Yong Zhang Kenneth Wenger | Resource availability | 8 | 8 | 24 | 0 |
| 1.7 Code review | 1.2 | Yong Zhang | Resource availability | 8 | 8 | 10 | 0 |
| 1.8 Test case review | 1.5 | Liviu Solomon | Resource availability | 4 | 4 | 45 | 0 |
| 1.9 Test procedure review | 1.5 | Liviu Solomon | Resource availability | 4 | 4 | 17 | 0 |
| 1.10 Software life cycle audit #2 | 1.7 | Resource availability | 16 | 16 | 8 | 0 | |
| Totals | 168 | 275 | 327 | 0 | |||
Delivery [2] Software Accomplishment Summary Release
- Feature Description: Indicates all verification steps complete.
Note: The estimates below assume the use of an experienced developer that is fully cognizant of the problem domain and processes. Using any other type of resource will likely result in an estimate 2x to 3x higher.
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 2.1 Requirements coverage analysis | 1.2 | Resource availability | 16 | 16 | 8 | 0 | |
| 2.2 Conformity inspection - SQA build Witness | 2.1 | Kelly Leonard | None | 8 | 6 | 6 | 0 |
| 2.3 SCAT/ABC qualification (v4.2.0 is PPC only) | N/A | Resource availability | 8 | 8 | 4 | 0 | |
| 2.4 Integration review | 2.2, 2.3 | Kelly Leonard | None | 16 | 16 | 6 | 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 | Resource availability | 32 | 32 | 2 | 0 | |
| 2.7 Verification audit | 2.6 | Kelly Leonard | None | 8 | 8 | 4 | 0 |
| 2.8 Certification documents: SAS, SLCECI, SCI | 2.6 | Resource availability | 24 | 24 | 4 | 0 | |
| 2.9 Population of certification archive (PCA) | 2.8 | Resource availability | 8 | 8 | 1 | 0 | |
| 2.10 Software conformity audit | 2.9 | Kelly Leonard | None | 8 | 8 | 4 | 0 |
| Totals | 136 | 134 | 47 | 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.
