IEEE WG 12 Software Meeting
09
August 9, 2001
Meeting Minutes - Approved
The
ninth meeting of the working group was held on February 27 and 28, 2001 at the
Safetran offices in Rancho Cucamonga, CA.
The
agenda was accepted as distributed. See
attachment.
The
committee approved the minutes from meeting 08. The final meeting minutes will be posted on the website.
1.
Draft Standard Concept Acceptance Paul
Jamieson
2.
J-STD-016 Usage Tom
McGean
Paul Jamieson reported for Tom McGean that J-STD-016
could be either referenced or used in part in P1588. IEEE owns the standard copyright. The document will be available through Global Engineering. Tom McGean’s response was emailed on
02/20/01.
.
3.
Adobe Acrobat Text Extraction John
Corvin
John Corvin provided the extraction technique that
can be used. Some issues exist when the
document is only graphics there is no text to extract. The information was emailed on 01/23/01.
4.
IEEE 12207 Coordination Tom
McGean
Paul Jamieson reported for Tom McGean that
coordination with IEEE/EIA 12207 is not required due to the operation change
implemented by the Standards Governing Board.
Tom McGean’s response was emailed on 12/08/00.
5.
Reference Standards Paul
Jamieson
The standard reference listing was updated and
includes information on standard availability, current activities and usage
within P1588. The listing was emailed
on 02/06/01.
Paul Jamieson to revise the listing to show ATA 102
Computer Software Manual has been withdrawn and correct spelling errors.
John Corvin to provide a set of reference standards
including J-Std-016 to the primary team members.
6.
RTM Document Sample Tibor
Simon
Tibor Simon forwarded a RTM sample document for the
working group review. The document was
emailed on 02/08/01. Direction for the
RTM is described in section 7.
7.
Standard Usage
Reports from the working group members are as
follows:
SPMP/SDP/SCMP Shanti
Morar
SPMP (Software Project Management Plan) will replace
the SDP in the standard. IEEE 1058 will
be utilized as a basis for the document.
Review the PMBOK (Product Management Body of Knowlegde) for incorporation
Shanti Morar to map the SDP requirements into SPMP.
SPMP needs to address the safety concerns throughout
the process including coding standards.
SCMP still needs to be mapped for usage in the
standard.
Shanti Morar to prepare an outline (straw man) for
an SPMP to replace the SDP.
Paul Jamieson to update Process Flow Diagram to
include SPMP, safety activities and maintenance document changes.
SQAP John
Corvin
The document has not been revised from the last
meeting. The author received no
comments. Based on the SPMP effort, the
SQAP will need to be reviewed and modified as required.
SPS, SVD, CPM, FSM/LCP, SUM, SIP Tom Tougas
SVD and SPS are combined and may be called SVD. The name will be reviewed against IEEE
12207.
SUM will include the information contained in the
FSM. FSM includes the LCP in section
3.x.5. Therefore, a separate LCP is not
required.
The SIP has been deleted as the topics deal with the
system installation.
CPM will not be required as custom designed
processors and compilers are not being utilized within the industry.
Tom Tougas shall create a graphic showing the
relationship of the maintenance document.
STD, STR, STP Denise
Edgecomb-Cope
STD and STR information was distributed. STR provides a summary of all test
activities. These documents apply to
the any testing level. The J-STD-016
STD combined several activities that were individually defined in IEEE
829. The STD designation will be
changed to STPr (Software Test Procedures).
Denise Edgecomb-Cope will map IEEE 829 requirements against the
SVVP and SVVR. A recommendation for final
document configuration will be made.
STP (Software Test Plan) was not available for this
meeting.
SRS, IRS, SDD, IDD, DBDD Bill MacArthur
Comments to these documents are contained in the
attached information prepared by Bill MacArthur and Linda Martinez.
SVVP, SVVR Byron
Frank
SVVP and SVVR mapping appears in the attached
document.
SVVP as defined in IEEE 1012 includes many
references to the safety requirements that may not be applicable to IEEE
P1588. IEEE 1012 includes the
validation of tools utilized.
STR and SVVR need to be reviewed during final
document preparation to assure that duplication does not occur.
SPMP will contain instructions when the SVVR will be
updated such as at the completion of each phase.
RTM Lori
Karr
The RTM sample was review by the group
RTM needs to address these topics:
Mapping back to the source
Define what is a requirement
What documents do you need to map forward such as
SDD, SPS, STD, STR, etc. including the specific reference.
Codes for allocation
Source code traceability
Lori Karr to update the RTM for review based on the
comments and present at the next meeting.
8.
Document Format Paul
Jamieson
Requirements for a document outline were distributed
by email on 02/19/01.
9.
Feasibility Implementation Tibor
Simon
No report was made.
The NYCT R160 project may be applicable due to timing of the standard
completion and project award.
10.
Safety Critical System Requirements Denise
Edgecomb-Cope
Denise Edgecomb-Cope reported that there are no
additional requirements for safety-critical systems. Denise’s response was emailed on 02/19/01.
IEEE 1483 starts with a safety assurance plan and
addresses the verification and validation efforts.
Introduction needs to address the gray blocks of the
process flow diagram and training is essential for proper use, requirements are
the most difficult to identify and clearly define
Paul Jamieson to revise the draft standard.
Action
Item Review Paul
Jamieson
Action items were assigned. (wg12ail10.doc)
The
next working group meeting will be on May 8 & 9, 2001 at LTK Offices –
Ambler, PA.
The
meeting was adjourned on February 28 at 3:00 PM
The
following information distributed at the meeting appears on the following
pages:
Agenda
– separate file
Roster
– separate file
RTVIS
P1588 Presentation – separate file
APTA
Rail Transit Standards Presentation – separate file
Reference
Standard matrix – separate file
Software
Development Plan (SDP) Outline
Software
Quality Assurance Plan (SQAP) Outline
Requirements
Documents (SRS, IRS, SDD, IDD, DBDD) Outline
Test
Documents (STP, STPr STR) Outline
Verification
& Validation (SVVP, SVVR) Outline
User
Manual (SVD,SUM) Outline
Document
Format Outline
Action
Item Listing – separate file
Software Quality Assurance Plan (SQAP) Outline
SQAP
Consider:
Since the J-STD-016-1995 was chosen as the “standard of choice” for the Software Development Plan, it seems a likely place to start. Per the standard,
“This EIA/IEEE Interim (Trial-Use) Standard is based upon the major technical content of ISO/IEC 12207 Information Technology Software Life Cycle Process, 22 February 1995, for the software development process.”
The intent of IEEE/EIA 12207.0 is to “… provide clarifications, additions, and changes accepted by the Institute of Electrical and Electronics Engineers (IEEE) and the Electronic Industries Association (EIA) …” to ISO/IEC 12207. Thus, we have a tight coupling here too.
Finally, Annex A of IEEE Std 730-1998 explores the correlation between the IEEE Std 730-1998 and IEEE/EIA 12207.0-1996. In general, it finds that IEEE Std 730 is more prescriptive with respect to process and format, but lists several areas where additional information is required.
Therefore, it seems appropriate to use a modification of IEEE Std 730 for our standards effort.
One warning, however. Per J-STD-016-1995, the “EIA/IEEE Interim (Trial-Use) Standards contain information deemed to be of technical value to the industry, and are published at the request of the originating Committee without necessarily following the rigorous public review and resolution of comments which is a procedural part of the development of an EIA/IEEE Standard.” The lack of the rigorous review probably means that our use of the J-STD-16 will be controversial in some circles.
|
Section |
SQAP Content List |
Applicable to Railway Software Standards |
Amendments For Railway Software Standards |
|
Cover |
Date of issue and
document status |
Mandatory |
12207 |
|
Inside Cover |
SQAP Change
History |
Mandatory |
12207 |
|
1.0 |
Purpose |
Mandatory |
|
|
1.1 |
SQAP Purpose |
Mandatory |
|
|
1.2 |
Scope |
Mandatory |
|
|
1.4 |
SQA Objectives |
Mandatory |
Documents motivating the SQAP shall be referenced - 12207 |
|
1.5 |
Software Items Covered |
Mandatory |
|
|
1.6 |
SQA Life Cycle |
Recommended |
|
|
1.7 |
SQAP Standards |
Mandatory |
|
|
1.8 |
SQAP Maintenance |
Mandatory |
12207 |
|
2.0 |
References |
Mandatory |
|
|
2.1 |
Document References |
Mandatory |
|
|
2.2 |
Acronyms |
Mandatory |
12207 |
|
2.3 |
Definitions |
Mandatory |
12207 |
|
3.0 |
Management |
Mandatory |
|
|
3.1 |
Organization |
Mandatory |
Identify issuing organization |
|
3.1.1 |
Quality Element Description |
Mandatory |
|
|
3.1.2.1 |
SQA Project Estimates |
Mandatory |
(cost, effort, size, etc.) 12207 |
|
3.1.2.2 |
SQA Independence |
Mandatory |
12207 |
|
3.1.n |
Organizational Element n |
Recommended |
List all elements that interact with or approve the SQAP |
|
3.2 |
Tasks |
Mandatory |
|
|
3.2.1 |
SQA Task 1 |
Mandatory |
|
|
3.2.1.1 |
Life Cycle Portion |
Mandatory |
12207 |
|
3.2.1.2 |
Task Milestones and Schedule |
Mandatory |
12207 |
|
3.2.2 |
SQA Task n |
Mandatory |
|
|
3.2.2.1 |
Life Cycle Portion |
Mandatory |
12207 |
|
3.2.2.2 |
Task Milestones and Schedule |
Mandatory |
12207 |
|
3.3 |
Responsibilities |
Mandatory |
|
|
3.3.1 |
Software Quality Assurance Engineer |
Mandatory |
|
|
3.3.2 |
Project Software Engineer |
Mandatory |
|
|
3.3.3 |
Project System Engineer |
Recommended |
|
|
3.3.4 |
Customer |
Recommended |
|
|
3.3.5 |
Organizational Element n |
Recommended |
|
|
4.0 |
Documentation |
Mandatory |
|
|
4.1 |
Purpose |
Mandatory |
|
|
4.1.1 |
Governing Documentation |
Recommended |
|
|
4.1.2 |
Document Validation |
Mandatory |
|
|
4.2 |
Minimum Documentation Requirements |