Mailbox Transport Library Project
This effort is in support of the SLS_Program.
Description
The Mailbox Transport Library needs some updates to make it easier for our SLS_Program customers to use, maximize its reuse potential, and to 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:
- Link against the updated ANSI Library that has been converted to Electronic Library Format.
- Add an example application to demonstrate the use of 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.
- Add a document number to the user guide. See PCR 2466.
- Fix tracing problems. For each requirement in the requirements document
- read the requirement
- find that requirement in the code file(s), and ensure the tracing is "logical" or reasonable using your engineering judgement.
- find that requirement in the test case document, and ensure the tests described in the test case document are logically related.
Optional Changes
One or more of the following updates may also be made if time and resources allow:
- Address structural coverage issues from previous certification. See PCR 2007.
- Address test review issues from previous certification. See PCR 1700.
- Convert the documentation to the new XML/Docbook scheme.
- Add videostream output to the debug version.
Tasks
Initial Budget: $46,736
TTD: $49,113
Current ETC: $963
Current EAC: $50,076
| Delivery | Due Date | Estimated Delivery | Delivered | Percentage Complete |
|---|---|---|---|---|
| [1] Certification Candidate Release | 21-Dec-07 | 24-MAR-08 | 24-MAR-08 | 100% |
| [2] Software Accomplishment Summary Release | 31-Mar-08 | 21-APR-08 | 11-JUN-08 | 100% |
For milestone [1], the delivery date is derived by assuming the tasks are 70% serialized (total effort * .7)
For milestone [2], the delivery date is derived by assuming the tasks are 100% serialized
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 that due to the limited life-cycle data changes, not all DO-178B activities will need to be performed. Only those activities needed are listed.
| Task | Dependency | Assignee | Risk | Original Estimate | Current Estimate | Elapsed | Remaining |
|---|---|---|---|---|---|---|---|
| 1.1 Requirements / User Guide change: Add a document number to the user guide. SGML-to-XMLPCR 2466 | N/A | SPS | None | 32 | 13 | 13 | 0 |
| 1.2 Requirements review | 1.1 | Yong Zhang | Resource availability | 32 | 32 | 32 | 0 |
| 1.3 Software life cycle audit #1 | 1.2 | Kelly Leonard | None | 8 | 8 | 8 | 0 |
| 1.4 Test case development Test cases should be modified to resolve the defects found in PCR:2007 Additionally, this task includes the a traceability analysis as described at the top of this wiki under the required changes. | 1.1 | Andrei Davidov | Resource availability | 32 | 48 | 48 | 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.4 | 64 | 94 | 94 | 0 | ||
| 1.7 Code review | 1.2 | Yong Zhang | Resource availability | 16 | 20 | 20 | 0 |
| 1.8 Test case review | 1.5 | Yong Zhang, Liviu Solomon | Resource availability | 8 | 8 | 12 | 0 |
| 1.9 Test procedure review | 1.5 | Yong Zhang Andrei Davidov, LS | Resource availability | 8 | 40 | 43 | 0 |
| 1.10 Software life cycle audit #2 | 1.7 | Kelly Leonard | None | 16 | 8 | 8 | 0 |
| 1.11 Training the Staff | None | 0 | 80 | 71 | 9 | ||
| Totals | 216 | 351 | 342 | 9 | |||
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.2 | Resource availability | 16 | 16 | 13 | 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 | 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 | Resource availability | 32 | 32 | 23 | 0 | |
| 2.7 Verification audit | 2.6 | Kelly Leonard | None | 8 | 5 | 5 | 0 |
| 2.8 Certification documents: SAS, SLCECI, SCI | 2.6 | Resource availability | 24 | 24 | 24 | 0 | |
| 2.9 Population of certification archive (PCA) | 2.8 | Resource availability | 8 | 8 | 6 | 0 | |
| 2.10 Software conformity audit | 2.9 | Kelly Leonard | None | 8 | 8 | 8 | 0 |
| Totals | 136 | 131 | 117 | 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.
