The second meeting of the working group was held on July 07 and 08, 1999 at the New York City Transit Offices in Brooklyn, NY.
The agenda was accepted as distributed.
The meeting 01 minutes from April 30, 1999 were distributed and no corrections were made. Thomas Tougas moved and Kenneth Teu seconded the motion to approve the minutes. The minutes were approved by voice vote.
The proposed wording was reviewed. The scope was revised to indicate that the process is an integral part of the documentation development. The scope and purpose will also address the test and maintenance equipment that incorporates software.
The revised scope and purpose is attached to these minutes. Document: sw scope purpose 02.
Information developed by Leroy Denney was distributed and discussed.
Information provided by Bombardier was distributed for further review.
Information developed by Kawasaki was discussed in detail regarding the applicability as documentation deliverables.
There are several possibilities of software categorization based on the end user needs. These needs include operations only, parameter modification and maintenance/modification.
The process and documentation were broken down into phases with a status regarding whether the document is required [RQD], recommended [REC] or not required [NR] determined. The table is attached.
Full Committee Recommendations
Proceed with scope and purpose for agreement of the full committee.
Develop a tiered approach to documentation based upon end user requirements for understanding, parameter modification and full support.
Establish core terminology that does not exist in the IEEE Dictionary.
Documents must be applicable to PTE and BTE applications.
Develop template recommendations for each software document based on IEEE/ISO standards.
1. Review scope and purpose with full committee and prepare PAR. Paul Jamieson
2. Identify contract, equipment and procurement types that delineate the process and documents needed. John Corvin and Sophia Georgiadis
3. Define these terms: software configurable item, firmware configurable item, hardware configurable item, critical, safety critical and functional critical. Eldridge Mount
4. Review standards 829 and J Std 016. Define the testing requirements for validation. Dave Falkenberg and Shantilal Morar
5. Define the requirements for version description and support documents. Chris Pacher and Tom Tougas
6. Expand the existing tables based on the meeting discussions. Leroy Denney
The next meeting will be held on September 23 and24, 1999 at the LTK offices 317 Madison Avenue, Suite 1621, New York, NY. The Thursday meeting will start at 9:30AM. An agenda will be distributed prior to the meeting.
Provide information on local hotels. Chris
Pacher
sw mtg 02.doc
Process and Documentation Table
Status |
ID |
Description |
Comments |
|
|
|
Planning |
|
|
RQD |
SPMP |
Software Project Management Plan |
Integrator’s responsibility |
|
RQD |
SDP |
Software Development Plan |
Suppliers responsibility |
|
|
SPIP |
Software Process Improvement Plan |
Minimum one required per system |
|
REC |
SCE Findings |
Software Compatibility Evaluation Findings |
Various audit types acceptable |
|
REC |
SRE Report |
Software Risk Evaluation Report |
|
|
|
|
Management |
|
|
RQD |
SQAP |
Software Quality Assurance Plan |
Can be integrated as part of the SDP |
|
RQD |
SCMP |
Software Configuration Management Plan |
Can be integrated as part of the SDP |
|
RQD |
SVVP |
Software Verification and Validation Plan |
Can be integrated as part of the SDP |
|
RQD |
SVVR |
Software Verification and Validation Report |
Validation to SRS level |
|
|
|
Design |
|
|
|
SFD |
System Functional Description |
Allocates function into hardware/software (May be split into SSS and SSDD) |
|
RQD |
SSS |
System Segment Specification |
|
|
RQD |
SSDD |
System Segment Design Document |
|
|
RQD |
SRS/FRS |
Software Requirements Specification |
May include firmware |
|
RQD |
SDD/FDD |
Software Design Description |
May include firmware |
|
NR |
SPS |
Software Product Specification |
|
|
NR |
FSM |
Firmware Support Manual |
Memory map, source code listing and time |
|
|
|
Testing |
|
|
|
STP |
Software Test Plan |
Status subject to working group results |
|
|
STSR |
Software Test Summary Report |
Status subject to working group results |
|
|
|
Miscellaneous/Maintenance |
|
|
RQD |
VDD |
Version Description Document |
History and load control procedures |
|
RQD |
|
|
Contains information on modules, compiler, special tools, hardware, software development and write files |
|
NR |
COTSR |
Commercial Off The Shelf Software Reports |
Not Required |
|
NR |
DTCR |
Date and Time Compliance Report |
Not Required |